Identify required inputs, decisions, and cross-workstream handoffs
Walks each deliverable and surfaces what it needs to start — client data, prior decisions, cross-workstream handoffs — producing a dependency log.
In / outWorkstream and deliverable list → dependency log (per-deliverable: required inputs, prerequisite decisions, cross-workstream handoffs)
You might say…
“We've had a deliverable slip by three weeks because nobody said it needed data from Workstream 2 first — I want the dependency log before we start.”
What it does
Walks each deliverable and surfaces what it needs to start — client data or access, decisions that must land first, handoffs from other workstreams — producing a dependency log. Used during plan-building to make the prerequisite structure of the engagement explicit.
Trigger: Use during plan-building to make the full prerequisite structure of the engagement explicit before the timeline is set.
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