Work has stalled, and the cause isn’t obvious. Several things are stuck; everyone’s chasing the item in front of them - but clearing it doesn’t help, because the thing that’s stuck usually isn’t the thing that’s blocking you. The real hold-up is often several hidden “waiting on” links further up the chain. This traces the chain to the source, so you fix the blocker instead of the symptom.
A feature hasn’t shipped for two weeks. Everyone says QA is blocking it, so the team pushes QA harder. When they trace the dependency chain, QA is actually waiting on a security review, Security is waiting on an infrastructure approval, and Infrastructure is waiting on a vendor certificate nobody realised had expired. QA wasn’t the blocker - it was just where the delay became visible.
So you write the stuck item, then ask “what are we waiting on?” and draw an arrow to it. You repeat from there - what is that waiting on? - until the arrows stop. The node at the far end is the real blocker. You circle it and pick one move to clear it.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.
Team ✓ · About 15–25 minutes, with a facilitator.
The time required is indicative and will depend on the nature of the problem and the size of the team.
The facilitator should read the short facilitation guide first - about 10 minutes. It’s a downloadable PDF on this page.
Use it when work has stalled, and you can’t tell why.
Good signs it’s the right tool:
You’ve done it well when: the team agrees on the real blocker (not the symptom) and leaves with one owned move aimed at it.
When work stalls, people naturally push on the task they can see. But that task is usually waiting on something else. Tracing each dependency reveals the real source of the delay, so effort goes where it actually unblocks the work.
A real piece of stalled work. Something that has stopped moving and where the cause isn’t obvious. The tool only works with a real blockage.
A board or wall. Somewhere to place the nodes and draw the dependency chain.
Sticky notes and a marker. One note per dependency.
Roles - Team: a facilitator (keeps the team tracing to the far end, not stopping at the first link) and participants (name the dependencies and trace the chain).
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.