The Change Formula: Diagnose Why Change Stalls

A Formula That Predicts Whether Change Will Hold

Most transformation efforts do not fail for lack of effort. They fail because one necessary ingredient was missing and nobody noticed until momentum was gone. The change formula, usually written as C = D × V × F > R, gives project managers and business analysts a way to spot that gap early. Change happens when Dissatisfaction, Vision and First steps, multiplied together, exceed the Resistance in the system.

David Gleicher first sketched the idea at Arthur D. Little in the early 1960s. Richard Beckhard published it in 1975 and Kathie Dannemiller simplified it into the form practitioners use today. The letters have moved over the decades, the logic has not.

Why the Change Formula Multiplies Instead of Adds

The single most useful property of the change formula is that the left side multiplies rather than adds. If Dissatisfaction, Vision or First steps is zero, the entire left side collapses to zero, and no quantity of the other two will move the organization past its resistance. A change does not stall because one factor is weak. It stalls because one factor is absent.

This reframes the usual conversation. When a rollout loses steam, leaders tend to ask how to push harder on what is already working. The formula asks a sharper question: which of the three factors has dropped to zero, and why.

Reading the three factors

Dissatisfaction is the felt sense that the current situation is no longer acceptable. Without it, people have no reason to spend energy on anything new, however elegant the plan. Vision is a concrete picture of the target state, specific enough that someone can tell whether a decision moves toward it or away from it. First steps are the credible, visible actions available right now, the ones that remove the objection that nobody knows where to begin.

Each factor fails in a recognisable way. Vision without first steps produces cynicism, because people believe in the destination but see no road. First steps without vision produce busywork, activity that consumes budget and points nowhere. And either of those without dissatisfaction produces nothing at all, because comfortable people do not change.

Applying the Diagnosis to an Agile Transformation

Consider a company two years into an agile transformation that has quietly plateaued. Teams hold the ceremonies, the boards are up, and yet nothing important moves faster than before. Running the formula turns a vague sense of disappointment into a specific finding.

Dissatisfaction is often present, developers and customers alike feel the old delivery pace, so that factor is not zero. Vision is frequently the culprit. Ask ten managers what a successful agile organisation looks like here and you get ten different answers, which means the shared picture is missing. First steps may exist on paper but be blocked in practice, because the first genuinely agile decision would require someone senior to give up a reporting line. When you locate the zero, you know where to spend the next quarter.

Resistance comes down when a left-side factor goes up

Change programmes spend enormous energy fighting resistance directly, through communication campaigns and workshops designed to win people over. The formula suggests this is often misdirected. Resistance sits on the right side of the inequality, and you rarely reduce it by attacking it. You overcome it by raising a factor on the left, most often the one that has fallen to zero. A team that can see a credible first step stops resisting a vision it previously found abstract.

Using the Formula in Practice

The formula is a heuristic, not an equation you solve with real numbers. Its value is the discipline it imposes: before launching another initiative to rescue a stalled change, name each factor and rate it honestly as present, weak or absent.

A short example shows how quickly this pays off. A project manager inherits a process change that three previous attempts failed to land. The file is full of resistance-management artefacts, stakeholder maps, objection logs, a communication calendar, and none of it worked. The formula reveals why. Dissatisfaction was high, everyone hated the old process. Resistance was real but ordinary. The missing factor was First steps: every proposed action required sign-off from a committee that met monthly, so nobody could take a visible step between meetings. The fix was not more persuasion. It was delegating one small decision so a team could act that week.

A business analyst can run this diagnosis in an afternoon of stakeholder conversations. If Vision scores zero, the answer is a facilitated session to build a picture everyone shares. If First steps score zero, the answer is to find one small, safe, visible action and remove whatever blocks it. Change that holds is rarely the product of pushing harder. It is the product of noticing which ingredient went missing and restoring it before the effort runs out.