Cumulative Flow Diagram
A stacked area chart that tracks how work items move through workflow stages over time — revealing bottlenecks, WIP, and lead time at a glance.
// 01 — The chart
What it looks like
A CFD showing work items across three stages. Band thickness reveals WIP; the horizontal gap between bands shows lead time.
// 02 — Definition
What is a cumulative flow diagram?
A cumulative flow diagram (CFD) is a stacked area chart where each band represents a stage in a workflow (e.g. Backlog, In Progress, Done). The y-axis shows the cumulative count of work items, and the x-axis shows time.
The key insight is geometric: the vertical distance between two adjacent bands at any point shows the number of items in that stage (work-in-progress). The horizontal distance between two bands shows the average time items spend between those stages (lead time or cycle time).
CFDs are core to Kanban and Lean practices. They make bottlenecks visible: when a band widens, work is piling up in that stage faster than it’s leaving.
// 03 — Anatomy
Parts of a CFD
// 04 — Usage
When to use it — and when not to
- Tracking Kanban or agile workflow health over time
- You need to spot bottlenecks — stages where work piles up
- Monitoring WIP limits and throughput trends
- Estimating lead time and cycle time visually
- Reporting project progress to stakeholders without burndown charts
- Your work items don't flow through sequential stages
- You have only two stages (backlog + done) — a burndown is simpler
- The audience doesn't understand cumulative metrics
- You need individual item tracking — a CFD shows aggregates only
- Work items vary wildly in size and you're counting them uniformly
// 05 — Reading guide
How to read a CFD
Identify the stages
Each coloured band represents a workflow stage. 'Done' is usually at the bottom; 'Backlog' at the top.
Check band thickness for WIP
A thickening band means work is accumulating in that stage — a potential bottleneck.
Measure lead time horizontally
Pick a point on the top band and trace horizontally to the same height on the bottom band. That distance is lead time.
Look for flat lines
If the 'Done' band flattens, throughput has stalled. If the 'Backlog' flattens, no new work is arriving.
Watch for widening gaps
If the gap between 'In Progress' and 'Done' is growing, work is stuck.
// 06 — Data format
What data you need
A date column and one count column per stage (cumulative totals). Each row is a snapshot — typically daily or per-sprint.
// 07 — Construction
How to build one
Step 1: Record daily cumulative counts for each workflow stage.
Step 2: Stack the areas bottom-up: Done at the bottom, Backlog at the top.
Step 3: Colour each band distinctly. Use muted tones for "waiting" stages and strong tones for "Done".
Step 4: Add stage labels and optional annotations where bottlenecks or pattern changes occur.
// 08 — Common mistakes
Mistakes to avoid
Non-cumulative data
The y-axis must show cumulative totals. Using daily counts produces a completely different — and misleading — chart.
Too many stages
Beyond 5–6 stages, bands become thin slivers. Merge related stages or use a separate chart.
Ignoring item size variation
Counting stories uniformly when some are 10× larger than others gives a misleading picture. Consider story-point-weighted CFDs.
Missing stage labels
Without clear labels, readers can't tell which band is which.
// 09 — Real-world examples
Where you’ll see them
Kanban boards (Jira, Azure DevOps)
Most agile tools offer a built-in CFD view for tracking flow metrics across sprints.
Manufacturing (Lean)
CFDs originated in Lean manufacturing for monitoring production throughput and inventory.
Support ticket tracking
Customer support teams use CFDs to monitor ticket inflow, resolution, and queue buildup.
// 10 — Quick reference
Key facts
// 11 — Accessibility
Making it accessible
Provide a data table with cumulative counts per stage per day. Use distinct colours with high contrast between adjacent bands. Add ARIA labels describing WIP and trend direction. Ensure stage labels are readable at small sizes.
// 12 — Variations
Common variations
Normalized CFD
Bands are scaled to 100% height, showing the proportion of work in each stage over time.
CFD with WIP limits
Horizontal threshold lines mark WIP limits, making violations immediately visible.
Throughput overlay
A line showing daily completion rate is overlaid on the CFD for combined insight.
Story-point-weighted CFD
Each item's contribution is weighted by effort, giving a more accurate picture of work volume.
// 13 — FAQs
Frequently asked questions
What is a cumulative flow diagram?+
A cumulative flow diagram (CFD) is a stacked area chart where each band represents a stage in a workflow (e.g. Backlog, In Progress, Done). The y-axis shows the cumulative count of work items, and the x-axis shows time.
When should you use a cumulative flow diagram?+
Use a cumulative flow diagram when tracking Kanban or agile workflow health over time. It also works well when you need to spot bottlenecks — stages where work piles up, and when monitoring WIP limits and throughput trends.
When should you avoid a cumulative flow diagram?+
Avoid a cumulative flow diagram when your work items don't flow through sequential stages. It is also a poor fit when you have only two stages (backlog + done) — a burndown is simpler, or when the audience doesn't understand cumulative metrics.
What data do you need to make a cumulative flow diagram?+
A date column and one count column per stage (cumulative totals). Each row is a snapshot — typically daily or per-sprint.
How is a cumulative flow diagram different from a stacked area chart?+
Both a cumulative flow diagram and a stacked area chart can look similar at first glance, but they answer different questions. Reach for a cumulative flow diagram when the comparisons and patterns it was designed to reveal match what you need to communicate, and choose a stacked area chart when its particular strengths better fit your data and audience.
What is another name for a cumulative flow diagram?+
Cumulative Flow Diagram is also known as CFD, cumulative flow chart. The name varies between fields, but the visualisation technique is the same.
What size of dataset works best for a cumulative flow diagram?+
Cumulative Flow Diagram works best for 3–6 workflow stages, daily snapshots. Outside that range the chart either looks empty or becomes too cluttered to read clearly.
Are cumulative flow diagrams accessible to screen readers?+
Provide a data table with cumulative counts per stage per day. Use distinct colours with high contrast between adjacent bands. Add ARIA labels describing WIP and trend direction. Ensure stage labels are readable at small sizes.