Design the Decision, Not Just the Org Chart

Ask a room of senior leaders to draw their org chart and they can do it in minutes. Ask the same room who has the authority to make a specific, contested decision, and watch the room go quiet.

Structure is not the same as authority

Org charts describe reporting lines. They do not describe decision rights. A vice president can sit at the top of a clean, well-documented structure and still have no clear authority to resolve a disagreement between two departments that both report to her. The chart looks fine. The decision still stalls.

This is one of the most common, least discussed reasons transformations lose momentum. Leaders assume that because the structure is sound, decisions will flow through it cleanly. They rarely do, because structure and decision architecture are two different design problems.

What decision architecture actually means

Decision architecture is the explicit answer to a small set of questions: who decides, who is consulted, who is informed, and what happens when there is disagreement. It sounds simple. Almost no organization writes it down, which means almost every organization relies on informal precedent and personal relationships to answer it in the moment, under pressure, differently each time.

The cost shows up as delay. A decision that should take a week takes six because three different people believe they have a say, and no one has been explicit about whose input is advisory and whose is final.

Designing it deliberately

The fix is not another layer of process. It is a short, honest exercise: for the handful of decisions that will actually determine whether a transformation succeeds, name the decision-maker in writing, before the pressure hits. Leaders who do this find that disagreements resolve faster, not because people agree more, but because everyone knows where the decision ultimately lands.

An org chart shows where people sit. Decision architecture shows how the organization actually moves. Building both is the difference between a transformation that stalls politely and one that keeps its pace.

A short exercise that surfaces the problem quickly

Try this in your next leadership meeting: name one significant decision your organization needs to make in the next quarter, and ask everyone in the room, independently, who they believe has the final say. It is common for three or four different names to surface, each defended with a reasonable rationale. That disagreement, surfacing in a room full of experienced, well-intentioned leaders, is the clearest evidence that decision architecture has not been designed. It has been assumed.

Why informal precedent is not a substitute

Most organizations rely on informal precedent to answer decision-rights questions: whoever spoke up last time, whoever has the loudest voice, whoever technically owns the budget line. Precedent works reasonably well when stakes are low and time is not a factor. It breaks down exactly when it matters most, under pressure, when a fast, clear decision is needed and the room instead spends its energy negotiating who gets to make the call.

Making the architecture visible

The fix does not require a large governance initiative. For the handful of decisions that will actually determine whether a transformation succeeds, write down, in plain language, who decides, who is consulted, and who is simply informed. Share it before the pressure hits, not during it. Leaders who do this consistently find that disagreements still happen, but they resolve in hours instead of weeks, because everyone already knows where the decision lands.