Organisation Debt, Part II: From Metaphor to Managed Reality

If your organisation doesn’t put “organisation debt” on the management agenda with targets, owners, and a pay-down plan, AI, platform modernisation, and Consumer Duty ambitions will continue to stall. Treat it like a real liability with an interest bill, a maturity profile, and a monthly statement—then refinance, retire, or ring-fence it.

Why this matters now

In my previous article I argued that organisation debt—the accumulated cost of poor structures, decisions, controls, data semantics, processes and platforms—acts like a shadow liability. Since then, three shifts have amplified the cost of carrying it:

1. AI at the edge exposes broken decision rights, messy data contracts, and brittle processes.
2. Operational resilience and customer-outcomes scrutiny turn “internal inefficiency” into customer harm risk.
3. Platform/API strategies collide with legacy operating rhythms and opaque accountabilities.

Five provocations for executives

1. Make it financial: publish an Organisation Debt Service Ratio (ODSR)—the percentage of change and run capacity spent on workarounds, rework, failure demand, and handoffs. If ODSR > 25%, you are paying usurious interest.
2. Shift ownership: CFO sponsors the ledger, COO/Chief Architect operate the Credit Committee (Design Authority), and the Board Risk Committee sees the maturity profile quarterly.
3. Retire, refinance, or ring-fence: not every debt should be paid down—some should be refinanced (platformised), others ring-fenced (isolated from critical flows) until sunset.
4. Stop funding interest: no new money for change unless 10–20% is ring-fenced to reduce principal in the impacted capabilities.
5. Price the harm: link debt interest to time-to-value, customer detriment, and resilience gaps for Important Business Services.

A practical taxonomy (beyond “process” and “tech”)

• Decision Debt: unclear accountabilities, multi-step approvals, policy ambiguity.
• Control & Risk Debt: manual compensating controls, duplicated attestations, inherited SOP sprawl.
• Data & Knowledge Debt: divergent definitions, ungoverned reference data, tribal knowledge not codified.
• Platform & Integration Debt: point-to-point “spaghetti,” local tooling, non-composable patterns.
• Experience Debt: inconsistent journeys, channel fragmentation, call-deflection below target.
• Operating Rhythm Debt: planning cadences misaligned to value streams; design authorities convened too late.
• Capability Debt: under-invested core capabilities (e.g., Pricing Strategy, Claims Triage, Partner Enablement).

Measure it like a balance sheet

• Principal: the structural backlog to remove the cause (work items, £ estimate, or story-point equivalent).
• Interest: the recurring waste—cycle-time premium vs benchmark, rework %, failure demand %.
• Maturity Profile: where interest is highest in the next 12 months (map to value streams).
• Coverage & Default Risk: resilience gaps, key-control weaknesses, single-points-of-failure.

Failure demand (for clarity): customer contacts created by the system failing to deliver the right outcome first time (e.g., chasing, correcting, clarifying). Track it per service and segment; aim for a delta vs baseline improvement target (e.g., from 45% to 30% in two quarters).

The Organisation Debt Ledger (template you can lift)

For each capability × value stream intersection:

• Capability & flow (e.g., Underwriting—Quote to Bind)
• Debt type(s) & description
• Principal (effort/cost) and Interest (monthly waste or delay)
• Owner (single executive) and Maturity date
• Risk of default (customer harm, resilience breach, regulatory exposure)
• Remediation instrument: paydown, refinance (platformise/standardise), or ring-fence (isolate/contain)
• Savings realisation plan and re-investment rule (portion hypothecated to further debt reduction)

A 90-day pay-down playbook

Weeks 0–2: Baseline & expose

• Select top five value streams (e.g., FNOL-to-Settlement, Quote-to-Bind, Mid-Term Adjustments, Collections, Partner Onboarding).
• Quantify ODSR, failure demand, rework %, and cycle-time premium vs external/internal benchmark.

Weeks 3–4: Prioritise principal

• Identify the top 10 structural drivers of interest.
• Classify each: paydown, refinance, ring-fence. Commit owners and maturity dates.

Weeks 5–8: Micro-amortisations

• Deliver 30–60 day structural fixes: retire duplicate approvals; codify policy-as-code; remove non-value checks; consolidate reference data; standardise handoffs.

Weeks 9–12: Refinance

• Replace local tools with platform services (rules, workflow, document, ID&V) and data products with contracts.
• Introduce decision catalogues and knowledge graphs where AI/automation is targeted.

Governance: The Design Authority = Credit Committee. No new change approved without a declared debt impact (creates, carries, or pays down).

AI lens: why pilots stall

Most AI proofs don’t fail on model quality; they fail on organisation debt:

• Decision debt: no canonical decision model; approvals hidden in email culture.
• Data debt: weak semantics; missing lineage; no policy-as-data.
• Control debt: manual checks that block straight-through decisioning. Fix these first—AI then scales cleanly.

Insurance-specific signals (what to watch)

• Underwriting workbench adoption capped by product reference-data divergence and duplicate sanction checks.
• Claims leakage from inconsistent triage rules and unresolved policy wording ambiguity (decision & control debt).
• Open Insurance/API programmes slowed by non-standard data products and partner enablement gaps (platform & capability debt).
• Consumer Duty remediation generating recurring manual workarounds rather than structural fixes (interest spirals).

What “good” looks like in metrics & OKRs

• ODSR: −10 to −15 percentage points in two quarters on targeted flows.
• Cycle-time premium vs benchmark: halve the delta.
• First-time resolution: +10–15 pts; contact rate per policy −20%.
• Pattern adoption (platform refinance): >70% of new change on standard services in two quarters.
• Control automation: replace top 5 manual controls with policy-as-code.

Boards should ask

1. Where is our debt interest highest, and what is the maturity profile?
2. Which debt are we refinancing via platform, and which are we ring-fencing until sunset?
3. How much of every investment is hypothecated to principal reduction?
4. Which Important Business Services would breach outcomes if we miss maturity dates?

And finally, publish the statement

Move organisation debt from rhetoric to reporting. Put the Organisation Debt Statement alongside financials monthly. When leaders see the interest bill, they stop funding it.