Managing change — AQA A-Level Business

Managing change in AQA A-Level Business examines how businesses respond to internal and external pressures for change, including the reasons for change, the importance of organisational culture, and the role of leadership in overcoming resistance. It also covers models such as Lewin's force field analysis and Kotter's eight-step model, and evaluates the impact of change on stakeholders and business performance.

Managing change is a critical topic in AQA A-Level Business that explores how businesses adapt to internal and external pressures. It covers the reasons for change, such as technological advancements, market shifts, and leadership transitions, and examines how organisational culture and stakeholder interests influence the change process.

Understanding change management is essential because businesses operate in dynamic environments where failure to adapt can lead to decline. This topic equips students with theoretical models like Lewin's force field analysis and Kotter's eight-step model, enabling them to evaluate strategies for implementing change effectively and overcoming resistance.

• →Internal and external causes of change: including new technology, changing consumer tastes, economic conditions, and mergers or takeovers.
• →Lewin's force field analysis: a tool to identify driving and restraining forces for change, and strategies to strengthen driving forces or weaken restraining forces.
• →Kotter's eight-step model: a sequential approach to leading change, from creating urgency to anchoring new approaches in culture.
• →Organisational culture: the shared values and behaviours that can either facilitate or hinder change; Handy's four culture types (power, role, task, person) are relevant.
• →Resistance to change: reasons include fear of the unknown, loss of status, and disruption of routines; strategies to overcome include communication, training, and participation.

• Classifying the change in the case correctly, since an internal reorganisation and an external shift in regulation call for different responses and different budgets.
• Distinguishing gradual from disruptive by the effect on the business model rather than by the size of the spend.
• Building a force field from forces actually quoted in the extract, weighting them, and then saying which restraining force is cheapest to weaken.
• Explaining why the pressure bites now, linking the cause to a stated objective such as protecting margin or holding market share.
• Putting a number on the benefit wherever the case allows, a cost saving, a rise in capacity utilisation, a margin recovered, rather than claiming it is good for morale.
• Naming what doing nothing would cost, since the gain is always measured against the alternative of leaving things as they are.
• Judging against the firm’s position, so a business with weak cash flow and an exhausted workforce values a modest step more highly than a transformation.
• Recognising that the benefit builds over time, so a short term fall in profit is not by itself evidence of failure.
• Linking a specific form of flexibility to the problem in the case, e.g., delayering to solve a cost/speed issue or flexible contracts for seasonal demand.
• Explaining the consequences of a structural change, such as delayering leading to wider spans of control and potential manager overload.
• Using data from a case study (e.g., labour turnover, unit costs) to evaluate whether a flexible model is proving successful.
• Explaining how a specific knowledge management system, like a customer relationship management (CRM) database, enables a firm to adapt its marketing mix more quickly.
• Distinguishing the records a firm holds from the expertise it has built, and identifying which of the two the case business is at risk of losing.
• Connecting better information to a specific decision, reordering stock earlier or pricing a promotion, rather than to vague talk of efficiency.
• Costing the effort, so the systems and the staff time needed to capture expertise appear alongside the benefit claimed.
• Naming the route by which it leaks away: staff turnover, a data breach, or a takeover that carries expertise elsewhere.
• Attributing the opposition in the case to a named source, so a union representative defending jobs is self interest while a long serving engineer doubting the machine is a different reading of the situation.
• Separating people problems from resource problems, since no amount of communication fixes a shortage of finance or a missing skill.
• Explaining the consequence in business terms, lost output, delay, higher labour turnover or a slipped launch date, rather than stopping at unhappy staff.
• Acknowledging that opposition can carry useful information about a genuine flaw in the plan.
• Matching the method to the source of resistance, so involvement answers a different reading of the situation while support answers a low tolerance for upheaval.
• Justifying the choice by the urgency and the power in the case, since a business weeks from running out of cash cannot wait for consensus.
• Costing the method, because facilitation, negotiation and retraining all land in the budget and squeeze the saving the change was meant to deliver.
• Weighing the effect on trust beyond this project, not only whether the change goes through this quarter.

