Poor execution in leadership teams is usually structural, not behavioral. When decision authority, role accountability, escalation pathways, and governance are weakly designed, even capable executives produce slow, reopened, and inconsistent decisions. The recurring failure modes are nameable — and each maps to a specific, measurable dimension of leadership architecture.
You have probably already tried the obvious things. You hired stronger people. You added a weekly sync to "improve alignment." You sent the leadership team to an offsite. And yet the same decisions stall, the same arguments resurface, and the same issues keep landing back on your desk. If that sounds familiar, you are not looking at a motivation problem or a talent problem.
You are looking at an architecture problem. And the good news about architecture problems is that they are specific. They have names, they recur in predictable patterns, and — unlike "culture" — they can be measured and redesigned.
Executive teams rarely fail to execute because individuals lack skill or commitment. They fail because the decision system around them is unclear: who decides what, when something escalates, and how a decision becomes consistent action. Those are properties of structure — the configuration of decision authority, role accountability, escalation pathways, and governance — not of personality.
Put simply: the same capable people produce different results inside a different decision structure. I have watched a high-performing executive stall for three weeks on a decision that was entirely within their competence — not because they could not decide, but because the structure gave them no clean way to. Two peers believed they shared ownership. There was no threshold that said when it should rise. So it sat, politely, until someone forced it.
This matters because the default response to weak execution is to work on the people: coach them, add meetings, replace a leader or two. If the cause is structural, those interventions don't hold — the new hire inherits the same ambiguity, and the extra meeting becomes another place to not decide. The durable fix is to redesign the decision system so that good decisions become repeatable regardless of who is in the room. About a decade ago, a large-scale study by Donald Sull, Rebecca Homkes, and Charles Sull in Harvard Business Review pointed at the same culprit from a different angle: execution rarely fails for lack of effort or alignment up and down the hierarchy. Surveying thousands of managers, they found that 84% could rely on their boss and direct reports all or most of the time, but only 9% could rely on colleagues in other units all the time (and just half most of the time) — strategy unravels in the seams between people, exactly where the decision system is supposed to do its work. The structural lens is not new. What is missing for most teams is a way to measure it.
Six structural failure modes account for most chronic execution breakdown. Each is a defect in how decisions are coordinated — not in the individuals involved. They map across the five Leadership Architecture Index dimensions — and Decision Clarity appears twice, because it is the most common structural fault: it underlies both unclear authority and decisions that will not stay closed. Decision Authority Dependency (DAD) is tracked separately as a moderator, not part of the LAI mean.
When it is genuinely ambiguous who owns a decision, choices stall, get made by default, or are quietly contested after the fact.
Decisions fall between roles or are owned by no one, so commitments are made but never clearly carried by an accountable owner.
Without clear thresholds for what rises and what is resolved locally, either everything escalates upward or genuine cross-functional conflicts never surface.
Decision load concentrates on one person, creating a bottleneck that caps the speed and volume of decisions the team can absorb.
Decisions are revisited and relitigated because authority and the decision itself were never unambiguously closed; chronic reopening also strains Escalation Discipline.
Decisions are made but not translated into consistent action across functions, so the same decision is interpreted and implemented differently downstream.
In the field, these modes rarely show up one at a time. They cluster. A few patterns recur often enough that you may recognize your own organization in them.
Picture a fifty-person software company. Product, sales, and finance each believe they own pricing. None of them is wrong, exactly — the boundary was simply never drawn. So every pricing question becomes a negotiation, and because the negotiation has no defined owner (unclear decision authority) and no threshold for resolution (escalation indiscipline), it routes to the founder. The founder, sensibly, wants to be consulted. Six months later, the founder is the company's de facto pricing committee, and no one notices the bottleneck because everyone is being so collaborative about it. On the diagnostic, this shows up as low Decision Clarity and Escalation Discipline, with a Leadership Load Balance reading concentrated on one node.
A leadership team agrees on the hiring bar in March. By May, a tough candidate prompts someone to ask, "Are we sure about this?" — and the whole question reopens. This is the signature of weak decision closure: the decision was announced but never structurally owned, so any future discomfort can reopen it. Teams in this pattern mistake their problem for indecisiveness. It is not. It is that nothing in the architecture tells them a decision is closed and who would have to reopen it. That is a Decision Clarity problem wearing an Escalation Discipline costume.
The most expensive pattern is also the quietest. The leadership team aligns on a strategy in the room. Everyone nods. Then each function walks out and implements its own interpretation, because the decision was never translated into who-does-what at the next level down. Quarter after quarter, the gap between intent and action is blamed on "execution discipline" or "buy-in." Structurally, it is Execution Alignment — the dimension that measures whether decisions become coordinated action rather than parallel, divergent effort.
Notice what all three have in common: capable, well-intentioned people, and a structure that quietly guarantees the outcome. That is the whole thesis of Leadership Architecture in one sentence — address the structure first, and behavior follows.
Naming a failure mode is the first step; locating it in the structure is what makes it fixable. The Leadership Architecture Index (LAI) scores decision-system capability across the five dimensions above — Decision Clarity, Role Ownership & Accountability, Escalation Discipline, Leadership Load Balance, and Execution Alignment. Each failure mode is the observable expression of a low score on one of them. Instead of "our execution is weak," you get "Decision Clarity is the constraint, and it is dragging Execution Alignment with it."
Capability on its own is only half the picture. A structure that is more than adequate for a simple organization can be dangerously thin for a complex one. That is why the CEO Fit Diagnostic reads capability against your Decision Coordination Demand (DCD) — how much coordination your size, growth, and complexity actually require — and produces an Architecture Capability Estimate (ACE) and a Fit Score. The relationship between demand and capability classifies your archetype: for example, Architecture Stress (demand outrunning a once-adequate structure) or Structural Chaos. Two companies with identical capability can sit in completely different archetypes because they carry different demand.
One construct is deliberately kept outside the LAI mean: Decision Authority Dependency (DAD), the degree to which the system structurally depends on a single authority. It is tracked as a moderator rather than folded into the score, because a team can post a respectable LAI and still be one person's holiday away from gridlock. Measuring it separately is what lets you see that fragility instead of averaging it away.
You do not need a full engagement to begin. You need to stop diagnosing the symptom and start diagnosing the structure. Three concrete moves:
If you want the structured version of that exercise — a scored read of all five dimensions against your actual coordination demand — that is exactly what the CEO Fit Diagnostic does, in about five minutes.
Most often structural. Capable executives still execute poorly when decision authority, accountability, escalation, and governance are weakly designed. People-focused fixes — coaching, more meetings, replacing leaders — rarely hold if the underlying decision system is the cause. Diagnosing and redesigning the structure addresses the actual source of breakdown.
Reorganizing the org chart changes who reports to whom; it rarely changes who decides what, when something escalates, or how a decision becomes consistent action. If the decision system underneath the new boxes is still ambiguous, execution stays the same. Measure the five dimensions first, then redesign the parts that score low.
Decision reopening is when a settled decision is relitigated, signaling that authority and closure were never unambiguous — primarily a Decision Clarity weakness. Escalation indiscipline is about whether issues rise to the right level at the right time — an Escalation Discipline weakness. They often coexist, but they are distinct structural defects measured by different dimensions.
The Leadership Architecture Index (LAI) scores decision-system capability across five dimensions: Decision Clarity, Role Ownership & Accountability, Escalation Discipline, Leadership Load Balance, and Execution Alignment. Each failure mode maps to one dimension, so a low score localizes the structural cause precisely rather than attributing breakdown to a vague culture problem.
Founder arbitration overload — decision load concentrating on one person — is measured by Leadership Load Balance within the LAI. The broader pattern of the system depending on one authority is captured by Decision Authority Dependency (DAD), a separate moderating construct tracked alongside the LAI rather than included in it.
Source: Sull, D., Homkes, R. & Sull, C. (2015). “Why Strategy Execution Unravels — and What to Do About It.” Harvard Business Review.
Five minutes. No account. See which structural dimension is constraining your execution.