You've heard of technical debt — the shortcuts in code that work today and cost you tomorrow. Process debt is the same idea applied to how your company actually runs, and it's worse, because nobody's tracking it.
Every undocumented workflow, every "just ask Sarah," every process that lives only in the founder's head is a loan you took out to move fast. The loan was the right call at the time. The problem is the interest, and you're paying it on every hire, every handoff, and every day Sarah is out sick.
Most companies don't know they're carrying it. That's what makes it dangerous. Let's name it, find it, and pay it down.
What Process Debt Actually Is
Process debt is the gap between how your company runs and how your company is documented to run. When those two are far apart, the difference lives in people's heads — and a process that lives in someone's head is a liability with a heartbeat.
It accumulates the same way technical debt does: through reasonable decisions made under time pressure. You didn't write down the onboarding process because you only did it twice and you were busy. You didn't document how deals get approved because everyone just knew. Each shortcut saved you an hour then. Each one now taxes everyone who touches that workflow without the context in their head.
The cruel part is that process debt is invisible while the people who hold the undocumented knowledge are still around. It only becomes visible the moment they leave — and then it becomes very visible, very fast.
How to Spot the Tax
You can't see process debt directly, but you can see its symptoms everywhere once you know the shape. The tells:
- Onboarding takes forever and varies wildly. New hires take months to get productive because the real process isn't written anywhere — they have to absorb it from whoever has time to explain it.
- Key-person risk everywhere. There are people whose vacation makes you nervous because nobody else knows how to do what they do.
- The same questions, forever. The same handoffs generate the same confusion every time, because the process was never made explicit, only re-explained.
- Quality depends on who did it. The same task produces wildly different results depending on which person ran it, because there's no shared definition of "done right."
If any of those feel familiar, you're paying the tax. The question isn't whether you have process debt — every growing company does. It's whether you're paying it down or letting it compound.
A process that lives only in someone's head isn't a process. It's a single point of failure you've agreed to call a person.
Why It Compounds
Process debt isn't linear. It compounds, because every undocumented process makes the next one harder to fix. When the onboarding is undocumented, the new hire learns the workflows wrong, which creates more variation, which makes documentation harder, which means the next hire learns it even more wrong.
And it compounds across scale. At five people, everyone's head holds the whole company, and undocumented works fine. At twenty-five, the heads don't connect anymore, and the gaps between them become friction on every handoff. The exact informality that made you fast at five is what caps you at twenty-five. Most companies hit a growth ceiling and blame the market or the talent. Often it's just process debt finally coming due.
Paying It Down on a Cadence
You don't pay down process debt in a heroic documentation sprint. Those produce binders nobody reads. You pay it down the way you pay down any debt — steadily, on a rhythm, prioritized by what's costing you most.
This is where an operating cadence does the work. In Trinity Cadence, process debt surfaces as issues on the Dock and gets paid down through the weekly Pulse and quarterly Anchors. When a handoff breaks for the third time, it goes on the Dock as an issue. The fix — documenting that one workflow — becomes a small, owned piece of work. You're not boiling the ocean. You're paying down the highest-interest debt first, one Pulse at a time.
The Forge Loop is the mechanism that keeps it honest. Each cycle, you ask whether the system is getting clearer or muddier — whether you're paying debt down or taking more on. That recurring question is what turns documentation from a project you never finish into a practice the cadence sustains.
Where AI Changes the Economics
The reason process debt accumulated in the first place is that documenting things was expensive and boring. The Human + Machine Equation changes that math. AI has made capturing a process nearly free — it can watch how work actually flows, draft the documentation from what people already do, and keep it current as the process changes.
In Trinity Cadence, the machine helps surface the debt and carry the cost of paying it down: spotting which workflows generate the most repeated confusion, drafting the first version of the missing documentation, and flagging when a documented process has drifted from how the team actually works. The humans still own the process and decide how it should run. The machine just removes the friction that let the debt build. For the first time, the cost of staying documented is lower than the tax of staying undocumented. That's a new thing, and it's worth acting on. Find your highest-interest process debt, put it on the Dock, and start paying it down this quarter — before the person whose head holds it decides to take a vacation.