Why Digital Adoption Software Issues Are Really People Problems
Software adoption fails when the focus stays on tools and ignores people. Discover the root causes of digital adoption issues and how to solve them...
Force field analysis helps organizations map driving and restraining forces before implementing change. Learn how it works, how to apply it, and where it
Force field analysis is a decision-making tool that maps the forces driving and restraining a proposed change, so leaders can act on the right pressure points before a transition begins. Developed in the 1940s by social psychologist Kurt Lewin, the method identifies driving forces that push toward change and restraining forces that push against it. When the driving forces outweigh the restraining ones, change becomes viable. When they do not, the analysis shows exactly where to intervene. Organizations use it widely in change management planning to anticipate resistance and make informed decisions.
Force field analysis is a structured framework for evaluating the competing forces that influence any proposed organizational change. Kurt Lewin, who also created the three-stage Unfreeze-Change-Refreeze model, designed it to help leaders visualize why a situation stays stable and what it would take to shift it. The core idea is that the current state of any system is held in equilibrium by opposing forces. Change happens only when that equilibrium is deliberately disrupted.
Lewin's force field analysis rests on two categories of force:
Lewin embedded this concept in his three-stage change model, which moves through unfreezing (preparing the organization), changing (implementing new behaviors), and refreezing (stabilizing the new state). Force field analysis is most useful in the unfreezing stage, where understanding the balance of forces shapes the entire approach to the transition.
The primary objective is to give decision-makers a clear, visual picture of what is working for a change and what is working against it, before resources are committed. Specifically, the analysis helps organizations:
A well-executed field force analysis translates a complex change situation into a manageable action plan, which is why it remains a standard component of a successful change management strategy.
Conducting a force field analysis follows a repeatable three-step process. Using a force field analysis template, whether a whiteboard diagram or a spreadsheet, helps keep the exercise structured and inclusive.
Define the proposed change clearly at the top of the template, then list every force that supports it on one side and every force that opposes it on the other. Engage stakeholders from multiple functions to avoid blind spots. Driving forces might include regulatory requirements, competitive pressure, or efficiency goals. Restraining forces might include low digital literacy, limited budget, or distrust of leadership.
Assign a numerical score to each force, typically on a scale of 1 (weak) to 5 (strong). Total both sides. If the restraining forces score higher, the change is unlikely to succeed without deliberate intervention. This scoring step makes the balance of power visible and gives teams an objective basis for setting priorities.
Focus on the forces where action will move the score most. Practical options include:
"Nobody resists change; everybody resists change pushed by others. So change has to come from oneself."
Force field analysis applies to any situation where a deliberate change is being considered. Two common organizational examples illustrate the method in practice.
Example 1: Implementing a New Software System
When a company introduces a new PLM (Product Lifecycle Management) software, the force field analysis might look like this:
| Driving Forces | Score | Restraining Forces | Score |
|---|---|---|---|
| Reduced operational costs | 4 | Employee resistance to new tools | 4 |
| Improved cross-team collaboration | 4 | High training costs | 3 |
| Cloud accessibility | 3 | Risk of workflow disruption | 3 |
| Integration with existing systems | 3 | Technical implementation complexity | 2 |
The scores are close, so the team would focus on reducing employee resistance through structured onboarding and in-app guidance to tip the balance toward adoption.
Example 2: Transitioning to a Remote or Hybrid Work Model
Driving forces include increased flexibility, reduced real-estate costs, and access to a wider talent pool. Restraining forces include productivity concerns, collaboration difficulties, and cybersecurity risks. The analysis guides investment decisions: if cybersecurity scores high as a restraining force, that is where budget and training effort should go first.
Force field analysis is valuable, but it works best when its limitations are understood and addressed with complementary tools.
| Advantages | Limitations |
|---|---|
| Provides a clear visual map of competing forces | Scoring is subjective and depends on data quality |
| Supports structured, evidence-based decisions | May oversimplify highly complex change situations |
| Encourages proactive resistance management | Does not account for forces that emerge during implementation |
| Useful for communicating change rationale to stakeholders | Requires genuine stakeholder input to be meaningful |
To address these limitations, organizations often pair force field analysis with tools such as stakeholder mapping, risk registers, or the ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) model to build a more complete picture of the change landscape.
A common example is a company implementing new software. Driving forces include cost savings, improved efficiency, and cloud accessibility. Restraining forces include employee resistance, high training costs, and workflow disruption. Each force is scored by strength, and the team develops actions to amplify driving forces and reduce restraining ones.
A SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis evaluates an organization's overall strategic position across four categories. Force field analysis focuses specifically on a single proposed change, mapping the forces that support or resist it. SWOT is broader and strategic; force field analysis is narrower and action-oriented around a defined change goal.
Kurt Lewin, a social psychologist, developed force field analysis in the 1940s as part of his work on organizational change. The model holds that any situation is held in balance by competing driving forces (pushing for change) and restraining forces (resisting change). To achieve change, leaders must either strengthen driving forces, weaken restraining forces, or both.
First, define the proposed change clearly. Second, list all driving forces that support the change and all restraining forces that oppose it. Third, score each force on its strength, typically on a scale of 1 to 5. Fourth, total the scores on each side to see which outweighs the other. Finally, develop specific actions to reinforce the strongest driving forces and reduce the most significant restraining forces.
Software adoption fails when the focus stays on tools and ignores people. Discover the root causes of digital adoption issues and how to solve them...
From Foundation to ITIL Master, discover every ITIL certification level, what each requires, and how the full Information Technology Infrastructure...
SaaS tool fatigue overwhelms employees and drains IT budgets. Learn what causes it, how to spot the NRR zombie syndrome, and four strategies to fix...