▮ WHAT YOU WALK AWAY WITH
✓A solution design brief that defines the concept, the target workflow, who uses it, and what it produces, written to guide build, vendor, or prototype conversations
✓A target workflow model showing how the work should flow and what decisions or outputs the solution supports
✓A user role and interaction model that says who touches the solution and what they need to do
✓A system touchpoint map plus a data input and output view, including where each piece of data should come from and what the source of truth is
✓A dashboard or reporting concept and an automation and integration opportunity map, with AI-enabled workflow considerations where they apply
✓A logged set of design assumptions, tradeoffs, constraints, risks, and dependencies, so nothing important is hidden going into build
✓A clear recommendation for the next step: mockup, prototype, proof of concept, pilot, MVP, requirements, implementation, or stop
▮ HOW IT RUNS
01We frame the opportunity: confirm the business problem, the sponsor's goals, the users, the systems context, the constraints, and the decision this design has to support.
02We set design criteria: the things the solution has to satisfy across workflow fit, usability, feasibility, data, automation, governance, visibility, and business value.
03We design the target workflow and solution concept, and map the system, data, dashboard, and automation implications.
04We stress-test the design against real scenarios, edge cases, constraints, and implementation realities.
05We recommend the right next move and deliver the solution design brief with the rationale, tradeoffs, risks, and decision points.
▮ IS THIS THE RIGHT MOVE?
] THIS IS FOR YOU IF
A leader with a defined systems or workflow opportunity, an accountable sponsor, and access to real users and system owners, who needs solution clarity before committing to a prototype, vendor, requirements, or build.
] NOT THE RIGHT MOVE IF
It's not the right move if there is no executive sponsor, the underlying problem is still too vague to design around, or you have already decided on a tool and just want it validated rather than genuinely designed.
] FIRST STEP
Start with a focused scoping conversation to pin down the business problem, the opportunity, the sponsor and users, the current systems context, the constraints, the decision you need to make, and whether the work is actually ready for solution design.
Not sure this is the right one? Start with the Work Systems Assessment and we'll name the next best move.