Organisational design

Span of control is the number of subordinates (1) that a manager is directly responsible for or supervises (1).

One benefit is faster communication (Knowledge 1). Because FlowTech's flat structure has few levels of hierarchy, information and decisions pass through fewer layers between its developers and managers (Application 2). This lets FlowTech respond quickly to changing customer needs and technology — a real advantage in fast-moving software — and empowers staff with more autonomy, raising motivation (Analysis 1).

Effect 1 — greater responsibility (positive). Delayering pushes decisions down and widens spans (Knowledge). GrowCo's remaining staff therefore gain more responsibility and autonomy over their work (Application). Using Herzberg, responsibility is a motivator, so their motivation and job satisfaction can rise, improving performance (Analysis).

Effect 2 — insecurity and overload (negative). Delayering also removes jobs and widens managers' spans (Knowledge). GrowCo's staff may feel job insecurity and be overworked as fewer managers cover more people (Application). Using Herzberg, insecurity and poor conditions are hygiene factors that cause dissatisfaction, which could lower motivation and raise stress and turnover (Analysis).

Decentralising decisions could benefit GlobalBev because its bottling, distribution and marketing operations span many different countries. Local country managers, close to their markets, could tailor flavour formulations, SKU ranges and promotional calendars to local tastes, adapt to national labelling and food-safety regulations, and react to regional competitors and distributor networks faster than a distant head office — and the extra responsibility would motivate them (a Herzberg motivator), improving local sell-through and responsiveness in ways a centralised head office cannot match.

However, decentralisation carries risks. It reduces consistency and central control, so local decisions on formulation, packaging or pricing might clash with GlobalBev's global brand and strategy — diluting carefully-built international brand equity. It also relies heavily on the calibre of local managers, and can fragment procurement and duplicate marketing effort across countries, eroding the economies of scale and bulk-buying leverage a global drinks firm depends on.

Whether it is a good move therefore depends on how different GlobalBev's local markets are and how capable its local managers are. For a firm whose portfolio spans diverse markets, some decentralisation clearly fits — but the best approach is usually to decentralise local operations (product mix, promotions, distribution) while keeping brand architecture, core formulation standards and overall strategy centralised, so GlobalBev gains local responsiveness and motivation without sacrificing the brand consistency and scale economies its global position depends on.

Delayering could strip out UrbanCo's management overheads and compress its decision-making cycles, but whether it is the best route to efficiency depends on the trade-offs and alternatives.

The case for delayering. Removing management levels strips out payroll overheads (fewer managerial salaries) and compresses the chain of command, so approvals, information and decisions flow faster with less latency. It can also empower remaining staff with more responsibility (a Herzberg motivator), lifting motivation and productivity. For a growing firm that has accumulated bureaucratic layers as it scaled, a flatter structure can genuinely raise operational efficiency.

The case against / limits. However, delayering widens spans of control, potentially overloading the remaining managers and thinning the supervision and support staff receive — which can harm throughput and quality. It triggers redundancies, damaging morale and creating insecurity (Herzberg hygiene problems) that lower motivation and may raise staff turnover, and it drains the tacit know-how of experienced managers. Alternatives to lift efficiency include investing in automation and workflow systems, re-engineering processes, targeted training, or decentralising decision-making without cutting headcount.

Judgement. On balance, delayering is the best route to efficiency only if UrbanCo genuinely carries surplus management layers and its remaining managers can absorb the wider spans — then it cuts overheads and accelerates decisions with a motivation bonus. But if it leaves managers overloaded and staff insecure, it could worsen efficiency, and process re-engineering or automation might deliver more without the morale damage. So delayering suits a firm that has become over-layered, but UrbanCo should weigh the overhead and speed gains against the overload and morale risks — and consider whether better processes or technology would raise efficiency more safely.

As ScaleUp grows, its structure must support fast decisions, motivated staff and coordination — but the 'most appropriate' structure depends on its size, strategy, markets and people, so there is no single right answer.

The case for a flat, decentralised structure. For a fast-scaling firm, a flat structure with decentralised decision-making has strong appeal. Few levels mean short communication lines and quick responses to change; delegation and empowerment motivate staff (Herzberg motivators) and develop the next tier of managers; and lower management overheads suit a firm watching its cash burn. Pushing decisions down to those closest to the customer cuts decision latency — valuable when ScaleUp is moving fast and needs agility.

The case for more hierarchy and central control. However, rapid scaling also creates a need for coordination and control. Too flat a structure can overload managers with unmanageable spans of control, leave staff under-supported, and produce inconsistent decisions across a growing headcount. Some hierarchy and central control secure a consistent brand, quality and strategy, standardise processes, and clarify accountability as headcount rises. A purely flat, decentralised structure risks operational chaos at scale, especially if ScaleUp's staff are inexperienced.

Evaluation. The most appropriate structure depends on several factors. It depends on size and stage: a small ScaleUp can run flat and informal, but as headcount climbs it needs more structure and standardised processes to coordinate. It depends on strategy and markets: a firm competing on agility and innovation leans flat/decentralised, while one needing consistency and process control (or operating in regulated/quality-critical areas) needs more hierarchy. And it depends on the people: capable, motivated staff thrive with decentralisation, while inexperienced staff need more direction. Crucially, the right structure changes as ScaleUp grows — what fits at 20 employees won't fit at 500.

Conclusion. On balance, the most appropriate structure for ScaleUp is a relatively flat, decentralised structure that preserves agility, short communication lines and motivation, but with enough hierarchy and central control to coordinate its growth — decentralising day-to-day operations while centralising brand, strategy and key standards. There is no permanent answer: ScaleUp should keep its structure as flat as possible for speed and motivation, adding levels, standardised processes and control only as growth genuinely requires them, and review it as it scales. The best structure is therefore contingent — matched to ScaleUp's size, strategy and people, and evolving as the business grows.