IB Business Management HLTopic 2 — Organisational StructurePaper 1, 2 & 3Core skill | Diagrams~10 min read
Reading Different Organisation Charts
Businesses draw themselves in a handful of standard shapes: tall, flat, grouped by function, by product, or by region. Exam questions rarely say “this is a flat structure” — they describe one and expect you to recognise it. This page teaches you to read the shape, then argue about it.
📘 What you need to know
Tall structures have many levels and narrow spans, and tend to be centralised with a long chain of command.
Flat structures have few levels and wide spans, tend to be decentralised, and give staff more autonomy.
By function groups people by what they do — finance, marketing, operations, HR. It is the most common structure.
By product groups people around a product or project, so each one has its own team.
By region groups people by geography, which suits businesses trading in several countries.
None of these is “correct”. The best structure depends on size, spread, the market and how fast the business must react.
Tall against flat
Take the same group of employees and you can arrange them two very different ways. Nothing about the people changes; only the number of layers above them.
Tall structures are common in large organisations with complex operations, such as government departments and universities. Flat structures are typical of small firms and start-ups.
Tall structure
Clear hierarchy — everyone knows their role and who to ask.
Specialisation develops within each department.
Promotion steps exist, which motivates people to stay.
But decisions are slow, passing through many layers.
But communication gets distorted between top and bottom.
But more managers means a bigger wage bill and more bureaucracy.
Flat structure
Faster decisions — fewer people to go through.
Better communication between the top and the front line.
More autonomy, which can raise motivation and innovation.
But role ambiguity is common when the hierarchy is unclear.
But fewer promotions are available, so ambitious staff leave.
But staff take on several roles, which risks overload and burnout.
WORKED EXAMPLE
A warehouse employs 64 floor staff. Compare a structure with a span of control of 4 with one using a span of 8, assuming each layer supervises the layer below and there is one director at the top.
Option A: span of 464 ÷ 4 = 16 supervisors16 ÷ 4 = 4 managers, then 1 directortotal = 64 + 16 + 4 + 1 = 85 staff in 4 levelsOption B: span of 864 ÷ 8 = 8 supervisors, then 1 directortotal = 64 + 8 + 1 = 73 staff in 3 levelsOption B: 12 fewer staff and one level shorterCheaper, and instructions reach the floor faster. The risk: each supervisor now watches 8 people, so new or untrained staff get less help.
Grouping by function
This is the most common structure of all. Employees are grouped by the job they do, so the finance people sit with finance people and the marketers sit with marketers.
The danger with functional structures is that departments lose sight of the business as a whole. Marketing promises a delivery date that operations was never asked about.
Grouping by region
Once a business trades in several countries, geography usually wins. Each region gets its own management, so decisions can reflect local customers, local law and local culture.
Regional structures let a business respond to local customers while head office still sets the overall strategy. The cost is duplication — three regions may each run their own HR team.
Grouping by product
Here the business builds a team around each product or project, so that team can focus on one thing. A large food company might give each major brand its own group of people pulled from marketing, finance and production.
When a firm keeps its functional departments and lays product teams across them, it has a matrix structure. That is common enough, and awkward enough, to deserve its own page — it is covered next.
Structure
Groups people by
Best suited to
Main weakness
By function
The job they do
Single-product businesses of any size
Departments become silos
By product
The product or project they serve
Firms with several distinct brands
Duplication of effort across teams
By region
Where they are based
Businesses operating in several countries
Costly duplication and possible loss of consistency
🤔 How to decide which structure a case study is describing
Ask what the department names have in common. If they are jobs (finance, HR, operations), it is functional. If they are things the firm sells (snacks division, drinks division), it is by product. If they are places (North America, Asia-Pacific), it is regional. Then check the number of layers between the boss and the front line to decide whether it is tall or flat. Two quick questions, and you have named the structure.
A common Paper 2 trap: the stimulus describes a firm growing from 12 staff to 200. That is almost always a question about a flat structure that no longer works, so extra levels are needed — and about the staff who resent losing their direct line to the founder.
💡 Exam tip
Name the structure using the case study’s own words before you evaluate it. That secures the application mark early.
Tie the shape back to the terms. Tall means narrow spans and a long chain of command; flat means wide spans and a short one.
Growth changes the answer. A flat structure that suited 15 people usually breaks at 150.
Mention duplication whenever regional or product structures come up. It is the cost most students miss.
Use motivation as a link. Structure affects promotion chances, autonomy and communication, all of which feed into how motivated staff are.
If asked to draw a chart, keep it simple and label it. Neat boxes, clear lines and named roles get the marks; artistry does not.
⚠ Common mix-ups
Flat does not mean small. Some large firms deliberately run flat structures with very wide spans.
Tall is not automatically bureaucratic. It becomes bureaucratic when the layers plus the rules start slowing decisions.
By product is not the same as by function. Grouping by brand is not grouping by job.
Regional structures are not always decentralised. Head office can still control strategy, pricing and branding.
Do not list advantages without applying them. “Faster decisions” only earns marks when you say what decision, in what business, and why speed matters there.
Levels of hierarchy are not departments. Three departments side by side is still one level.
Up next: Flexible and Project-Based Structures — matrix teams, adapting to external change, and Charles Handy’s shamrock organisation.
Want this explained one-to-one?
Book a free session with an experienced IB Business Management tutor and get your trickiest topics made simple.
