When the Strategy Is Sound and Everything Still Goes Wrong
This is Episode 08 of The Coherence Effect — the first of eight case studies. If you're new here, start with Episode 01.
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.