Force field analysis — Organizational Development

Kurt Lewin's force field analysis models any current state as a quasi- stationary equilibrium: a balance between driving forces pushing toward change and restraining forces holding the status quo. Nothing is static; the apparent stability is a stalemate.

Evidence: Weak as a measurement tool, moderate as a principle. The ratings are subjective and the arithmetic is a conversation device. The underlying principle is better supported: behavioral research on friction, defaults, and choice architecture consistently finds that removing barriers changes behavior more reliably and more cheaply than increasing persuasion or incentive. Trust the principle; do not trust the numbers.

Use when: you need to understand why a change has stalled, or to plan a change before launching it.

Do not use when: nothing is holding the status quo in place, which is rare enough to be worth doubting.

The central insight

Most change efforts add driving forces: more urgency, more communication, more incentives, more executive pressure. Lewin's finding is that removing restraining forces is usually more effective, because adding driving force raises tension in the system and provokes counter-pressure.

Push harder and you get compliance plus resentment. Remove the obstacle and you get movement at lower cost.

How to run it

State the change clearly, as a target state, not a slogan.
List driving forces. Rate each 1–5 for strength.
List restraining forces. Rate each 1–5.
Draw them as opposing arrows, sized by rating.
For each restraining force, ask: can we remove it, weaken it, or convert it?
Only then consider adding driving force.

Do this with the people who will be restrained, not about them. The restraining forces list is nearly always wrong when written by leadership alone.

Typical restraining forces

Loss of status, autonomy, or identity.
A reward system that pays for the old behavior.
Genuine capability gaps that nobody wants to admit.
Prior failed changes: "we tried this in 2019".
Physical or technical constraints: rooms, rotas, systems, licences.
Workload — no slack in which to change anything.

The last one is the most common and the least often addressed. People are not resisting; they have no capacity.

Examples by audience

Health care: hand hygiene compliance. Driving forces: audits, posters, professional duty. Restraining forces: dispensers positioned wrong, gloves taking longer, skin damage, understaffed shifts. Moving the dispenser beats another poster.
Software: adopting trunk-based development. Driving: faster delivery. Restraining: a two-hour test suite, a manual approval board, and one person who owns release and likes owning it. Address the test suite first.
Executive: a return-to-office mandate. Driving forces are asserted (collaboration, culture). Restraining forces are concrete (commute cost, caregiving, desk shortage, teams already hired remote). Mandates that ignore concrete restraints produce attrition rather than presence.

Limitations

Subjective ratings; the numbers are a conversation device, not measurement.
Static snapshot — forces change as the change proceeds.
Can produce a comforting list with no owner attached. Assign each restraining force a named owner and a date, or the analysis is decorative.

Questionnaire

A paired, copy-and-use diagnostic instrument for this model: force-field-analysis-questionnaire.