How I diagnose recurring structural failure and specify the change sequence.
The purpose of this method is to identify what is structurally producing recurring failure — and to convert that diagnosis into the agreed artifact path: either a Diagnostic Artifact alone, or a complete four-artifact governed sequence in the Full Structural Engagement — Translation Artifact, Diagnostic Artifact, Redesign Executive Summary, and Full Redesign Artifact.
Most recurring failure is not a matter of local execution, poor communication, or one bad decision. It is structural. Something in the system is doing the wrong job, no job at all, or forcing humans to absorb work the system should carry.
This method starts where symptom-level explanation stops being sufficient.
This method applies when the same problem keeps returning under different names, when teams do not share the same structural read, when workarounds have quietly become load-bearing, or when builders are being forced to invent the design while implementing it.
The purpose is not to generate more commentary around the problem. The purpose is to produce one serious structural read — then, where the full engagement is commissioned, carry that read into the shared-language, executive, and builder-specification layers required for change.
How the diagnosis works
Define the system properly
The first task is to identify what system is actually under analysis — the real boundary, real scope, adjacent systems, and where work actually lives. Domain and team names often describe the surface, not the operational structure. This step must come first because every subsequent diagnostic claim depends on having the right system in scope. A diagnosis of the wrong system is not a partial diagnosis. It is a different artifact entirely.
Identify the primitive and governing rules
Once the system is defined, I identify its primitive — the smallest unit of real work the system is organised around — and the rules, constraints, and invariants that govern that action. The question is not what the policy says. It is what must actually hold for the system to function without drift. This step must come before failure tracing because a broken rule can only be identified once the governing rule has been named.
Trace the failure path
With the system and its governing rules established, I trace where rules become real, where they fail, and what happens when they do — interfaces, handoffs, decision points, enforcement points, and places where burden moves elsewhere. I look for where humans have become the hidden reliability layer. This step must precede diagnosis because the failure path shows where the break actually lives, which is rarely where it first appears.
Form the governing diagnosis
This is the central moment of the method. The governing diagnosis is the structural truth from which the rest of the failure follows — the one claim that, if correct, explains why prior fixes have not held and what must change before any intervention will. It separates what the client thinks is failing from what is actually producing the failure. Everything in the artifact either leads toward this paragraph or flows from it. It is the paragraph decision-makers will circulate internally.
Make the stakes legible
A diagnosis is incomplete if it does not make consequence visible. I make the current cost of the failure legible: operational cost, human cost, financial cost, coordination cost, and future compounding risk. This step matters because structural cost that remains vague continues to be absorbed invisibly — and invisible cost does not produce structural decisions.
Lock the diagnostic frame
The redesign does not begin until the governing diagnosis is locked. This prevents premature solutioning and ensures the change sequence flows from the structural break rather than from preference, urgency, or stakeholder pressure. A redesign produced before the diagnostic frame is locked is speculative. A speculative redesign is not what this practice delivers.
Produce the artifact
The final task is to produce the agreed artifact path — either a Diagnostic Artifact alone, or the complete four-artifact governed sequence in the Full Structural Engagement. In the full engagement, the same locked diagnosis produces four linked outputs:
- Translation Artifact — shared language layer for leadership, operations, and non-specialist audiences
- Diagnostic Artifact — governing diagnosis, evidence base, and build map
- Redesign Executive Summary — board-level public summary of the restricted specification
- Full Redesign Artifact — restricted builder specification: corrected primitive, transition sequence, dependency order, refusal invariants, recapture gates, and builder handoff
How diagnosis becomes redesign
Redesign is not produced by brainstorming solutions against a problem statement. It follows from the locked diagnosis. Once the structural break, primitive, invariants, and failure path are established, the redesign defines the corrected boundary, transition sequence, dependency order, interface changes, and drift refusal gates — in the order that prevents the same failure returning under a different name.
In the Full Structural Engagement, the locked diagnosis produces two redesign outputs. The Redesign Executive Summary converts the replacement logic into board-level form — designed to circulate internally and externally. The Full Redesign Artifact specifies the complete restricted builder sequence: corrected primitive, target boundary, transition order, refusal invariants, recapture gates, pilot validity conditions, and handoff logic. The sequence matters: executive summary without full specification becomes rhetoric; full specification without locked diagnosis becomes speculation.
How the four artifacts relate
The four artifacts are not four separate opinions. They are four layers of the same structural judgment.
The Translation Artifact makes the diagnosis legible to non-specialist audiences before the full evidence base is circulated.
The Diagnostic Artifact carries the evidence, failure trace, governing diagnosis, and build map.
The Redesign Executive Summary converts the replacement logic into board-level form.
The Full Redesign Artifact specifies the restricted builder sequence: corrected primitive, target boundary, transition order, refusal invariants, recapture gates, proof conditions, and handoff.
Translation without diagnosis becomes simplification. Diagnosis without redesign leaves builders without a change path. Executive summary without full specification becomes rhetoric. Full specification without locked diagnosis becomes speculation.
What I am looking for
Across different systems, I am often looking for the same classes of structural problem. The goal is not to collect every symptom. The goal is to identify the smallest set of structural truths that explains the recurring pattern.
I am also looking for places where a failure appears local but is actually systemic, where a named product is really functioning as something else, or where burden is being displaced onto the wrong people, teams, or functions.
- A function that is nominally present but operationally absent
- A burden that is being carried by the wrong person, team, or process
- A product or system that is functionally something different from what it is officially defined to be
- A correction that keeps being applied without ever touching the primitive
- A workaround that has become load-bearing
- A boundary that is stated but not enforced — or enforced against the wrong party
When diagnosis cannot be completed
Sometimes the available material is not sufficient to produce a diagnostic conclusion that can hold under scrutiny. The failure pattern may be too ambiguous, the system boundary too contested, or the material too thin to distinguish structural failure from local variance. In these cases, I will say so rather than produce an artifact that appears complete but is not.
The artifact is only useful if it is accurate. A plausible-sounding diagnosis that is wrong is actively harmful. Refusal to proceed when conditions are not met is part of the method, not a failure of it.
Redesign proceeds only from a locked diagnostic frame. If the diagnosis shows that redesign is not valid within the engagement boundary, I will stop at that point rather than produce a speculative Full Redesign Artifact. Any commercial adjustment is handled according to the agreed engagement terms.
What the artifacts contain
The Diagnostic Artifact gives your team one structural read. In the Full Structural Engagement, the four artifacts carry that same read across shared language, evidence, executive decision-making, and builder specification.
- Plain-language explanation of the structural failure
- Shared vocabulary across leadership, operations, and non-specialist roles
- Accessible explanation of the governing diagnosis
- Why prior fixes have not held
- Plain-language summary of the replacement direction
- Audience routing guidance — who reads what and where to go next
- A clear definition of the system under analysis
- A structural view of how work actually flows
- The primitive and governing rules
- The key interfaces and failure path
- The distinction between stated and actual problem
- The governing diagnosis
- The present and future cost of the failure
- What must change first, and what depends on what
- Board-level replacement logic
- Corrected primitive
- Minimum valid replacement conditions
- Fake-progress tests
- Proof standard and consequence of deferral
- Dependency order in plain terms
- The corrected primitive — what the system must actually be organised to do
- Target boundary — what changes and what does not
- Transition sequence — the dependency-ordered change path
- Interface changes — what must be tightened, removed, or clarified
- Drift refusal gates — constraints that prevent regression
- Builder handoff — the execution-ready sequence
Why this is different
This is not a technical root-cause analysis, a live incident response service, or a general consulting workshop. It is not designed to debug one isolated bug, patch one urgent issue, or produce vague strategy language that every team can interpret differently.
It is designed to identify the structural layer beneath recurring failure and convert that diagnosis into the appropriate written artifact path — a standalone Diagnostic Artifact, or a complete four-artifact sequence that carries the diagnosis from shared language to builder specification.
Many systems are repeatedly fixed at the symptom layer while the governing structure remains untouched. This work starts where surface explanation stops being sufficient.
How I produce the work
The work is architecture-led. The frameworks, structural distinctions, diagnostic logic, and conclusions are mine. AI assists drafting and production — it helps me work more clearly and efficiently. In a Full Structural Engagement, AI may also assist with consistency checking across all four artifacts. It does not decide what is being diagnosed, which rule is breaking, or what must change first, and does not determine the final recommendations in any artifact.
- Drafting and refining prose
- Organising material into usable forms
- Testing phrasings and structures
- Structuring large volumes of background material
- Determine the governing diagnosis
- Decide the redesign boundary or correction order
- Generate the structural laws the work applies
- Replace review, judgment, or accountability
Review and accountability
Every artifact is reviewed before delivery. The structural conclusions are mine. The diagnostic sequence, governing laws, and correction order are not delegated to AI, pattern-matching, or probabilistic inference. The artifact is accountable to the evidence it presents and the structural logic it applies. If a claim cannot survive scrutiny, it does not belong in the artifact.
One clarification pass is included after delivery. For the Full Structural Engagement, one clarification pass applies to the Diagnostic Artifact and one to the Full Redesign Artifact. The Translation Artifact and Redesign Executive Summary are derived from those locked frames and do not require separate clarification passes.
The research behind the method
The method is grounded in a ten-paper Diagnostic and Replacement Series. The papers define the structural laws the method applies: primitive mismatch, function collapse, burden transfer, the missing redesign layer, institution migration, replacement pipeline construction, admissibility conditions, governed correction sequences, host-constrained primitive compression, and kernel reduction. The papers are not the method. They are the public form of the structural laws the method is built on. The artifacts are the applied form of those laws within a bounded system.
When to start
If the same failure keeps returning and your team cannot agree on what is actually producing it, send the failure pattern first. I will confirm whether the right path is the Diagnostic Artifact alone or the Full Structural Engagement. The method is the same either way. The diagnostic path produces one Diagnostic Artifact. The full engagement produces four linked artifacts — Translation Artifact, Diagnostic Artifact, Redesign Executive Summary, and Full Redesign Artifact — all derived from the same locked diagnostic frame.