The Problem with Central Planning and Outdated Organisational Myths

Every year, senior leaders gather to decide what the organisation will do next.

They review dashboards, compare forecasts, establish targets, assign budgets and turn their conclusions into a detailed plan. The presentation looks coherent. Responsibilities appear clear, milestones have dates and the coming year seems unusually manageable.

Then the plan meets reality.

Customer behaviour shifts. A supplier fails. Teams discover hidden dependencies. New regulations appear. Employees encounter practical problems that were invisible in the planning room.

Instead of revisiting the assumptions behind the plan, the organisation may demand greater compliance. More reports are requested, more approvals are added and local adaptations are treated as failures of discipline.

The problem is not that organisations plan. They need direction, budgets, standards and coordination.

The problem begins when a small group at the centre assumes it can know enough to prescribe, in detail, how everyone else should respond to changing conditions.

What Central Planning Means Inside an Organisation

Central planning does not include every decision made by senior leadership.

Some choices must be central because they affect the entire organisation. Leaders need to establish strategic priorities, allocate major investments, protect legal and ethical standards, and resolve conflicts between business units.

Central planning, as used here, refers to something narrower:

Detailed operational authority remains at the centre even when the knowledge needed to make those decisions exists closer to the work.

This model often rests on several assumptions:

Senior leaders can see the whole organisation.
Detailed plans create control.
Standardisation is always more efficient.
Accountability requires approval from above.
Decentralisation produces disorder.
Changing reporting lines changes how work happens.

These beliefs are attractive because they promise consistency and predictability. They also underestimate how much valuable information is local, incomplete and constantly changing.

Economist Friedrich Hayek described a broader version of this knowledge problem in The Use of Knowledge in Society. He argued that relevant knowledge is dispersed among individuals rather than available to one directing authority in a complete and integrated form.

A company is not the same as a market. Organisations have formal authority, shared objectives and reporting systems that markets do not. Hayek’s argument therefore cannot determine the correct structure of a business by itself.

It does, however, highlight the cost of assuming that local knowledge can always be collected, simplified and transferred upward without losing important context.

Myth 1: Senior Leaders Can See the Whole Organisation

Executives often possess the broadest organisational view.

They can see financial constraints, competitive pressures, investment priorities and dependencies that may be invisible to individual teams. That perspective is valuable, but breadth is not completeness.

Frontline employees may understand:

Why customers abandon a process
Which policies repeatedly delay work
Where systems fail under real conditions
Which unofficial workarounds keep operations functioning

As this information moves upward, it is summarised. Details are removed, unusual cases are grouped together and uncomfortable findings may be softened.

By the time senior leaders receive a presentation, a complicated local problem may have become a single red, amber or green indicator.

The centre sees the organisation through reports. Local teams experience it through actual interactions, constraints and trade-offs.

Effective organisational design must combine two types of knowledge:

Strategic knowledge: overall direction, investment, risk and organisation-wide priorities
Local knowledge: customer behaviour, technical realities, workflow constraints and changing conditions

The view from the top is wider. The view from the edge is often sharper.

Myth 2: A Detailed Plan Creates Control

A plan can improve coordination. It can also create the illusion that uncertainty has been removed.

Useful plans identify:

Desired outcomes
Available resources
Major dependencies
Known risks
Immediate actions
Review points

They become dangerous when following the plan matters more than responding to evidence.

Management scholar Henry Mintzberg drew an important distinction between formal planning and strategic thinking in The Fall and Rise of Strategic Planning. Planning relies on analysis: breaking objectives into steps, formalising them and describing their expected consequences. Strategic thinking also requires synthesis, intuition and creativity.

A plan begins turning into a liability when:

Targets remain fixed after their assumptions become false.
Teams hide information that threatens an approved commitment.
Deviations require several levels of permission.
Reporting activity becomes more important than results.
Forecasts are treated as promises rather than estimates.

Budgets, schedules and forecasts should not be abandoned. They should be treated as working hypotheses.

A responsible plan explains what the organisation intends to do, what assumptions support that intention and what evidence would justify changing course.

When Centralisation Is Necessary

The alternative to excessive central planning is not universal decentralisation.

Some decisions need central control because their consequences extend across teams, locations or business units.

Centralisation may be appropriate when:

A decision creates major legal, safety or ethical risks.
Several units must coordinate their actions closely.
An investment affects the entire organisation.
Shared infrastructure requires consistent standards.
Local incentives could harm customers or other teams.
Resources must be moved between competing priorities.
A crisis requires a rapid, unified response.

