Manu's Vault

Exception-Debt

4 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, exception debt uses the “debt” metaphor deliberately: 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 five-step reinforcing loop:

  1. Exception granted — manager approves a reasonable individual request outside the formal policy
  2. Word spreads — other team members learn this exception is available, often through informal channels
  3. Demand escalates — more people request the same exception; the manager must decide
  4. Fairness trap — granting to all normalizes the exception (policy gap); denying subsequent requests signals unfairness (“why did they get it but not me?“)
  5. Opacity grows — over time, the manager can no longer accurately describe the actual operating policy; different people have different informal arrangements

This is a reinforcing feedback loop: the more exceptions exist, the more are sought. See Systems-Thinking-Stocks-Flows-Feedback.

Signs of High Exception Debt

  • Manager cannot articulate the actual policy because exceptions have overtaken it
  • Long-tenured team members operate under different informal rules than newer joiners
  • New team members are confused about norms — onboarding reveals inconsistency
  • Manager spends significant time negotiating individual arrangements, not 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 shows up as slow deployments, bug rates, and developer frustration), exception debt is socially concealed:

  • Beneficiaries stay quiet — those with favorable exceptions have no incentive to surface them
  • No visible metric — exception accumulation doesn’t appear in any dashboard
  • Each exception seems fair in isolation — the problem is systemic, not individual
  • Crisis arrives suddenly — visibility only comes when a fairness conflict erupts publicly

Paying Down Exception Debt

  1. Audit — catalog all informal arrangements currently in effect; ask who is actually operating differently
  2. Categorize — distinguish policy-gap exceptions (these reveal a policy that needs updating) from genuine one-time events
  3. Formalize — convert policy-gap exceptions into explicit, updated policy that applies to everyone
  4. Communicate — announce the updated policy and sunset informal arrangements transparently
  5. Prevent — implement Work-the-Policy-Not-the-Exception going forward to stop new debt accumulating

Relationship to Other Debt Concepts

Exception debt is structurally analogous to technical debt (Cunningham, 1992): both are shortcuts that feel locally rational but generate compounding costs that must eventually be repaid. The critical difference is visibility — technical debt appears in code, build times, 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; “Shipping first-time code is like going into debt — every minute spent on not-quite-right code counts as interest on that debt.” Exception debt extends this same 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 how informal social norms (including informal exceptions to rules) become self-sustaining and sticky; once established, deviation becomes socially costly — explaining why exception debt is hard to revoke once accumulated

  • 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 within bureaucracies; the person who controls exceptions accumulates influence — explaining why exception-granting concentrates dependency on the manager

  • 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 “noise” in human discretionary judgment demonstrates that exceptions granted case-by-case produce high variance outcomes even with well-intentioned managers — structurally 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