The same end-of-cycle crunch keeps happening - the late nights, the weekend scramble, every release. Each time, it feels like bad luck or a one-off.
It isn’t. The crunch started weeks earlier, with a decision that looked completely reasonable at the time. This finds that the earliest decision - so you can break the cycle instead of surviving it again.
Imagine this: every release ends the same way - testing gets compressed, engineers work the weekend, and everyone blames the final week. The team rebuilds the release as a chain of decisions: the date fixed before scoping, the extra requests accepted, integration deferred. When they tip the first domino, they see the crunch actually began weeks earlier.
You rebuild the last crunch as a chain of decisions, laid out as dominoes in time order - from the earliest call to the final scramble. Then you tip the first domino and watch the whole chain fall in sequence. The fall shows that the late panic was already unavoidable early. You finish by finding the earliest decision you could move next cycle - the point where the chain breaks.
The dominoes deliver the moment; the decision cards carry the lesson. The point isn’t the falling tiles - it’s the real decisions written on them and which one to move next time.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.
Team ✓ About 45–90 minutes, with a facilitator.
The time required is indicative and will depend on the size of the team and the length of the chain.
The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.
Bring one real crunch the team keeps living through - the recurring late scramble, not a one-off emergency.
Use it whenever:
You’ve done it well when: the team stops blaming the last week and can point to the earliest decision that started the whole chain.
A recurring crunch is the visible end of an invisible chain of decisions. Each decision looked reasonable on its own, so no one saw the chain until the crunch arrived - and the team fixes the last week while the cycle repeats. Laying the chain out in time and tipping the first decision makes the cause and effect visible: the crunch was started early, not at the deadline.
One recurring crunch. A real, recent crunch the team keeps repeating - and recognises as a pattern, not bad luck.
One facilitator. They run the flow, keep the room hunting for the earliest decision rather than the last week, and tip the dominoes.
A large table or clear wall space. The chain is a physical layout, built left to right - you need room to lay the whole thing out so every link is visible.
The dominoes + timeline board. One domino represents one real decision that led to the crunch. They are laid out from the start of the cycle to the deadline. Tipping the first shows the chain fall.
Decision cards + pen. Write-on cards to name each real decision, so the chain is the team’s actual story - not a generic demo.
Output
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.