Skip to content

Organisational demand

Organisational demand is what a strategic change newly requires an organisation to do well, stated as observable work rather than ambition. It names the decisions that must move, the capabilities that now matter, the dependencies that must hold and the trade-offs that must be protected when the new strategy conflicts with the old.

A strategic shift must become an organisational demand; if it stays at the level of ambition, every function invents its own meaning.

Why it matters when the plan changes

A new direction usually arrives as ambition: grow in a new segment, move from expansion to profitability, integrate an acquisition. Ambition does not tell a finance team, a product lead or a regional manager what to do differently next week, so each fills the gap with its own reading, and the readings meet across units, where reliance is weakest. Donald Sull, Rebecca Homkes and Charles Sull found that only 9% of managers could rely on colleagues in other functions and units all the time.

The tension is precision against flexibility. A demand stated too loosely changes nothing; one stated too tightly turns strategy into a checklist and removes the judgement the people closest to the work need. The useful level names what must become observably true, by when, and which decisions must move, and leaves the method to the teams that carry it.

In practice

After a buyout the new owners set a margin target. Stated as demand, it becomes: pricing decisions move from regional heads to one commercial lead, discounting above a set threshold needs a second signature, and the product team now protects unit economics when a large customer asks for a custom build.

Evidence

What it cannot tell you

Organisational demand is a statement of what the strategy asks, not evidence that the organisation can supply it. It can be wrong when the strategy itself is unclear, and two leaders can translate the same shift into different demands without either being careless.

How Atlas reads it

Demand is the output of the first two moves: name what changed, then translate what must become different. A strategy is not translated until people can tell what they must decide differently on Monday. The demand is then read against present support, area by area, to locate where friction is likely to show.

Questions

A goal states where the company wants to be. Organisational demand states what the organisation must now do well to get there: which decisions move, which capabilities matter more than before, which dependencies must hold. The same goal can create very different demands in two companies with different starting points.

The leaders who own the plan, with the people who will carry it. Writing it only at the top produces a demand no team recognises; writing it only in the teams produces as many demands as there are functions. The test is whether a named team can say what it must decide differently.

Because many strategic shifts ask units to depend on each other in new ways, and that reliance starts low. In their 2015 Harvard Business Review research, Donald Sull, Rebecca Homkes and Charles Sull found that only 9% of managers could rely on colleagues in other functions and units all the time.

Broadly. A 2016 meta-analysis by Stav Fainshmidt and colleagues found dynamic capabilities, the capacity to reconfigure resources and routines, positively related to performance, with a corrected correlation of 0.296. It did not find the link stronger in more dynamic industries, so the evidence supports the mechanism with limits.

It has to be named as a trade-off, with a statement of what is protected. Without that, people carry both demands and resolve the conflict privately, one decision at a time, and the organisation learns nothing about which way it actually chose. The trade-off is part of the demand, not a footnote.