A wider Review band on your cumulative flow diagram means a higher recorded count. Before you lower the work-in-progress (WIP) limit, open the cards in that band. Did they spend time waiting in Review? Check for bulk status updates or changes to what the report counts.
How to read a cumulative flow diagram
On the cumulative flow diagram Kanban teams use to spot queues, time runs left to right and the work-item count runs up the vertical axis. Microsoft’s Azure DevOps guidance describes the cumulative flow chart as a count of work items by state or column over time. To count the cards in Review on a particular date, subtract the value at the band’s lower edge from the value at its upper edge.
The Kanban Guide defines throughput as the number of items finished per unit of time. For the recorded rate, compare how far the Done boundary rises over two intervals of equal length. If the scope and definition of Done stayed the same and no cards reopened or dropped out, the steeper line marks the interval with more recorded completions per unit of time. Under the same conditions, a flat line means the team recorded none. Check the dates against when people finished the work.
A cumulative flow diagram example: Same shape, different causes
A real review queue. With the same scope and timely board updates, four more cards entered Review than left it. Several sat there for days. Microsoft’s Azure DevOps guidance notes that the delay can be at the handoff to the next stage. Ask what has to happen before the cards can move on.
A catch-up update. Someone logged earlier handoffs in one batch and waited to update Done. Atlassian documents that Jira supports bulk transitions. Microsoft notes that irregular status updates can leave lines flat. Check when the work moved against the date someone changed the status.
Check that the filters, reporting windows, and column mappings match before you compare two charts. Atlassian’s board-specific CFD documentation explains that Jira counts cards that match the saved filter and uses the column mapping to place statuses. In It’s a Plan, you can save the board filter as a view and share it so the team opens the same set of issues.
Check card histories and time in Review
Open the histories for the cards in the wider band. Look for moves into and out of Review around the date the count changed. Atlassian’s Jira Data Center guidance points to ticket history to find out who recorded a transition. If the timestamps cluster, check any review records you have and ask the team whether the work moved in a batch or someone caught up on board updates.
The Kanban Guide measures work-item age from the workflow’s agreed start point for an item that hasn’t finished. To see how long a card has been in Review, count from the date it entered for its current stay. A card can have been open for a long time and still be new to Review.
Find out what the waiting cards need before you change a limit. If you find late updates or a change in what the report counts, correct the report or mark the change before comparing periods that count the same work in the same way.
Test one change before resetting the WIP limit
If cards are waiting for review, help finish the oldest reviews before pulling more work. ProKanban’s Kanban Pocket Guide recommends having people who finish an item help with aging work before starting another item. Give it until the next flow review and leave the WIP limit where it is.
At that review, count the cards in Review and check how long the oldest ones have been waiting. Keep the chart settings the same and compare how many items reached Done over windows of equal length. If the queue shrank, check where the cards went: did they move forward or drop out of the report? For any that are still waiting, go back to the handoff and ask what’s holding them there.
Bring your latest cumulative flow diagram to the next flow review and pick one widening band. Use your It’s a Plan Kanban board or the board you use to identify the cards in that stage. Check their status histories before changing a work-in-progress limit.
Key takeaway
A widening Review band shows that more cards were recorded in Review, not necessarily that work slowed down. Check when cards actually entered and left Review before changing your work-in-progress limit.

Andrii founded It’s a Plan and leads its product and roadmap, from the open-source edition to Pro for teams. He works with the project’s contributors and the teams that run It’s a Plan.
All posts by Andrii Poluosmak