Force Field Analysis (New Feature)

One of the recent additions to Goal Nabber is the Force Field Analysis. It was described as a Change Management technique by Kurt Lewin (1940s) to analyze competing forces. The same principals were described by Benjamin Franklin to balance pros and cons in a Decisional Balance sheet. Thus, two situations where this can be used are decision making and evaluating a desired change.

It is a simple and practical way to list and visualize opposite factors. The approach is the following:

  1. Define the situation to evaluate.
  2. Identify influencing factors distinguishing driving and retraining ones. This can be done separately. However, it often happens that they are identified simultaneously.
  3. Score their intensity based on greater or lesser influence.
  4. Analyze the result. Equal opposing forces and factors point to a status quo. For change to occur, the equilibrium must be disrupted. That can be done either by strengthening the driving factors, or by weakening the retraining factors.
Force field Analysis captured as highlight in Goal Nabber

There are potential weaknesses to be aware of. This is a subjective approach both while identifying and scoring factors. To overcome this, the team involved should be representative of all stakeholders. Stakeholders can be subject matter experts, manager, operators, support agents, change agents, suppliers and customers. Too small a team will not be representative of all perspectives. And, too many (e.g. over 10) will become inefficient. A representative team will provide a better insight to identify the different factors. And in absence of quantified information, it will also result in a richer discussion to determine the influence of the factors. By mitigating the weaknesses, the outcome of the force field analysis will give a better insight into the strongest factors and ones that can be changed.

Voice of Customer

For companies and projects, a critical success factor is to know the customer expectations. First reason is 95% of companies are reaching out to customers. Second reason is best in class VOC perform better. They have a 55% higher retention rate. Their customer support cost decreases 23% year to year. And, they have a greater employee engagement. And, it cost 25 times more to attract new customers then to retain them. In most cases, the objective is to implement changes or improvements that will increase customer satisfaction. Because it is crucial to project success, it is one of Goal Nabber features.

Where and When

VOC is used to understands the customer’s want, needs and requirements. Otherwise, the probability of meeting expectation is greatly diminished. It should be part of the first steps of any project or initiative. It avoids dissatisfaction and wasted effort. During the project, it is a reference for decision making and validating outcomes. Even in “sure” cases, it allows to confirm the alignment with the sponsors, customers and the team.

Customers

There are usually many customers. One distinction is external (e.g. end customers, users, leads, prospects), and internal (e.g. sponsors, business stakeholders, management). When looking at a process, a SIPOC is a good way to ensure that customers have been identified. Before beginning to collect information, check the list of customers. It should have the stakeholders that have influence or are impacted.

Collecting needs and expectations

With the customers identified, the next step is to obtain useful information with the least effort. There are several methods available to gather customer inputs. Interviews, Focus groups, Surveys, Observation, Online reviews are possible methods. Each have their strength and weaknesses. They all need preparation starting with having an idea of the information to gather. One place to start is confirming that the customer has something to gain from the project objective. A combination of open and close questions to understand the why’s and the what’s. While gathering information, keep an open mind. Save statistics and trends for the analysis. Avoid too many, changing or wrong questions. Take negative feedback as an opportunity to improve. Most of all show the customers that you are listening constructively to their feedback.

Customer needs through VOC in Goal Nabber

Analyze

The analysis will depend on the amount and type of information available. It will likely involve different information sources, sorting Needs & Wants, figuring out the reasons. This is about translating verbatim comments and other data into customer requirements. To demonstrate active listening, the outcome should be shared to get acknowledgement or adjustment. This also gains buy in from the stakeholders.

Action

One pitfall that happens too often is to not action the VOC. There is no need to wait for later. It can define criteria the decision making. Objectives can be aligned with customer expectations. Trigger new improvements initiatives and projects. Making these actions visible to the customer will increase their interest and fidelity.