Making human resource decisions: improving organisational design and managing the human resource flow — AQA A-Level Business

Organisational design involves structuring a business's hierarchy, span of control, and decision-making to meet its objectives. Managing the human resource flow covers the recruitment, training, retention, and exit of employees to ensure the business has the right people with the right skills at the right time.

This topic explores how businesses structure their workforce and manage the flow of employees from recruitment to exit. It covers organisational design concepts such as hierarchy, chain of command, span of control, and centralisation versus decentralisation, as well as the human resource flow model: recruitment, training, retention, and exit. Understanding these elements is crucial for analysing how businesses achieve efficiency, motivation, and competitive advantage.

In the wider AQA A-Level Business course, this topic links to motivation theories, leadership styles, and operations management. It is essential for evaluating how internal structures and people management affect business performance, and it frequently appears in exam questions requiring analysis and evaluation of human resource strategies.

• →Organisational design: the formal structure of roles, responsibilities, and reporting lines, including hierarchy, chain of command, and span of control.
• →Span of control: the number of subordinates directly supervised by a manager; wide spans create flatter structures, narrow spans create taller structures.
• →Human resource flow: the process of recruiting, training, retaining, and managing the exit of employees to meet business objectives.
• →Labour turnover and retention: turnover measures the rate at which employees leave; high turnover increases costs and disrupts operations, so retention strategies are vital.
• →Centralisation vs decentralisation: centralised decision-making is concentrated at the top; decentralised pushes decisions closer to the customer, affecting speed and motivation.

• Describing the structure through the case, for example that the firm has a separate managing director and sales team for each product range.
• Naming one specific benefit and one specific cost of the structure the firm uses rather than listing features of all four.
• Recognising that a matrix gives an employee two managers, and explaining the conflict over priorities and deadlines that follows.
• Linking structure to strategy, so a business growing by entering new countries has a reason to move to regional divisions.
• Judging fit against size and pace of change, since a structure that suited fifty staff rarely suits five hundred.
• Defining the span of control as the number of subordinates reporting directly to one manager and linking it to the number of layers in the structure.
• Separating the delegated task from accountability, which does not move.
• Explaining why this firm can widen its spans, for example because staff are experienced or because a system now reports performance automatically.
• Using a motivation theorist to explain why pushing decisions downward can raise effort, rather than asserting that staff like having a say.
• Weighing the saving from removing a layer against the loss of supervision and of promotion opportunities.
• Naming the specific change, such as removing a regional tier, rather than writing about reorganisation in general.
• Quantifying the saving where the case allows it, for instance the salaries of the posts that disappear, and setting redundancy payments against it.
• Explaining the effect on the staff who remain, including wider spans, heavier workloads and the insecurity that lifts labour turnover.
• Using Kotter and Schlesinger or Lewin to say how the change should be handled, matched to the type of resistance the case describes.
• Reaching a judgement on whether the structure, rather than the strategy or the product, was causing the problem in the first place.
• Setting forecast labour needs against the labour the firm already expects to have, so the recommendation answers a measured gap.
• Comparing internal and external recruitment on cost, speed and effect on motivation rather than listing recruitment methods.
• Explaining why moving staff to another role may beat cutting posts in this case, for example where the skills transfer to a growing site.
• Recognising the full cost of redundancy, including notice, statutory payments and the effect on those who stay.
• Linking the decision back to a stated workforce objective such as retention or the skills mix the strategy needs.

