In any Six Sigma project, change is inevitable. Whether it’s improving a process, reducing defects, or cutting down cycle time, change is the goal. However, not all change happens smoothly. People resist. Systems push back. That’s where Force Field Analysis comes in.
This strategic tool helps teams identify and balance the forces that drive and resist change. When used correctly, it can turn a failing project into a successful one. In this article, you’ll learn how Force Field Analysis fits into Six Sigma, how to perform it step by step, and how to use it to drive sustainable improvements.
- What Is Force Field Analysis?
- Why Use Force Field Analysis in Six Sigma?
- When to Use Force Field Analysis
- How to Conduct a Force Field Analysis in Six Sigma
- Real-World Example: Force Field Analysis in Action
- Integrating Force Field Analysis With Other Six Sigma Tools
- Tips for Effective Force Field Analysis
- Common Pitfalls to Avoid
- Recommended Tools for Force Field Analysis
- Conclusion
What Is Force Field Analysis?
Force Field Analysis is a change management model developed by Kurt Lewin in the 1940s. He viewed any situation as a balance between two opposing sets of forces:
- Driving forces that push for change.
- Restraining forces that resist change.
To implement a successful change, you must either strengthen the driving forces or reduce the restraining forces.
Here’s a simple visual:
| Type of Force | Definition | Example |
|---|---|---|
| Driving Forces | Promote or support the desired change | Customer pressure, technology upgrades |
| Restraining Forces | Block or resist the change | Employee resistance, legacy systems |
By identifying and addressing these forces, teams can create a roadmap for change that actually works.
Why Use Force Field Analysis in Six Sigma?
Six Sigma focuses on process improvement using data-driven methods. Every Six Sigma project involves change, whether it’s in systems, workflows, or behavior.
But here’s the problem: people don’t like change.
Force Field Analysis helps Six Sigma teams recognize this resistance early. It enables them to develop strategies that increase buy-in and reduce pushback.
Benefits of Force Field Analysis in Six Sigma
| Benefit | Description |
|---|---|
| Visualizes change dynamics | Offers a clear picture of what drives or hinders improvement |
| Enhances planning | Identifies obstacles and success factors before implementation |
| Builds consensus | Engages stakeholders and opens honest discussions |
| Supports DMAIC framework | Fits naturally in the Define, Analyze, and Improve phases |
| Encourages proactive action | Helps develop strategies before issues escalate |
When integrated into the Six Sigma methodology, Force Field Analysis becomes a powerful planning and communication tool.
When to Use Force Field Analysis
Force Field Analysis is not limited to a single point in a project. Use it whenever resistance to change threatens your success.
Here are the best times to apply it:
- During the Define phase to identify stakeholders and concerns.
- In the Analyze phase to explore barriers to improvement.
- In the Improve phase to guide solution implementation.
- When project momentum slows due to internal or external resistance.
You can also revisit the analysis during the Control phase to assess whether new forces have emerged.
How to Conduct a Force Field Analysis in Six Sigma
Force Field Analysis follows a straightforward six-step process. Each step contributes to a clearer understanding of the change environment.
Step 1: Define the Desired Change
Begin with a specific, measurable change goal. This will serve as the foundation of the analysis.
Example Goal:
Reduce product rework by 30% in the final assembly line within 90 days.
Be clear. Vague goals will lead to incomplete or misleading force identification.
Step 2: Identify the Driving Forces
Next, list the factors that support the change. These can be internal or external. Think of what motivates the organization or individuals to pursue the change.
Common Driving Forces:
| Force | Source |
|---|---|
| Customer complaints | External (market) |
| New leadership direction | Internal (management) |
| Potential cost savings | Internal (finance) |
| Regulatory pressure | External (compliance) |
Encourage team members to brainstorm broadly. Use data and customer feedback to support each item.
Step 3: Identify the Restraining Forces
Now identify what stands in the way. These are the barriers that slow down or block change. Again, include both people and systems.
Common Restraining Forces:
| Force | Source |
|---|---|
| Fear of job loss | Internal (workforce) |
| Poor process documentation | Internal (operations) |
| Lack of training | Internal (HR) |
| Legacy software systems | Internal (IT) |
The goal is not to complain but to list factors that you can address with action plans.
Step 4: Score Each Force
Now assign a strength score to each force on a scale from 1 (weak) to 5 (strong). This adds structure and helps prioritize which forces need the most attention.
Example Force Table:
| Force | Type | Strength (1–5) |
|---|---|---|
| Customer dissatisfaction | Driving | 4 |
| Management support | Driving | 5 |
| Employee resistance | Restraining | 5 |
| Training gaps | Restraining | 3 |
| Outdated machines | Restraining | 2 |
This numerical approach makes it easier to see which forces are most influential.
Step 5: Create the Force Field Diagram
Draw a simple diagram to visualize the results. Use arrows pointing toward the desired change.
Diagram structure:
Longer arrows represent stronger forces. This visual helps teams quickly grasp the situation.
Step 6: Develop Action Plans
Now the real work begins. Use the analysis to build targeted action plans. You can either:
- Increase driving forces
- Reduce restraining forces
- Do both
Focus first on forces that scored 4 or 5.
Action Plan Example:
| Force | Action | Owner | Deadline |
|---|---|---|---|
| Employee resistance | Host open Q&A sessions about project impact | Change Manager | Next 2 weeks |
| Training gaps | Launch skill workshops for new assembly procedures | HR | Next 30 days |
| Management support | Share regular updates to sustain executive sponsorship | Project Lead | Ongoing |
These actions should be assigned to specific people with clear deadlines. This creates accountability and ensures momentum.
Real-World Example: Force Field Analysis in Action
Let’s apply Force Field Analysis to a Six Sigma project in a manufacturing setting.
Project Goal:
Reduce production lead time by 20% within four months.
Driving Forces:
| Force | Score |
|---|---|
| Customer delivery complaints | 4 |
| Competitive market pressure | 3 |
| Executive urgency | 5 |
| Expected cost reduction | 4 |
Restraining Forces:
| Force | Score |
|---|---|
| Resistance from middle managers | 4 |
| Complex legacy workflow | 5 |
| Poor data tracking | 3 |
| Limited IT support | 2 |
Total Driving Score: 16
Total Restraining Score: 14
Next Steps:
- Assign a task force to simplify the legacy workflow.
- Offer change management training for mid-level managers.
- Improve tracking with better dashboards.
- Request IT resources to prioritize automation.
In this example, the project team now has a clear plan to increase support and reduce opposition.
Integrating Force Field Analysis With Other Six Sigma Tools
Force Field Analysis works even better when combined with other Six Sigma tools.
| Tool | How It Helps |
|---|---|
| SIPOC | Identifies stakeholder-related forces |
| Fishbone Diagram | Explores root causes behind strong restraining forces |
| Voice of the Customer | Validates customer-related driving forces |
| FMEA | Prioritizes risks from change and restraining forces |
| Control Charts | Monitors outcomes after implementing action plans |
By layering tools, teams gain deeper insights and stronger results.
Tips for Effective Force Field Analysis
To get the most value from this method, follow these best practices:
- Involve stakeholders early. Bring in voices from all affected departments.
- Be honest. Don’t sugarcoat problems or inflate support.
- Keep it visible. Use whiteboards or software to share updates with the team.
- Review often. Revisit the analysis at every major milestone.
- Document decisions. Keep records of each force, rating, and decision path.
Common Pitfalls to Avoid
While Force Field Analysis is simple, it’s easy to misuse. Here’s what to avoid:
| Mistake | Impact |
|---|---|
| Ignoring low-scoring forces | These can grow stronger over time |
| Failing to assign owners | Without accountability, action plans stall |
| Overcomplicating the analysis | Focus on the top 3–5 forces on each side |
| Leaving out frontline employees | You miss practical insights from those doing the work |
Always aim for clarity and action, not just analysis.
Recommended Tools for Force Field Analysis
Here are tools that can support your Six Sigma Force Field Analysis:
| Tool Type | Examples | Why Use It |
|---|---|---|
| Spreadsheets | Excel, Google Sheets | Easy to score, share, and update analysis tables |
| Diagramming Software | Lucidchart, Miro | Great for visualizing force fields |
| Project Management | Trello, Asana, Monday.com | Track progress of force-related actions |
| Six Sigma Software | Minitab, JMP | Integrates with DMAIC, FMEA, and stakeholder tools |
Conclusion
Force Field Analysis is a simple but powerful tool. It helps Six Sigma teams understand what drives or resists change. When used properly, it reduces surprises, builds alignment, and leads to better outcomes.
It fits naturally into the Six Sigma DMAIC framework. By visualizing the forces at play, teams make smarter decisions and create lasting improvements.
