Conditions Before Change: Before You Ask People to Change, Examine What Must Be True

Organizations spend enormous effort deciding what needs to change.

A new strategy. A new technology. A different operating model. A restructuring. A new process. A shift in leadership expectations.

Then attention turns quickly to implementation.

How will we communicate it?

How will we train people?

How will we drive adoption?

How will we manage resistance?

Those questions matter. But there is a set of questions that should come first:

What must be true for this change to work?

Do those conditions exist today?

If they do not, which ones can we change before asking people to adapt?

Change Collaboration introduced this idea as Conditions Before Change in its September 25 article for OCM practitioners.

This companion article applies the concept to a different decision: how leaders can examine the environment receiving a change before treating adoption, resistance, communication, capability, or willingness as the problem.

The idea is simple.

A change does not enter an empty organization.

It enters a system that already has priorities, incentives, workloads, leadership behaviors, histories, assumptions, capabilities, relationships, and constraints.

Those conditions matter.

Readiness is important, and decades of research support its importance.

Bryan Weiner's organizational readiness research describes readiness in terms of shared commitment to a change and shared confidence in the organization's ability to implement it. Readiness is influenced by factors including resources, task demands, and situational conditions.

More recently, HBR published an article recommending that leaders evaluate a team's appetite, capacity, and capabilities before rolling out a new strategy. That is useful guidance.

But Conditions Before Change asks a broader question.

Readiness asks whether people and the organization are prepared to execute a change.

Conditions Before Change asks whether the conditions surrounding the change support the intervention in the first place.

A team can be capable and motivated while the underlying diagnosis is wrong.

Managers can be ready to support a change while existing incentives reward the opposite behavior.

Employees can understand a new process while competing priorities make it nearly impossible to follow.

Leaders can be aligned around an intervention while holding different assumptions about the problem the intervention is supposed to solve.

An organization can therefore be “ready” in several conventional senses and still be attempting change under conditions that undermine the desired result.

Readiness belongs inside the conditions conversation.

It is not the entire conversation.

One of the easiest mistakes in organizational change is to move too quickly from observation to explanation.

Adoption is low.

Therefore, people are resisting.

Managers are not reinforcing the change.

Therefore, they are not committed.

Employees keep using the old process.

Therefore, they need more training.

Those explanations may be correct.

They may also be wrong.

Research on resistance to change has long shown that behavior described as resistance can have multiple causes. People may fear loss, misunderstand what is being asked, disagree with the proposed direction, distrust the process, or be responding rationally to other constraints.

The implication is important:

Behavior does not identify its own cause.

Before selecting an intervention, leaders should distinguish among four things:

What we know: What the available evidence actually demonstrates.

What we think: Our interpretation of that evidence.

What we are assuming: Things we are treating as true without sufficient evidence.

What we do not yet know: Information that could materially change the decision.

That distinction sounds simple.

In practice, it can fundamentally change the intervention.

If low adoption is caused by conflicting performance expectations, additional training will not resolve it.

If managers lack capacity, another communication campaign will not create time.

If employees understand the change but believe leadership will abandon it within six months, explaining the rationale again addresses the wrong problem.

A well-executed intervention against the wrong diagnosis is still the wrong intervention.

Research on absorptive capacity provides another useful lens.

Organizations differ in their ability to recognize, assimilate, and apply new knowledge. Existing capabilities and prior knowledge affect what an organization can absorb.

That has an obvious implication for transformation.

The same technology, process, strategy, or operating model can enter two organizations and encounter very different environments.

Imagine two companies implementing the same enterprise platform.

The first has clear priorities. Leaders agree on what the technology is intended to change. Managers have capacity to support new behaviors. Old work is being retired as new work is introduced.

The second installs the same platform successfully.

But managers retain their existing workloads. Business units interpret the purpose differently. Previous systems remain available. Performance measures continue rewarding old behavior.

The technology may be identical.

The conditions are not.

The outcome should not be expected to be identical either.

This is why Conditions Before Change is not a judgment about whether the solution is good.

It is a question about the relationship between the solution and the system receiving it.

Conditions will differ by organization and by intervention. This is not a universal checklist.

But four questions can expose important gaps before they become implementation problems.

Start with evidence.

