Judgment · Ownership · Accountability
HOW FULL AFFAIR WORKS
Find what is limiting the result.Build the right capability.Improve through every outcome.
Start with the outcome your business needs. Examine how the work and decisions actually happen. Test what is most likely limiting the result, then coordinate people, AI agents and technology around a focused capability that can be measured and improved.
For established businesses with a valuable outcome to improve, access to the relevant work and evidence, an accountable owner and the ability to act on the findings.
Intelligence · Speed · Scale · Consistency
Context · Workflow · Data · Integration
Can this work in a business like mine?
The method works around the result your business needs and the way your work actually happens. The discipline remains consistent. The diagnosis and intervention change.
Growth
- Valuable opportunities are leaking between marketing and sales.
- Response or follow-up is inconsistent.
- More activity is not producing predictable revenue.
- Customer learning does not improve future acquisition or retention.
Operations
- Work slows at handoffs, approvals or missing information.
- More volume creates more coordination pressure.
- Employees repeatedly reconstruct information.
- Delivery depends on a few people remembering what to do.
Intelligence
- Leaders see important changes too late.
- Reports create discussion without clear decisions.
- Knowledge remains fragmented across people, documents and tools.
- The same mistakes and questions keep returning.
AI Implementation
- Employees use AI without a coordinated plan.
- AI experiments are disconnected from measurable outcomes.
- The business knows AI matters but does not know where to begin.
- A tool or agent is being considered before the work is understood.
The method is organised around the limiting business condition, not around an industry template or predetermined technology package.
THE COMMON FAILURE
The wrong solution can make the real problem harder to see.
- 01
Automating a broken workflow
- 02
Generating more demand while fulfilment remains constrained
- 03
Adding a dashboard without defining the decision it must improve
- 04
Introducing AI agents without reliable context or ownership
- 05
Optimising one department while total performance remains unchanged
- 06
Treating the documented process as the way work actually happens
A useful solution aimed at the wrong problem is still an expensive mistake.
Begin with the outcome and the system producing it, not with a predetermined service, platform, software package or AI tool.
This illustrates a hypothesis. It is not a diagnosis.
- 01ObjectivePressure may accumulate
- More marketing applied here02Demand or signalPressure may accumulate
- 03DecisionPressure may accumulate
- 04WorkPossible limiting condition
- 05Customer outcomeFlow may weaken
- 06Economic resultFlow may weaken
- 07Measurement and learningFlow may weaken
More marketing is shown at Demand or signal, while Work remains the possible limiting condition. The whole flow must be examined before the intervention is justified.
Understand the outcome, the real work and the uncertainty around both.
Desired outcome
What must become meaningfully better for the customer and the business?
- Business significance
- Customer consequence
- Economic value
- Owner
- Baseline
- Expected change
Current reality
How does the work actually happen?
- Informal workarounds
- Decisions
- Handoffs
- Exceptions
- Delays
- Customer behaviour
Connected system
Which people, decisions, information, workflows, technology and economics produce the result?
- People
- Decisions
- Information
- Workflow
- Technology
- Economics
Most plausible limitation
Which condition currently appears to restrict more of the desired outcome?
- Accumulation
- Delay
- Leakage
- Capacity
- Policy
- Downstream effect
Readiness
What must exist for reliable implementation?
- Ownership
- Knowledge
- Controls
- Integrations
- Measurement
- Operating conditions
Uncertainty
What is known, assumed or not yet observable?
- Known
- Assumed
- Disputed
- Incomplete
- Delayed
- Biased
Assumptions are made visible. Competing explanations are compared. Evidence that could prove the leading diagnosis wrong is actively sought.
Assumptions exposed. Evidence challenged. Commitment sized to confidence.THE CONTROLLED IMPROVEMENT CYCLE
From an unclear problem to verified business change.
Every stage creates evidence and a decision. Work does not advance simply because the previous activity was completed.
Define the outcome
What valuable result must improve?
- What happens
- Agree the result, its business significance, who owns it and how meaningful change will be measured.
- Output
- Desired outcome, owner, baseline and measurement model.
- Decision gate
- Is the desired result valuable, owned and measurable?
Observe the actual system
How is the result really produced today?
- What happens
- Observe decisions, handoffs, workarounds, information, technology and customer behaviour in the real workflow.
- Output
- Current-state system map and operating baseline.
- Decision gate
- Is the actual system understood well enough to develop explanations?
Develop explanations
What could explain the gap?
- What happens
- Compare plausible causes of the gap and make the assumptions behind each explanation visible.
- Output
- Leading explanation, alternatives and visible assumptions.
- Decision gate
- Does one explanation justify being challenged and tested first?
Challenge the diagnosis
What evidence or conditions would show that the explanation is incomplete or wrong?
- What happens
- Seek contradictory evidence and design a bounded test that can update confidence in the leading explanation.
- Output
- Contradictory evidence, confidence update and test design.
- Decision gate
- Has the diagnosis survived enough challenge to size the next commitment?
Prepare the foundations
What must be ready for reliable change?
- What happens
- Prepare ownership, approved context, controls, integration, measurement and adoption conditions.
- Output
- Ownership, context, controls, integration, measurement and adoption plan.
- Decision gate
- Are the owners, context, controls, baseline and adoption conditions ready?
Build and test the capability
What is the smallest complete capability capable of materially changing the outcome?
- What happens
- Design and deploy a complete human-and-AI capability inside controlled boundaries, with exceptions and fallbacks defined.
- Output
- A focused human-and-AI operating capability inside controlled boundaries.
- Decision gate
- Is the capability safe, usable and complete enough to test against the outcome?
Measure, learn and improve
What changed, what failed and what should happen next?
- What happens
- Compare outcomes with the baseline, capture exceptions and decide what to retain, change, stop or address next.
- Output
- Validated learning, system updates and the next decision.
- Decision gate
- Did the outcome materially improve, and what does the evidence support next?
Learning returns to the desired outcome and informs the next justified cycle.
01Define the outcome
What valuable result must improve?
- What happens
- Agree the result, its business significance, who owns it and how meaningful change will be measured.
- Output
- Desired outcome, owner, baseline and measurement model.
- Decision gate
- Is the desired result valuable, owned and measurable?
02Observe the actual system
How is the result really produced today?
- What happens
- Observe decisions, handoffs, workarounds, information, technology and customer behaviour in the real workflow.
- Output
- Current-state system map and operating baseline.
- Decision gate
- Is the actual system understood well enough to develop explanations?
03Develop explanations
What could explain the gap?
- What happens
- Compare plausible causes of the gap and make the assumptions behind each explanation visible.
- Output
- Leading explanation, alternatives and visible assumptions.
- Decision gate
- Does one explanation justify being challenged and tested first?
04Challenge the diagnosis
What evidence or conditions would show that the explanation is incomplete or wrong?
- What happens
- Seek contradictory evidence and design a bounded test that can update confidence in the leading explanation.
- Output
- Contradictory evidence, confidence update and test design.
- Decision gate
- Has the diagnosis survived enough challenge to size the next commitment?
05Prepare the foundations
What must be ready for reliable change?
- What happens
- Prepare ownership, approved context, controls, integration, measurement and adoption conditions.
- Output
- Ownership, context, controls, integration, measurement and adoption plan.
- Decision gate
- Are the owners, context, controls, baseline and adoption conditions ready?
06Build and test the capability
What is the smallest complete capability capable of materially changing the outcome?
- What happens
- Design and deploy a complete human-and-AI capability inside controlled boundaries, with exceptions and fallbacks defined.
- Output
- A focused human-and-AI operating capability inside controlled boundaries.
- Decision gate
- Is the capability safe, usable and complete enough to test against the outcome?
07Measure, learn and improve
What changed, what failed and what should happen next?
- What happens
- Compare outcomes with the baseline, capture exceptions and decide what to retain, change, stop or address next.
- Output
- Validated learning, system updates and the next decision.
- Decision gate
- Did the outcome materially improve, and what does the evidence support next?
EVIDENCE BEFORE COMMITMENT
The next step depends on what the evidence supports.
The purpose of the audit is to identify the right next action, even when that action is not to build.
The audit is a decision product, not a disguised implementation sale.Prepare
The opportunity appears valuable, but foundations required for reliable implementation are missing.
Verify
The explanation is plausible, but additional evidence or a bounded test is required before a larger commitment.
Proceed
The evidence, readiness and economic value justify building a focused capability.
Stop
The proposed intervention is unlikely to create enough value, addresses the wrong problem or carries unjustified risk.
- No prescription before investigation
- No automation before understanding the work
- No hiding uncertainty behind confident language
- No scope expansion merely because more work is possible
- No activity metrics presented as business outcomes
- No continuing weak work to preserve a retainer
A CONTROLLED CUSTOMER JOURNEY
A focused path from clarity to lasting improvement.
- 01
Forensic Audit
Understand the desired outcome, actual work, most plausible limitation, readiness, uncertainty and correct next decision.
- 02
Focused Capability Design
Define the human-and-AI operating model, required foundations, ownership, controls, measurements and implementation plan.
- 03
Controlled Implementation
Build the capability within clear boundaries, approvals, fallbacks and named responsibility.
- 04
Validation
Compare the actual outcome with the expected result and determine whether the diagnosis survived contact with reality.
- 05
Continuous Intelligence
Monitor outcomes, capture exceptions and strengthen the system as the business and its environment change.
START WITH THE EVIDENCE
Find what is limiting the result before investing in another solution.
The Forensic Audit identifies the outcome you need, how the current system produces it, what is most plausibly limiting it and which controlled next action the evidence supports.
You are not committing to a company-wide transformation. The audit determines whether the right next action is to prepare, verify, proceed or stop.