The Five Failure Modes
Organizations don't break randomly. They break in a predictable cascade of five structural failure modes. Here's how to diagnose which one is active in yours.
Every product organization I've worked inside, or been hired to fix, exhibits at least one of five structural failure modes. They're not personality problems. They're not hiring problems. They're architecture problems, as surely as a building with a cracked foundation is an architecture problem.
What makes these modes dangerous is that they form a cascade. Each one produces the conditions for the next. Fix the wrong one and you're treating symptoms while the structural cause compounds underneath. The cascade is: Unclear Outcomes, Priority Thrash, Collapsed Ownership, Misaligned Constraints, and Process as a Shield.
It starts with Unclear Outcomes. Leadership has a strategy. It lives in a slide deck, a quarterly memo, maybe an all-hands presentation. But it never translates into outcomes specific enough for teams to act on. The 'why' never reaches the people doing the work. Teams fill the vacuum with their own interpretations, and now you have twenty teams executing against twenty different understandings of success.
Unclear Outcomes produce Priority Thrash. When nobody knows what success looks like, everything feels urgent. Roadmaps churn quarterly. Initiatives launch before the last ones finish. Teams learn to start everything and finish nothing, because next quarter's priorities will overwrite this quarter's anyway. The organization is busy. The product is going nowhere.
Priority Thrash produces Collapsed Ownership. When priorities shift constantly, teams stop investing in outcomes and start complying with requests. Why own the result when the goal will change before you ship? Ownership collapses into task completion. Teams stop pushing back, stop advocating for users, stop making judgment calls. They do what they're told and nothing more.
Collapsed Ownership produces Misaligned Constraints. When teams stop owning outcomes, the real constraints (technical debt, capacity limits, regulatory requirements, integration dependencies) stay hidden. Nobody surfaces them because nobody feels responsible for the outcome those constraints affect. Leaders make decisions with incomplete information. Timelines are fiction. Scope is negotiated after the deadline passes, not before.
Misaligned Constraints produce Process as a Shield. When the real limitations are invisible and ownership has collapsed, the organization reaches for the one thing it can control: process. Stand-ups, retros, planning ceremonies, status reports, approval gates. Each one added with good intentions. Collectively, they become a shield against accountability. The rituals replace learning. The organization performs productivity without producing results.
The cascade is not inevitable. But it is the dominant pattern. I've watched it play out at startups, mid-size companies, and enterprises. The surface symptoms vary (missed deadlines, low morale, product inconsistency, customer churn) but the structural sequence is remarkably consistent.
The diagnostic question is not 'what's wrong with our team?' It's 'where in the cascade are we?' Because the intervention for Unclear Outcomes is completely different from the intervention for Process as a Shield, even though both produce the same feeling of organizational frustration.
This cascade is the structural backbone of The Coherence Gap. Part II of the book maps each failure mode in detail: how it forms, how it compounds, and what closing it actually requires. What I've learned across twenty-five years is that most organizations are treating symptoms at the bottom of the cascade while the cause lives at the top.