When organisations talk about redesign, they reach almost instinctively for the org chart. Boxes get moved, reporting lines get redrawn, new functions appear, old ones disappear. Six months later, the same problems resurface in a slightly different shape.
The reason is that most operating model failures aren't structural — they're behavioural.
What people actually respond to
A role definition is a piece of paper. A reporting line is a pixel on a slide. What actually shapes behaviour inside an organisation is much less tidy: who gets listened to in a meeting, whose disapproval people fear, which decisions feel safe to make alone and which require cover.
When roles are unclear or accountability is ambiguous, people don't freeze. They default — to the patterns that feel safe, not necessarily the ones that work. They escalate. They wait. They duplicate effort just to be sure. They write longer emails.
Designing for the behaviour you want
Good organisational design treats the structure as a set of cues, not a set of commands. It asks:
- What decisions does this role need to make alone?
- What does saying "yes" cost — and what does saying "no" cost?
- Where will people instinctively go for cover, and is that the right place?
Structure isn't the answer. It's the environment in which the answer emerges.
The organisations that get this right tend to spend less time on the chart and more time on the rituals, decision rights, and incentives that make the chart meaningful.
A short test
Next time you're tempted to redraw a structure, try this: pick the three most contested decisions in the business. Trace, honestly, who actually makes them today and how. Then ask whether the new structure would change that — or just relabel it.
If the answer is "relabel", the design isn't done yet.