You are viewing a free preview of this lesson.
Subscribe to unlock all 17 lessons in this course and every other course on LearningBro.
Spec mapping: AQA 7138 Unit 3.2.1 — People Management (refer to the official AQA specification document for exact wording). This lesson develops organisational structure at A-Level depth — the canonical structural types (functional, divisional / product, regional, matrix, project), the tall-vs-flat dimension and its span-of-control logic, the centralisation-vs-decentralisation dimension, the diagnostic question of which structure fits which business, the team-effectiveness analytical layer that Annex 8 model #a5 (Hackman) opens, and the evaluative framework an examiner expects on a 9-mark Assess question.
Connects to:
An organisational structure defines how activities — task allocation, coordination, decision-making and supervision — are arranged to deliver corporate strategy. Structure shapes six load-bearing organisational properties:
Chandler's classic insight — structure follows strategy — is the foundational A-Level lens. A business that changes strategy (e.g. diversifies into new product lines) without changing structure typically experiences the strategic transition as friction; the existing structure cannot deliver what the new strategy requires. Equally, a structure imposed without the strategy to justify it (e.g. a matrix in a stable single-product business) creates complexity without payoff.
Definition: Organisational structure is the formal arrangement of roles, reporting relationships, decision rights and resource allocations through which a business converts strategic intent into operational delivery.
A functional structure groups employees by specialism — marketing, finance, operations, people, sales, IT — with each function led by a senior manager reporting to the CEO.
| Strengths | Weaknesses |
|---|---|
| Economies of scale in specialist expertise within each function | Silo mentality — departments optimise for their own KPIs |
| Clear career progression within each function | Slow cross-functional coordination; communication friction |
| Easy to manage and control with defined functional responsibilities | Difficult to scale when the business diversifies |
| Efficient for single-market, single-product businesses | Innovation suffers when functions do not collaborate |
Functional structures are most commonly found in small-to-medium-sized businesses operating in a single market, and in larger businesses whose product range is narrow (e.g. a UK regional law firm).
A divisional structure organises the business into semi-autonomous divisions, each responsible for a product line, brand or business unit. Each division typically replicates the functional layer internally (its own marketing, operations, finance team).
| Strengths | Weaknesses |
|---|---|
| Each division focuses on its specific product / market — responsiveness | Duplication of functional resources across divisions — higher cost |
| Easier to measure performance of individual products / brands | Internal competition between divisions over resources |
| Promotes accountability — divisional managers own their P&L | Coordination across divisions can be difficult |
| New products / markets can be added as new divisions without disrupting existing operations | Risk of inconsistent practices and culture |
Divisional structures are typical in large diversified businesses (e.g. Unilever's Beauty & Personal Care, Home Care, Foods & Refreshment divisions) where the product-portfolio breadth makes functional centralisation impractical.
A regional structure organises the business by geographic area — UK, Europe, Asia-Pacific, North America — with each region operating with material autonomy under its own management team.
| Strengths | Weaknesses |
|---|---|
| Allows response to local market conditions, regulation, customer preferences | Duplication of roles and resources across regions |
| Local knowledge improves marketing effectiveness and service | Coordination between regions can be challenging |
| Reduces logistical complexity — regional supply-chain ownership | Difficult to share best practice across the organisation |
| Supports international expansion via dedicated regional leadership | May weaken global brand identity if regions operate too independently |
A matrix structure combines two or more structural axes — typically functional plus project-based or product-based — so that employees report to both a functional manager and a project / product manager. The grid arrangement is the structural signature.
| Marketing Manager | Finance Manager | Operations Manager | |
|---|---|---|---|
| Project A Lead | Marketing specialist on Project A | Finance analyst on Project A | Ops specialist on Project A |
| Project B Lead | Marketing specialist on Project B | Finance analyst on Project B | Ops specialist on Project B |
| Strengths | Weaknesses |
|---|---|
| Brings together cross-functional specialist expertise on projects | Dual-reporting can create confusion and conflicting priorities |
| Encourages cross-functional collaboration and communication | Conflict between functional managers and project managers over resources |
| More flexible — teams can be assembled and disbanded as projects require | More complex to manage — requires strong communication and conflict-resolution discipline |
| Employees develop broader skills across projects | Decision-making can be slow if multi-manager agreement is required |
The matrix is frequently examined because it illustrates the structural tension between specialisation and coordination. It tends to work in consulting firms, technology businesses, and engineering project organisations; it tends to underperform in stable manufacturing operations where dual-reporting friction outweighs the cross-functional benefit.
Independent of the structural type (functional / divisional / regional / matrix), every structure also makes a choice about hierarchical depth. A tall structure has many levels of management, narrow spans of control (each manager supervises few people), and clear progression rungs. A flat structure has few levels, wide spans of control, and greater individual autonomy.
| Aspect | Tall structure | Flat structure |
|---|---|---|
| Levels of hierarchy | Many | Few |
| Span of control | Narrow | Wide |
| Communication speed | Slower; multiple layers | Faster; fewer layers |
| Distortion risk | High (messages pass through many levels) | Low |
| Career progression | Many rungs | Fewer promotion opportunities |
| Management cost | Higher (more managers) | Lower |
| Autonomy | Limited | Greater |
| Risk of manager overload | Lower | Higher |
The modern trend favours flatter structures, driven by demands for speed, flexibility and employee empowerment. Delayering (removing layers of hierarchy) is a common restructuring lever. But flat is not universally better: complex regulated industries (banking, pharmaceuticals) often need more hierarchical depth than flat-structure advocates allow, because the supervisory control function the additional layers provide is non-optional.
A third structural dimension is where decision-making authority sits in the organisation. Centralised structures concentrate decisions at the top; decentralised structures distribute decision rights down the hierarchy.
| Centralisation | Decentralisation |
|---|---|
| Consistent decisions across the organisation | Faster local responsiveness |
| Easier to coordinate strategy | Greater employee autonomy and engagement |
| Slower; concentrated risk | Risk of inconsistency across units |
| Suited to stable environments, cost leadership | Suited to volatile environments, differentiation strategies |
In practice, businesses centralise some decisions (capital allocation, brand strategy, pricing architecture) and decentralise others (local hiring, daily operational choices, customer-service judgement). The structural design question is which decisions are best centralised and which are best decentralised — not a binary choice.
flowchart TD
Strategy["Corporate strategy"] --> Choice["Structural choice"]
Choice --> Type["Type<br/>(functional / divisional /<br/>regional / matrix)"]
Choice --> Depth["Depth<br/>(tall vs flat —<br/>span of control)"]
Choice --> Rights["Decision rights<br/>(centralised vs<br/>decentralised)"]
Type --> Outcome["Operational outcome<br/>(efficiency, communication,<br/>motivation, coordination,<br/>accountability, flexibility)"]
Depth --> Outcome
Rights --> Outcome
Outcome --> Performance["Business performance"]
Performance -. variance .-> Choice
style Choice fill:#1d4ed8,color:#fff
style Performance fill:#15803d,color:#fff
The dotted feedback arrow is the analytically important move: structural-performance evidence over time feeds back into the next structural-design decision. Structures are not designed once and frozen; they evolve as strategy, scale and the external environment change.
Annex 8 model #a5 lists Hackman's model of team effectiveness as a sophisticated concept. Hackman is rarely deployed at A-Level — most candidates default to Belbin or Tuckman — which makes Hackman's model an under-used Top-band differentiator on structure questions.
Hackman's five conditions for effective teams (paraphrased — The Wisdom of Teams and Hackman's later work):
The structural relevance: a structure choice (functional / divisional / matrix) is partly a choice about which Hackman conditions are easy to satisfy. A matrix structure typically struggles with condition 1 (real team) because dual reporting blurs boundaries; a functional structure with strong silos struggles with condition 4 (supportive context) for cross-functional initiatives. A 9-mark Assess answer that names Hackman explicitly and uses one or two conditions to frame the structural-fit analysis earns Top-band sophisticated-concept credit that almost no candidate at this tariff achieves.
The second Annex 8 concept that surfaces naturally on structure questions is Stakeholder vs shareholder approaches (Annex 8 analytical concept #d8). A pure shareholder-return frame on structural design optimises for efficiency, layer-cost reduction and accountability concentration — pushing toward flat, divisional, P&L-led designs. A stakeholder frame weighs the structural impact on employees (engagement, voice, autonomy), customers (consistency of service across units), suppliers (single relationship vs fragmented contact points), and the community (regional employment commitments). Restructuring decisions framed only through shareholder return often miss the stakeholder consequences that later erode the financial case.
A canonical example is a regional restructure that consolidates several local branches into a single regional centre. The shareholder-return case typically shows clear operating-cost savings; the stakeholder analysis surfaces customer-relationship erosion (local presence valued by long-tenure clients), employee-relocation friction, and reduced community visibility. The structural change may still be the right call — but only if the stakeholder consequences are weighed transparently, not hidden behind the shareholder arithmetic.
The choice of structure depends on several diagnostic factors:
| Factor | Influence on structure |
|---|---|
| Size of the business | Larger businesses need more formal structures; small businesses often operate informally |
| Product / service diversity | Diverse product ranges suit divisional; single-product firms suit functional |
| Geographic spread | Multinational operations may need regional |
| Strategy | Innovation-led businesses may favour matrix; cost leadership favours functional centralisation |
| Culture | Collaborative cultures suit flatter, matrix designs; hierarchical cultures suit taller, functional |
| Rate of environmental change | Fast-changing environments require flexible (flat / matrix / divisional) structures |
| Workforce capability | A capable, autonomous workforce can be trusted with wider spans and decentralised authority |
| Regulatory environment | Heavily regulated industries need additional supervisory layers |
There is no single "best" structure. The structural question is one of fit: which structure delivers this strategy, in this market, with this workforce, at this stage of the business's life cycle?
Brightline Software is a hypothetical UK B2B SaaS business that supplies workflow-management software to mid-market manufacturers. Revenue has grown from £4.8m in 2022 to £18m in 2025, headcount from 48 to 172. The business currently operates a functional structure (Engineering, Product, Sales, Customer Success, Marketing, Finance, People) with seven layers between the CEO and a junior engineer. Engagement has fallen from 74 % to 61 % over the past 18 months; mid-tier engineers complain of slow decision-making, especially on cross-functional product launches that require coordination between Engineering, Product and Customer Success. The two founder-directors are weighing two structural options for 2026: Option A — flatten the hierarchy by removing two middle-management layers and widening spans of control, and Option B — strengthen the functional silos by recruiting two additional senior functional heads (a Chief Engineering Officer and a Chief Product Officer) to drive deeper functional specialism. The CFO has flagged that any restructure should improve labour productivity and reduce slow-decision cost.
Figures and company are fabricated for illustrative purposes; not affiliated with any actual business.
Assess whether Brightline Software should flatten its hierarchy or strengthen its functional silos. (9 marks)
Subscribe to continue reading
Get full access to this lesson and all 17 lessons in this course.