Force Field Analysis is a structured method for identifying the forces that support a proposed change and the forces that resist or restrain it.
The method is useful when a technically sound improvement still depends on behavior, resources, policy, capability, or stakeholder support.
The objective is not to label people as for or against. The objective is to understand the conditions shaping the change.
Define the proposed change
Start with a specific change. “Improve maintenance” is too broad. A clearer statement might define exactly what work will move, who will perform it, and by when.
A precise change makes the forces easier to identify.
Identify driving forces
Driving forces may include customer need, safety improvement, leadership support, financial benefit, employee frustration with current work, available technology, or regulatory requirement.
These are conditions that make the change more likely to succeed.
Identify restraining forces
Restraining forces may include lack of skills, workload, unclear ownership, fear of job impact, system limitations, capital constraints, conflicting measures, or previous failed changes.
Stakeholder Analysis can help identify which groups experience these forces and why.
Avoid treating resistance as a personality problem
A restraining force may be rational. Operators may resist a new inspection task because the standard is unclear, there is no time in the cycle, tools are missing, or responsibility conflicts with policy.
Understanding the barrier produces better countermeasures than telling people to embrace change.
Reduce restraining forces first
Teams often focus on more communication, pressure, incentives, or leadership messaging. Sometimes the better approach is removing the barrier by simplifying the method, providing training, changing conflicting metrics, improving tools, clarifying decision rights, or piloting the change.
Change Management is stronger when implementation addresses actual barriers rather than only communication frequency.
Score only when useful
Some teams assign relative strength scores to each force. That can help prioritize discussion, but the numbers should not create false precision.
The important output is understanding which forces matter, which are controllable, which need mitigation, and which assumptions need evidence.
Connect to Nemawashi
Nemawashi can help build alignment before a formal decision. Force Field Analysis can identify where that dialogue is most needed.
For example, a restraining force such as “Maintenance believes operators will miss early failure signs” suggests a need for joint discussion and perhaps a pilot.
Revisit after implementation begins
Forces can change. A successful pilot may reduce uncertainty. A new workload issue may create resistance. The analysis should be updated when the implementation environment changes materially.
Common mistakes
Defining the change vaguely, labeling individuals as restraining forces, using scores without evidence, trying only to increase pressure rather than remove barriers, ignoring legitimate operational concerns, and never revisiting the analysis are common mistakes.
Practical sequence
- define the proposed change.
- identify driving forces.
- identify restraining forces.
- understand evidence behind each force.
- identify controllable forces.
- prioritize important barriers.
- reduce restraining forces where practical.
- strengthen useful support.
- test the change.
- revisit the analysis as conditions evolve.
The practical lesson
Force Field Analysis helps teams see that change success depends on more than the quality of the idea. Improvement becomes easier when the system removes the forces that make the new behavior difficult.