QCE Business - Unit 4 - Transformation of a business
Lewin, Kotter and Force Field Analysis | QCE Business
Compare Lewin's change model, Kotter's change model and force field analysis for QCE Business transformation.
Updated 2026-05-18 - 4 min read
QCAA official coverage - Business 2025 v1.3
Exact syllabus points covered
- Explain change management theories or models, including Lewin and Kotter.
- Explain force field analysis as an analytical tool.
- Analyse the relationship between Lewin and Kotter change management models and transformation.
- Analyse a business in post-maturity using force field analysis.
Lewin's model describes change as unfreeze, change and refreeze. Unfreeze means preparing the business to leave old habits by explaining the need, challenging assumptions and reducing resistance. Change is the transition where new behaviours, systems or structures are introduced. Refreeze means embedding the new approach through policies, culture, training, rewards and performance measures. The model is simple and useful for explaining broad phases of transformation.
Original Sylligence diagram for business force field.
Kotter's model
Kotter's model is more detailed. It is commonly summarised as creating urgency, building a guiding coalition, forming a vision, communicating the vision, removing obstacles, creating short-term wins, sustaining acceleration and anchoring change in culture. The value of Kotter is that it highlights leadership, communication and momentum. It is useful when transformation is complex and involves many stakeholders.
Comparing Lewin and Kotter
Lewin gives a clean three-stage structure. Kotter gives a sequence of leadership actions. They are not enemies. Kotter can be used inside Lewin's broad phases: urgency and coalition help unfreeze; vision, obstacle removal and short-term wins support change; anchoring change supports refreezing. A strong response selects the model that best explains the case rather than reciting steps.
Force field analysis
Force field analysis compares driving forces that push change with restraining forces that resist it. Forces can be scored by strength. A transformation is more likely to succeed if driving forces outweigh restraining forces or if management reduces resistance. Driving forces may include competition, legislation, technology, customer demand and leadership vision. Restraining forces may include cost, fear, culture, lack of skills, poor communication and stakeholder distrust.
Using force field analysis in evaluation
Force field analysis should lead to action. If resistance is mainly lack of skills, training is more useful than threats. If resistance is cost, staged implementation or finance options may matter. If resistance is cultural, leadership and communication are central. The tool is strongest when it identifies which forces management can influence and which are external constraints.
In a written response, name the forces precisely and connect them to likely behaviour. "Employees resist change" is too broad. "Experienced sales staff may resist the new customer relationship management system because they fear lower commission during the learning period" is more useful because it points to training, phased targets and communication. Likewise, a driver such as "competition" should be tied to evidence, such as a rival offering faster delivery, lower prices or a stronger online channel.
Summary table
| Model/tool | Focus | Best use | | --- | --- | --- | | Lewin | Broad phases of change | Simple transformation explanation | | Kotter | Leadership sequence | Complex change needing momentum | | Force field | Driving and restraining forces | Diagnosing resistance and feasibility |
How to use this in a response
Start with the business context, not the definition. Identify the stage of the business life cycle, the relevant stakeholder groups, the evidence in the stimulus and the objective of the decision. Then apply the concept to that evidence. A good QCE Business paragraph usually moves from concept, to case evidence, to criterion-based judgement. This is what turns description into analysis and evaluation.
When the question asks you to evaluate, make the trade-off visible. For example, a strategy may be effective because it directly solves the problem, but inefficient because implementation costs are high. Another strategy may satisfy customers but create pressure for employees. Use this tension to justify the recommendation rather than writing that every option is simply good or bad.