A company debt audit turns a vague sense of drag into an inspectable operating conversation. The goal is not to find every flaw. The goal is to identify the liabilities that are now shaping speed, trust, customer quality, margin, and decision clarity.

Start by separating debt from pain. Pain is what people feel. Debt is the underlying liability that keeps producing the pain. Too many meetings may be coordination debt, decision debt, trust debt, or process debt. The audit should avoid treating the symptom as the category.

The first section of the audit is debt type. Review decision debt, trust debt, coordination debt, narrative debt, customer debt, pricing debt, implementation debt, process debt, data debt, talent debt, and technical debt. The categories are not perfect. They are prompts that force the company to look beyond engineering.

The second section is carrying cost. For each debt, estimate what the company is paying: slower decisions, lower win rate, higher churn risk, margin drag, executive time, employee cynicism, implementation load, product distraction, support burden, or strategic constraint.

The third section is origin. Some debts were good trades at the time. Some were accidents. Some were political compromises. Some were created by success. Naming the origin helps leaders avoid moralizing. The question is not who to blame. The question is whether the original trade still makes sense.

The fourth section is repayment option. Retire, redesign, refinance, automate, document, reassign, renegotiate, or consciously carry. Not all debt should be paid immediately. A company that tries to clean everything at once creates a different form of debt: transformation overload.

The fifth section is ownership. Debt without an owner becomes culture. If everyone knows the issue and nobody owns the repayment path, the company has normalized the liability. Ownership should sit with the person who can change the system, not merely the person experiencing the pain.

The audit should start with prework. Ask each function to bring three debts it owns, three debts it receives from another function, and one debt it believes the company should continue carrying. That last question matters. It prevents the audit from becoming a cleanup crusade and forces leaders to name the debts that are still buying useful speed, learning, or market access.

During the review, group symptoms before assigning owners. If support names repeat tickets, implementation names data cleanup, and product names configuration complexity, the shared debt may be product architecture, qualification, or packaging. If each team only defends its local view, the audit will reproduce the coordination debt it is trying to expose.

The output should be a short repayment portfolio. Pick one debt to retire, one to redesign, one to document, one to consciously carry, and one to revisit after a trigger. This keeps the company from trying to fix everything at once. It also makes the tradeoff visible: the company is choosing which liabilities matter most this quarter.

The sixth section is trigger. Some debts are tolerable until a stage change. A custom implementation process may work at twenty customers and break at two hundred. A pricing exception may be manageable until expansion motion matters. A narrative gap may be survivable until hiring scales.

The audit is successful only if it changes planning. A company debt item should affect roadmap, hiring, enablement, packaging, customer commitments, operating cadence, or executive attention. If it does not change any allocation decision, it is not yet an operating liability in the company's real system. It is just a well-described frustration.

The audit should end with owners and triggers, not a long list of observations. Each selected debt needs one accountable owner, one repayment path, one expected change in operating behavior, one trigger that will bring it back to review, and one next review date. Without those fields, the audit becomes another document about work instead of a mechanism for changing work.

Debt repayment fails when it is treated as background hygiene that everyone supports and nobody funds. Put the repayment work into the same operating cadence as product bets, hiring plans, GTM initiatives, and finance commitments. If a debt item matters, it deserves an owner, a milestone, and a tradeoff. If it does not deserve those things, it should not sit on the executive list.

This is the useful discipline of the debt metaphor. It does not say every liability is bad. It says liabilities should be known. A company can carry debt when the debt buys speed, learning, or market access. It gets into trouble when the debt becomes invisible, when the interest is paid by teams with no authority to repay it, and when leaders plan the future as if the liability were not there.

It also helps to keep a conscious-carry list. Not every debt should be repaid immediately. Some debts buy learning, speed, market access, or focus. The discipline is to name the bargain and revisit it. A debt that is consciously carried should have a reason, a limit, and a date for reconsideration. Otherwise conscious debt quietly becomes unmanaged debt.

AI can help run the audit by reading plans, notes, tickets, support logs, call summaries, contracts, and retros. It can cluster symptoms and draft candidate debt items. But the final audit needs executive judgment because repayment is resource allocation.

The operator test: ask the executive team to agree on the top five company debts before planning the next quarter. If the list does not affect priorities, resourcing, or kill decisions, it was not an audit. It was a vocabulary exercise.

This is part 10 of 10 in Company Debt Beyond Tech Debt.