The Resolution Playbook

Chapter 8: The Resolution Playbook

The resolution of pattern debt follows a principle I call respectful replacement.

The word “respectful” matters. Pattern debt was created by people who were doing their best under the conditions they faced. The decisions they made were correct at the time. Treating those decisions as mistakes — as evidence of incompetence or short-sightedness — is both inaccurate and counterproductive. The decisions were good. The conditions changed. The decisions did not.

Respectful replacement acknowledges the original decision’s validity while replacing it with a decision appropriate to current conditions. The acknowledgment is not ceremonial. It is functional: by understanding why the original decision was made, the organization can ensure that the replacement addresses the same concerns under the new conditions, rather than simply overwriting the past.

The Four Steps

Step 1: Identify the fossilized decision. This is the output of the audit framework in Chapter 6 — a specific pattern, with its origin date, its original rationale, and its estimated cost.

Step 2: Map the load. Before removing or replacing any pattern, determine what depends on it. The dependencies are often non-obvious. A naming convention that seems arbitrary may encode a distinction that matters to a downstream system. A meeting cadence that seems outdated may serve a social function — keeping two teams in contact — that is independent of its stated purpose. A cultural norm that seems outdated may protect against a risk that the organization has forgotten it faces.

The mapping technique: for each identified pattern, ask three questions.

What breaks if this pattern disappears tomorrow? (Technical dependencies.)
Who notices if this pattern disappears tomorrow? (Social dependencies.)
What becomes possible if this pattern disappears tomorrow? (Opportunity unlocked.)

The first two questions identify the load. The third question identifies the value of resolution. Both are necessary for a sound decision.

Step 3: Design the replacement. The replacement must satisfy three criteria:

It reflects current conditions. (If it does not, it will become debt immediately.)
It carries the identified load. (If it does not, it will break things.)
It includes its own rationale. (If it does not, it will fossilize without explanation, repeating the cycle.)

The third criterion is the one most often neglected and the one that prevents the next generation of pattern debt. Every replacement decision must be documented with its rationale — not just what was decided, but why, under what conditions, and when those conditions should be reviewed.

Step 4: Execute the replacement. The execution depends on the type of debt.

Execution by Type

Structural Pattern Debt

Structural replacement is technical migration. The principles:

Migrate completely, not incrementally. Incremental migration — maintaining both old and new structures in parallel — creates a transition period during which the system is more complex than it was before, because both structures exist simultaneously. The transition period has its own cost, and the cost is often high enough to stall the migration indefinitely, leaving the organization with both structures forever.
Use the strangler fig pattern. Build the new structure alongside the old, redirect traffic gradually, and retire the old structure only when the new one has proven stable. The key distinction from incremental migration: the strangler fig has a defined end state (the old structure is retired) and a defined timeline (the retirement date is scheduled, not deferred).
Establish a vocabulary cut-over. On a defined date, the organization’s vocabulary changes. “We no longer say ‘user_data.’ We say ‘customer_profiles.’ The old term is deprecated.” The vocabulary cut-over is as important as the technical migration because vocabulary shapes thought, and thought shapes decisions.

Procedural Pattern Debt

Procedural replacement is process redesign. The principles:

Zero-base the process. Do not patch the existing process. Design the process from scratch, given current conditions, current team size, current tools, current objectives. Compare the zero-based design to the existing process. The differences are the resolution.
Preserve the social function. Many procedures serve social functions — maintaining relationships, providing visibility, creating accountability — that are independent of their stated purpose. Identify the social function. Preserve it through an alternative mechanism. Then retire the procedure.
Assign an expiration date. Every new procedure should include a review date. “This process will be reviewed in twelve months.” The review date forces the question: do the conditions that justified this process still hold? The question prevents fossilization.

Cultural Pattern Debt

Cultural replacement is the hardest and the most important. The principles:

Name the pattern. Cultural patterns are invisible by definition — they are “the way we do things here.” Naming them makes them visible. Visibility is the prerequisite for change.
Model the replacement. Cultural patterns change through behavior, not through announcement. The new pattern must be modeled by leaders — visibly, consistently, long enough for the organization to observe and adopt it.
Tolerate the transition. Cultural change is slow. The old pattern and the new pattern will coexist for months. The coexistence is uncomfortable. The discomfort is not a sign of failure — it is a sign of change in progress.

The Preservation Principle

Not everything should be replaced. Some pattern debt is load-bearing in ways that are essential to the organization’s function, even if the original rationale has expired. The meeting that serves no stated purpose but that keeps two teams in communication. The naming convention that is outdated but that encodes institutional knowledge about data lineage. The cultural norm that is constraining but that prevents a specific kind of failure the organization has forgotten it is vulnerable to.

The preservation principle: before resolving any pattern debt, verify that the pattern’s load-bearing properties are either no longer needed or are carried by the replacement. If you cannot verify this, do not resolve the debt. Document it. Mark it as load-bearing. Review it annually. But do not remove it until you understand what it carries.

The principle is conservative. It errs on the side of caution. It will sometimes preserve patterns that could safely be removed. This is acceptable. The cost of preserving unnecessary patterns is linear — it is the annual cost of accommodation. The cost of removing load-bearing patterns is catastrophic — it is the cost of systems, processes, or cultures failing in ways that are difficult to diagnose because the stabilizing pattern is no longer present.

The Timeline

Resolution takes longer than expected. This is invariant across every engagement I have conducted. The timeline estimate should be multiplied by 1.5 for structural debt, 2.0 for procedural debt, and 3.0 for cultural debt.

The multipliers reflect the hidden work of resolution: the dependencies that were not identified in the mapping phase, the social negotiations required to change processes, and the behavioral change required to shift cultural patterns. The hidden work is not a sign of poor planning — it is a property of pattern debt itself, which is by definition partially invisible. You cannot fully map what is partially invisible. You can account for the partial invisibility by budgeting extra time.

After the Resolution

The resolution is not complete when the new pattern is in place. The resolution is complete when:

The new pattern has been stable for ninety days.
The old pattern’s artifacts have been retired (old tables dropped, old meetings canceled, old norms explicitly superseded).
The new pattern’s rationale has been documented.
A review date has been assigned.

The four criteria prevent the most common failure mode of pattern debt resolution: the partial migration, where the new pattern exists alongside remnants of the old, and the remnants gradually accumulate their own dependencies, creating a new layer of debt more complex than the original.

Complete resolution. Clean retirement. Documented rationale. Scheduled review. That is the protocol. The protocol works.