The Real Test of an Org Design Is Who Gets to Decide
Most leadership teams treat organizational design as a question of structure. How many layers should there be? How wide should the spans of control run? Which functions report to whom? Should the business be organized by region or by product line? These are legitimate questions, but they are the wrong place to begin because they describe the shape of an organization without touching the detail that determines how it performs. That detail is how decisions get made.
An organization is a decision-making machine before it is anything else. What it produces, underneath the products and revenue, is a continuous stream of choices about where to spend money, which customers to prioritize, what to build next, and whom to put in which seat. The quality and speed of those choices is the real output. Structure earns its keep only to the degree that it improves them. A clean reporting diagram that leaves the important decisions stuck, contested, or pushed up to the executive team has produced a well-drawn organization unable to act.
Structure Without Decision Rights Is Just a Diagram
When a company reorganizes, it moves boxes and redraws lines. What it rarely does with the same rigor is specify who now holds which decisions. The assumption is that authority follows the chart, that if you report to someone, the two of you will sort out who decides what. In practice, that assumption is where most friction lives.
Consider a firm that reorganizes its commercial teams around industry verticals to get closer to customers. The chart looks sharp. Then a pricing exception comes up that spans two verticals, and it turns out no one knows whether the vertical lead can approve it, whether it needs to go to the head of sales, or whether finance holds a veto. The decision stalls. It gets escalated. A meeting is scheduled. The new structure did nothing to answer the only question that mattered in the moment, which was who gets to decide this.
Reporting lines tell you who manages whom. They are close to silent on who decides what, and decisions are the part that governs how fast and how well the company moves.
The Symptoms Look Like Speed, Not Structure
Leaders rarely describe their problem as a decision-rights problem. They describe it as slowness. Everything takes too long to get approved. Too much lands on the executive team's desk. Meetings end without resolution and reconvene a week later with the same people and the same open question. Good managers hesitate to act because they are not certain the call is theirs to make.
Those are not culture problems nor talent problems, though they often get diagnosed as both. They are the predictable result of an organization that specified its structure and left decision rights ambiguous. When it is unclear who owns a decision, the safe move for any individual manager is to escalate or to wait, and an organization full of people escalating and waiting will feel sluggish no matter how elegant the chart.
The instinct when a company feels slow is to reorganize again, to flatten a layer or consolidate a function. That treats the symptom and misses the cause. The slowness usually has less to do with how many boxes exist and more to do with the fact that nobody knows which box a given decision belongs in.
Design the Decisions First
The more useful sequence runs in the other direction. Before settling the structure, identify the decisions that drive the business. How capital gets allocated across the portfolio. How pricing exceptions get approved. How a new market gets entered. How trade-offs between two product lines get resolved. How senior hires get made. The list is rarely longer than fifteen or twenty decisions that genuinely matter.
For each one, get specific about who recommends, who decides, who must be consulted first, and who needs to be informed after the fact. Clarity is worth more than any refinement to reporting lines, and it exposes the real design questions. When two roles both believe they own the same decision, you have found a conflict the chart was hiding. When a decision has no clear owner at all, you have found a gap that no amount of restructuring will close on its own.
Structure should follow from that work, not precede it. Once you know which decisions matter and who should hold them, the reporting lines that best support those decision rights tend to become obvious. Build the structure first and you are guessing at the shape and hoping the decisions sort themselves out inside it.
The measure of good organizational design is never how logical it looks on a slide. It is whether the people inside it know who decides what, and can act on that knowledge without a meeting. Get the decisions right and the boxes take care of themselves. Get the boxes right and leave the decisions vague, and you have drawn a very tidy picture of an organization that cannot move.