What is Flow and why does it matter?

Flow is the rate at which work moves through a system from the moment it is requested to the moment it delivers value. It sounds simple, but most organisations have never measured it — and almost none of them manage it directly.

Instead, they manage inputs. They track how many projects are in flight, how many sprints have been completed, how many features have been shipped. These measures feel productive, but they tell you almost nothing about how well the organisation is actually serving its customers or meeting its goals.

Flow thinking shifts the focus from activity to throughput. The question is not how busy are your teams, but how quickly and reliably does work move from request to outcome — and what is getting in the way?

When you start mapping flow, a few things tend to become visible almost immediately. The first is how much work is in progress at any given moment. In most organisations, this number is far higher than it needs to be. Work starts before earlier work finishes, priorities shift mid-flight, and teams end up carrying a weight of partially-done things that collectively slow everything down.

The second is where the delays are. Flow analysis tends to reveal that the majority of elapsed time in any delivery process is wait time, not work time. Work sits waiting for a decision, a review, a dependency, or a conversation that has not yet happened. Speeding up the work itself often makes very little difference if the waits are not addressed.

The third is the relationship between flow and quality. When work moves too fast, or when too much is in progress at once, quality tends to suffer. Defects increase, rework accumulates, and the system becomes self-defeating — teams work harder but deliver less.

Understanding flow does not require complex tooling or a lengthy analysis programme. It starts with a simple question: how long does it take for a piece of work to move from the moment it is requested to the moment it is genuinely done? Answering that question honestly — and then asking why — is one of the most practical things a leadership team can do.

Flow is not a methodology. It is a lens. And once you start looking through it, it is very hard to unsee what it reveals.