Shape the solution's structure and design logic
Develops the structural logic and organising principles of the proposed solution — what it consists of, how the parts relate, and why this architecture meets the requirements.
In / outRecommendations + implementation context + constraints → solution design (components, relationships, design rationale, explicit assumptions)
You might say…
“The recommendations were right but the solution design was vague — every implementation question exposed a gap we hadn't thought through at design time.”
What it does
Single-judgement skill: the consultant points it at the agreed findings and brief and it works the design into shape — proposing the operating-model structure, strategy logic, or implementation blueprint; naming the major components and how they fit; surfacing the design choices that carry real consequence and the trade-offs between them. Used at the start of design once analysis is settled, with the consultant in the loop to own the architecture; the value is the structured reasoning about what the solution should be, not a finished diagram.
Trigger: Use when transitioning from 'what to do' to 'how to do it'; provide the agreed recommendations and the client's implementation context.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation