EVERYDAY ANALOGY Signing up for a marathon before you can run a 5K isn’t inspiring — it’s a setup for injury and withdrawal. The race is real. The training foundation isn’t there yet. You can’t build the base and run the race at the same time and expect either to go well. Organizations do this with every major system implementation that assumes capabilities the organization hasn’t built yet.

In October 2018, Haribo — the German confectionery company that has been making gummy bears since 1920 — began converting sixteen candy factories across ten countries to SAP S/4HANA. Some of those factories were running systems from the 1980s. The need to modernize was real. The strategic case for consolidation was legitimate. The intent was sound.

Within weeks of go-live, the company couldn’t track raw materials or inventory across its own manufacturing network. Shelves went bare at supermarkets across Germany. Sales of the Gold Bear — Haribo’s signature product and the reason most people have ever heard of the company — dropped 25 percent in 2018.

The post-mortem produced a familiar list of causes: poor testing methodology, insufficient executive engagement, inadequate planning, processes incompatible with the software. All of it true. None of it the actual diagnosis.

Here is what the post-mortem missed.

Haribo had been operating sixteen factories in ten countries, each running separate regional systems, some decades old, managing more than 1,500 product variants across a complex multi-country manufacturing and distribution network. That is not a simple operating environment. It carries high operational complexity, heterogeneous process legacy, and significant data integrity risk across every facility simultaneously.

SAP S/4HANA is a capable platform. It was never built as an out-of-the-box fit for Haribo’s specific operational complexity. The assessment that should have happened before vendor selection wasn’t a question of whether SAP was good software. It was a question of whether the build-buy-partner model Haribo was about to commit to — a single platform, simultaneous multi-country deployment, on a compressed timeline — was matched to the actual risk and complexity of what they were delivering.

It wasn’t. The platform was chosen because it was the industry standard, and Haribo was among the first companies in Germany to roll out the full S/4HANA feature set at once. The capability model was selected on the basis of technology reputation and competitive positioning — not on a rigorous assessment of whether that model could deliver in this specific environment against this specific risk profile.

This is what I call Type III coherence failure — Capability Inversion. The organization treats delivery capability as a function of technology selection rather than as a co-equal dimension with its own structural requirements. The assumption is that if you choose the right platform, capability follows. It doesn’t. Capability asks whether your build-buy-partner model is matched to your actual operational complexity and your actual risk tolerance. When that question is never asked — when capability is subordinated to the strategy layer’s preference for a particular solution — you cannot execute your way out of the mismatch. More discipline, better testing, stronger governance: none of it addresses a model that was wrong before the first line of configuration was written.

The diagnostic signature of Type III failure is subtle and consistent.

The organization experiences delivery failures it can’t explain through performance metrics. Vendors are underperforming, but the data doesn’t show why. Technology investments aren’t returning expected value, but the gap can’t be located in any specific failure of execution. The same problems recur in different forms across different vendor relationships or platform implementations, and each recurrence gets treated as a new execution problem rather than as evidence of a structural mismatch in the capability model.

The corrective response is always more rigor — better contracts, tighter SLAs, stronger governance, more comprehensive testing. These interventions aren’t wrong. They’re applied to the wrong problem. When the capability model is mismatched to the operational environment, execution discipline can’t close the gap. You need a different model, not a better-run version of the wrong one.

Haribo’s problem wasn’t that their testing was inadequate, though it was. Their problem was that they had selected a deployment model — simultaneous multi-country go-live with a platform still proving its own implementation maturity — that was structurally misaligned with the complexity of their manufacturing environment. No amount of testing would have resolved that mismatch. The right corrective would have been a different sequencing of the deployment: a pilot in a single facility, an honest assessment of whether the S/4HANA implementation ecosystem in 2018 had the maturity to handle what Haribo was asking of it. Those are capability model questions, not execution questions.

Industry post-mortems of the Haribo failure converged on a similar root cause: Haribo’s international manufacturing and supply chain expansion had outpaced what its SAP transformation was actually built to support. That’s a model mismatch diagnosis. The transformation was never matched to the future-state operating model. The platform was selected before the operating model was defined.

I have spent thirty years working with organizations on exactly this failure mode — often in circumstances where the vendor relationship had already been signed and the model mismatch was only becoming visible through delivery underperformance. The conversation in those circumstances is always the same: the client wants to know how to fix the vendor. Better governance. Tighter accountability. Escalation protocols.

The honest answer is that you cannot govern your way out of a model mismatch. The vendor is underdelivering because they’re being asked to deliver something the engagement model was never designed to support. The conversation that should have happened before contract execution — what does our operational complexity actually require, and is this model capable of meeting that requirement — is now a much more expensive conversation to have.

The organizations that avoid this failure mode do one thing differently. They treat the capability assessment as a separate, prior step from vendor selection. Before any platform is named, before any vendor is invited to present, they ask: what are we actually trying to deliver, what does our operational environment require, and what build-buy-partner model is matched to that requirement given our actual risk tolerance? Only after that question is answered does vendor selection begin.

That sequence feels slow. It is significantly faster than the alternative.

The question for you: think about the last significant vendor relationship or technology investment your organization made. Was the capability model — the build-buy-partner decision — assessed independently of the platform selection? Did someone, before any vendor was in the room, map your operational complexity against the delivery model options and ask whether there was a match? Or did the platform selection happen first, driven by industry reputation or competitive benchmarking, with the assumption that capability would follow from the right choice of technology?

If the answer is the second — if the model was never independently assessed — the question isn’t whether you have a capability problem. The question is when it becomes visible enough to name.

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 II: Dimension Collapse — The Peloton Story

10 · Type III: Capability Inversion — The Haribo Story

11 · Types VI & VIII: The $42M That Was Never Missing

12 · Type IV: We Don’t Do That

13 · Type V: Authority Diffusion

14 · Type VII: Structural Theater

Phase Four — Series Close

15 · What Comes After the Diagnosis

The OCI Diagnostic identifies which of the three structural dimensions is being treated as less than co-equal in your organization — and what that subordination is costing you per quarter. Start the conversation here.

The full research: https://doi.org/10.5281/zenodo.19456590

Kent Hallmann is the founder of PrecisionPath Consulting — the diagnostic instrument for the Coherence Problem. 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.

Next episode: Type III — Capability Inversion. An analogy about signing up for something before you’re ready for it. And a case study about what happens when a ninety-eight-year-old company runs a technology implementation that the technology itself wasn’t ready for either.Where is your organization carrying a Capability Inversion right now?

The young professional who put everything into the career.

Long hours, weekend work, every promotion taken, every opportunity chased. The income was real and the family felt it — better house, better vacations, better schools. But the marriage got whatever was left after the job was done, which was rarely much. The kids grew up with a provider who was mostly a guest. By the time the career leveled out and he had time to look around, the distance in the room didn’t close the way the bank account had.

He hadn’t neglected his family out of selfishness. He’d just fed one dimension of his life so completely that the others ran on fumes for too long.

That is Dimension Collapse. It does not require bad intent. It does not require negligence. It requires only that one dimension receives so much sustained attention that the others quietly starve — and that the organization has no structural mechanism for noticing what it is trading away until the trade has already been made.

Peloton made exactly that trade. On a scale that cost them billions of dollars and very nearly the company itself.

The Peloton Case — Dimension Collapse at Scale

On a September 2020 earnings call, a financial analyst asked Peloton’s CEO John Foley a direct question. Peloton had been riding an extraordinary pandemic-driven demand surge. Gyms were closed. People were buying exercise equipment. The question was straightforward: how was Peloton managing the risk that demand would normalize when pandemic restrictions lifted?

Foley’s answer: “We feel like there’s such a massive opportunity that we need to invest heavily in the supply chain for years and years to maintain it. When you say ‘normalize coming out of Covid’ — we don’t see that.”

Eighteen months later, Peloton had 500 days of inventory in warehouses. Hardware sales were half what they had been the previous year. Hardware inventory was double. The $420 million Precor acquisition — one of America’s largest exercise equipment manufacturers — was a sunk cost. The planned $400 million Ohio factory had been shelved. The stock had fallen more than 90% from its peak. Net losses for fiscal year 2022 reached $2.83 billion — more than the company had lost in its previous five years combined.

The analysis that followed focused almost entirely on the demand forecasting error. Leadership had mistaken a temporary surge for a permanent trend. They hadn’t read the market correctly.

That analysis is accurate. It is also incomplete.

The demand forecasting error was a symptom. The structural failure that produced it was something different.

What the post-mortem missed.

Peloton’s vertical integration strategy was not a bad strategy. Controlling your manufacturing, ensuring quality, protecting margins — these are legitimate competitive objectives, particularly for a premium brand selling $4,000 exercise equipment. The intent was defensible. The capability investment — the Precor acquisition, the Ohio facility — was a coherent expression of that intent.

The failure was not in the strategy or in the capability investment. The failure was in the collapse of the boundary between them.

Peloton’s executive team had no structural mechanism for translating demand signals into manufacturing decisions. When analysts asked the question directly on that September 2020 earnings call, the answer revealed that nobody in the organization had authority or mandate to evaluate the capability investment against the execution reality. The decision to invest $820 million in manufacturing infrastructure was made from the intent layer — from a belief about where the market was going — without an execution structure that could pressure-test that belief against the operational signals coming from the market.

Every problem was addressed through capability investment. Supply chain delays — invest in domestic manufacturing. Delivery windows extending — charter aircraft, expedite freight. Quality issues — acquire a manufacturer. The organization’s single response to any signal of misalignment was to spend more on capability. The possibility that the problem might be in the execution architecture itself — in the decision-making structure, in the accountability mechanisms, in the absence of anyone with the authority to say stop — was structurally invisible.

That is Dimension Collapse. Not a failure of strategy. Not a failure of capability. A failure of the boundary between them — the collapse of the execution layer that should have been translating signals into decisions independent of the intent layer’s optimism.

CFO Jill Woodworth’s admission, eleven months after the Precor investment, was precise: “It is clear that we underestimated the reopening impact on our company and the overall industry.” That sentence describes a forecasting failure. What it doesn’t describe is the structural reason the forecast went unchallenged. Organizations with coherent execution structures have mechanisms for pressure-testing leadership assumptions before they become billion-dollar commitments. Peloton had no such mechanism because it had no independent execution layer — only a strategy layer and a capability layer, with the assumption that the two would naturally align.

The useful contrast.

Clorox provides it. Their products experienced the same pandemic demand surge. Their leadership team increased production but did not commit hundreds of millions of dollars to new facilities. The decision was made by people who had the information, the authority, and the structural mandate to evaluate short-term demand against long-term capacity risk. The dimensions were in right relationship. The signal was received and acted on correctly.

The difference between Peloton and Clorox in 2020 was not strategic intelligence. Both leadership teams understood that pandemic demand was abnormal. The difference was structural. Clorox had an execution layer that could translate the signal into a decision. Peloton had collapsed that layer into its strategy, and had no mechanism to hear what its own data was telling it.

The diagnostic signature.

Dimension Collapse is recognizable in any organization where the same intervention keeps getting applied to different problems. Revenue declines — invest in sales capacity. Delivery fails — invest in logistics. Platform underperforms — invest in technology. Each investment made from the intent layer, without an execution layer asking whether the investment is matched to the actual source of the problem.

The question for any executive reading this is about the boundary between your intent and your capability.

When your organization makes a significant investment — in technology, in infrastructure, in a vendor relationship, in an acquisition — who has the authority to pressure-test the assumption behind the decision before it becomes a commitment? Is there an execution layer that is structurally independent of the strategy layer, capable of asking the question that the strategy layer cannot ask about itself?

If the answer is that strategy and execution are the same conversation, handled by the same people, evaluated against the same assumptions — the dimensions have already collapsed. The only question is which signal you will fail to receive before it matters.

The career that consumed everything else looked like ambition for a long time. So did Peloton’s growth story. Both were Dimension Collapse. Both announced themselves only when the cost of feeding one dimension at the expense of the others became impossible to ignore.

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 II: Dimension Collapse — The Peloton Story

10 · Type III: Capability Inversion — The Haribo Story

11 · Types VI & VIII: The $42M That Was Never Missing

12 · Type IV: We Don’t Do That

13 · Type V: Authority Diffusion

14 · Type VII: Structural Theater

Phase Four — Series Close

15 · What Comes After the Diagnosis

The OCI Diagnostic identifies which of the three structural dimensions is being treated as less than co-equal in your organization — and what that subordination is costing you per quarter. Start the conversation here.

The full research: https://doi.org/10.5281/zenodo.19456590

Next episode: Type III — Capability Inversion. An analogy about signing up for something before you’re ready for it. And a case study about what happens when a ninety-eight-year-old company runs a technology implementation that the technology itself wasn’t ready for either.

You’ve decided to eat better. You mean it. You’ve even told people about it.

Then someone brings donuts to the meeting and you take one because it felt rude not to.

The intent was real. It just wasn’t strong enough to hold when something easier showed up. There was no structure underneath the decision — no rule, no commitment architecture, nothing that made the stated priority authoritative when pressure arrived. So the priority lost.

Organizations do this constantly. The stated priority is genuine right up until the moment it costs something. When it costs something, whatever has structural authority wins. And in most organizations, nobody has ever explicitly designed what that is.

That is Intent Subordination. It presents itself in boardrooms and in break rooms, in billion-dollar programs and in thirty-day operational crises. The scale changes. The structural failure is identical.

The Boeing Case — Intent Subordination at Maximum Consequence

Boeing’s 737 MAX program is the most consequential manufacturing case study of the last twenty years: two crashes, three hundred and forty-six deaths, a twenty-month grounding, twenty billion dollars in documented losses. The technical story is MCAS, the flight control system that misfired in both crashes. The organizational story is older. Facing Airbus’s A320neo, Boeing chose to update the existing 737 rather than design a new aircraft — a sound, fast commercial call. What was never built was the structure to carry that intent through the organization: who had authority over which decisions when technical reality pushed back against the commercial timeline.

The 1997 McDonnell Douglas merger had shifted Boeing’s center of gravity from engineering to finance — a shift a 238-page congressional investigation later traced directly to the outcome. Engineers raised concerns about MCAS; a Boeing Authorized Representative flagged them internally in 2016. The concerns never reached the FAA. The people closest to the technical reality had knowledge and no mandate; the people with mandate had no proximate knowledge. That gap is where three hundred and forty-six people were lost — and it’s the same diagnostic signature every time: after a failure, the conversation goes backward to a scapegoat instead of forward to who actually had the authority to decide. Boeing’s corrective isn’t a software patch. It’s decision rights redesigned so authority sits where the knowledge is.

The Circuit Nobody Dropped — Intent Subordination at Ground Level

The Boeing case operates at a scale most executives will never encounter. What follows is the same failure mode in a situation most of them have lived.

The CEO of a newly divested food processing division had one job: get the organization off the parent company’s ERP and infrastructure within six months or start paying penalties large enough to fundamentally alter the divestiture’s economics. The clock was running.

With thirty days left, both networks went down.

Not dark. But significantly enough that production operations on both sides — parent company and newco simultaneously — were impaired. And in food processing, impaired production means product not moving, orders not filling, and a leadership team watching the penalty threshold approach while technical teams escalated, scheduled meetings, and prepared slide decks.

Seventy-two hours passed. Nobody had fixed the problem.

The institutional response had kicked in within hours. Vendors called. Escalation paths activated. The structured crisis management that large organizations deploy to demonstrate that a situation is being taken seriously — status calls, leadership visibility, meetings generating more meetings — was fully operational.

I watched it for a while and realized that what I was watching was an organization responding to the appearance of the problem rather than the problem itself. Escalation theater has its own momentum. It is designed to manage the organizational anxiety a crisis produces, not to solve the crisis.

I found one of the parent company’s network leads — not a manager, not someone whose job was to represent the organization’s position. Someone who actually understood how the network was designed and how it was supposed to work. I asked him to draw it out for me. No theatre, just draw the network as you understand it.

He did.

There it was. A routing loop. A circuit still connected that should have been dropped by the telecommunications provider when the newco network came up. The telco had never completed the disconnection. Every packet that should have been routing cleanly between the two networks was cycling through a connection that shouldn’t be there.

Twenty minutes. One whiteboard. One network lead who had the answer the moment someone asked him the right question in the right way.

The problem was fixed. The deadline was met. No penalties were paid.

And then the blame started.

Some people were relieved the solution had been that straightforward. Others needed to find someone responsible for the seventy-two hours. The reflex — in the moment when the organization should have simply moved forward — was to look backward and find someone to hold.

That reflex is not malicious. It is structural. When nobody owns the outcome, everybody deflects the consequence. Blame is what happens when accountability and authority are not matched — when people are held responsible for results they were never given the structural authority to produce.

The network lead who drew the routing loop on the whiteboard had not been given authority to fix it unilaterally. Knowledge without mandate. The leaders managing the crisis had mandate without localized knowledge. The gap between those two was where seventy-two hours went.

The Pattern Across Both Cases

Boeing. A food processing divestiture. One costs hundreds of lives and twenty billion dollars. One costs seventy-two hours and a penalty threshold that nearly triggered.

The structural failure is identical in both.

The person who knew could not reach the person who could act. The escalation architecture — designed to protect the organization from incomplete information — was the mechanism that kept the answer away from the decision. The stated priorities were real. When pressure arrived, whatever had structural authority won.

In your organization: when a crisis hits, does the person with the relevant knowledge have a direct path to the person with the authority to act on it — or does that knowledge travel through a structure that will reshape it before it arrives?

If the honest answer is the second, the routing loop is already drawn on someone’s whiteboard. The question is how many hours — or years — it will take for someone to ask them to show it to you.

The OCI Diagnostic identifies where decision authority and operational knowledge are misaligned in your organization — and what it is costing you per quarter. Start the conversation here.

The full research: https://doi.org/10.5281/zenodo.19456590

Next episode: Type II — Dimension Collapse. An analogy about a choice most people have made. And a case study about what happens when an organization optimizes so hard in one direction that everything else stops mattering — until it’s too late.

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.

1. People problem. Wrong people in the wrong seats.

2. Technology problem. The systems are not keeping up.

3. 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.

When something isn’t working inside an organization, the response follows a familiar pattern.

1. A diagnosis gets made.

2. An intervention follows.

3. A program launches.

Six months later, the program ends and a version of the original problem is still present — sometimes wearing a different name.

I have watched capable leadership teams cycle through this loop for years. They weren’t careless. The diagnosis was pointed at the wrong level.

The interventions were reasonable responses to what the symptoms looked like. They just weren’t responses to what was actually causing the symptoms. And until the right level is identified — structural rather than behavioral — the loop continues. New program, same underlying source, same result. Wash, rinse and repeat.

The wrong level.

When something breaks, most organizations reach for one of three explanations.

• People problem: wrong leaders in the wrong seats.

• Technology problem: the systems aren’t keeping up.

• Strategy problem: we need to refine the direction.

Each of these may be partially true. None of them is the root cause.

What I have found, consistently, across thirty-five years of working inside these problems, is that the real constraint is almost never the one being named. The fix gets applied. The loop resumes. And the next time something breaks, the same three explanations are waiting.

The reason the fix doesn’t hold is not that the people executing it weren’t serious. It’s that behavioral interventions do not fix structural problems. The source stays intact. The symptom returns.

Eight patterns. One framework.

There are eight specific ways this structural failure presents itself. Eight patterns I have seen repeatedly — in manufacturing, regulated industries, public sector organizations, and mid-market companies at every stage of growth. Each one has a name. Each one has a specific signature. And each one requires a different intervention.

Some of them look like leadership problems until you trace them to their source. Some of them look like people problems until you watch the same dynamic repeat with entirely different people. Some of them are invisible until something expensive fails — and then they’re the only thing in the room.

The eight failure modes are not a theory. They are a diagnostic. They are what I look for when an organization calls me because the obvious interventions have already been tried and the problem is still there.

Over the next nine episodes I’m going to take each one apart. Not in the abstract. With real cases — organizations you’ll recognize — and with the specific structural question each one demands.

But before the cases, the framework has to be in place. That’s the job of the next episode.

What this series is for.

By the end of this series my goal is straightforward: I want you to be able to look at your own organization — or one you work inside — and identify not just that something is wrong, but specifically what kind of wrong it is. That precision matters. Because you cannot treat a structural failure with a culture initiative. You cannot solve an authority problem by changing the strategy. The intervention has to match the diagnosis.

That’s what the next eight weeks are for.

A question worth contemplating before we start.

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 to that second question 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. The next episode names the framework.

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 · Something Was Being Missed

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

After thirty-five years of watching the same cycle repeat, I knew something was being missed.

In capable organizations with smart leadership, real resources, and genuine intent to do things differently this time. Repeatedly, consistently - not occasionally.

The cycle was always some variation of the same story.

A new technology platform promised to transform operations. Or a structural reorganization was going to fix the coordination failures. Or a talent infusion — dozens of new hires with the right credentials — was going to bring the capability the organization had been lacking. The announcements were confident. The investment was real. The commitment from leadership was visible and, as far as I could tell, sincere.

And then, within six to nine months, the layoffs would come.

Because the organization had chased the solution before it understood the problem — and the gap between what was promised and what was delivered had become too expensive to sustain. The headcount that had been added to support the transformation became the cost reduction that followed it.

Then the hiring would start again.

I watched this cycle repeat across industries, across decades, across organizations that had every reason to break it and somehow never did. Manufacturing. Regulated industries. Professional services. The specific technology changed. The specific reorganization changed. The specific people changed. The outcome did not.

What I felt watching it was not frustration with the organizations or the leaders. Most of them were trying. Most of them believed in what they were doing.

What I felt was that something structural was being missed. That underneath the visible cycle — the investment, the promise, the disappointment, the reset — there were forces in discord. Something in the way these organizations were constituted was preventing them from sustaining the progress they were capable of making.

As the years accumulated, I watched something else happen that troubled me more than the cycle itself.

Values fell away to earnings targets. Principles fell away to press releases. The organizations that had once been willing to ask hard structural questions about themselves became organizations that managed the appearance of progress rather than the reality of it. The quarterly result became the organizing principle. Everything else — the people, the capability, the structural integrity of the organization — became a variable to be managed against it.

The cycle accelerated. The resets became more frequent. The human cost became more visible.

And still the same solutions were being proposed. More technology. Better processes. Different people. As if the problem had never been diagnosed correctly in the first place.

I started the research that became the Coherence Problem because I believed it had not been.

The dimensions every organization requires had each been studied in isolation. What had never been adequately named was the structural logic of what happens when they drift apart — and why every corrective organizations reach for consistently targets the wrong level of the problem.

The Coherence Problem is an attempt to provide that structural vocabulary. A diagnostic to use; not a framework to admire. A way of naming specifically what is out of balance — which failure mode is present, what it costs, and what the corrective is — so that organizations can stop cycling through solutions that address symptoms and start addressing sources.

Thirty-five years of watching the cycle convinced me the problem was real, structural, and solvable.

The vocabulary to solve it had been sitting in an unlikely place for sixteen centuries.

That is the story this research tells.

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 · Something Was Being Missed

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

Episode 04 of The Coherence Effect. If you are just joining — the series begins with You Already Know This. It builds

I want to tell you about a meeting I walked into in the early 2000s — because what happened there has shaped how I think about leadership communication ever since.

The setup: I was on a large ERP implementation for one of Japan’s largest electronics manufacturers. One week before go-live, we learned the hosting provider had not completed their compliance requirements. Not close. A real gap. Two weeks of work remaining on a one-week clock.

The client’s executives were flying in from Tokyo. My boss called. Be on a plane tomorrow.

New York.

I flew. What I walked into was a meeting already in progress — three senior executives from our side seated across from four executives who had made the journey from Japan.

I was the lowest-ranking person in the room. I took my seat and watched.

Our senior executives had come prepared. Agendas. Decks. The kind of structured presentation built to walk a client through a difficult situation in the most professionally managed way possible — framing the problem, documenting what had gone right, charting a path forward.

It was competent work. I don’t doubt it was well-intentioned. But as the presentation continued, something was happening on the other side of the table.

The Japanese executives were still seated. Still formally composed. Still observing every protocol the situation required.

But they were leaving. Not the room — their attention. The careful, alert presence they had brought into that meeting was quietly withdrawing. What was replacing it was something more polite and more distant: the expression of people who have concluded, without saying so, that what they are watching is not what they came to see.

There was a pause in the presentation.

My boss spoke. He suggested, quietly but clearly, that I address the situation.

I had not been prepared for this. No slides. No prepared remarks. No strategy. I was the lowest-ranking person in the room and the assumption — my assumption — was that this conversation belonged to the people above me.

What I had, in that moment, was the truth. And my commitment to fix the problem.

I want to be honest about what I was aware of. This was a real CLM (career limiting move) if it went wrong. The people across the table were powerful. The people beside me were my superiors. There was no deck to retreat behind, no structure that would slow the arrival of any difficult moment.

So I gave them the only thing I actually had.

I acknowledged the problem; the actual situation. The compliance gap, what it meant for the timeline, and how long it would take to resolve.

I described what was already being done. Specifically and without embellishment.

And then I looked them in the face — directly, not at my notes, not at the table — and I gave them my word as a professional that this would be resolved within 72 hours.

Then I stopped talking. Something I did not expect happened. They stood up.

They thanked me. Formally, sincerely, in the way that Japanese business culture expresses genuine acknowledgment. And they said — clearly, without qualification — that they were very comfortable this was no longer an issue.

The meeting concluded. They made their long journey back to Japan. With, I believe, some peace of mind they had not walked in with.

I have spent a long time thinking about what changed in that room.

It was not the information. The facts were the same before and after I spoke. What changed was the quality of the signal.

Those executives had not flown from Tokyo because they lacked information. They had flown because they needed to take the measure of the people responsible for the outcome. The presentation they received told them nothing they needed to know. The conversation that followed told them everything.

The armor that protects the presenter also prevents the message from landing. When you are in full armor, the person across the table cannot see you. They can evaluate the narrative. But they cannot do the one thing they most need to do in a moment like that — assess whether the human being in front of them is someone they can trust.

That question has only one answer. And the answer cannot be prepared in advance.

The engagement survived the compliance delay. The program delivered what it was supposed to deliver.

But that is not the point. The point is what those executives took back to Japan. Not a plan, framework or deck.

A judgment: I met the person responsible for this, I heard their commitment directly, and I believed them.

That judgment — not the slide, not the narrative — was what kept the relationship intact through the weeks that followed.

I had nothing in that room except what I actually knew and what I was genuinely willing to promise.

It turned out that was the only thing anyone was waiting for.

The structural version of this problem — organizations full of capable people communicating managed versions of reality to each other until the gap between what is being said and what is actually true becomes too expensive to sustain — is one of the most consistent patterns I have diagnosed across thirty-five years of organizational work.

When the presentation replaces the truth often enough, the organization loses the ability to act on what is actually happening. The people closest to the problem stop surfacing what they know because they have learned what happens to it. The people at the top keep receiving polished versions of a reality that no longer exists.

That is not a communication problem.

It is a structural one.

And it is exactly what the Signal Check is designed to surface — the specific places in your organization where the gap between what is being presented and what is actually true is widest.

Five minutes. Free. Instant output.

www.precisionpathllc.com/how/signal

Next episode: Why I Built This — the thirty-five years behind the framework, and what I had to become before I understood what I was actually trying to build.

Kent Hallmann is the founder of PrecisionPath Consulting — the diagnostic instrument for the Coherence Problem. Fixed fee. Defined scope. Senior practitioner on every engagement — no handoffs, no substitutes.

Zenodo: https://doi.org/10.5281/zenodo.19456590 · SSRN: http://ssrn.com/abstract=6479301

I’d like to tell you about a phone call I received when I was fourteen years old.

It was 1976. I was a freshman at Germantown High in Memphis, Tennessee. Two weeks into two-a-day football practices in the kind of August heat that makes you question every choice you have ever made. I was seriously thinking about quitting the team. Money, concerts, girls — all of it felt more real and more immediate than another afternoon in the sun. Then Coach called.

He didn’t lecture me over the phone. He didn’t remind me what I owed the team. He simply asked if he could come by and talk — just thirty minutes, he said. Something in his voice made it hard to say no.

A little while later, there he was on my front porch. A grown man, a coach, sitting with a fourteen-year-old kid who had other things on his mind. For thirty minutes, he asked questions and listened. And then, without drama, he helped me see something I hadn’t fully considered: that the choices we make when we’re young have a way of following us.

He wasn’t there to save his roster. He was there for me.

I have sat through leadership seminars, read the books, and worked alongside some genuinely talented executives in the fifty years since that evening. But the clearest picture I have ever had of what a leader should be was formed on a front porch in Memphis — by a man who never once seemed to think he was doing anything extraordinary.

Here is what that season taught me about what real leadership actually looks like.

On the very first day of practice, Coach didn’t say a word about winning.

No talk of championships. No speech about records. He stood before a group of boys from entirely different backgrounds — different neighborhoods, different families, different everything — and told us what he was actually there to do.

He was going to turn us into a team of young men.

That was his mission. And it was more noble than any trophy.

Most leaders spend enormous energy communicating strategy and almost none communicating what they are actually there for. Those are different conversations. The second one is the one people remember.

Declaring a mission is one thing. The harder test is what you do when someone inside the team threatens it.

We were in the third quarter against the strongest team in our conference when our star quarterback lost his composure.

He started screaming at the offensive line right there on the field. The crowd could see it. For a second, it felt like everything might unravel.

Coach called timeout. Walked calmly onto the field. And pulled him out of the game. The booing started almost immediately.

But Coach understood something the crowd didn’t: without mutual respect, a team isn’t a team at all. There was no room for superstars at the expense of the people around them.

When the quarterback came back into the game, something had shifted. Before every huddle for the rest of that season, he made a point of thanking the line for protecting him. Every time. Without fail.

Doing the right thing when the crowd is booing is not a personality trait. It is a practice. And like most practices, it is built in small moments before the big ones arrive.

Pulling your best player when the crowd is booing takes nerve. Walking into a losing locker room at halftime and asking your team what they would do differently takes humility.

I remember a game that wasn’t going well later in the season.

At halftime, instead of delivering a fiery speech or drawing up a new scheme, Coach did something that stopped us all cold.

He asked us what we would do differently in the second half.

And he meant it. He listened — not politely, not while waiting for his turn to talk, but sincerely. He heard us. Then he adjusted accordingly.

We went back out and won the game.

The rarest quality in any leader is not intelligence or vision or decisiveness. It is the humility to seek counsel from the people doing the work, and the wisdom to act on what they tell you. Most leaders consult. Very few listen. Coach did something different — he trusted that the people closest to the problem knew something he didn’t.

They usually do.

After every game we won, Coach quietly stepped aside.

No postgame speeches positioning himself at the center of the story. No interviews about his strategy. He understood that a leader’s job in victory is to get out of the way.

But it was the one game we lost that revealed his true character.

After the final whistle, he gathered us, asked us to congratulate the other team, and sent us back to the locker room. Then he stood out on that field — alone — for an hour. The press came. The frustrated fans came. The second-guessers and the critics came.

He stood there and took all of it. Every bit of it. So that we didn’t have to.

We never knew, in the moment, exactly what he was doing. But we felt it. There is something that happens to a team when they realize their leader will stand between them and the storm.

It doesn’t make them soft. It makes them loyal in a way that no pep talk or motivational poster ever could.

I have been carrying that image — a man alone on a field — for fifty years. And I keep returning to it because I keep watching its contrast play out in boardrooms.

A man standing alone on a field after a loss — with a different kind of leader.

Not a high school football coach. Someone who showed up in a Gulfstream. Who showed up in a board meeting. Who showed up in a carefully worded memo to employees that began with the words I take full responsibility for the decisions that led us here.

And then left — with the money.

You know the names. The CEOs who presided over collapses measured in billions, in layoffs, in destroyed livelihoods — and walked away with compensation that made the damage they caused look arithmetically surreal. The language is always the same: restructuring, right-sizing, difficult macroeconomic environment. Each phrase performs the same function: it removes human agency from the narrative. Nobody decided to do this. It happened.

Coach didn’t issue a statement after that loss. He stood on the field. In public. For an hour. And took it.

That is the difference. Not a memo or a carefully worded apology. Presence, visibility, and accountability. The willingness to take the hit on behalf of the people you lead. That is the job.

I want to be careful here. Because this is not a story about corporate villains. The executives I have described were not all bad people. Many were talented. Some genuinely believed they were doing the right thing.

Here is what I have learned watching good leaders slowly become bad ones: accountability doesn’t fail all at once. It erodes. Quietly. One small choice at a time. One decision hoarded instead of delegated. One hard conversation avoided. One loss where you wrote the memo instead of standing on the field.

The distance between Coach and the executives I just described is not a distance of character. It is a distance of accumulated choices.

I stayed on the team.

Looking back across fifty years, I realize that what Coach gave us that season wasn’t a set of football strategies, a magic playbook or a management framework. It was a living example. He didn’t talk about integrity. He practiced it, quietly, in moments when no one was grading him and nothing was guaranteed.

He sat on a porch with a kid who was about to quit. He pulled a star player out of a game when the crowd was booing. He asked his team what they would do differently at halftime. He stood alone on a field for an hour after a loss. He stepped aside after every win.

None of those moments made the headlines. None of them showed up on a performance review.

They were just choices. Made consistently, in the small moments that nobody was watching.

And fifty years later, I am still talking about them.

The people who work for you are making the same assessment about you right now. Not based on what you say in all-hands meetings. Based on what you do in the small moments.

• When your high performer starts going quiet — do you notice? Do you show up?

• When the decision needs to be made and it’s hard and the crowd is booing — do you have the courage to make it anyway?

• When the project fails — do you stand on that field, or do you write the memo?

You don’t have to be perfect. Coach wasn’t perfect either. He was just consistent.

That consistency, over one season, produced bonds that lasted fifty years.

Imagine what it could produce in your organization over the next five.

Next issue: I want to tell you about the most expensive thing I’ve ever watched a room full of senior executives do.

They built a very good presentation.

And in doing so, they lost the one thing the people across the table had flown from Tokyo to find.

The Coherence Effect — Series Guide

Phase One — Human Foundation

1. You Already Know This. You Just Haven’t Named It Yet.

2. The Piano Man

3. The Porch

4. No Deck Required

5. Why I Built This

Phase Two — The Framework

6. Your Diagnosis Is Probably Wrong

7. Your Organization Isn’t Broken. It’s Incoherent.

Phase Three — The Case Studies

8. Type I: Intent Subordination — The Boeing Story

9. 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

We were sitting at a bar on Sixth Street in Austin — a team blowing off steam after a long day — when I first noticed the old man at the corner table.

He was African American, older. I guessed his eighties. He sat alone most nights, watching whatever band was playing. Occasionally he would walk up, exchange a few words with the musicians, and sit down at the piano.

And when he did, something in the room changed.

I noticed it before I could explain it. It wasn’t technical sophistication or musical complexity. It was the quality of what he created — the way certain notes seemed to linger in exactly the right places. Not manufactured. Not performed. Something closer to authentic emotion translated directly into sound.

The other musicians were playing music. He was doing something else entirely.

The others were skilled and they knew it — reading the room, managing the impression that skill creates. He had stopped doing all of that. Ninety-four years of playing had stripped away everything that wasn’t essential until what remained was simply the thing itself. He wasn’t performing the blues. He was the last living thread to the people who invented it, and when he played, that thread ran straight through the room without losing anything.

What you heard was what he was. No distance between them.

I offered to buy him a drink. He declined politely and told me that was a part of his life he had left behind some time ago. Then he asked if I would like to join him at his table.

What followed was two of the most illuminating hours I can remember. He never announced himself, never listed his accolades or credentials. He didn’t need to. Much like the way he played, there was an unmasked authenticity in his conversation that told you everything you needed to know about who he was.

I didn’t learn his name until later that night. When I asked the bartender who he was, he looked at me somewhat surprised and said: That’s Pinetop Perkins.

I had no idea.

Pinetop Perkins played with Muddy Waters for more than a decade. He won a Grammy at 97. He was considered one of the last living direct connections to the original Delta blues tradition — a man who had known and played alongside the people who invented the form.

And I felt none of that when I heard him play.

What I felt was something I recognized without any context to explain it. The authenticity preceded the biography. The quality was present before the credential arrived to ratify it.

I didn’t need to know who he was to know that what he was doing was real in a way that most things are not.

That gap — between what I felt and what I later learned — has stayed with me for years. It remains the clearest example I’ve ever encountered of a principle I’ve spent thirty years trying to understand in organizational settings.

Humans can detect coherence. We feel it before we can name it. We know, at a level below articulation, when someone’s inside self and outside presentation are the same thing. And we know when they are not.

Pinetop Perkins, at 94, had stopped needing to prove anything. Whatever distance most people maintain between who they are and who they are performing had, in him, closed entirely. When he sat down at that piano, what you heard was what he was. No credential required. No biography necessary. You felt it in the room before you knew his name.

I have spent thirty years asking a question I couldn’t fully articulate until reflecting on that evening in Austin.

Why do organizations full of capable, well-intentioned people so consistently fail to deliver what they are capable of?

Not for lack of strategy. Not for lack of intelligence or resources or genuine commitment. Something structural. Something directly related to what I felt in that bar.

The answer is coherence. Not the motivational-poster version.

Structural coherence — the specific alignment between what an organization declares it is doing, how that intent is organized and translated into action, and whether the delivery infrastructure actually exists to produce what the organization has committed to delivering.

When those three dimensions are aligned, the organization moves the way Pinetop Perkins played. Decisions reach the right level, unencumbered by performance or politics. Work moves toward outcomes the way great music moves toward resolution — without force, without waste. The whole system converts effort into results with a directness that is, when you have experienced it, as unmistakable as the real thing.

When they are not aligned, something different happens. The organization performs. Strategy documents that never generate authority. Governance processes that produce meeting agendas rather than decisions. Accountability assigned to people who were never given the authority to exercise it. Capability configured for a version of the organization that no longer exists.

The result is an organization that looks like it is working — the meetings are happening, the reports are being produced, the initiatives are in motion — while producing outcomes well below what the talent and the genuine commitment of the people inside it would otherwise generate.

I have sat in enough boardrooms to recognize the performance version of this on sight.

• The presentation that answers a question nobody asked.

• The initiative designed to look like a solution rather than function as one.

• The framework with the client’s name on the cover and someone else’s organization inside it.

These aren’t failures of intelligence. They are failures of coherence — systems optimized for the appearance of progress rather than the production of it. And like any performance, they require constant maintenance. The organizations built on theater have to keep refreshing the presentation because the work underneath it doesn’t hold attention on its own.

What no credential can produce, and what no amount of polish can manufacture, is coherence. People don’t need a name for it to feel its absence. The organizations I work with are full of people who know, without being able to say exactly why, that the accountability and the authority don’t match. That the strategy being presented and the strategy actually driving decisions are not the same one. Something in the room is off. The meetings are happening. The initiative is funded. And the outcomes still aren’t there. That gap is not a mystery. It is a structural condition. It has a name, specific causes, and it responds to specific interventions.

My job is to locate it precisely — and then help close it.

Pinetop Perkins passed away in 2011, at 98, in Austin, Texas. Some years earlier, he sat down at a bar piano on Sixth Street and played something that a 46-year-old consultant felt but could not yet explain.

It took me a decade to find the right words for it. But I recognize it now — in the organizations that have it, and in the ones that don’t — the same way I recognized it that night.

Before I knew who he was.

Next issue: I want to tell you about a phone call I received when I was fourteen years old.

A coach. A front porch. Thirty minutes that I’ve spent fifty years thinking about.

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.

08 · What the Gap Was Always Pointing At

Phase Three — The Case Studies

09 · Type I: Intent Subordination — The Boeing Story

10 · Type I: The Circuit Nobody Dropped

11 · Type II: Dimension Collapse — The Peloton Story

12 · Type III: Capability Inversion — The Haribo Story

13 · Types VI & VIII: The $42M That Was Never Missing

14 · Type IV: We Don’t Do That

15 · Type V: Authority Diffusion

16 · Type VII: Structural Theater

Phase Four — Series Close

17 · 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

There’s something we understood about people by the time we were ten years old that we’ve spent the last four decades pretending we don’t.

We knew who the bully was. We knew what they were doing. We knew it was wrong. And in most cases — not always, but most — the adults around us agreed, named it, and acted on it. You didn’t get to run the classroom by making the other kids afraid of you. That was considered a problem to be solved, not a management style to be admired.

Then something strange happened on the way to adulthood. The same behaviors we recognized instinctively at age nine got rebranded. Intimidation became “holding people accountable.” Humiliation became “direct feedback.” The need to dominate every room became “executive presence.” Cruelty toward anyone who challenged you became “high standards.”

And somehow, we bought it.

I’ve spent years inside organizations trying to figure out why good strategies fail in execution. One pattern I see more than almost any other: a single leader — usually mid-level, sometimes at the top — whose need to be the most powerful person in the room is slowly destroying the organization’s ability to function. Not dramatically. Not in ways that show up immediately in a quarterly report. But steadily, and at enormous cost.

Here’s what that actually looks like in practice. The warnings don’t get raised because the person who raises them gets made an example of. The capable people leave — not with a dramatic exit, just quietly, for somewhere else — and nobody connects the turnover rate to the leader who made their lives miserable. The decisions get worse over time because the only information reaching the top is the information that person wants to hear. The organization gradually loses its ability to tell itself the truth.

That’s not a culture problem in the abstract. That’s an execution failure with a specific cause and a specific cost.

What I’ve never fully understood is why we tolerate it. We didn’t in fourth grade. The research is fairly consistent that the psychological profile doesn’t change much — the kid who got what they wanted through fear and control grows up to be the adult who gets what they want through fear and control. The tactics get more sophisticated. The vocabulary gets more corporate. But the underlying pattern is the same thing we recognized on the playground and correctly identified as a problem.

Part of the answer is that organizations accidentally build systems that reward it. Short-term results create cover. Up-or-out promotion structures favor the aggressive over the effective. And because the damage is mostly invisible — it shows up in attrition, in suppressed ideas, in decisions that never got made well — it’s easy to look at the quarterly numbers and conclude that whatever’s happening must be working.

Part of it is that the people above them in the hierarchy often don’t experience the behavior. Narcissistic leaders are frequently excellent at managing up. They’re charming, confident, and politically astute with the people who control their futures. The cruelty flows downward, which means the people positioned to stop it often have the least exposure to it.

And part of it, I think, is that we’ve confused dominance with competence for so long that we’ve lost the ability to tell them apart. When someone takes up all the air in a room, we read it as capability. When someone is certain they’re the smartest person present, we take that certainty at face value. We mistake aggression for decisiveness, fear for respect, and compliance for alignment.

The organizations that figure this out — the ones that learn to distinguish actual leadership capability from dominant behavior — consistently outperform over any meaningful time horizon. Not because they’ve solved a culture problem. Because they’ve solved an execution problem. When people can tell the truth, decisions get better. When the capable ones don’t leave, institutional knowledge compounds. When disagreement is safe, bad ideas get caught before they become expensive.

We knew all of this in fourth grade. We knew that the kid ruling the playground through fear wasn’t the one you’d want leading anything that actually mattered. We knew the difference between someone earning authority and someone taking it.

The question worth sitting with: how did we get to a place where the boardroom applies a lower standard than the fourth-grade classroom?

Most leaders reading this already know who I’m describing. In some cases it’s someone they work for. In some cases it’s someone they’ve protected. The fourth-grade version of you knew exactly what to do about it. That instinct was right then. It’s still right now.

You already know the difference.

You felt it the last time you walked into a restaurant where everything just worked — the host who remembered your preference without being asked, the server who knew the menu well enough to steer you away from something you would have regretted, the kitchen that sent food out the way it was described. You did not consciously evaluate any of it. You just felt at ease. You went back.

You felt the opposite the last time you hired a contractor who showed up late, quoted one number and invoiced another, blamed the supplier when the work was wrong, and somehow made you feel responsible for a problem they created.

You knew, if you are honest, before it was over. Probably before it started. Something in the first conversation told you this was going to be more complicated than it should be.

That feeling is not intuition. It is a structural signal. And it is telling you something specific about the organization or the person in front of you — something you can learn to read before the invoice arrives.

The people and organizations you trust have something in common.

They are the same on the inside as they are on the outside.

What they say they will do and what they actually do are the same thing. Not approximately or usually. Consistently. When they cannot deliver what they committed to, they tell you before you have to ask. When something goes wrong — and things go wrong — they own it without performance. They do not say “I take full responsibility” and then explain at length why it was someone else’s situation to manage.

They listen before they talk. Not “politely-waiting-to-talk” listening. Actually listening — adjusting what they say next based on what you just told them, rather than continuing the script they arrived with.

They know what they are good at. And they know what they are not. The contractor who tells you “that’s not really my area, let me recommend someone” is telling you something more valuable than their capabilities. They are telling you they have enough self-knowledge to be trusted with the things that are their area.

Their commitments are specific. Not “we’ll take care of it” but “we will have that resolved by Thursday and I will call you when it is done.” Specificity is a form of accountability. Vague commitments are how people leave themselves room to disappoint you without technically breaking a promise.

The ones that cost you more than they deliver have something in common too.

The first signal is almost always the same: they talk more than they listen.

Not because they are enthusiastic or knowledgeable. Because they are not actually interested in your situation. They have a solution and they are looking for a problem it fits. The conversation is a formality. The outcome was decided before you started.

The second signal is convenience asymmetry. Everything that benefits them happens quickly. Everything that requires something from them requires follow-up, patience, or escalation. They are available when they need something from you. They are managing their schedule when you need something from them.

The third signal is the commitment gap. What gets promised in the sales conversation and what gets delivered in the engagement are measurably different. Not because of honest miscalculation — because the promise was made to close the deal, not to describe the reality. You can usually detect this early if you ask for specifics. Vague answers to specific questions are the tell.

The fourth signal is where accountability goes when something fails. Watch this one carefully. The contractor who explains why the delay is the supplier’s fault, the vendor who attributes the missed deadline to your unclear requirements, the service provider who needs more information before they can tell you what went wrong — these are not isolated behaviors. They are organizational reflexes. They tell you what this relationship is going to look like every time something does not go as planned.

And things will not always go as planned.

Here is what this actually is.

The businesses and people you trust are coherent. What they intend to do, how they are structured to do it, and what they are actually capable of delivering are aligned. That alignment does not require perfection. It requires honesty — about capability, about timelines, about when something has gone wrong.

The businesses and people that cost you are incoherent. Not necessarily dishonest — most of them believe their own promises in the moment they make them. But what they say, what they can do, and what they actually deliver are three different things operating independently of each other. The gap between them is where your time, your money, and your patience go.

You already knew this. You have been reading these signals your entire life — in the contractor, the restaurant, the vendor, the doctor’s office, the airline, the service provider who made you feel like a problem to be managed rather than a person to be served.

What you may not have had is the language for it.

Three questions worth asking before you commit to any significant engagement:

When something goes wrong — and something will — what does accountability look like here? Ask directly and observe whether the answer is specific or general.

What are you genuinely not good at? The person or organization that can answer this question honestly is telling you they are coherent. The one that cannot is telling you something equally important.

Can you give me a specific commitment — date, deliverable, named person responsible — rather than a general one? Specificity is accountability made visible. Resistance to specificity is the gap making itself known before the engagement begins.

You already know how to feel the difference.

Now you have the words for it.

The organizational version of this problem — the structural misalignment between what businesses intend to do, how they are built to do it, and what they are actually capable of delivering — is what PrecisionPath diagnoses.

The Signal Check takes five minutes and tells you specifically where the structural gap lives in your organization: www.precisionpathllc.com/how/signal

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.

precisionpathllc.com · linkedin.com/in/bkhallmann · gap.precisionpathllc.com

The Coherence Problem research: Zenodo https://doi.org/10.5281/zenodo.19456590 · SSRN http://ssrn.com/abstract=6479301

The Coherence Effect begins tomorrow — a series built on the human moments behind thirty-five years of organizational diagnosis.

But before it does, I want to close this one properly.

Over the past several weeks I have been writing about the gap between what organizations intend to do and what they actually deliver.

The slow decisions. The initiatives that launch and drift. The capable people who eventually stop fighting the system. The governance that produces meetings instead of movement. The strategy that gets revised again without anyone asking whether the execution environment is capable of supporting it.

If you have been reading this series, something in that list probably landed close to home.

Not as an abstract organizational problem. As a specific feeling you have had — sitting in a particular meeting, watching a particular initiative stall, feeling the specific friction of a decision that should have taken twenty minutes taking three weeks.

That feeling is not a morale, culture or people problem.

It is a structural signal. And it has been trying to tell you something specific about your organization for longer than you have had words for it.

The Execution Gap named the symptoms. The Coherence Effect explains why they keep coming back.

Not in framework language. Not in academic abstraction. In the language of three moments from my career that I have spent years trying to understand — because each one showed me something about organizational coherence that I could feel before I could explain.

An old man at a piano in Austin who changed the room before anyone knew who he was.

A football coach who sat on a front porch in Germantown, TN with a teenager who was about to quit — not to save his roster, but because he genuinely cared what happened to the kid.

A conference room in New York where a room full of senior executives lose a client’s confidence with a very polished presentation — and then watched it come back in the twenty minutes that followed when someone finally said what was actually true.

Three moments. Three rooms. The same thing happening in all of them.

A performance fell away. And what was underneath it changed everything.

That is what The Coherence Effect is about.

Not a framework, taxonomy, or an academic argument — though the research exists and the academic argument has been made.

A series of stories about what organizational coherence actually looks like when it is present — and what its absence costs when it is not.

If you have found the Execution Gap useful — what comes next is the explanation for why the gap exists and what it actually takes to close it.

I hope you will stay for it.

The Coherence Effect begins next week. If you are not yet subscribed — the link is below.

If someone in your network has been describing the same organizational friction in different words for longer than they should have to — share this. The series that follows is for exactly that person.

Take the free Signal Check diagnostic at www.precisionpathllc.com/how/signal

Kent Hallmann is the founder of PrecisionPath Consulting — the diagnostic instrument for the Coherence Problem. 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.