Draft the ordered step checklist
Translates a phase into a concrete ordered checklist of analyst actions, including decision rules and branching where steps differ by client type or data availability.
In / outNamed phase + input spec + completeness gates → ordered action checklist with decision rules and branching logic
You might say…
“Writing every step as an action meant the person following it never had to figure out what to do — they just did the next thing.”
What it does
Translates a phase into a concrete ordered checklist of analyst actions, including decision rules and branching where steps differ by client type or data availability. Used to convert each mapped phase into repeatable procedural how-to instructions.
Trigger: Use to convert each mapped phase into repeatable procedural instructions an analyst can follow without interpretation.
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