• 💡Questions here often supply a table of internal and external pressures and ask which matters most, so rank them by effect on the objective the case states.
• 💡If you use the force field, draw the conclusion it is built for: removing resistance is usually cheaper and longer lasting than increasing the push.
• 💡These questions are nearly always assess or evaluate, so build both sides and then decide, taking the deciding reason from the case rather than from a textbook.
• 💡Anchor at least one point in a figure from the appendix, because an argument with no evidence rarely climbs into the higher levels.
• 💡When presented with an organisation chart and data (e.g., labour turnover), use both to build your argument. The chart shows the structure (spans of control, layers), while the data reveals the human and financial consequences.
• 💡For 'recommend' questions, justify your choice of one flexibility method over others for the specific business in the case. This comparative analysis demonstrates higher-level evaluation skills.
• 💡This is often examined through a case where a key employee leaves or a rival copies a process, so look for the point at which expertise escapes the firm.
• 💡Analyse questions want a chain, so run from better records to a specific decision to a cost or revenue effect, and stop at a consequence the case supports.
• 💡The extract normally quotes somebody, a supervisor, a union representative, a long serving employee, and that quotation is the evidence for which source to name.
• 💡Assess questions want weight, so say which obstacle would sink the project and which is merely inconvenient, and use the case to justify the ranking.
• 💡The question is usually recommend or evaluate, so pick one or two methods, apply them to the named resistance, and reject the others with a reason drawn from the case.
• 💡Look for the deadline in the extract, because the time available normally decides which of the six is realistic here.
• 💡Always use the case study to illustrate your points. For example, if the case mentions a family-run business, discuss how a power culture might resist change.
• 💡When evaluating, consider both short-term and long-term impacts of change, and the perspectives of different stakeholders such as employees, customers, and shareholders.
• 💡Use specific terminology accurately: 'driving forces', 'restraining forces', 'unfreeze', 'refreeze', 'change agent', 'cultural web', etc.

• Producing a general scan of external factors with nothing drawn from the case, which earns knowledge marks and stops there.
• Treating force field analysis as a head count of items rather than of weighted forces, so one powerful restraint is outvoted by a handful of trivial drivers.
• Calling every large project disruptive, when disruption means a new model that leaves the old one uncompetitive, not simply an expensive change.
• Arguing that a business simply must keep up with its competitors, which is assertion dressed as analysis and scores very little.
• Ignoring the cost of the transition itself, so lost output, retraining and redundancy never appear on the other side of the balance.
• Assuming a workforce absorbs upheaval indefinitely, when repeated reorganisation is a documented cause of higher labour turnover and lost productivity.
• Confusing delayering (removing a management tier) with redundancy among operational staff. The former changes the hierarchy; the latter reduces production capacity.
• Presenting flexible contracts as a purely cost-saving measure, ignoring potential downsides like reduced employee commitment, higher turnover, and inconsistent service quality.
• Stating that organic structures are inherently superior, without recognising that mechanistic structures are often more efficient for businesses in stable markets with standardised production.
• Treating this as a software purchase, when most of the value comes from habits, incentives and training that make staff share what they know.
• Assuming more data automatically improves decisions, which ignores both data quality and the delay that overload causes.
• Forgetting that customer records carry a legal duty, so a breach costs fines and trust as well as the price of the fix.
• Listing all four sources as though each applied equally, instead of choosing the one the extract actually evidences and building on it.
• Treating opposition as a failing of the workforce, which closes off the strongest evaluation available, that the plan itself may be wrong.
• Confusing an obstacle with a cost, so the price of new equipment gets written up as staff resistance.
• Recommending better communication for every situation, which does nothing about a genuine loss of earnings or a missing skill.
• Treating coercion as either always wrong or as costless, when a genuine crisis sometimes leaves nothing else and the bill still arrives later in turnover and mistrust.
• Describing all six methods without choosing one, so the answer explains the model instead of using it on the business named in the case.
• Students often think that all change is planned and proactive; in reality, much change is reactive to external shocks or crises.
• Students may assume that resistance to change is always negative; however, it can highlight flaws in the change plan and lead to improvements if managed constructively.
• Students sometimes confuse Lewin's force field analysis with his three-step model (unfreeze, change, refreeze); the former is a diagnostic tool, while the latter is a process for implementing change.

1. 1Day 1-2: Learn the key reasons for change and the difference between internal and external triggers. Create a table of examples for each.
2. 2Day 3-4: Study Lewin's force field analysis and practice applying it to a real business case, identifying driving and restraining forces.
3. 3Day 5-6: Learn Kotter's eight-step model and create a mnemonic to remember the steps. Apply it to a case study of a well-known business change (e.g., Netflix's shift to streaming).
4. 4Day 7-8: Explore organisational culture and resistance to change. Use Handy's model to analyse how culture affects change implementation.
5. 5Day 9-10: Practice exam-style questions, focusing on evaluation and application. Review mark schemes to understand what earns full marks.

• 📋Multiple-choice questions on reasons for change or definitions of key terms.
• 📋Short-answer questions (4-6 marks) asking to explain a model or concept, e.g., 'Explain how Lewin's force field analysis can help a business manage change.'
• 📋Case study analysis (9-12 marks) requiring application of change management theories to a specific business scenario, often with evaluation.
• 📋Essay questions (20-25 marks) evaluating the effectiveness of different approaches to managing change, requiring a balanced argument and conclusion.