Three failure case studies: Hargrove, Meridian, Vantara — what late intervention costs

The Frustration Condition includes three composite case studies that the framework uses to teach what late intervention costs. The cases are composites — they are drawn from the doctoral fieldwork and the consulting practice that followed it, and the company names are pseudonymous to protect the participating organisations. The architectures, the timelines, and the cost shape are real.

All three cases share the same structural shape. The frustration cluster was readable in the open-text 12-24 months before the engagement score moved. The architecture was one of the five — Decision Bottlenecks, Approval Loops, Priority Churn, Role Ambiguity, or Unspoken Constraints. The eventual remediation addressed the same architecture the cluster had named. The cost of waiting was not the cost of the structural change; it was the cost of credibility.

Hargrove Industries — Approval Loops

Hargrove Industries is a $400M industrials business that was acquired by a mid-market PE fund in Year 0. By Month 9, the most experienced operators on the manufacturing side had begun to package their work — pretty decks, defensive memos, multiple rounds of "socialisation" — before the actual work happened. The clusters in the open-text were unambiguous: every approval gate the work touched had been added back after a Month 6 reorg, and the people doing the work no longer believed any of the gates were there to catch real risk.

The architecture was an Approval Loop. The fix recipe — audit every gate, risk-tier them, remove or collapse the lowest tier first — would have taken a single Three Columns Workshop. The intervention that actually happened arrived 14 months later, after a $9M cost overrun on a customer programme had made the cost of the loop visible to the operating partner.

When the audit was finally run, more than half of the gates the work touched were Tier 3 — habit, with no remembered origin. The structural change took six weeks. The credibility change took the next two years; two of the three operators who had named the cluster in Month 9 had left by the time the gates came down.

Meridian Health — Role Ambiguity

Meridian Health is a regional non-profit health system that grew through three small acquisitions in 18 months. By the second year, the most common explanation for missed work in two adjacent service lines was "I thought X was doing it" or "I didn't realise that was on me." The org chart showed a clean split between the two service lines; the actual work was full of cross-boundary outcomes that nobody owned, and the boundary kept getting re-litigated in escalation meetings.

The architecture was Role Ambiguity. The fix recipe — name the outcome, assign one owner, write down what the owner is explicitly NOT on the hook for, and stand up parallel infrastructure where the work genuinely spans the boundary — was within the COO's authority to call. It was not called for 19 months, because every escalation cycle ended with a renewed attempt to redraw the org chart instead.

When parallel infrastructure was eventually stood up — a 30-minute weekly forum between the two service-line leaders with a recorded decision log — the escalation rate on cross-boundary outcomes dropped by roughly 70% within a quarter. The credibility cost was different in shape from Hargrove: at Meridian, the people who had named the cluster were still there, but they had stopped raising the issue, because the previous 19 months had taught them that raising it produced another reorg attempt rather than a structural decision.

Vantara Capital — the Quiet Reversal

Vantara Capital is a third-generation family-owned asset management business with a non-family CEO appointed in Year 11 of the second generation's tenure. The non-family CEO made three structural decisions in the first 100 days. Within six weeks, two of them had been quietly softened by the founding generation in side conversations with the senior team. No announcement was made. The team learned about each reversal by watching what actually happened, not by being told.

The architecture is the Quiet Reversal — the book's name for the family-business pattern in which the formal authority of the org chart is overruled by the informal authority of the family system. By Year Twelve, the team had learned that the org chart was not where decisions lived, and the most capable non-family executives had begun to invest their effort accordingly: two had taken outside roles, and the third had stopped raising structural issues because the family-system reversals had taught the room that raising them did not produce structural change.

The intervention that eventually worked was not a reorg. It was a Family Reversal Log — a written record of every decision the non-family CEO had made, every reversal the family system had initiated, and what the team had learned from each reversal. The log was brought to the family system, not to the team. It was the first time the asymmetry had been named in writing. The reversal rate over the following two quarters dropped by more than half.

What the three cases share

• The structural read was available in the open-text 12-24 months before the engagement score moved.
• The architecture named in the cluster was the architecture the eventual remediation addressed — the framework was right; the framework was just used late.
• The cost of waiting was credibility, not data. The structural change was always within authority. What was not within authority, by the time the change was made, was the team's belief that the change would hold.
• An early Three Doors decision, walked through the room in Three Doors voice, would have changed the trajectory in every case — and would not have required any structural authority the leader did not already have at the moment the cluster first appeared.

How to use these cases inside your own workspace

The three cases are not benchmarks. They are diagnostic mirrors. Read each one against your own current pattern board: which architecture is the cluster pointing at, how long has the cluster been visible, and what would the equivalent of an early Remove or Defer With Clarity decision look like in your room this week. The framework's claim is that the structural change is rarely the hard part. The hard part is making it before the team has been taught not to invest in it.