• 💡Questions pair a structure with a problem in the case, such as slow product launches, so answer the problem rather than the textbook.
• 💡Analyse marks come from a chain that ends at an objective: structure, decision speed, time to market, then revenue.
• 💡For evaluate, weigh the cost of reorganising against the gain, because the chart can be redrawn in an afternoon and the behaviour cannot.
• 💡The command word is usually analyse or assess, so take one design decision and follow it through to an objective rather than defining every term in the list.
• 💡Bring in the pace of change in the market, since a fast moving market is the strongest argument for pushing decisions downward.
• 💡If the case gives staff numbers and layers, use them; working out the average span makes the argument concrete.
• 💡This is high tariff evaluate territory, so decide the conclusion first and select the two arguments that carry it.
• 💡Use a change model as the shape of the answer, not as a name dropped into the opening line.
• 💡Say what would change your mind, for example that delayering is right while demand is stable but dangerous just before a launch.
• 💡Expect a recommend or justify question that hands you two options, so commit to one and explain why you rejected the other.
• 💡Use the timeline in the case, since a short dip in demand argues for redeployment and shorter hours while the permanent loss of a contract argues for cutting posts.
• 💡Finish by linking back to the workforce objective in the extract, because that is where the evaluation marks sit.
• 💡Use specific business examples to illustrate your points. For instance, link a tall hierarchy to a traditional bank versus a flat structure in a tech startup.
• 💡When evaluating, always consider the trade-offs: cost versus motivation, control versus flexibility, short-term versus long-term impact.
• 💡Learn key formulas such as labour turnover and retention rates, and practise applying them to case study data.

• Describing the chart and stopping, so the answer never says what the structure does to the speed or quality of decisions.
• Treating a flat structure and a matrix as the same thing, when one is about the number of layers and the other about who reports to whom.
• Claiming a matrix improves communication with no mention that the same employee now carries two sets of deadlines.
• Assuming the formal chart is what happens, ignoring the informal networks and the culture that decide how quickly anything moves.
• Confusing the span of control with the chain of command, so the answer claims a wide span produces a tall structure.
• Writing that delegation reduces a manager's workload without noting the time taken to train and monitor whoever takes the task on.
• Assuming decentralised decisions always motivate, when handing responsibility to an untrained supervisor produces stress rather than satisfaction.
• Treating central control as old fashioned, when a brand that must look identical in every store depends on it.
• Presenting delayering as pure cost saving, ignoring redundancy payments, lost expertise and the dip in output while the change beds in.
• Naming Lewin and then describing the change without ever using unfreeze, change and refreeze to organise the answer.
• Assuming staff resist out of stubbornness, when the case usually shows a rational fear about workload or job security.
• Recommending a new structure without saying what it costs to get there or how long it takes to work.
• Treating redundancy as an immediate saving, when payments and lost output often make the first year more expensive than doing nothing.
• Describing the stages of recruitment in detail when the question asked whether to recruit at all.
• Assuming training pays for itself without asking whether those trained will stay long enough for the firm to collect the benefit.
• Ignoring process and law, so a recommendation to cut staff never mentions consultation or selection criteria.
• Students often think a wide span of control is always better because it saves money. In reality, it can lead to poor communication and reduced motivation if managers are overstretched.
• Many believe that internal recruitment is always cheaper and better. While it saves on advertising and induction, it limits new ideas and can cause resentment among external candidates.
• Some confuse 'human resource flow' with just recruitment. It actually covers the entire employee journey: recruitment, training, retention, and exit.

1. 1Day 1-2: Learn key terms: hierarchy, chain of command, span of control, centralisation, decentralisation, and human resource flow stages.
2. 2Day 3-4: Create a table comparing wide vs narrow span of control and tall vs flat structures, noting impacts on cost, communication, and motivation.
3. 3Day 5-6: Study recruitment methods (internal vs external) and training types (induction, on-the-job, off-the-job), with pros and cons.
4. 4Day 7-8: Analyse labour turnover and retention, including formulas and strategies to reduce turnover.
5. 5Day 9-10: Practise exam-style questions, especially 6-mark and 9-mark analysis/evaluation questions, using case studies.

• 📋Multiple-choice or short-answer questions on definitions (e.g., span of control, labour turnover).
• 📋Data response questions requiring calculation of labour turnover or retention rates and interpretation of results.
• 📋6-mark analysis questions on how organisational design affects motivation or productivity.
• 📋9-mark evaluation questions on whether a business should change its structure or recruitment approach.