The Reorg Will Not Fix a Decision Problem

A client told us last year that they had reorganized twice in three years and were preparing to do it again. The complaints going into each one were identical. Decisions took too long, nobody could say who had final say, the same two functions kept colliding over the same short list of issues.

Both reorgs redrew reporting lines, renamed a few groups, and moved around thirty people. Roughly eighteen months later, the friction came back wearing different job titles.

This happens often enough that it is worth being precise about the mechanics. While an org chart answers the question of who manages whom, most of the pain inside a company comes from a different question, which is who decides what. Leadership teams treat those as one problem, and under any kind of pressure they come apart.

Structure answers a narrower question than most leaders expect

An org chart encodes supervision, career path, and headcount, and those things matter, but is says very little about authority over the specific calls that determine how a company performs: pricing exceptions, hiring above band, capital spend below the board threshold, which roadmap item slips when engineering capacity gets tight, which customer relationships you are willing to let go.

Those decisions get made dozens of times a quarter. When ownership of them is unclear, people resolve the ambiguity themselves: they escalate, they build a workaround, or they wait. Each response is rational for the individual and expensive for the company, and none of it shows up on the chart you just spent four months redrawing.

The symptom usually arrives described as a people problem

When a leadership team calls us about friction, the first framing is almost always about communication or personality. Two leaders who cannot get along. A function that has become territorial.

In one case, the friction traced back to capital spend. Two executives had each been told, at different points and by different people, that they approved equipment purchases in their region above a certain threshold. Neither had any reason to doubt it. Their teams had spent the better part of a year routing requests through whichever of the two was likely to say yes faster, and the vendors had figured this out before anybody internal did.

Neither executive was difficult. They were behaving sensibly given what they had been told. The structure produced the conflict, and the conflict arrived looking like a relationship issue because that is the first place people look.

Start with the decisions, not the boxes

The exercise we run at the front of an org design engagement takes about a week and rarely requires new data: pull together the fifteen to twenty decisions that most determine whether the business hits its plan, then ask five or six leaders, separately, who owns each one. Four failure patterns show up in the results, and each call for a different fix.

·        Ownership is duplicated: two people believe the call is theirs. It's the pattern that generates the most visible conflict, and the easiest to resolve once it's written down.

·        Ownership is missing: everyone names a different function, and no function claims it. These tend to be the decisions sitting between departments, which is also where a disproportionate share of customer experience problems live.

·        Ownership sits too high: the decision technically belongs to someone three levels above the work, gets made slowly with worse information, and the person closest to the customer learns to stop asking.

·        Ownership has drifted: authority and context have come apart, usually because the business changed, and the delegation never caught up.

Working through that list alone solves some problems without moving a single person, which beats any restructuring, since restructuring costs momentum and burns goodwill you may need later.

Then structure follows, and it has a job to do

Once decision rights are placed, the structural questions get much easier, because you're no longer guessing what the structure is for. The focus shifts to how value gets created rather than historical accidents and spans wide enough that managers manage rather than hover but narrow enough that they can support their people.

These are the mechanics of org design, and they work well, but only once someone has agreed on what the organization is supposed to decide.

The part that determines whether any of it survives

A new structure with an old scorecard reverts. We see this constantly, and it's the single most reliable predictor of whether an org design holds. Move pricing authority to the regional level while the comp plan still pays on volume, and pricing discipline erodes within two quarters, without anyone doing anything wrong.

So, the last phase of org design work is the least glamorous and the most load-bearing: metrics that map to the decisions you just assigned, incentives that pay for the behavior the new structure requires, and a review rhythm that gives the new owners a forum where their decisions actually get discussed, which is how authority becomes real to everyone watching.

What it looks like when the design is holding

The signals are quiet - escalations to the executive team drop, and the ones that remain are genuinely novel, and meeting invite lists shrink because fewer people need to be there to protect their interests.

The clearest signal is that nobody is talking about the org chart anymore. When the design is right, it stops being a topic and goes back to being a document.

Most organizations are structured for where they've been. Getting to a structure that fits where the business is going starts earlier than most leadership teams assume, and it starts with a list of decisions rather than a diagram.