Your Organization Isn’t Broken. It’s Incoherent.
This is Episode 07 of The Coherence Effect. If you’re new here, the series begins with You Already Know This — it’s the right place to start.
There is a specific kind of exhaustion that comes from fixing things that don’t stay fixed.
You know the work was real. The effort was genuine. The people involved were capable and committed. And six months later you are looking at a version of the same problem wearing a slightly different name, wondering what you missed.
What you missed was probably not the people, not the technology, and not the strategy.
It was the structure underneath all three.
The problem is not what you think it is.
The response to organizational underperformance follows a familiar pattern. A diagnosis gets made. An intervention follows. A program launches. Six months later, the program ends and a version of the original problem is still present — sometimes wearing a different name.
Three diagnoses get reached for most often.
People problem. Wrong people in the wrong seats.
Technology problem. The systems are not keeping up.
Strategy problem. We need to refine the direction.
Partially true, maybe. Root cause, definitely not.
What I have observed across thirty-five years of organizational diagnosis — in manufacturing, regulated industries, government, and professional services — is that most persistent underperformance is not a broken part problem. The people are usually capable. The culture is usually a symptom, not a cause. The strategy is usually not the constraint.
What is failing is the structural environment in which people are trying to execute the strategy — the architecture of how decisions get made, how authority is distributed, how work moves from intent to delivery.
When that architecture is incoherent, it doesn’t matter how talented the team is or how sound the strategy is. The environment consumes the effort before it converts to results. You hire a strong leader into a broken decision structure and the leader either burns out or becomes the problem. You run a culture initiative inside misaligned governance and you get better vibes and the same outcomes. You sharpen the strategy and launch it into an execution infrastructure built for a different version of the company.
The new plan meets the same friction as the old one. Because the friction was never about the plan.
Three dimensions. One system.
Every organization operates across three structural dimensions simultaneously. Not sequentially. As co-equals.
Intent is your strategic direction — what leadership has decided to pursue, why, and in what sequence. Most organizations invest heavily here. Off-sites, frameworks, OKRs, vision documents. The intent dimension is usually the most developed. It is also the one most likely to be treated as if it operates alone.
Execution is the structural apparatus through which intent becomes action — decision rights, authority architecture, accountability assignments, approval structures. Not effort. Not culture. Structure. This is where most organizations are thinnest, and where the gap between what leadership decided and what the organization actually does lives.
Capability is your delivery infrastructure — the build-buy-partner model, vendor relationships, and operational systems that must ultimately produce what the strategy declared. Not a support function. A co-equal structural dimension with its own design requirements that most organizations have never formally assessed.
Here is the part most frameworks miss.
These three are not sequential. You do not complete intent and then move to execution and then build capability. They are mutually constitutive — each one is defined by its relationship to the other two. The moment any one is treated as subordinate or secondary, the system produces friction that looks, from the outside, like a hundred different problems.
It isn’t a hundred different problems. It is one problem, showing up everywhere at once.
What subordination actually looks like.
When execution is subordinated to intent — when leadership treats strategy as the serious work and execution as implementation detail — decision rights never get clarified. The assumption is that clarity of intent will produce clarity of action. It won’t. It produces activity, which is a different thing entirely.
When capability is treated as a function of execution — when the organization believes better process will close a delivery gap that is actually a model mismatch — you spend months solving the wrong problem with extraordinary discipline. You cannot execute your way out of a capability problem.
When intent is disconnected from capability — when the strategy declares commitments that the delivery infrastructure cannot support — the gap doesn’t show up on the reports that are supposed to catch it. It shows up six months later as a project that quietly died, a vendor relationship that never quite delivered, and an initiative that launched well and landed nowhere.
Here is what coherence failure looks like from the inside.
The meeting that ends with another meeting scheduled. Nobody in the room had the authority to end it.
The initiative that launched with strong executive support and quietly died six months later. Nobody owned it below the level that launched it.
The vendor that keeps underdelivering. The contract gets renegotiated. The problem continues. Because the contract was never the issue — the model was.
The reorganization that reorganized the boxes without changing how authority actually flows. The new org chart looks different. The operating reality does not.
If any of this sounds familiar — keep reading.
Four patterns you will recognize immediately.
There are eight specific ways coherence failure presents. Four of them are the most common in mid-market organizations. The remaining four — and the cases that illustrate all eight — are what the next eight episodes are for.
1. Your decisions live two levels above where they should. Strategy is clear at the top. Below that, nobody has been given the authority to act on it. Decisions escalate. Initiatives drift. Work happens — but not on the right things. The language that gives it away: “I’ll need to check with [senior leader] on that.” That phrase is not a cultural artifact. It is the behavioral expression of an authority architecture that was never designed.
2. Your improvement programs keep failing. Not because the programs are wrong. Because the same intervention is being applied to different structural problems. Vendor issues addressed with contract renegotiation when the model is wrong. Technology investment made to close gaps that are actually decision rights failures. Process improvement applied to what is actually a governance problem. Each program treats a symptom. The structural source remains.
3. Your capability model was designed for the organization you were — not the one you are. The vendor relationships, technology platforms, and delivery infrastructure that exist today were built for a previous version of your organization. Nobody has formally assessed whether they still match your current strategic requirements. They usually do not. And the gap doesn’t become visible until a growth inflection, an acquisition, or a strategic pivot forces the question. By then it is expensive.
4. Your org chart and your operating reality are two different things. The authority is documented. It just does not exist in practice. Decisions that nominally belong to directors are actually made by executives. Accountability that nominally sits with VPs dissipates into committee when something goes wrong. The tell: someone in your organization pulls every new hire aside in their first week to explain how things actually work. When that conversation is happening routinely, your organization is being held together by specific people — not by design. And the day those people leave is the day the fragility becomes visible.
The diagnostic question that reveals it fastest.
Before the instruments, before the assessment, before any structured conversation — there is one question that exposes alignment failure more reliably than almost anything else.
When something goes wrong in your organization, where does the conversation go?
In a coherent organization it goes to the structural cause. Decision rights. Ownership gaps. Sequencing failures. The conversation is diagnostic and forward-looking.
In an incoherent organization it goes to the nearest available explanation — a vendor, a team, a market condition. The explanation changes with every quarter. The underlying structure that produced the failure remains untouched.
That pattern is not a culture problem. It is not a leadership personality problem. It is a structural alignment problem. And it has a specific source in one of the three dimensions — or in the relationship between them.
Why the standard fixes do not hold.
Better communication. Stronger accountability. Clearer metrics. Leadership development. These are behavioral interventions applied to structural problems. They improve things temporarily. They do not hold — because the structural source of the dysfunction remains intact after the intervention ends.
Coordination improves until the next cross-functional priority creates a conflict the structure cannot resolve.
Accountability improves until the next reorganization creates new ambiguities the measurement system cannot capture.
Trust improves until the next leadership transition reveals that the shared understanding was being carried by people, not embedded in structure.
The corrective that holds is structural. It targets the specific failure mode — not the general symptom. That specificity is only possible once the failure mode has been correctly named.
There are eight of them. The next eight episodes locate each one — with a real case, a plain-language analogy that makes the pattern recognizable before it’s been named, and the specific structural question each one demands.
The question worth ten minutes of your time.
Think about the last significant problem your organization tried to fix. What was the diagnosis? And if the fix didn’t fully take, what was offered as the explanation?
Most of the time, the answer is a version of one of the three wrong diagnoses: we need better people, we need a stronger culture, we need a clearer strategy.
If you’ve heard that answer more than once about the same underlying problem — you’re probably looking at something structural.
Structural problems have names.
And the corrective, applied to the structural source rather than the behavioral symptom, is the one that actually holds.
If you’re already recognizing the pattern in your own organization — the OCI Diagnostic is the structured assessment that identifies which failure mode is present and what it’s costing. Start the conversation here.
The Coherence Effect — Series Guide
Phase One — Human Foundation
01 · You Already Know This. You Just Haven’t Named It Yet.
02 · The Piano Man
03 · The Porch
04 · No Deck Required
05 · Why I Built This
Phase Two — The Framework
06 · Your Diagnosis Is Probably Wrong
07 · Your Organization Isn’t Broken. It’s Incoherent.
Phase Three — The Case Studies
08 · Type I: Intent Subordination — The Boeing Story
09 · Type I: The Circuit Nobody Dropped
10 · Type II: Dimension Collapse — The Peloton Story
11 · Type III: Capability Inversion — The Haribo Story
12 · Types VI & VIII: The $42M That Was Never Missing
13 · Type IV: We Don’t Do That
14 · Type V: Authority Diffusion
15 · Type VII: Structural Theater
Phase Four — Series Close
16 · What Comes After the Diagnosis
PrecisionPath Consulting works with mid-market leadership teams who know something is wrong but can’t locate exactly where. The OCI Diagnostic identifies which of the eight coherence failure modes are costing your organization performance — and what to do about it.
Kent Hallmann is the founder of PrecisionPath Consulting. Thirty-five years diagnosing organizational friction at Deloitte, KPMG, Wipro, and SAP. Fixed fee. Defined scope. Senior practitioner on every engagement — no handoffs, no substitutes.
The Coherence Problem research: Zenodo https://doi.org/10.5281/zenodo.19456590 · SSRN http://ssrn.com/abstract=6479301
Next episode: The first of the eight failure modes. A case most people will recognize. And an everyday analogy that makes the organizational pattern unmistakable before it has been named.