Force field analysis is a change management tool that maps the forces pushing toward a proposed change against the forces resisting it. Developed by social psychologist Kurt Lewin in the 1940s, the method gives teams a structured way to score both sides, see whether a change is viable, and decide where to focus effort before committing time and budget. You list the driving forces on one side and the restraining forces on the other, weight each one, and compare the totals. The result is a clear picture that replaces gut feeling with evidence.
That mapping works best when the whole team does it together, and a shared MindMeister map lets everyone add forces at the same time in a brainstorm, then organize and weight them together on the free plan, one of the everyday benefits of mind mapping.
What force field analysis is and how it works
Force field analysis is a change management tool developed by Kurt Lewin in 1951 that maps the forces pushing toward a desired change, called driving forces, against the forces resisting it, called restraining forces. You place the proposed change in the middle, list the driving forces on one side and the restraining forces on the other, then weigh the two sides against each other. The result is a clear picture of the pressures acting on a single decision. Laid out this way, the map doubles as a force field analysis diagram you can revisit whenever the situation shifts.
The core logic is simple.
So to make a change more likely to succeed, you have 3 levers: strengthen the driving forces, weaken the restraining forces, or do both. Lewin's work pointed to a useful bias here. Reducing restraining forces is generally more effective than adding to the driving forces, because removing a blocker clears the path, while adding pressure often just hardens the resistance you already have.
Force field analysis earns its place in 3 situations. Use it before you launch a major change initiative, so you enter with your eyes open. Use it when a change is stalling despite real effort, to find the blocker you missed. And use it when a team needs to build consensus around a decision, because the map gives everyone the same view. In each case, the same simple picture, a change in the center with forces lined up on either side, gives everyone a shared starting point for the conversation.
One honest caveat matters here. Force field analysis is a qualitative tool, not a quantitative one. The strength scores you assign to each force are subjective, and they reflect your team's judgment rather than an objective measurement. That is not a weakness to hide. The scoring is exactly what surfaces disagreement and forces a conversation, so the team ends up with a shared, negotiated view instead of one person's hunch. Treat it as a structured way to think together, not as a scientific formula that hands you the answer. The number on a branch is a prompt for discussion, not a verdict.
How to build a force field analysis in MindMeister
You can build a force field diagram on a whiteboard, but a shared map keeps every force, score and action in one place your whole team can edit, the same reason mind maps for project managers work so well. There is no pre-built force field analysis template in the MindMeister library, so you start from a blank map and build the structure in 4 steps. The example below follows one team deciding whether to migrate all its teams to a new project management tool by Q3.
Step 1: Place the proposed change in the center
Open a blank MindMeister map and put the change in the central node. State it specifically. "Migrate all teams to a new project management tool by Q3" gives you something you can weigh. "Improve our project management" does not, because it is too vague to have clear forces acting on it. The sharper the central node, the sharper the rest of the map, which is the same discipline that makes project planning with mind maps work.
Step 2: Add driving and restraining forces
Add 2 main branches off the center, one labeled Driving Forces and one labeled Restraining Forces. Under each branch, add a sub-branch for every force your team can name. Run this as a silent brainstorm first, the same way you would structure any focused session such as running agile ceremonies with mind maps. Everyone adds forces at the same time without discussion, which keeps louder voices from steering the map and surfaces the honest blockers people might not say out loud. Once the ideas are down, review them together and merge duplicates.
Step 3: Score each force from 1 to 5
Give each force a strength score from 1 to 5 and record it as a note on the sub-branch. A 5 is a powerful force, a 1 is a minor one. Color-code the branches by strength so the strongest forces stand out in a more prominent color. This is the point where your map becomes a real force field diagram, and where the honest debate about scores does most of its work. Record the reason behind each score in the note too, so the team can see why a force earned a 5 and revisit that logic later.
Step 4: Compare the totals and plan actions
Add up each side and compare. If the driving forces clearly outweigh the restraining forces, the change is viable, so focus your energy on maintaining momentum.
Instead, identify which restraining forces you can actually reduce, then add an Actions branch with specific steps for each one. It often helps to run a root cause analysis for identifying blockers on the strongest restraining forces first. Because reducing blockers moves the needle more than adding pressure, this is usually where the real plan lives. If you want a head start on the branch structure, MindMeister offers mind map templates for every project phase you can adapt.
Force field analysis examples
Below are 2 short examples of how the map plays out in practice, one organizational and one product-focused, and you can see more mind map examples for business professionals if you want a wider set.
Organizational change: annual reviews to continuous feedback
A company is weighing moving from annual performance reviews to continuous feedback cycles. The central node states that change. On the driving side sit regulatory pressure (4), employee engagement data showing dissatisfaction with annual reviews (4) and manager training already completed (3). On the restraining side sit HR system limitations (3), manager time constraints (4) and cultural resistance to frequent feedback conversations (5). The restraining forces around manager capacity and culture score highest, so the action plan focuses on reducing those before launch, with lighter-weight check-ins and clear time expectations, rather than on adding more pressure to change. Because the strongest blockers are cultural, the team runs a pilot with 2 departments before any wider rollout.
Product decision: rebuild or iterate
A product team decides whether to rebuild a legacy feature from scratch or keep iterating on the existing codebase. The rebuild sits in the central node. Driving forces include reducing technical debt (4) and improving developer velocity (4). Restraining forces include delivery timeline pressure (5) and customer dependency on the current behavior (4). With the restraining forces slightly ahead, the recommendation is to phase the rebuild behind a compatibility layer, which reduces the timeline and dependency blockers, rather than betting the roadmap on a single big-bang release. That keeps developer velocity moving while the team chips away at the timeline pressure that scored highest.
Force field analysis vs SWOT analysis: when to use each
Both tools analyze the factors affecting a decision, but they answer different questions. A SWOT analysis is broader. It covers internal strengths and weaknesses alongside external opportunities and threats, and it works best for strategic planning when you are still weighing a range of options. A force field analysis is narrower and more action-focused. It zooms in on one specific proposed change and asks a blunt question: do the forces for and against it make this change viable right now, and if so, how do you tip the balance?
That difference tells you which to reach for. Use a SWOT analysis for strategic planning when choosing among strategic directions. Use a force field analysis when you have already chosen a direction and need to understand whether and how to execute it. In MindMeister, both tools use the same branching format, so the real difference is how you frame the central question. Frame it as a broad question about your options and you are running a SWOT, while framing it as a single go or no-go decision turns the same map into a force field analysis.
Map your change forces in MindMeister
