Map interdependencies and sequencing constraints between sub-problems
Reviews a decomposed sub-problem tree and identifies which sub-problems depend on which, surfacing sequencing constraints and shared inputs that will shape the delivery approach.
In / outLogic tree of sub-problems → dependency map with sequencing constraints and shared-input flags
You might say…
“We can't run those two workstreams in parallel — one feeds the other, and we need to say so now.”
What it does
Reviews the decomposed sub-problems and identifies which depend on which, flagging constraints that force ordering or shared inputs across workstreams. Used after the problem tree exists to surface what must precede what before methods are chosen.
Trigger: Use after the problem tree exists and before method selection, to expose ordering constraints that restrict how workstreams can be structured and sequenced.
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