Stability mistaken for health
Nothing is burning, so nothing gets reopened.
Who we helpEnterprise
Nobody is in crisis, which is exactly why the loss compounds quietly.
The system is mature and the dysfunction is expensive precisely because it is stable. No burning platform demands attention, so the loss keeps compounding for years before anyone puts a price on it.
Stage read
Stable, and quietly expensive.
The loss has no single owner
It is distributed across functions and quarterly reporting.
Nobody is incentivised to look
Raising it costs more locally than leaving it alone.
Definitions differ by region
The same metric is calculated three ways and reported as one.
Process outlived its reason
Steps survive because removing one needs somebody to sign for it.
Loss thin enough to vanish
Stability and dysfunction are not opposites at this stage.
Nothing is burning, so nothing gets reopened. The cost is absorbed into next year’s baseline rather than flagged as a loss.
The symptom is reported at the surface. The cause sits underneath it.
Stability read as health
Nothing is burning, so nothing gets reopened.
Surface · what gets reportedThe loss has no single owner
It is distributed across functions and absorbed by quarterly reporting.
Structure · what produces itQuestioning it carries career risk
Raising a mature process costs more locally than leaving it alone.
System · where it breaksCost compounds into the baseline
It is absorbed into next year’s plan rather than flagged as a loss.
Consequence · what it costsCause and consequence rarely surface in the same place.
What it looks for here
Find the loss hidden inside a stable operating model.
The diagnostic tests all six dysfunction families and follows the evidence without assuming which financial consequence matters most. It looks for losses created by functional silos, duplicated systems, competing KPIs, portfolio complexity and legacy governance, where every local process can appear to work while the whole commercial system underperforms.
- Commercial leadership across regions
- Operations, finance and portfolio owners
- Multi-year trends
- Regional definitions
- Governance forums
- Duplicated workflows
Stability with no burning platform changes how the strain presents.
What the next stage demands
Someone has to own a loss that is spread across functions.
Nothing is burning, which is exactly the problem. What this stage demands is the authority and the evidence to reopen something that looks stable.
A named owner for a distributed loss
A cost absorbed across several functions and smoothed by quarterly reporting has no owner, and unowned losses do not get fixed.
Evidence strong enough to reopen a settled question
Questioning a stable system carries career risk. The only thing that lowers it is evidence the organisation cannot easily dismiss.
Coordination cost made visible
At this size the expensive thing is rarely a broken process. It is the volume of work spent keeping several working processes aligned.
Permission to examine what is not failing
Stability read as health is the mechanism that lets a loss compound for years. Examining it has to be a routine, not an escalation.
What happens next
Three ways in, depending on what the evidence already says.
Executive Workshop
Three hours with the people who can change the system. One condition named, in writing, before any evidence is gathered.
Explore the Workshop →Diagnosis
Interviews, the records you already produce and your own rates. What is breaking, what it costs, what to change first.
Explore the Diagnosis →Strain Check
Ten questions, two minutes. A first read on which part of your commercial system is carrying the most strain.
Take the Strain Check → FAQ
Before you assume stable means fine.
Our numbers are healthy, why would we need a diagnostic?
Healthy numbers tell you the system is not failing. They do not tell you what it would produce if the dysfunction sitting underneath it were removed, which is a different question with its own answer.
We have run internal audits before, how is this different?
An internal audit is usually run by people inside the system being audited, which limits what gets questioned. The diagnostic is run by someone outside it, using role-based interviews across the organisation rather than a self-review.
How disruptive is this to a large, established organisation?
The interview list and scope are agreed with you before anything starts, and the engagement is designed to run alongside normal operations rather than interrupt them.
Who typically sponsors this internally at enterprise scale?
Usually a commercial or revenue leader with visibility across functions, since the loss at this stage rarely sits inside a single team's remit and needs someone able to act across the boundary.
Get started
Nothing looks broken. That is exactly why the loss is worth pricing.
Use 30 minutes to define the operating question, test what evidence exists and decide whether Kihon has a role at all. No scope is proposed before that is clear.
Discuss the operating problem