Force Field Analysis is a change-planning tool that compares driving forces and restraining forces so teams can strengthen support, reduce resistance, and make implementation more realistic.
Definition
Force Field Analysis is a structured method for evaluating the forces that support or resist a proposed change. Driving forces push the change forward; restraining forces hold the current state in place. The method helps teams decide whether to strengthen drivers, reduce barriers, change the plan, or pause until conditions improve.
The tool is often used in Lean, Six Sigma, change management, project planning, and leadership facilitation because many improvement failures are not technical. They fail because incentives, habits, workload, fear, policy, training, or resources work against adoption.
History
Force Field Analysis is associated with Kurt Lewin’s work on change theory. Lewin framed behavior as the result of forces acting for and against change. The method later became a practical tool in organizational development, quality improvement, and project management.
It remains useful because improvement teams often underestimate restraining forces. A simple visible map of forces can make change risk easier to discuss before implementation.
When to Use
Use Force Field Analysis when planning a process change, new standard work, technology rollout, organizational change, Kaizen follow-up, policy change, or improvement that depends on people changing behavior. It is especially useful when resistance is likely or when previous attempts have failed.
It can also be used during project selection. If restraining forces are overwhelming and cannot be reduced, the project may need a different scope, sponsor, sequence, or support plan.
Step-by-Step
- Define the change. State the proposed future condition clearly.
- List driving forces. Identify customer need, business pressure, leadership support, data, pain points, incentives, or available resources.
- List restraining forces. Identify fear, workload, skill gaps, unclear roles, policy conflicts, cultural norms, system limits, or competing priorities.
- Rate force strength. Use a simple scale to estimate the relative influence of each force.
- Prioritize action. Focus on reducing strong restraining forces, not only adding more pressure.
- Define countermeasures. Add training, communication, resource support, pilot design, policy changes, involvement, or sponsor action.
- Update the implementation plan. Build actions into the project timeline with owners and dates.
- Review during rollout. Reassess forces as adoption begins and new barriers appear.
Examples
- Standard work rollout: Drivers include reduced defects and customer pressure; restraints include time pressure, old habits, and unclear supervisor expectations.
- Software implementation: Drivers include better data visibility; restraints include training gaps and fear of productivity loss.
- Safety change: Drivers include injury prevention; restraints include awkward PPE design and slow material flow.
- Kaizen sustainment: Drivers include visible early results; restraints include no owner, no audit cadence, and conflicting metrics.
Common Pitfalls
- Listing symptoms instead of forces. A force should explain what pushes or blocks behavior.
- Ignoring informal culture. Peer norms and supervisor behavior often matter more than formal policy.
- Trying only to add pressure. Reducing restraining forces is usually more effective than pushing harder.
- No action plan. The analysis must lead to owners, dates, and countermeasures.
- Underestimating workload. People resist changes they do not have time to absorb.
- Using it once only. Forces change as implementation proceeds.