Cumulative Flow Diagram (CFD)

What a CFD Shows

The cumulative flow diagram is a stacked area chart with time on the x-axis and cumulative item count on the y-axis. Each kanban-board stage gets its own colored band. Reading from bottom to top, the bands represent items completed (Done), items in later stages, items in earlier stages, and items not yet started (Backlog).¹

The result is a single chart that simultaneously visualizes:

• Arrival rate (top band's growth).
• Throughput (bottom band's growth).
• Work in progress (vertical thickness of in-progress bands).
• Cycle time (horizontal distance from arrival to completion at any item count).

Four metrics, one chart. The information density is the CFD's defining strength.

Reading the CFD

Healthy CFD

• Bands grow at roughly parallel slopes (steady arrival and throughput).
• Mid-flow bands (In Progress, Review, Test) remain thin.
• The Done band grows steadily.

Bottleneck signal

One band thickens dramatically while bands above it remain thin and bands below stay flat. The thick band is where work is piling up — the bottleneck. The thin bands above show that work isn't reaching the bottleneck stage; the flat bands below show throughput has stalled.

WIP runaway

Total mid-flow thickness grows over time. The team is starting work faster than they're finishing it. Eventually the cycle time becomes catastrophic.

Batching

Bands appear in "steps" — flat for several days, then sudden jumps. The team is releasing in batches rather than continuously. Often a sign of a hardening cycle or a release ceremony that batches deployment.

Stalls

Bands go flat for an extended period — no movement. Either work isn't being done, isn't being tracked, or the board isn't being updated. Investigate.

How to Build a CFD

Most modern tools (Jira, Azure DevOps, Linear, GitHub Projects) generate CFDs automatically from the board's state history. If yours doesn't, the calculation is straightforward:

• Each day, count the items in each column.
• Plot the counts as stacked areas over time.
• The y-axis is cumulative — bands stack, they don't overlap.

A spreadsheet with daily column counts produces a serviceable CFD in five minutes.

What CFDs Are Good At

• Surfacing system-level patterns that per-team or per-item metrics hide.
• Communicating health visually. A team's CFD across a quarter tells a story even a casual reader can follow.
• Diagnostic conversations. The chart prompts specific questions: "what's causing this thick band?" "why did throughput drop here?"
• Triggering retrospective topics. Anomalies in the CFD become natural retro discussion points.

What CFDs Are Not Good At

• Item-level detail. The CFD aggregates. To investigate specific items, you need other views (scatter plots, item details).
• Forecasting. The CFD shows what has happened; throughput data feeds Monte Carlo for forecasts.
• Stakeholder reporting. Many stakeholders find the chart hard to read. Burndowns and burn-ups are more accessible.
• Very small teams or short periods. Below a few weeks of history and a handful of teams, the chart is too noisy to be informative.

Pairing the CFD With Other Views

The CFD is most powerful when paired with:

• Cycle time scatter plot: shows individual items, surfaces outliers, complements the CFD's aggregate view.
• Aging chart: shows how long current items have been in progress, complementing the CFD's historical view with present-moment status.
• Throughput histogram: shows the distribution of weekly throughput, useful for forecasting.

Coaching Tips

Teach reading explicitly.

Show the team example CFDs with annotated patterns. The patterns aren't self-evident.

Use it in every retro.

The chart prompts specific questions about the system. Pin it on the wall during retro.

Watch for thickening mid-flow bands.

The earliest warning sign. If the in-progress band is growing over weeks, address WIP before cycle time collapses.

Pair with scatter plots.

CFD shows the aggregate; scatter plots show the outliers. Together they tell the full story.

Don't ship to stakeholders raw.

CFDs require interpretation. For stakeholder reporting, translate into outcomes or use simpler charts.

Investigate stalls immediately.

A flat band for a week usually means the board isn't being updated, not that work has stopped. Verify both possibilities.

Summary

The Cumulative Flow Diagram is the most information-dense visualization available to flow-conscious teams. By stacking workflow stages over time, the chart simultaneously shows arrival, throughput, WIP, and cycle time — and exposes the patterns (bottlenecks, batching, stalls) that single-metric charts miss entirely. Teams that learn to read CFDs gain a diagnostic capability that prevents the slow accumulation of dysfunctions invisible at the item level. Like all visualization, the CFD's value depends on the team actually reading it — once learned, the patterns are unmistakable.

Back to Flow & Forecasting