Surface load-bearing assumptions and draft the risk register
Stress-tests the plan by naming the assumptions it depends on and drafting a risk register of planning risks that could break the project before delivery begins.
In / outCurrent plan + dependency log → risk register (load-bearing assumptions + planning risks, each with description and impact if wrong)
You might say…
“Every plan has beliefs baked in that nobody has said out loud — I need those named and tracked before we call this plan final.”
What it does
Stress-tests the plan by naming the assumptions it depends on and the planning risks that could break it before it starts, drafting a short risk register the client and team can track. Used as a distinct planning artefact alongside the dependency log, before delivery begins.
Trigger: Use as a distinct planning step alongside the dependency log, before delivery ramps up, to make hidden assumptions and early-stage risks explicit.
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