Force Field Analysis

Thinking Tools4.1 Root Causes and the Case for Going Back

Originated by Kurt Lewin (Frontiers in Group Dynamics, 1947).

Lists the forces pushing toward a change and those holding it back, scores each, and points the effort at weakening the strongest restraints.

Forces for and against moving a sales team to a new CRM, scored and balanced

Score each force from 1 (negligible) to 5 (decisive). Driving forces push right, restraining forces push left, and the outlined bar is the net: at the opening scores the restraints win by two. Lower the strongest restraint, then try pushing a driver up by the same amount instead, and compare the tension in the field. Illustrative.

4
3
4
3
5
4
3
4
Driving forces, total
14
Restraining forces, total
16
Net push toward the change
−2
Tension in the field (both totals together)
30
Pushing for the CRMHolding it backPipeline visibilityWeb leads lostSales head backs itBoard wants forecastData entry fearsCommission reportsQuarter-end trainingTop reps feel slowedNet pushPushing for the CRMHolding it backPipeline visibilityWeb leads lostSales head backs itBoard wants forecastData entry fearsCommission reportsQuarter-end trainingTop reps feel slowedNet push

An example

A building-products distributor had bought a new CRM for its forty-person sales team, and four months after launch most reps still kept their pipeline in spreadsheets. The head of sales had sent two reminder emails and announced that commission would depend on CRM data. Usage went up for a week and fell back.

The sales operations manager ran a force field session with six reps. Above the line they listed what pushed toward the change: managers wanted to see the whole pipeline, the old system lost web leads, the head of sales backed the move, and the board wanted a better forecast. Below it they listed what held things in place, and scored both sides. The strongest restraint, at 5, was data entry: reps expected the CRM to eat an hour a day. Commission reports still ran on the old system, which scored 4. The team dropped the next reminder, built a phone screen that logged a call in three taps, and moved the commission report into the CRM. Within six weeks most reps had dropped their spreadsheets.

Why it works

A situation that refuses to change is held in place by forces pushing both ways that happen to balance, and adding force on one side brings more resistance from the other. Leaders who meet a stalled change usually push harder, with mandates, reminders, and incentives, and each push raises the tension without moving the line much.

Listing the restraints by name makes the other lever visible. Removing a restraint shifts the balance and lowers the tension in the same move, so the change sticks with less effort to hold it there. Scoring both sides keeps the discussion honest: a team that has to put a number on each force cannot treat resistance as one vague mood, and the strongest specific restraint is usually where the work should start.

The thinking behind it

Kurt Lewin Kurt Lewin, a German-American psychologist and a founder of social, organizational, and applied psychology, set out the idea behind force field analysis in Frontiers in Group Dynamics (Human Relations, 1947). His field theory treats a situation as held in balance by forces driving toward a change and forces restraining it. A level of behavior, such as a team's output or its use of a new tool, stays where it is because the two sets of forces offset each other, and it moves only when the balance between them shifts.

How to run it

  1. State the change as an end state. Write what will be true when the change is done, specific enough to check: most reps log every call in the CRM.
  2. List the driving forces. Include the people, pressures, and benefits pushing toward it, and say who holds each one.
  3. List the restraining forces. Name each one specifically, such as lost status, a broken workflow, or a bad memory of the last rollout; resistance in general cannot be worked on.
  4. Score every force from 1 to 5. Score as a group and argue about the large gaps, since the arguments surface what each force really is.
  5. Total both sides. If the totals are close the situation is unstable, and small events will tip it either way.
  6. Pick two or three moves, most aimed at restraints. Ask for each strong restraint what would make it weaker, and prefer that to another push.
  7. Give each move an owner and an expected effect. Rescore after the move to see whether the force really fell.

Where it goes wrong

The most common failure is a list of restraints written as attitudes: people resist change, the culture is not ready. Nobody can weaken a mood. Spot it when a restraint has no obvious owner or fix, and ask what specifically people would lose.

The second is treating the scores as measurements. They are a group's judgment, and a total of 14 against 16 does not mean the change is stuck by two units. Use the scores to rank forces and start arguments, then act on the ranking. The third is spending all the moves on drivers because they are easier to announce. If every move adds pressure, expect the restraints to grow to match.

When to use something else

  • COM-B Model. When the change is one specific behavior and the question is whether capability, opportunity, or motivation is missing.
  • Power-Interest Grid. When the restraints are mostly people and the work is deciding how to engage each one.
  • Theory of Constraints. When one bottleneck in a process holds everything back and the forces are not mainly human.

Where it sits in SOLVE eX

Go to the source

  • Frontiers in Group Dynamics, Human Relations, 1947

Back to the catalog