Software teams borrow against the future all the time. They take a shortcut to ship faster, promising to clean it up later. Individually these shortcuts are reasonable. The trouble is that they accumulate. Technical debt is the name for this buildup, and looking at it through the lens of stocks and flows reveals why it grows quietly for a long time and then suddenly seems to strangle a team ability to move.
A stock, not an event
The most useful reframe is to stop thinking of technical debt as a series of isolated bad decisions and start thinking of it as a stock, an accumulating quantity. Every shortcut adds to the stock. Every cleanup subtracts from it. Like water in a bathtub, the level depends on the balance between the inflow of new debt and the outflow of repayment. If you only ever add and rarely subtract, the level rises steadily even if no single addition felt significant.
Why it stays invisible then bites
A stock can grow for a long time without obvious consequences, which is exactly what makes technical debt dangerous. For months the code is a little messier but everything still works, so the rising level goes unnoticed. Then the stock crosses a threshold where the accumulated complexity starts slowing every new change. Suddenly features take longer, bugs multiply, and the team feels stuck. The pain arrives all at once, but the cause was accumulating the entire time.
The reinforcing loop that makes it worse
Technical debt tends to feed itself. As debt rises, every change becomes harder and slower, which increases the pressure to take more shortcuts to hit deadlines, which adds still more debt. This reinforcing loop can spiral a codebase into a state where the team spends most of its energy fighting the accumulated mess rather than building anything new. The loop is why debt left unmanaged does not stay constant, it compounds.
Managing the flows
- Track the stock, making the level of debt visible rather than letting it hide in the code.
- Fund the outflow, treating cleanup as ongoing work rather than a someday project.
- Slow the inflow, by deciding deliberately when a shortcut is worth taking and when it is not.
- Watch for the reinforcing loop, and intervene before slow-and-messy becomes a spiral.
A general pattern
Technical debt is a specific case of a pattern that appears everywhere: a stock that accumulates from small, reasonable decisions until it dominates the system behavior. Deferred maintenance on roads, unaddressed health issues, and neglected relationships all follow the same shape. Once you can see the stock and its flows, you can manage the level deliberately instead of being surprised when it finally overwhelms you.
The lesson is not to avoid all debt, which is impossible and often unwise. It is to treat it as an accumulating stock that needs active management, so that borrowing against the future stays a choice rather than becoming a trap.
Discussion