Every delivery team has done it. A high-priority request comes in, so the team drops what they were doing and pushes it through. The urgent item ships, everyone exhales, and the board looks healthy again. What almost no one notices is that the speed came from somewhere. It was borrowed from every other task still in progress.
That borrowing has a name. It is called flow debt, and like any debt, it is easy to take on and expensive to ignore.
What Flow Debt Actually Is
Flow debt is what happens when the cycle time of a task in progress is reduced by borrowing cycle time from other tasks in progress. When you expedite one item, you are not adding capacity. You are redirecting attention. The expedited task moves faster because everything around it waits longer. Those waiting items keep aging on the board while the team’s focus sits elsewhere.
The trouble is that the cost is invisible at the moment you take it on. The expedited item ships on time, so the decision looks free. The price lands later, and somewhere else, on the work that aged while no one was looking.
You can see flow debt without any special charts. Look at the average age of your work in progress, how long the items currently on your board have been open, and compare it to your average cycle time, how long work normally takes to finish. When the two are roughly equal, your system is healthy. When the average age of your work in progress starts climbing past your cycle time, your current work is taking longer than your finished work normally does, and that distance is the size of your flow debt.
The Three Ways Flow Debt Builds Up
Flow debt rarely comes from a single bad decision. It accumulates from three recurring patterns, and knowing which one you are dealing with tells you what to change.
The first is expediting. Every urgent item that jumps the line and breaks the work-in-progress limit borrows time from everything else in flight. One or two of these is survivable. Treating every request as urgent turns the exception into the operating model.
The second is a missing pull policy. When nothing governs what the team picks up next, work gets started and then set aside for something newer. Low-priority tasks have a way of becoming high-priority problems when they are left alone too long.
The third is blockers. Work that cannot move between stages sits and collects age while attention shifts elsewhere. A blocked item is still in progress, still aging, and still part of the debt, even though no one is touching it.
Why Flow Debt Costs More Than a Late Task
It is tempting to think the damage from flow debt is the handful of items that finished late. That is the cheap part. The delay of those other work items is the less costly effect of flow debt.
The expensive part is what it does to predictability. Flow debt breaks the assumptions your forecasts depend on. As it accumulates, your delivery times get harder to predict and your estimates get less accurate. Weeks after an expedite, a forecast slips, and almost no one traces the slip back to the decision that caused it. The team gets asked why it has slowed down, when the real answer is a debt the system took on and never recorded.
There is an honest exception worth naming. Flow debt is not always a mistake. In a genuine emergency, the short-term benefit of expediting can be worth the long-term cost. The danger is borrowing without knowing it, and treating every urgent request as if it were free.
What to Do Next
You do not need new tooling to start. You need to make that comparison a habit rather than a rescue.
Put your average WIP age and your average cycle time on the agenda of your planning meetings, not only the ones called after a date has already slipped. When the age starts climbing, you have caught the debt early, while you can still act on it. And before you approve the next expedite, name the trade out loud: what finishes later, or stops, so this one can go fast. An expedite you have not priced is the one that ends up costing the most.
This is the kind of signal that is hard to watch by hand once you are accountable for more than a handful of teams. The Aging Chart at Nave ranks your work in progress by how long each item has been sitting, so the oldest work surfaces first and the debt becomes visible before the forecast tells you about it. You can see it at getnave.com.
Flow debt is easy to take on and easy to miss. Measure the age of your work in progress against your cycle time, and you turn a hidden cost into one you can manage before it reaches your forecast.
I’ll see you next week, same time and place for more managerial goodness. Bye for now!
