Decision Method
Force Field Analysis for Teams
Map the forces driving and resisting a change. Rate their strength and see which side wins before you commit.
Last updated: April 2026
What is a Force Field Analysis?
Force Field Analysis is a decision framework developed by social psychologist Kurt Lewin in the 1940s. It is based on the idea that every situation is maintained by a balance of opposing forces: "driving forces" push toward change, "restraining forces" resist it. By mapping and rating both sides, you see whether the balance favors action or caution before you commit resources.
The method adds something a Pro/Con list cannot: strength. Five weak arguments for a change look impressive on a list, but they don't outweigh one strong force against it. Force Field Analysis assigns a strength rating (1-5) to each force, so you can see whether a single powerful restraining force outweighs a dozen minor driving forces. The visual balance indicator makes the net direction obvious at a glance.
The method is widely used in change management, organizational development, and strategic planning. It is part of the standard toolkit in project management frameworks (PMI, IPMA, GPM) and change management models (Kotter, ADKAR). In German business practice, it is known as Kraftfeldanalyse and referenced in change management certifications and consulting methodologies.
When to Use Force Field Analysis
- Before implementing organizational changes (new tools, processes, team structures) to understand whether the forces in favor are strong enough to succeed
- When evaluating whether to adopt a new policy or strategy and you need more than just a list of pros and cons
- During team decision-making to surface hidden objections that people are reluctant to voice openly
- When a decision feels stuck and you cannot explain why, because the blocking forces are invisible or unspoken
- In change management workshops to build buy-in by making supporters and resisters visible
- When you need to manage change in your team and want a structured way to see what is driving vs. blocking the transition
Step-by-step guide
- 1
Define the change clearly
State the proposed change as a specific question: "Should we switch to a 4-day work week?" or "Should we migrate from on-premise to cloud?" Precision matters. "Improve our processes" is too vague to analyze. The question should be specific enough that someone can answer yes or no. If you cannot frame it as a yes/no question, you probably need to break it into smaller decisions first.
- 2
Brainstorm driving forces
List every factor pushing toward the change. Think beyond the obvious business benefits: include employee expectations, market pressure, competitive moves, regulatory requirements, technology trends, and internal motivations. Also include emotional and cultural forces. "The team is burned out and wants something different" is a legitimate driving force. Aim for 5-8 forces. If you have fewer than 3, you haven't thought broadly enough.
- 3
Brainstorm restraining forces
List every factor resisting the change. Be honest about political resistance, not just rational objections. "The VP of Operations will resist because it threatens their authority" is a real restraining force. Include risk, cost, cultural inertia, dependencies on the current approach, stakeholder concerns, and transition effort. The forces that teams are reluctant to name are usually the strongest.
- 4
Rate each force (1-5)
Assign a strength rating to each force. 1 = weak influence, barely matters. 5 = strong influence, could determine the outcome alone. This is where the method separates itself from a plain list. A single restraining force rated 5 (like "client contracts require 5-day availability") outweighs three driving forces rated 2. Have team members rate independently before discussing. Group ratings converge toward safe middle values because nobody wants to be the outlier.
- 5
Analyze the balance and plan action
Look at the total strength on each side. If driving forces dominate, the change is viable. But don't just proceed. Focus your energy on weakening the strongest 2-3 restraining forces rather than adding more driving forces. Removing a strong blocker is more effective than adding motivation. If restraining forces dominate, either strengthen your case or reconsider the timing. The balance indicator shows the net direction and how close the decision is.
Pro tip: Have each team member rate forces silently before revealing results to the group. The first number spoken anchors everyone. Silent independent rating followed by discussion produces the most honest results and surfaces disagreements about force strength that matter for the decision.
Pro tip: Focus on weakening the 2-3 strongest restraining forces rather than adding more driving forces. In practice, removing a blocker rated 5 is more effective than discovering three new driving forces rated 2. Most change programs fail because they pile on motivation instead of removing obstacles.
Pro tip: Include emotional and political forces, not just rational ones. "The CTO feels threatened by this change" is a real restraining force that a pure logic-based analysis would miss. The forces that are hardest to name are usually the most powerful ones.
Pro tip: Revisit the analysis after 2-4 weeks or after a pilot. Circumstances shift, new data emerges, and forces change strength. A force rated 4 might drop to 2 after a successful pilot removes the uncertainty behind it.
Example
A tech company evaluated introducing a 4-day work week:
Driving Forces
- –Employee satisfaction (5)
- –Talent attraction (4)
- –Reduced burnout (4)
- –Environmental impact (2)
Restraining Forces
- –Client expectations (4)
- –Workload compression (3)
- –Management resistance (3)
- –Transition costs (2)
Driving: 15 vs. Restraining: 12. Net: +3 in favor of the change.
Worked Example
A German Mittelstand technology company (200 employees) evaluates introducing a 4-day work week. The leadership team mapped forces during a strategy offsite. Each participant rated forces independently before the group discussed the results.
| Force | Strength | Reasoning |
|---|---|---|
| Employee satisfaction | 5 | Exit interviews consistently cite work-life balance as top concern |
| Talent attraction | 4 | 3 recent candidates chose competitors offering flexible schedules |
| Reduced burnout | 4 | Sick days increased 20% year-over-year, correlated with overtime |
| Productivity research | 3 | Microsoft Japan 4-day trial showed 40% productivity increase |
| Environmental impact | 2 | Reduced commuting, aligns with sustainability goals but not a primary driver |
| Total driving | 18 | |
| Force | Strength | Reasoning |
| Client expectations | 4 | SLA contracts guarantee Monday-Friday availability |
| Workload compression | 4 | Current work volume designed for 5 days, redistribution unclear |
| Management resistance | 3 | Two department heads openly skeptical, worried about control |
| Legal questions | 2 | Labor law implications of changing standard work hours unclear |
| Transition costs | 2 | New scheduling tools, process redesign, client communication |
| Total restraining | 15 |
The Force Field Analysis prevented two mistakes. First, it stopped the CEO from implementing the change company-wide immediately ("the balance is positive, let's go"), which would have violated client SLAs. Second, it showed the team exactly which force to weaken first, turning vague resistance into a specific action item with a timeline.
Force Field Analysis vs Pro/Con List
| Dimension | Force Field Analysis | Pro/Con List |
|---|---|---|
| What it measures | Forces FOR and AGAINST a change, with strength ratings | Arguments FOR and AGAINST, unweighted |
| Key advantage | One strong force can outweigh many weak ones. The strength rating reveals this. | Fast, simple, everyone understands it instantly |
| Visual output | Balance indicator showing net direction and magnitude | Two columns of text |
| Best for | Change decisions where hidden resistance matters | Quick gut-check on 2-3 options |
| Limitation | Only evaluates one proposed change at a time | Doesn't show which arguments matter most |
Use Pro/Con when you need a fast, lightweight evaluation and the arguments are roughly equal in importance. Use Force Field when the decision involves change resistance, political forces, or when you suspect a few strong factors outweigh many weak ones. If your Pro/Con list has items that clearly differ in importance, upgrade to a Force Field Analysis.
Common Mistakes
1 Rating all forces as 3 to avoid disagreement
If every force is rated 3, the analysis tells you nothing. The value comes from differentiation. A client SLA obligation rated 5 is qualitatively different from an employee preference rated 2. Push the team to commit to ratings at the extremes. If everything feels like a 3, the team hasn't been honest enough.
2 Listing only rational factors
Teams naturally focus on business logic: cost, revenue, risk, efficiency. But the forces that actually block change are often emotional or political: fear of losing control, attachment to the current way, interpersonal dynamics, ego. If your Force Field has zero emotional or political forces, you're analyzing the decision on paper, not as it exists in reality.
3 Treating the analysis as a vote
The Force Field is a diagnostic tool, not a democracy. If driving forces score 18 and restraining forces score 15, that does not mean "the change wins 18-15." It means the balance slightly favors change, but strong individual restraining forces could still block it. The goal is understanding, not tallying.
4 Forgetting to act on the restraining forces
Mapping forces without acting on them is just documentation. The most important output of a Force Field Analysis is the action plan: which specific restraining forces will you weaken, how, and by when? Without this step, the analysis sits in a slide deck and nothing changes.
Try the free interactive tool
Use this method right now in your browser. No signup required, with PDF export.
Frequently asked questions
- Kurt Lewin, a German-American psychologist, developed it in the 1940s as part of his work on social psychology and change theory. It remains one of his most practical contributions to management science.
- A Pro/Con list simply counts items. Force Field Analysis adds strength ratings (1-5) and a visual balance indicator, revealing whether a few strong forces outweigh many weak ones.
- Aim for 4-6 per side. Fewer than 3 suggests you haven't explored deeply enough. More than 8 per side dilutes focus. If you have too many, consolidate related forces. 'Employee satisfaction' and 'Work-life balance improvement' can often be merged.
- Yes, but it works best for change decisions (should we do X or not?) rather than choice decisions (which of A, B, C?). For personal decisions involving change, like relocating for a job, the driving vs. restraining forces framework is especially useful because it surfaces emotional factors alongside practical ones.
Related from the blog
Related methods
Pro/Con Analysis
List arguments for and against each option to create a clear basis for discussion. Ideal when the decision is qualitative and you want the whole team involved.
SWOT Analysis
Systematically evaluate Strengths, Weaknesses, Opportunities, and Threats for each option. Gives you the full picture before you commit.
Scenario Analysis
Think through best case, worst case, and realistic outcomes before you commit. Reduces surprises and prepares your team for different results.