What has been observed?

What evidence supports the diagnosis?

What alternative explanations could also account for what we are seeing?

What information would change our conclusion?

Evidence-based management has long argued that better decisions require leaders to separate evidence from convention, assumption, and intuition.

That principle becomes particularly important during change because once an intervention gathers momentum, questioning the original diagnosis becomes harder.

Before asking whether people are ready for the solution, ask whether the organization has sufficient evidence that it is solving the right problem.

Every intervention carries assumptions.

If a new operating model depends on faster cross-functional decisions, decision rights must support that behavior.

If a transformation requires managers to coach employees differently, managers need the authority, capability, clarity, and capacity to do it.

If a new technology depends on people abandoning an old workflow, systems and incentives cannot continuously pull them back toward the old one.

Make those dependencies explicit.

Ask: What has to be true for this to work?

Then test whether those things are actually true.

Organizations approve initiatives separately.

People experience them collectively.

A technology implementation, cost-reduction program, restructuring, regulatory change, leadership transition, and AI rollout may each have a rational business case.

Employees do not experience five business cases.

They experience five simultaneous changes competing for the same attention and capacity.

That distinction matters increasingly as organizations manage multiple transformations at once.

Conditions Before Change therefore asks leaders to look beyond the initiative itself.

What else is happening?

What work is stopping?

What priorities conflict?

What capacity actually exists?

The question is not whether another change is important.

It is whether the organization can absorb it under the conditions that exist now.

Not every condition is controllable.

Leaders cannot eliminate market uncertainty.

They cannot always change regulatory deadlines.

They cannot guarantee that people will support every decision.

But leaders influence a great deal.

They influence priorities.

Resources.

Decision rights.

Incentives.

Leadership behavior.

Sequencing.

Communication.

Participation.

What is measured.

What stops.

What continues.

Conditions Before Change does not require perfect conditions.

It requires leaders to distinguish between conditions they must accept and conditions they are responsible for shaping.

Two recent HBR articles illustrate how close this issue is to current executive concerns.

In August 2026, Steven Morris argued that leaders should assess appetite, capacity, and skillset before rolling out a strategy.

In the September–October 2026 issue, Evgeny Kaganer and Christoph Loch argued that transformation should be treated as a learning journey because fixed, top-down programs can become misaligned as their environments change.

Both point toward a larger reality:

The environment surrounding a change is not background noise. It is part of the change itself.

Conditions Before Change extends that reasoning.

The question is not only whether people are ready.

It is not only whether the transformation can adapt over time.

It is whether leaders have sufficiently examined the conditions surrounding the intervention before asking the organization to absorb it.

The shift is subtle but consequential.

Instead of: How do we get people to adopt this?

Ask: What conditions will make the intended behavior possible?

Instead of: Why are people resisting?

Ask: What else could explain what we are seeing?

Instead of: Are we ready to launch?

Ask: What must be true before we launch?

Instead of: What change-management activity do we need?

Ask: What does the evidence say is actually preventing the desired outcome?

These are not semantic differences.

They can lead to entirely different decisions.

Sometimes the answer will be communication.

Sometimes training.

Sometimes leadership alignment.

Sometimes more capacity.

Sometimes a different sequence.

And sometimes the evidence may suggest that the intervention itself needs to change.

Organizations cannot study themselves into certainty.

Markets move.

People behave unpredictably.

New information appears.

Transformation always carries risk.

The purpose of Conditions Before Change is not to eliminate uncertainty before action.

It is to prevent avoidable uncertainty from being mistaken for unavoidable uncertainty.

That means examining what is known.

Making assumptions visible.

Testing plausible competing explanations.

Identifying the conditions the intervention depends on.

And changing the conditions leadership can influence before asking people to carry the consequences.

Organizations have become increasingly sophisticated at designing transformation.

The next opportunity is to become equally deliberate about the environment into which transformation is introduced.

Readiness matters.

Capacity matters.

Leadership alignment matters.

Evidence matters.

Organizational context matters.

But none of those elements exists independently.

Together they help answer a more fundamental question:

Have we created the conditions under which this change has a reasonable chance to work?

That is the question behind Conditions Before Change.

Before asking people to change, examine what must be true.

Then determine whether it actually is.