The Chart That Shows Where Work Gets Stuck
Burndown charts tell you whether you’re on pace for a deadline. Cumulative flow diagrams tell you where in your process work accumulates — which is often a more useful question.
A CFD plots the count of tasks in each status over time, stacking them as filled bands from bottom to top. The x-axis is time. The y-axis is the total number of tasks. Each band represents one status or status category, colored distinctly.
How to Read a CFD
In a healthy flow, each band grows at roughly the same rate — tasks move through statuses at a consistent pace and no band widens disproportionately over time.
When a band widens, tasks are accumulating in that status faster than they’re leaving. This is where your bottleneck is.
Common patterns:
Wide “In Review” band — code review or approval is a bottleneck. Either there are too few reviewers, reviews are too slow, or tasks require multiple rounds of revision.
Wide “Ready for QA” band — the handoff between development and testing is creating a queue. QA capacity doesn’t match development throughput.
Narrow “Done” band with wide “In Progress” — work is starting faster than it’s completing. WIP limit may need tightening.
Flat top line — new work has stopped entering the flow. Could mean sprint planning hasn’t happened, or you’ve reached your WIP limit.
Throughput Is the Slope
The slope of the top edge of the chart (the total line) is your throughput — how many new tasks are entering the flow per unit time. The slope of the bottom band’s upper edge is your completion rate. When completion rate is less than throughput, work accumulates.
A healthy CFD shows these slopes roughly equal over time. A diverging CFD (completion rate slower than throughput) shows a team taking on more than they can ship — a pattern that compounds as the backlog grows.
CFDs vs. Burndowns — When to Use Each
Burndowns answer: “will we finish on time?” They require a defined scope (sprint or milestone) and a deadline.
CFDs answer: “where is work getting stuck?” They work on continuous flows without fixed deadlines.
For Kanban teams, scrum teams, and any flow where understanding process efficiency matters, CFDs are the more diagnostic tool. Burndowns are the more useful communication tool for stakeholders who care about deadlines.
FlowEra generates both, from the same underlying task data. You don’t have to choose.
Using CFDs for Process Improvement
The value of a CFD is in the conversation it enables. When the “In Review” band widened over the last two sprints, you can point at the chart and say: “here’s where we’re losing time.” This makes the abstract (“our review process is slow”) concrete (“tasks sit in review for an average of 2.3 days based on this chart”).
Concrete data changes the conversation from opinions about process to facts about process. Teams that review their CFD regularly tend to identify and address bottlenecks earlier, because they have a shared language for describing the problem.