When to use it
Use Force Field Analysis when you know what needs to change but the organisation won't move, when you're facing resistance you can't quite name, or when you've been pushing harder on the same levers with diminishing returns.
Particularly useful for corporate innovators and intrapreneurs in The Test who need to navigate stakeholder dynamics and political resistance before committing to an intervention strategy.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a Force Field Analysis looks like in practice:
What you get
A complete force field map with impact scores, a prioritised intervention list, and a single recommended next action. Reveals which forces are genuinely structural vs. which are political, and names the human dynamics most organisations prefer not to talk about.
Your downloadable report includes the full force field with scores, WAiDE's intervention strategy, and relevant Wade programs for corporate innovators and change leaders.
Foundation
Developed by social psychologist Kurt Lewin in "Resolving Social Conflicts" (1948). One of the most cited frameworks in organisational change management. Used by McKinsey, KPMG, and NHS change programmes, and taught in Wade Institute's corporate innovator programs.
Why it works
Kurt Lewin's field theory was built on a deceptively simple insight: the status quo is not a neutral starting point — it's an active equilibrium, held in place by forces that are pushing in both directions simultaneously. Change fails not because driving forces are too weak, but because restraining forces go unaddressed. Lewin proved that reducing restraint is typically more effective than increasing drive, because adding more driving force often increases restraining force in response — the organisational equivalent of Newton's third law.
This reframe is counterintuitive for most managers, who instinctively respond to change resistance by pushing harder — more communications, more executive sponsorship, more urgency. Force Field Analysis redirects attention to the other side of the ledger: what specifically is generating the resistance, and can it be reduced or removed? The most productive interventions are often not the most visible ones. They involve quietly addressing a mid-level manager's fear of loss, or resolving a technical concern that's been politely avoided, rather than sending another all-staff email.
Lewin also introduced the concept of "unfreezing" — the idea that before change can happen, the equilibrium itself must be destabilised. Force Field Analysis is partly a diagnostic of whether unfreezing has occurred: if restraining forces still dominate, the organisation hasn't yet accepted that the status quo is no longer viable. That acceptance, not the change plan itself, is often the real work of change leadership.
The mechanism: Visualising forces on both sides of the change creates shared language for a conversation that is otherwise politically difficult. When the restraining forces are named explicitly — including the political ones — they can be addressed rather than politely avoided. The map doesn't guarantee change will succeed; it makes the honest conversation about why it might not both possible and productive.
Frequently asked questions
How do I score the forces — isn't that subjective?
Scoring is inherently qualitative, but that's not a weakness. The value of assigning 1-5 scores is not precision — it's prioritisation. Once forces are scored, you can direct energy toward the highest-scoring restraints rather than the most convenient ones. WAiDE will help you calibrate scores by asking what evidence supports each rating. The score is a hypothesis; what matters is the conversation it generates about relative weight and credibility.
What's the difference between a restraining force and just a risk?
Risks are potential future events — things that might happen. Restraining forces are active in the present — forces that are already working against the change. The distinction matters because they require different responses. A risk gets a mitigation plan. A restraining force needs to be understood, reduced, or worked around right now. In practice, some restraining forces are people — individuals or groups whose interests are threatened by the change — which is why they're often the hardest to name honestly.
Should I focus on increasing driving forces or reducing restraining forces?
Lewin's research consistently found that reducing restraining forces is more effective, and his field theory explains why. Increasing driving force (more urgency, more directives, more resources) often increases restraining force in response — resistance hardens when people feel pushed. Removing or reducing a restraint, by contrast, allows existing driving forces to move the system without triggering defensive reactions. Start with the restraining forces, particularly the political and relational ones.
How do I handle restraining forces that are people — colleagues or stakeholders who oppose the change?
Name them as the force, not as individuals. "Loss of budget control for the finance team" is a restraining force that can be addressed. "Dave from finance is obstructive" is a personality attribution that closes down strategic options. Once the force is named accurately, you can ask: what would reduce it? Often the answer involves understanding what the resisting party stands to lose, and finding a way to address that loss — either by involving them, protecting their interest, or making the case that the status quo is more threatening than the change.