Manu's Vault

Exception Debt

3 min readStatus:Seedling

Exception debt is the accumulated informal parallel policy system that forms when managers repeatedly grant individual exceptions instead of improving the underlying policy. Like technical debt and Organizational-Debt, each exception is a shortcut that feels locally sensible but compounds interest over time — paid eventually through fairness crises, management overhead, and cultural resentment.

How Exception Debt Accumulates

The accumulation follows a reinforcing loop:

  1. Exception granted — manager approves a reasonable individual request outside formal policy
  2. Word spreads — other team members learn the exception is available through informal channels
  3. Demand escalates — more people request the same exception
  4. Fairness trap — granting to all normalises the exception (policy gap); denying subsequent requests signals unfairness
  5. Opacity grows — the manager can no longer accurately describe the actual operating policy

See Systems-Thinking-Stocks-Flows-Feedback for the reinforcing feedback dynamic.

Signs of High Exception Debt

  • Manager cannot articulate the actual policy because exceptions have overtaken it
  • Long-tenured members operate under different informal rules than newer joiners
  • Manager spends significant time negotiating individual arrangements rather than doing systemic work
  • Resentment from those who follow rules toward those who successfully negotiated exceptions

Why Exception Debt Is Especially Invisible

Unlike technical debt (which appears in slow deployments and bug rates), exception debt is socially concealed: beneficiaries have no incentive to surface their arrangements, there is no visible metric, each exception seems fair in isolation, and the crisis arrives suddenly when a fairness conflict erupts publicly.

Paying Down Exception Debt

  1. Audit — catalog all informal arrangements currently in effect
  2. Categorize — distinguish policy-gap exceptions (policy needs updating) from genuine one-time events
  3. Formalize — convert policy-gap exceptions into explicit, updated policy applying to everyone
  4. Communicate — announce the updated policy and sunset informal arrangements transparently
  5. Prevent — implement Work-the-Policy-Not-the-Exception going forward

Relationship to Other Debt Concepts

Exception debt is structurally analogous to technical debt (Cunningham, 1992): both are shortcuts generating compounding costs. The critical difference is visibility — technical debt appears in code and incident rates; exception debt is invisible until a social rupture surfaces it. Exception debt is also a specific form of Organizational-Debt, the broader category of deferred structural decisions.

Sources

  • Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9. Chapter 3.3.

    • Original articulation of exception debt as the natural consequence of repeated exception-granting; introduces the informal parallel policy system framing

  • Cunningham, Ward (1992). “The WyCash Portfolio Management System.” OOPSLA ‘92 Conference Proceedings, Vancouver.

    • Original articulation of the technical debt metaphor; exception debt extends this interest-bearing logic to informal policy

  • Akerlof, George A. (1980). “A Theory of Social Custom, of Ostracism, Discrimination, and Jobs.” Quarterly Journal of Economics, Vol. 94, No. 4, pp. 749–775. DOI: 10.2307/1885667.

    • Formal economic model showing informal social norms become self-sustaining; once established, deviation becomes socially costly — explaining why exception debt is hard to revoke

  • Crozier, Michel (1964). The Bureaucratic Phenomenon. University of Chicago Press. ISBN: 978-0-226-12183-3.

    • Classic study of how informal rule-bending creates informal power structures; the person who controls exceptions accumulates influence

  • Kahneman, Daniel, Rosenfield, Andrew M., Gandhi, Linnea, and Blaser, Tom (2016). “Noise: How to Overcome the High, Hidden Cost of Inconsistent Decision Making.” Harvard Business Review, October 2016.

    • Research on discretionary judgment demonstrates exceptions granted case-by-case produce high variance outcomes — reinforcing the case for policy over discretion

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks