A single claim, and what follows from taking it seriously.
The method rests on a single claim: the execution breakdowns growth-stage leadership teams experience originate in structural conditions rather than in the people operating inside them.
Structural here does not mean the org chart. It means how authority binds, how decisions are routed, which forums carry which decision rights, and how information reaches the people deciding. Redrawing reporting lines rarely touches any of that.
The claim has consequences. If dysfunction is structural in origin, then the interpersonal and internal dynamics a leadership team can see — the guarded meetings, the hedging, the leader who keeps stepping in — are downstream effects rather than root causes. Working on them directly produces real improvement that erodes, because the conditions generating them are untouched.
But the reverse shortcut fails too. You cannot simply repair the structural conditions and expect a team to operate inside the new architecture. Team members carry learned patterns that persist past the conditions that produced them. Leaders carry internal calibration that shapes whether they hold the new structure or quietly undermine it. And without reinforcement mechanisms, early improvement reverts the first time the organization comes under pressure.
The method therefore has two halves. Diagnosis locates which of five integration domains is the primary constraint. Intervention addresses that constraint across four levels at once — structure, team, leader, and reinforcement.
What each one governs, what its breakdown looks like from inside the team, and what diagnostic work examines to establish whether it is the primary constraint.
Authority Integrity is about bindingness: whether a decision made by the leadership team actually settles into shared operating reality, so that divided labor can reorganize around it. It is the foundational domain, because when decisions do not bind, nothing built on top of them holds either.
Breakdown takes four forms. Ambiguity — nobody is clear which category of decisions belongs to whom, so people hedge or escalate by default. Inconsistency — authority holds in some territory and not in other territory, usually the territory the leader cares about most. Misplacement — decisions sit at the wrong altitude, either held above the people with the information or pushed below the people accountable for the outcome. And shadow decision-making — the formal forum announces decisions that were actually bound somewhere else, in a pre-meeting, a hallway conversation, or a one-on-one with the leader.
From inside the team it feels like decisions that never quite close. Commitments are made in the room and stay open in practice. Work gets done twice. The leader finds themselves enforcing decisions that should have propagated on their own, and reads the pattern as an accountability problem in specific people.
It matters because authority arrangements are calibrated to a moment in a company’s history. Arrangements that worked at forty employees routinely fail at four hundred, not because the leaders became less capable but because structural fit degraded as the organization changed around them.
Diagnostic work traces what actually happens to a decision after it is made — where it propagates cleanly, where it needs enforcement, where interpretation diverges. It examines specific recent decisions that were believed settled but where execution did not match, identifies which of the four patterns produced the gap, and examines where binding actually occurs versus where it is formally supposed to.
Attention Precision is about altitude: whether the leadership team’s collective attention sits where the work only they can do actually is. Attention is the scarcest resource at the top of a company, and it is structurally allocated rather than individually chosen.
Breakdown runs in two directions at once. Attention gets pulled down into work that belongs below the leadership team — operational decisions, escalations that exist because escalation is the path of least resistance, detail that someone else owns. And the high-leverage work that only this group can do never enters the room. Strategic questions get deferred quarter after quarter, not through avoidance but because nothing routes them in.
From inside the team it feels like a full calendar producing nothing that compounds. Meetings are busy and the agenda reflects whatever is loudest. Leaders describe their weeks as consumed and are unable to name what they moved forward. Direct reports, meanwhile, operate with leadership engaged too far into their work.
It matters because attention allocation is a function of information routing and forum design, not of discipline. A leadership team cannot resolve it by resolving to focus better. What reaches collective attention is determined by structural conditions, which is also why it is structurally addressable.
Diagnostic work assesses altitude directly — what occupies leadership discussion time, what routes in, what routinely fails to route in, and what the leader believes they should be spending attention on versus where it actually goes. It examines what the team has adapted to, since sustained misallocation trains the organization to bring the wrong work upward.
Structural Dissent is about knowledge integration: whether specialized knowledge held by team members closer to specific parts of the work actually surfaces at decision points, or stays inside individual heads while decisions proceed on partial information.
Breakdown looks like concerns softened until they do not register, agreement that is nodded rather than held, dissent that surfaces in side channels instead of the room, and objections that arrive only after implementation is underway and the information becomes undeniable. Quiet gets misread as consensus, which is the specific failure mode that makes this domain dangerous. The leadership team believes it decided with full information.
From inside the team it feels like execution surfacing problems that someone must have known about. Post-mortems reveal that two people had reservations they never raised in a form anyone registered. The leader experiences a team that agrees in meetings and litigates afterward.
It matters because a leadership team exists to integrate specialized knowledge across divided labor. When structural conditions prevent that knowledge from reaching decisions, the organization decides with less information than it actually holds. That is a capacity problem, not a personality problem or a communication style problem.
Diagnostic work examines whether dissent surfaces early enough to change decisions, what happens in the room when someone disagrees with the leader, which team members have gone quiet and in what territory, and how the team’s learned patterns around disagreement formed. It distinguishes structural suppression of dissent from individual reticence.
Decision Velocity is about the path a decision travels: whether it matches what the work actually warrants — fast enough to hold momentum and capture opportunity, deliberate enough to integrate what needs integrating.
Breakdown is rarely that people are slow. It is the path itself. Too many people whose sign-off is required. Decisions routed through forum after forum, each adding a cycle. Unspoken veto points that make people pre-test and hedge before committing. Or the opposite failure, where the path is too short for the decision — commitments made without integrating what the organization knew, producing rework that looks like poor execution.
From inside the team it feels like decisions that take far longer than the work warrants, or that lose relevance before they are acted on. Momentum leaks in the gaps between when something is obvious and when it is committed. Leaders compensate by pushing individual decisions through personally, which works and does not scale.
It matters because different decisions require different processing depth. Structural conditions that force a uniform pace across varied requirements produce either delay on the simple decisions or inadequate integration on the complex ones. Velocity is a calibration question, not a speed question.
Diagnostic work traces the actual path of specific recent decisions — who was involved when, where the decision waited and why, where it was actually bound. It examines whether the path matches the class of decision, where hedging and pre-testing occur, and what the team has learned to expect about how long things take.
Performance Stability is about collective capacity under load: whether the team’s integration architecture holds during demanding conditions, or degrades in ways that persist past the pressure that caused them.
Breakdown shows up as a team that functions adequately in normal conditions and slips in exactly the high-stakes periods when reliability matters most. What distinguishes this domain from the others is that the damage lingers. Trust erosion, dropped rhythms, coordination breakdown, and unrepaired conflict from one hard stretch carry into the next, so the team operates worse long after the pressure itself has passed.
From inside the team it feels like a group that is fine until it isn’t. The leader can often name the period when something changed and has usually not treated it as something requiring repair. Teams frequently carry accumulated damage from a funding crunch, a failed launch, or a departure years earlier and have adapted around it rather than metabolized it.
It matters because an architecture that only functions under favorable conditions is not a functioning architecture. Growth-stage companies operate under load as their normal state, which means stability determines what the other four domains are actually worth.
Diagnostic work assesses current capacity and the accumulated damage separately — what the team is carrying from prior periods, what patterns activate specifically under pressure, and what the team’s learned responses to load have become. Stability work often surfaces material the team has never discussed directly.
Leadership teams rarely have five problems. They have one constraint carrying most of the weight and four domains showing its downstream effects.
This is why distributed effort produces local improvement without system-level change. Improvement effort that is not directed at the primary constraint produces local optima without system effect.
Constraints also move. What functions as the primary constraint at the start of an engagement may not be the primary constraint six months later, once initial intervention has addressed it.
Diagnosis identifies the constraint. Intervention addresses it, and does so at four levels simultaneously. The levels are not a menu. Each one determines whether the others hold.
Level one, structural work, changes the conditions themselves — how authority is assigned and protected, how decisions are routed, which forums carry which decision rights, how attention gets allocated. The changes are specific rather than aspirational: specific decisions placed at specific levels, specific escalation criteria with specific triggers, specific documentation practices. Ambiguity in the structural changes reproduces the ambiguity that broke the condition in the first place.
Level two, work with the team, addresses the learned patterns team members developed as adaptation to the broken conditions. Those patterns persist past the conditions that produced them. Without this level you get new architecture with old patterns operating inside it — the single most common failure mode in organizational redesign.
Level three, work with the leader, addresses the leader’s own calibration in the territory the constraint involves. A leader’s patterns determine whether structural change gets sustained or subtly undermined by how they engage with it. This is where the clinical background does its work.
Level four, reinforcement rhythms, builds the mechanisms that carry the change forward when engagement intensity reduces — review rhythms, documentation that keeps the changes visible, surfacing mechanisms that catch drift before it becomes crisis. Most approaches treat reinforcement as an implementation detail. Here it is one of the four essential dimensions.
The framework is grounded in established organizational theory rather than assembled from consulting practice. Four bodies of work do most of the grounding.
Structural contingency theory — Lawrence and Lorsch, Woodward, Perrow — establishes that structural effectiveness depends on fit with contingent factors, and that there is no universally correct structure. This grounds why authority and attention arrangements fail specifically at growth-stage transitions: the contingencies changed while the structure didn’t.
Organizational information processing theory — Galbraith, extending Simon’s work on bounded rationality — establishes that organizations are information processing systems, and that performance degrades when processing requirements exceed capacity. This grounds Structural Dissent as a capacity problem rather than a communication problem.
Theory of constraints — Goldratt — establishes that every system has a primary constraint limiting overall performance, and that improvement effort not directed at it produces local optima without system effect. This is direct application rather than analogy.
The attention-based view of the firm — Ocasio — establishes attention as the fundamental strategic resource, allocated by organizational structures rather than by individual discipline. This grounds the Attention Precision domain.
Each of the approaches below does real work. The distinction is not about quality. It is that each operates at one level of an architecture that requires four.
Executive coaching does important work at level three. What it cannot reach is the structural conditions the leader operates inside, the patterns the team has learned from those conditions, or the reinforcement architecture that determines whether change holds. Existing coaching work continues as level three within the broader intervention rather than being replaced by it.
Team development work does important work at level two. What it cannot reach is the structural conditions generating those patterns. When the structure keeps producing what team development addressed, the improvements do not hold.
Organizational development and design consulting operates primarily at level one. Its characteristic failure is the redesign that produces new structure with old patterns operating inside it, because team-level and leader-level work were treated as adjacent rather than essential.
Operating systems such as EOS are substantial work at level one with some reinforcement cadence built in. What they typically do not address in depth is the learned patterns inside the team, the leader’s own calibration, and the integration of specialized knowledge at decision points. The method works alongside an operating system rather than replacing it.
Large consultancies bring analytical rigor, benchmarking, and global expertise. For leadership team work specifically, their engagement structures tend toward standardization and are oriented toward defined deliverables rather than the sustained relationship the leader-level work requires. That is a difference of fit, not of quality.
Frameworks addressing specific dynamics — the Five Dysfunctions, communication models such as Radical Candor — do substantive work at level two on what enables productive conflict and clear commitment. They address how people talk to each other. The method addresses whether the structural conditions support the conversations people need to have.
Diagnostic work identifies the primary constraint for your specific team, and what intervention would actually involve. It is a standalone engagement — three to five weeks, no commitment to what follows.