Operational debt.
Operational debt is technical debt for your whole business: the compounding gap between what a company decided and what it actually does. Every unverified decision, drifted process, and undocumented handoff adds to the balance. Nobody decided to create it. Entropy doesn't need permission.
This page covers it where I live: DTC and ecommerce brands doing $5–50M, and the agencies that serve them. Not all operational debt. Yours.
It always wears one of three faces.
Decisions that were made but never verified.
Monday's pricing call doesn't exist by Friday. The BOGO ships at full price. The dashboard says 4x and the bank says no.
The way it's written down and the way it's done have drifted apart.
The SOP says one thing, the team does another. Every launch reinvents the checklist. The refund policy has three versions and support quotes a fourth.
The knowledge lives in one head instead of one place.
Everything routes through the founder or it stalls. Onboarding takes a quarter. Every departure is a small data-loss event.
Businesses don't fail from a lack of ideas. They fail because entropy eats their decisions before they reach the customer.
The interest gets collected at the customer: the launch they saw wasn't the launch you approved, the discount didn't apply, the winback email never went out. None of it was a bad idea. All of it was decided. It just never survived the trip.
You don't pay it off. You put it on a cadence.
Name it, so the team can see it. Map it, ranked by what each gap costs. Fix each gap once, with an owner and a way to verify it held. Then put verification on a standing rhythm, so drift gets caught in days instead of quarters. That's the whole discipline. It's not glamorous. It compounds.
I write one worked example a week in Clearly Commerce, sit beside founders doing it through advisory, and build Lore to catch the launch-shaped kind automatically.
Operational debt, in questions.
What is operational debt?
Operational debt is technical debt for your whole business: the compounding gap between what a company decided and what it actually does. Every unverified decision, drifted process, and undocumented handoff adds to the balance, and the interest gets collected at the customer.
Is it the same as technical debt?
Same mechanic, wider blast radius. Technical debt lives in a codebase and slows engineers down. Operational debt lives in the whole company, in decisions, processes, and handoffs, and it slows everyone down. Code review catches one; almost nothing catches the other.
Who does it hit hardest?
Growing DTC and ecommerce brands, roughly $5M to $50M, and the agencies that serve them. Small enough that nobody owns follow-through, big enough that drift costs real money. The team is 10 to 40 people, decisions move fast, and verification is nobody's job.
How do I know if I have it?
Five checks: launches ship different from what was approved; Monday's decisions don't exist by Friday; the SOP says one thing and the team does another; your dashboard and your bank disagree; everything routes through you or it stalls. Two or more and you're paying interest.
How do you fix it?
Name it, map it, fix it once, then verify on a cadence. Rank the gaps between decision and customer by what each one costs, give every fix an owner and a way to check it held, and put a standing rhythm on it so drift gets caught in days instead of quarters.
Where does the term come from?
The framing here comes from Matt Lady, an ecommerce operator who spent ten years watching good decisions evaporate between the meeting and the customer, and started treating the gap the way engineers treat technical debt: as a balance you name, measure, and pay down.
Think you're paying interest?
The call's on me. Bring the drift that bugs you most and we'll price it live.