How to do a Force Field Analysis

force field analysis

A force field analysis is a decision making tool which clarifies the advantages and disadvantages of making a decision.  It is an important tool for project managers and executives, and basically anyone who needs to get a firm grasp of the underlying issues before making a big decision.

It’s pretty basic.  In fact, it’s so simple you might wonder why it has a name.

If you are wondering whether to pursue a course of action within in your organization (or anywhere), then force field analysis is for you.  It works like this:

  1. Identify all of the forces which that are working for the change.  i.e. why you would want to do it.  These are called the driving forces.
  2. Identify all of the forces against the change.  i.e. why you would not want to do it.  These are called the restraining forces.
  3. Give each a score.  1 – 10 works pretty good.  Positive for driving forces, negative for restraining forces.
  4. If the score is positive, proceed with the change.
  5. Manipulate the score by managing, controlling, or mitigating each factor, if that is your intent.

Of course, each underlying factor has now been itemized which makes for ease of communication and debate among stakeholders.  Force field analysis is a valuable decision making tool, even if it’s simple.

Example

In the following example, the positives outweigh the negatives, and the decision to undertake the re-design should be made:

force field analysis example

Analysis

I actually did a Force Field Analysis without knowing it a few years ago, when I was deciding whether to quit my job and start my own company.  Now I try to itemize and prioritize each factor (i.e. perform a Force Field Analysis) whenever there’s a big decision to make.

My experience is that many items tend to overlap so it’s important to differentiate between factors that are not mutually exclusive.  For example, in the above example “reduction of warranty expense” could be considered as a sub-item of “increasing sales/profit” and thus too many points are awarded when you include both.

There isn’t really a good way around that. If you want to include warranty expenses in the analysis, you have to make a reduction out of the profit item, or realize the analysis is slightly skewed.

Once the brainstorming is done, each of the items can be analyzed and investigated to see if they can be managed, controlled, or mitigated.  Here’s a quick checklist:

  1. Can the factor be modified?
  2. If so, how quickly, and what would the impact be on its score?
  3. Who are the stakeholders?
  4. Can a trade off be made to mitigate the factor?
  5. Can the factor be controlled using 3rd party methods?
  6. Can it be moved to another department (i.e. out of my decision)?
  7. Will the factor increase or decrease with time?

Origin

Force field analysis was developed by social psychologist Kurt Lewin in the 1940’s.  The name originates from the concept that when the factors pushing for a change overpower the factors opposing it, the change will occur.  To put it another way, when a change makes sense people will begin to push for the change, creating a “force field” for the change.  When the force field pushing for the change overpowers the force field resisting the change, it will occur.

The force field analysis simply itemizes the force field on both sides and breaks it down into it constituent parts.

“May the force be with you”

 

About Bernie Roseke, P.Eng., PMP

Bernie Roseke, P.Eng., PMP, is the president of Roseke Engineering. As a bridge engineer and project manager, he manages projects ranging from small, local bridges to multi-million dollar projects. He is also the technical brains behind ProjectEngineer, the online project management system for engineers. He is a licensed professional engineer, certified project manager, and six sigma black belt. He lives in Lethbridge, Alberta, Canada, with his wife and two kids.

View all posts by Bernie Roseke, P.Eng., PMP

Leave a Reply

Your email address will not be published. Required fields are marked *

*