Everyone looks busy. Meetings happen. But work still takes longer than expected to move through the team - and no single cause is obvious. That’s because work doesn’t slow down where people are working. It slows down where work is waiting - in the handoffs and queues between the steps that look busy, where nobody is watching. This activity finds those stalls, so you can fix the real delay instead of pushing harder on the parts that already move.
A feature takes three weeks to deliver, even though the team estimates only five days of actual work. When they map the journey, coding takes two days, testing takes one, and deployment takes a couple of hours. But the feature spends eight days waiting for code review, four days waiting for QA, and three days waiting for release sign-off. Nobody was working slowly. The work was simply waiting. Constraint Snapshot makes those invisible waits visible, so the team fixes the real delay instead of pushing people to work harder.
As a team, you map how one piece of work actually moves from start to finish. Then you mark every place where the work waited before the next step could begin - not where someone is working on it, but where it sits between steps. The biggest wait, not the busiest step, is where your delivery is really losing time.
Team ✓ · About 25–30 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 8–10 minutes. It is a downloadable PDF on this page.
Use it when delivery feels slow but no single cause stands out.
Good signs it’s the right tool:
You’ve done it well when: the team agrees where flow really breaks - and can point to a stall they’d been missing.
People naturally focus on the work they can see. But work often spends much more time waiting than being worked on - in handoffs, approvals and queues. By separating waiting time from working time, the biggest delay becomes visible - and that’s usually where the biggest improvement comes from.
One real piece of work. Something the team recently delivered, or is delivering now - this is the critical ingredient; without it the exercise has nothing to map.
A whiteboard, wall or large sheet of paper. Room to lay out the steps of that work, left to right.
Sticky notes and a marker. One note per step; a way to mark the stalls between them.
Roles - Team: a facilitator (keeps the map fast and rough, and holds the team to marking the waiting) and participants (map the work and size the waits).
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.