A map of structural failure

Where the problems actually live

The visible symptoms — slipping commitments, escalation, loss of confidence — emerge from a small number of places. Seven, in our experience.

Most leadership teams describe challenges in the language of outcomes: deadlines missed, costs overrun, confidence eroded. The cause is almost always somewhere else. It lives in the spaces between teams, between decisions, between what is said and what is true.

This page is a working map of those spaces. It is not exhaustive. It is the seven places we have found, repeatedly, that produce the symptoms leadership eventually has to deal with.

Symptoms surface where attention is. Causes live elsewhere.

In detail
01

Gaps between accountability, responsibility, and execution.

The named decision-maker and the person carrying the consequence are not the same person. Decisions are made in rooms that do not include the people who will live with them. Or they're not made, and silence results in inferred guidance.

Tells
  • "Who actually decided this?" is a difficult question to answer
  • The person held to account was not in the room when the choice was made.
  • Decisions are revisited because the right people were not present the first time.
02

Communication travels through a maze, not along a chain

Information loses precision at every hand-off. Caveats are smoothed out. Confidence is added that was not in the original analysis. By the time it lands at leadership level, the description bears only a family resemblance to the situation.

Tells
  • Reporting is consistently more confident than the underlying evidence or actual outcomes.
  • Bad news arrives later than it could.
  • Clarifying questions are answered with summaries, not source material.
03

Value is diminished at internal boundaries

Individual functions optimize locally. The system loses value at the boundaries between them, and nobody watching only their own side can see it.

Tells
  • Each function reports green; the joint outcome is amber or red
  • Cross-functional escalations dominate steering meetings.
  • Solutions require trades nobody is empowered to make.
04

Problem smoothing erodes precision and clarity

Real disagreement is filtered out through softening, deferrment, restatement as a question, before reaching senior leadership. Senior leaders consider decisions based on the cleaned, euphemized version. The original objections return later, as implementation problems.

Tells
  • People who saw the issue early did not feel able to surface it.
  • Decisions get made without the dissent being visible.
  • "I had concerns at the time" is heard after, not before.
05

The unwritten plan takes precedence

Two plans are being executed. The one in the slide deck is reported against, governed, defended to stakeholders. And the one teams are actually following is adjusted weekly and never written down. Where these plans differ is where the surprises live.

Tells
  • Reporting tracks to the plan; outcomes show something else.
  • Teams describe the work or goals in language the plan does not contain.
  • Replans happen in private; reports happen in public.
06

Translation drift undermines the strategy

Strategic intent translates into delivery scope. Each translation is reasonable; the cumulative effect is not. What gets built is not what the strategy described. Nobody notices, because the people who could compare both are no longer in the conversation.

Tells
  • Delivery teams cannot quote the strategic intent in their own words.
  • Strategy teams cannot describe what is being built in the language of the work.
  • Mid-flight course corrections come from outside the delivery execution system.
07

The execution system hasn't learned how to learn

New evidence cannot change the committed plan. The cost of revisiting is treated as higher than the cost of being wrong. Energy goes into defending, rather than testing, the existing direction.

Tells
  • Material new evidence does not change planning artifacts.
  • Re-planning is a political event, not an operational one.
  • Forecasts are revised but not the decisions they should inform.

These symptoms are not taxonomic categories. They are fault lines. A given organization rarely has a problem in all seven; most organizations have a problem in two or three.

Enumerating the symptoms and identifying their true root causes is the work of our Executive Decision Sessions. The knowledge leaders get from the deliverables that result from this work is clear, compelling, and actionable.

Symptoms appear where you can see them. Our work is to diagnose the unambiguous root causes.

Recognize any of these symptoms

If something on this page sounds familiar, that is usually a signal worth a conversation.

Begin a conversation →