Reduce time waiting for review
Use this when: Work is ready, but many tasks are stuck waiting for review or approval.
Review waits are coordination delay. Making them visible shows you where to improve.
1. Give waiting its own lanes
Section titled “1. Give waiting its own lanes”Create lanes for waiting for review and waiting for approval. Work buried in DOING is hard to count; in its own lane, the queue is visible on the board.
2. Always set a ball holder
Section titled “2. Always set a ball holder”When moving a task to review, pass the ball to the reviewer.
A review lane full of tasks without a ball holder leaves everyone unsure whether it is their turn. This is where the distinction between assignees and the ball holder matters.
3. Check your own ball each day
Section titled “3. Check your own ball each day”Filter by yourself as ball holder to see tasks waiting on you.
Have everyone check this once each morning, then act on or hand off the tasks they can move forward.
4. Review queues weekly
Section titled “4. Review queues weekly”Open Risks to find tasks that have been waiting a long time.
Focus on the lane where the waiting accumulates. A repeated queue in one stage points to a coordination bottleneck.
5. Reduce the bottleneck
Section titled “5. Reduce the bottleneck”| Pattern | Possible change |
|---|---|
| One person handles every review | Add reviewers or rotate the role |
| Approval has become a formality | Agree on cost or impact thresholds below which approval is unnecessary |
| Too many “just in case” checks | Document the conditions that do not need a check |
| Reviews are too large | Split tasks into smaller pieces or subtasks |
When a decision can be handled by an agreed rule, removing an unnecessary approval step can eliminate the queue at its source.
First goal
Section titled “First goal”Start by keeping the number of tasks with an empty ball holder at zero.