Research on coordination and organisation design shows why no universal rule works. Using data from managers at a large retailer, researchers found that volatile local conditions were associated with greater decentralisation when coordination needs between units were low. When those coordination needs were high, the same volatility could favour greater centralisation.

The design question is therefore not whether centralisation or decentralisation is generally better.

It is:

Which decisions depend most on local knowledge, and which require organisation-wide coordination?

Different decisions inside the same company may need different answers.

Myth 3: Standardisation Is Always More Efficient

Standardisation can reduce confusion, cost and unnecessary risk.

Organisations need consistency in areas such as:

Safety procedures
Financial controls
Legal requirements
Data protection
Cybersecurity
Shared technical interfaces

The mistake is assuming that every difference is wasteful.

Customers, locations, products and working conditions are not always interchangeable. A procedure designed for an average situation may perform poorly in many real situations.

Consider a national retailer that introduces one returns process for every store. Head office specifies the required documents, questions employees must ask and refund levels managers may approve.

The policy appears consistent. In practice, stores sell different products, encounter different fraud risks and operate with different staffing and technical constraints.

Local managers begin creating unofficial exceptions to keep the process workable. Head office sees the variation, interprets it as poor discipline and introduces more rules.

The organisation ends up standardising its response to problems caused partly by excessive standardisation.

A better principle is:

Standardise what must remain consistent. Decentralise what must respond to context.

The difficult part is deciding which category each decision belongs to.

Myth 4: Accountability Requires Permission from Above

Many organisations hold teams responsible for outcomes while withholding the authority needed to influence them.

A manager may be accountable for customer satisfaction but unable to change a broken process. A project leader may own a deadline without controlling staffing or priorities. A local team may carry a revenue target while pricing and product decisions remain entirely centralised.

When every meaningful choice requires approval, employees learn to:

Escalate problems instead of solving them
Wait for instructions when conditions change
Protect themselves through documentation
Follow weak decisions rather than challenge authority
Treat approval as more important than results

Real accountability requires:

A defined outcome
Authority over relevant decisions
Access to useful information
Clear spending and risk boundaries
Transparent measures
A process for reviewing results

Research on decentralisation, hierarchies and incentives treats delegation as a balance between local information, incentives and coordination. People close to the work may understand the situation better, while central leaders may be better placed to manage dependencies and organisation-wide consequences.

Accountability does not require permission for every action.

It requires clarity about who decides, which limits apply and how the decision will be evaluated.

Myth 5: Decentralisation Means Everyone Does Whatever They Want

Poorly designed empowerment often sounds like this:

“You own the problem now. Work it out.”

The team receives responsibility but no clear authority, shared data, resource access or practical boundaries. When the experiment fails, leadership concludes that decentralisation does not work.

That is not decentralisation. It is organisational abandonment.

Effective distributed decision-making needs:

A shared purpose and strategic priorities
Defined decision domains and resource boundaries
Reliable information and outcome measures
Non-negotiable policies
Clear escalation rules
Coordination mechanisms between teams

Research from the MIT Center for Information Systems Research describes four decision guardrails: purpose, accessible data, minimum viable policies and appropriate resource allocation. These constraints are intended to give teams room to act while keeping their choices aligned with company-wide interests.

The centre still has important responsibilities. It establishes direction, protects critical standards, supplies shared capabilities and resolves conflicts that cross organisational boundaries.

Teams decide how to pursue agreed outcomes within those conditions.

Decentralisation is not the absence of management. It is the deliberate distribution of decision-making.

Myth 6: Changing the Organisational Chart Changes the Organisation

Companies frequently announce reorganisations.

Departments receive new names. Teams move under different executives. Reporting lines are redrawn and new leadership roles appear.

A few months later, employees discover that little has changed.

The same people control the budgets. The same committees approve decisions. Information travels through the same channels. Teams remain dependent on one another in ways the official chart does not show.

An organisational chart describes reporting relationships. It rarely explains how work actually moves.

Meaningful organisational design must address:

Who makes which decisions
Where information is available
How funding is allocated
What teams own from beginning to end
How teams exchange services and knowledge
Which dependencies create delays
How performance is measured
Which behaviour receives recognition

The Team Topologies framework focuses on the flow of value, team responsibilities and explicit interaction modes. It distinguishes focused collaboration, X-as-a-Service relationships and facilitation rather than allowing every dependency to become an undefined working arrangement.

Moving boxes on a chart will not transform an organisation unless decision rights, incentives and team interactions move with them.

How Information Becomes Distorted

Central planning often becomes detached from reality through ordinary information loss rather than deliberate incompetence.

A local problem may travel through a hierarchy like this:

