Decompose the presenting problem into a logic tree of sub-problems
Takes the client's stated problem and produces a MECE breakdown into component sub-problems and candidate workstreams before any method choices are made.
In / outClient problem statement + SOW context → labelled logic tree of sub-problems with candidate workstream names
You might say…
“I need to know whether we're solving three separate problems or one — before we pick a single method.”
What it does
Takes the client's stated problem and proposes a MECE breakdown into component sub-problems and candidate workstreams. Used at the start of approach design, before any method choices, to map the logical anatomy of the problem.
Trigger: Use when a signed engagement exists and you need to move from the client's presenting question to a structured map of what the project must actually address.
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