When Flow Becomes Measurable: Scrum to Kanban and the Signals in the Data
3-4 min read
Last week, we explored the nature of flow, both as a system and as a state. We looked at how harmony emerges when challenges match capability, and when work progresses with focus rather than pressure. This week, we'll take that idea a step further. What happens when flow starts to show up in the data? And what might that tell us about how a team is really working?
One of our product teams recently made a quiet transition. After four years of consistent Scrum delivery, they began shifting toward a lighter, flow-based approach using Kanban. But it wasn’t a radical overhaul. Instead, the change happened gradually: timeboxes became less rigid, planning became more just-in-time, and the team started managing work in progress more deliberately. The first signs of change appeared in their metrics.
What the Numbers Showed
During their final year using Scrum, the team’s delivery volume varied significantly. Monthly throughput, measured in story points, ranged from 40 to 150. These swings were a regular part of life within a sprint-based model.
As the team focused more on flow, their monthly throughput began to stabilise. Over five consecutive months, their delivery looked like this: 140 to 165. The team size didn't change, and their capacity remained the same. Yet, the average throughput increased and became more consistent and predictable in the process.
This wasn’t the result of a target or a delivery push. It happened because the way they were working had shifted. With clearer limits on work in progress and a stronger focus on finishing rather than starting, delivery became smoother and more reliable.
We’ve seen this pattern before. When teams begin to adopt flow practices, throughput often becomes more predictable. Not because they’re trying to “go faster,” but because they’re removing friction and focusing on what matters most: moving work to completion steadily and sustainably.
Flow You Can See
The change wasn’t just in the numbers; it became visible in how work was progressing.
The team’s cumulative flow diagram, which visualises how much work is at each stage over time, began to flatten out. In their Scrum phase, the diagram showed turbulence. Peaks and troughs appeared around sprint planning and review, revealing a cycle of work starting and stopping in batches.
As the team embraced a more continuous rhythm, those spikes disappeared. Progress became steady. Work flowed more evenly through each stage, and the diagram reflected that balance.
Cumulative flow diagrams often get overlooked, especially in Scrum environments. But they’re incredibly valuable. They show where work is stalling, where queues are forming, and how efficiently the team is moving items through the system. In many ways, they are the clearest visual feedback on how well a team’s delivery process is performing.
Why This Matters
One of the core principles of Kanban is to "start with what you do now." Change doesn’t have to be disruptive. In fact, some of the most effective shifts happen quietly, through continuous reflection and small, intentional improvements. This team didn’t redesign their process overnight. They adjusted the way they worked, step by step, and the system responded.
That’s where the second principle of “pursuing improvement through evolutionary change” comes in. By paying attention to where effort was getting stuck and focusing more on flow than pre-defined commitments, they began to deliver in a steadier, more sustainable way.
A key mantra in our coaching practice is “stop starting and start finishing.” This team did exactly that. They focused less on pushing more work into the system and more on completing what they had already started. The result was a calmer process and more predictable outcomes.
When the data begins to stabilise, it’s often a signal that the team’s habits are maturing. It’s also an opportunity to reflect more deeply:
Are we spending our energy on the right things?
Where does work tend to stall?
What’s helping flow, and what’s holding it back?
As we explored last week, flow is about more than process. It’s about working in rhythm, with clarity and focus. When that rhythm emerges, both people and systems tend to perform at their best.
Key Takeaways
Teams transitioning to flow often see a drop in delivery variability, even without formal process changes.
Metrics like story point throughput and cumulative flow diagrams provide early signs of this shift.
Stable data often reflects deeper shifts in mindset and working practices.
“Stop Starting. Start Finishing”
Gene Kim
Got a moment? Let us know how we did with a quick star rating!