A frontline employee notices that customers are struggling.
A supervisor summarises several examples.
A manager removes details to make the issue easier to present.
A department head translates it into existing performance measures.
Executives receive a brief explanation and approve a standard response.
The response travels back down the hierarchy.
Local teams quietly modify it because the official version is impractical.

The final report may show that the policy was successfully implemented. Senior leadership may never learn that its apparent success depended on unreported local adaptations.

The organisation loses twice.

It first makes a decision using incomplete information. It then fails to learn how the work was actually accomplished.

Over time, leaders may develop a false impression that central policies work exactly as designed, while employees learn that making a plan appear successful is safer than revealing how much adaptation it required.

A Better Alternative: Distributed Planning

The alternative to rigid central planning is not an organisation without a plan.

It is a system in which planning occurs at several levels and decisions are placed near the knowledge needed to make them.

1. Set a clear central direction

Leadership should define:

Organisational purpose
Strategic outcomes
Major priorities
Non-negotiable constraints
Acceptable risk
Resource boundaries

Direction should be clear enough to guide decisions without prescribing every action.

2. Distribute operational judgment

Teams close to customers, systems and local conditions should decide how to achieve agreed outcomes within their boundaries.

Responsibility must be accompanied by usable authority.

3. Make decisions and results visible

Local authority should not create organisational blindness.

Teams should share:

Assumptions
Forecasts
Important decisions
Experiments
Results
Emerging risks
Lessons relevant to others

Leaders can then review outcomes and adherence to boundaries without dictating every method in advance.

4. Define decision rights

For important recurring decisions, clarify:

Who makes the final choice
Who contributes evidence
Who must be consulted
Who needs to be informed
What requires escalation
When the decision will be reviewed

MIT CISR defines governance partly through the allocation of decision rights and accountabilities: who has authority to make important choices and who is responsible for their consequences.

Ambiguous empowerment creates conflict. Explicit decision rights create usable autonomy.

5. Coordinate through clear interfaces

Teams need predictable ways to exchange information, request services and manage shared dependencies.

Not every interaction should require an executive decision or recurring meeting. Shared standards, internal services and escalation routes can provide coordination without constant central intervention.

6. Move authority when conditions change

Decision rights do not need to remain permanently centralised or decentralised.

An emergency, growing risk or new dependency may justify temporary central control. When circumstances stabilise, authority can move closer to the work again.

Organisational design should respond to the situation rather than defend one structure as an ideology.

A Practical Example: Redesigning a Returns Policy

Consider a retailer trying to improve customer returns.

Under a centrally planned model, head office creates one complete process. Every store receives the same script, approval levels, documentation requirements and targets.

The process soon encounters problems:

Product categories carry different fraud risks.
Some stores have specialist staff and others do not.
Local systems have different limitations.
Certain rules unnecessarily frustrate customers.
Managers create informal exceptions to prevent avoidable conflict.

Head office interprets the variation as poor compliance and introduces more controls.

Under a distributed model, the centre defines:

A consistent customer promise
Legal requirements
Fraud and financial limits
Required data collection
The result the organisation wants to improve

Store teams can adapt implementation within those boundaries. Their results are compared, useful approaches are shared and harmful variations are corrected.

This does not mean every store should invent a completely different policy. Excessive variation could confuse customers or create unfair treatment.

The company may therefore centralise the customer guarantee and financial boundaries while allowing stores to adapt staffing, communication and workflow.

The objective is not maximum local freedom. It is placing each decision at the level best equipped to make it responsibly.

Questions to Ask About Your Organisation

A company may be more centrally planned than its leaders realise.

Ask:

Do decisions move upward even when the relevant knowledge exists lower down?
Are teams responsible for outcomes they cannot meaningfully influence?
Does bad news become less specific as it approaches senior leadership?
Can employees respond to changing conditions without seeking several approvals?
Are plans revised when their assumptions fail?
Are unofficial workarounds essential to normal operations?
Do reorganisations change decision rights or only reporting lines?
Are shared standards protecting coordination, or merely preserving control?

The answers reveal more about the operating model than the organisational chart does.

Direction Without Remote Control

Central planning is appealing because it promises order. It suggests that enough data, expertise and authority at the top can make the organisation predictable.

But organisations operate through people responding to changing customers, technologies, constraints and information.

No central group can know everything. No local team can understand every organisation-wide consequence.

Strong leadership recognises both limits.

It establishes direction, protects essential standards, resolves major trade-offs and builds systems through which information can travel. It also gives people close to the work enough authority to use what they know.

The alternative to central planning is not an organisation without direction.

It is an organisation in which direction is shared, knowledge can travel and decisions are made close enough to reality to remain useful.