top of page

Fueling Agile Transformation Strategy: The Power of Force Field Analysis

Updated: Jun 13

Agile practices have enabled many organizations to embrace lean processes, fostering flexibility, collaboration, and rapid iteration. However, the path to Agile excellence is not without its challenges. From resistance to change to organizational inertia, navigating these obstacles requires a strategic approach.

My chosen strategic tool is the Force Field Analysis when faced with resistance. It is a dynamic tool that dissects the driving and restraining forces influencing your Agile transformation journey. By meticulously analyzing these factors, you gain invaluable insights into what propels your efforts forward and what holds them back. In the past, I used this tool in leadership workshops to create alignment, make impediments visible, and create a forward action.

A few months ago, I had the privilege of coaching an IT director in the commercial sector whose primary goal was transitioning away from outdated legacy systems. These systems posed significant financial burdens and created numerous internal challenges. Collaborating with my client and a select group of colleagues, we decided to review the existing strategy and collectively conduct a Force Field Analysis.

What we uncovered was eye-opening. Beyond the technical hurdles, we discovered organizational roadblocks and a lack of connections to decision-makers. It became evident that the existing strategy alone would not facilitate the successful adoption of new processes.

Through intensive discussions and actionable insights derived from the analysis, we charted a new course forward. The client's feedback was overwhelmingly positive, and the level of alignment achieved exceeded our expectations. Here are step-by-step instructions and a template for conducting a Force Field Analysis. I hope it proves as valuable for you as it did for my client and me.

Step 1

Identify the vision, opportunity, or goal for change. Describe your proposed change in ten words or less and place it in the center of the template. Some recent examples include migrating legacy systems to the cloud, adopting automated testing, implementing continuous integration and delivery pipelines, enhancing security protocols, and improving user interface design for a better customer experience.

Step 2

Brainstorm the external and internal forces that can support and drive the change. Identifying as many factors as possible that will influence the change is crucial. For example, if the proposed change is to migrate legacy systems to the cloud, the following forces can be included:

  1. Market Competition: Keeping up with industry standards and competitors adopting cloud solutions.

  2. Cost Efficiency: Reducing operational costs through scalable and flexible cloud infrastructure.

  3. Technological Advancements: Leveraging new technologies and innovations that are cloud-native.

  4. Regulatory Compliance: Meeting compliance requirements and ensuring data security and privacy.

When identifying the forces for change, consider asking the following questions:

  • What external pressures are driving the need for this change?

  • Are there technological advancements that support this change?

  • How will this change impact our competitive position in the market?

  • What are the potential cost savings or financial benefits?

  • Are there regulatory or compliance requirements influencing this change?

  • What internal challenges or inefficiencies does this change address?

  • How will this change enhance customer satisfaction or experience?

  • How does this change align with our strategic goals and vision?

Step 3

Brainstorm the external and internal forces against the change. Using the same example of the proposed change to migrate legacy systems to the cloud, the following forces can be included:

  1. Security Concerns: Fear of data breaches or losing control over sensitive information.

  2. Cost of Migration: High initial investment and uncertainty about return on investment.

  3. Resistance from IT Staff: Fear of job displacement or lack of skills for managing cloud infrastructure.

  4. Legacy System Dependence: Reluctance to let go of familiar systems and processes that have been reliable.

Consider asking the following questions to identify forces against change:

  • What concerns or fears might stakeholders have about this proposed change?

  • How might existing organizational culture or resistance to change hinder adoption?

  • Are there financial costs or resource constraints that could impede implementation?

  • What are the potential risks or uncertainties associated with this change?

  • Could this change disrupt current workflows or operations?

  • Could legal or regulatory barriers prevent or delay implementation?

  • How might this change impact employee morale or job satisfaction?

  • Are there competing priorities or initiatives that could overshadow this change?

  • How could this change conflict with existing organizational policies, practices, or norms?

Step 4

Now that both forces are plotted in the template, assign scores to each force. A score of one represents the lowest or weakest influence, while a score of five represents the highest or strongest influence. Assess each force and assign a score based on its impact on the proposed change.

To make this more engaging and visually effective during workshops, I recommend adjusting the arrows on the template to reflect the scores. Longer arrows can indicate higher scores, making it easier to see which forces have the most significant impact.

Step 5

Calculate the total scores for each force and specify them in the template. In this example, the total score against change (18) is higher than that for change (15). This indicates that the proposed change may face significant resistance.

To address this imbalance, having conversations with leadership about strengthening existing forces for change, creating additional forces for change, or mitigating the forces against the proposed change is crucial. By visualizing and scoring these forces, you can better understand the dynamics influencing the proposed change and take informed steps to ensure its successful implementation.

Often, coaches can sense and see resistance to transformation or new organizational changes, but articulating or diagnosing the cause of it is a different story. Force Field Analysis is one of the most effective ways to outline organizational information, making it easy for leadership to understand and see what needs to be done. I always say it is not a coach's job to create the change but to partner with a client to co-create it. Force Field Analysis helps to uncover inside information and facilitates a structured approach to managing change. By visualizing and scoring the forces at play, coaches and leaders can collaboratively identify strategies to bolster support for change and address resistance, ensuring a smoother and more successful implementation process.

Force Field Analysis Template
Download PPTX • 3.18MB

21 views0 comments


bottom of page