Experience Debt
Experience Debt is the future cost created when useful model structure must be reconstructed repeatedly because it was never made explicit, verified for its declared scope, and released for reuse.
How the Debt Forms
Experience Debt can form whenever the same operational structure must be reconstructed repeatedly. A team may repeatedly reconcile the same standards. Developers may repeatedly infer the same process dependencies from documentation. Different projects may independently translate the same domain rules into requirements and code.
If the resulting model remains implicit in one interpretation, one implementation, or scattered descriptive traces, the organization may pay for the same reconstruction again.
The debt is not the absence of documentation alone. It is the absence of a model that has been made explicit, verified for its declared scope, and released for reuse.
How Experience Debt Accumulates
Experience Debt accumulates through repeated loss of reusable structure. A useful model may be reconstructed during analysis, implementation, investigation, or problem solving, yet remain embedded in one-off code, project documents, scattered notes, or an individual's interpretation rather than becoming a reusable model asset.
The next team then pays again to reconstruct essentially the same structure. This loss of reusable structure is one mechanism by which Experience Debt grows.
Why Documents Do Not Automatically Eliminate It
An organization can possess every relevant document and still carry Experience Debt. The documents may describe pieces of the model in different places. Conditions may be implicit. Terms may conflict. A reader may need extensive domain knowledge to combine the sources correctly.
The debt decreases when the useful structure is reconstructed, verified to the level required for its declared scope, and released as a reusable model.
LLMs Change the Cost Curve
LLMs reduce the cost of reading, comparing, and synthesizing large bodies of descriptive material. This makes it practical to attack forms of Experience Debt that were previously too expensive to formalize.
The reconstructed candidate structure still requires verification. The gain comes from accelerating candidate model production while preserving explicit review of the resulting structure.
Paying Down Experience Debt
An organization reduces Experience Debt by identifying repeatedly reconstructed model structure, making it explicit, verifying it for its declared scope, and releasing qualified models for reuse. High-value targets are processes with frequent interpretation, expensive onboarding, complex rules, many dependencies, or high consequences for error.
The economic test is simple: if people repeatedly spend time rebuilding the same model, there is a candidate for capitalization.