Written-first, asynchronous, and bounded.
Most of the work happens through email, document review, and targeted written questions. I do not move into your workflow or begin with a chain of meetings. The aim is simple: keep the problem, scope, and conclusions explicit from start to finish.
Default mode
Email, document review, and written clarification. This keeps the engagement focused on structural signal rather than conversational noise.
Clarifying questions
If something important is missing, I may ask targeted questions. These are used to tighten scope and locate the real boundary — not to create a meeting cycle.
What this prevents
Premature implementation, endless alignment calls, and the slow drift that happens when the work stays verbally defined rather than written down.
A fixed sequence from entry to delivery.
Five steps. The entry signal differs by service, but the rule is the same: define the boundary before analysis begins, do the work inside that boundary, then deliver a stable written output.
Structural Lens: send a short description of the system, method, problem, or body of work whose architecture you want exposed. Recurring failure: send the Five-Line Brief — what keeps going wrong, what it costs, where it shows up, what has been tried, and what cannot change. Attach useful materials if you have them. Accuracy matters more than polish.
I determine whether the work is structurally suited to this approach and which scope fits: Structural Lens Brief, Diagnostic Artifact, or Full Structural Engagement. If the issue is not a fit, I say so here. For recurring failure, redesign is never selected as a shortcut around diagnosis.
The boundary, fee, delivery window, required inputs, and output are confirmed before work begins. Lens is a 7-day architecture extraction. Diagnostic is a 14-day structural diagnosis. Full is a £25,000 governed diagnosis-to-redesign engagement within a 14-day window, subject to timely diagnostic confirmation.
For Lens, I expose what the subject is actually built on: its underlying structure, functions, boundaries, dependencies, and tensions. For Diagnostic, I locate and name the governing structural break. For Full, the same work carries that diagnostic frame into the corrected boundary, transition sequence, dependency order, and builder handoff; the Diagnostic Artifact is delivered first and redesign is released after the frame is confirmed in writing.
You receive the output defined in scope: a 6–10 page Structural Lens Brief, one Diagnostic Artifact, or the complete four-artifact Full Structural Engagement. Lens and Diagnostic each include one minor clarification pass. Full includes one clarification pass on the Diagnostic Artifact, then — after written confirmation of that frame — release of the redesign artifacts and one clarification pass on the Full Redesign Artifact. New analysis or a widened boundary becomes separate work.
Three routes. Choose by the job you need done.
You do not need to learn the method before choosing. The distinction is practical: expose the architecture, diagnose the recurring failure, or carry a locked diagnosis into redesign.
Expose what it is built on.
Use this when you need the architecture beneath one problem, system, method, or body of work made explicit. It extracts the structure. It does not perform the full recurring-failure diagnosis.
Name why the failure keeps returning.
Use this when the same problem keeps coming back, different teams describe it differently, or previous fixes have not held. The output is the governing structural diagnosis and build map.
Diagnose it, then specify the replacement.
Use this when naming the failure is not enough. The same 14-day governed engagement carries diagnosis into the corrected boundary, transition sequence, dependency order, refusal gates, and builder handoff. The Diagnostic Artifact is delivered first; redesign is released after the diagnostic frame is confirmed.
If you are unsure, you do not need to diagnose yourself. Contact me with the situation. For a recurring failure, send the Five-Line Brief. For architecture extraction, request the Structural Lens. I will confirm the correct scope before any paid work begins.
Useful signal, not polished presentation.
You do not need a polished brief or a perfect document pack. Send the material that best reflects the real system. For a Lens request, that may be the method, product, workflow, document set, or problem you want structurally mapped. For recurring failure, the Five-Line Brief is the starting signal.
- 01 A Lens request or completed Five-Line Brief, depending on the work
- 02 Diagrams, policies, workflows, notes, contracts, or screenshots
- 03 Post-mortems, incident reports, or internal documents that show what actually happened
- 04 A clear statement of known constraints: technical, legal, budgetary, or operational
- 05 Timely written responses if clarifying questions are required
- → Accuracy over polish — rough materials are fine if they reflect reality
- → Operating reality over official narrative — what actually happens, not what the policy says
- → Boundary signal over volume — knowing what cannot change is as useful as knowing what keeps breaking
- → Honest constraints — hidden constraints discovered mid-engagement create scope problems
If you are unsure whether you have enough to send, send what you have. The fit assessment will determine whether there is sufficient signal to proceed.
All materials are treated as high-integrity inputs to the artifact and are not retained beyond the engagement lifecycle.
A written artifact — or governed artifact set — not a deck.
Every engagement ends with a defined written output. Lens delivers one concise Structural Lens Brief. Diagnostic delivers one Diagnostic Artifact. Full delivers four linked artifacts as one governed sequence. The work is designed to circulate, support decisions, and give builders a stable reference point.
Who it is for
Decision owners, operators, and builders who need a shared structural read without having to reconstruct the logic from meetings or scattered documents.
What it does
Makes the agreed level of structure explicit: architecture for Lens, governing failure for Diagnostic, and diagnosis plus correction sequence for Full.
What it is not
Not a slide deck, workshop package, implementation team, or open-ended advisory retainer. The scope and output are defined before work begins.
Not every problem belongs in this process.
The intake exists to determine whether this approach is appropriate — not to force every problem into the same engagement. If it is not a fit, I say so at the fit assessment stage.
Not a fit when
- The issue is too broad or undefined for a bounded written intervention
- The real need is implementation ownership, delivery leadership, or ongoing facilitation
- The available inputs do not contain enough signal to define a reliable boundary
- The failure is primarily operational noise rather than a structural problem
- Multiple unrelated failure modes are being combined into one request
If it is not a fit, I say so at the fit assessment stage. There is no charge for this. The point of the intake is to determine whether this approach is appropriate.
If the problem is structurally interesting but outside the defined scope of these engagements, I may be able to point toward a more appropriate route.
The engagement ends. The artifact does not.
The artifact is yours to circulate, act against, and use as a stable reference point. The engagement itself is bounded — it does not continue into ongoing advisory, retainer access, or implementation support.
Clarification pass
The Structural Lens Brief and Diagnostic Artifact each include one minor clarification pass. In 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 do not have separate revision rounds. Clarification does not include new analysis, extended scope, or additional research.
When new work is required
If the boundary expands, the problem changes shape, or new analysis is required after delivery, that becomes a separate engagement. Scope creep is not absorbed silently.
How to start the next one
Start with the signal that matches the job: a Lens request for architecture extraction, or a Five-Line Brief for recurring failure. I confirm scope before new paid work begins.
The Five-Line Brief is a fit screen for recurring failure, not the diagnosis itself. It helps determine whether the case is structurally diagnosable and whether the right scope is Diagnostic or Full. A Structural Lens request uses a simpler architecture-extraction brief because it is not necessarily a failure case.
If the case is one-off, purely technical, outside the available evidence, or otherwise not structurally suited to this work, I will say so.
- 01 What keeps going wrong? Describe the failure that keeps returning.
- 02 What is it costing? Describe the cost in money, time, trust, load, delay, or drift.
- 03 Where does it show up? Name the teams, roles, systems, or customer touchpoints involved.
- 04 What has already been tried? List any fixes, workarounds, or decisions already attempted.
- 05 What cannot change? State the non-negotiables, constraints, or conditions that must still hold.
Not sure whether the recurring problem is structural? Run the 60-Second Structural Scan before you send a brief.