What should happen in the first 90 days after a change rollout?

Why these blogs? Most leaders still believe in a quiet trade-off: you can do right by your people and the planet, or you can deliver strong returns, but not both. The data tells a different story. Companies that genuinely serve all their stakeholders don’t just feel better to work for; they outperform the market, attract the best talent, and weather crises far better than their competitors. The Conscious Business approach offers a practical, proven way to turn that “either/or” into a powerful “and”, and it starts with understanding where your organisation stands today.

The first 90 days after a change rollout are the period that most determines whether organisational change actually sticks. A structured post-rollout strategy, focused on visible leadership, early signals of adoption, and honest reflection at the 90-day mark, is what separates lasting change from a well-intentioned initiative that quietly fades. The questions below unpack what that looks like in practice.

Why do so many change initiatives stall after the launch?

Change initiatives stall after launch because the energy and attention that drove the rollout rarely transfers into the day-to-day. Most organisations invest heavily in the announcement and the initial programme, but underestimate what it takes to sustain change once the spotlight moves on. The result is a familiar pattern: early enthusiasm, followed by drift, followed by quiet abandonment.

There are a few consistent reasons this happens. The change was designed at the top but not genuinely owned at the middle and frontline levels. The “why” behind the change was communicated once rather than reinforced continuously. Managers were expected to carry the change forward without being properly equipped to do so. And the organisation moved on to the next priority before the first one had taken root.

There is also a structural issue. Many change programmes are built around a launch event rather than a change journey. The rollout becomes the finish line rather than the starting point. When the workshops end and the communications go quiet, people naturally revert to familiar patterns. This is not resistance in the negative sense: it is simply how human behaviour works under pressure and uncertainty.

What makes this particularly challenging is that the gap between intention and behaviour is rarely visible immediately. Teams may appear to be on board in the weeks following a launch. The real test comes later, when old habits reassert themselves and the change has not yet become embedded in how decisions are made, how people are recognised, and how the organisation actually operates.

What should leaders prioritise in the first 30 days after rollout?

In the first 30 days after a change rollout, leaders should prioritise visibility, listening, and removing early friction. This is not the time for evaluation: it is the time to signal that the change is real, that leadership is present, and that people’s questions and concerns are being heard. The first month sets the tone for everything that follows.

Concretely, this means:

Showing up consistently. Leaders who disappear after the launch send an unintentional message that the change is not a priority. Visible, engaged leadership in the first 30 days builds credibility and confidence.
Creating space for honest conversation. People need somewhere to raise concerns without feeling like they are obstructing progress. Team meetings, one-to-ones, and informal check-ins all serve this purpose.
Identifying and supporting early adopters. Some people will embrace the change quickly. Recognising and amplifying their experience helps others see what adoption looks like in practice.
Removing practical barriers. Often the biggest obstacles to change adoption are not cultural: they are operational. Processes, tools, or structures that make the new way of working harder than the old one will quietly undermine even the best-designed change initiative.

This is also the moment where conscious leadership matters most. Leaders who are self-aware, genuinely curious about how the change is landing, and willing to adapt their approach based on what they hear will build far more trust than those who simply manage the rollout from a distance.

How do you measure whether change is actually taking hold?

You measure whether change is taking hold by looking at behaviour, not just sentiment. Surveys and pulse checks have their place, but the most reliable signals are observable: are people making decisions differently, having different conversations, and using the new ways of working in their daily practice? Behaviour is the evidence; everything else is an indicator.

That said, a combination of qualitative and quantitative signals gives a fuller picture. Useful things to track in the post-rollout period include:

Whether managers are actively reinforcing the change in their team conversations and decisions
Whether the language and framing of the change are appearing naturally in meetings and communications, rather than only in formal contexts
Whether people at different levels of the organisation can articulate why the change matters, not just what it involves
Whether early friction points are being raised and resolved, or quietly ignored
Whether the change is showing up in how performance is discussed, how people are recognised, and how resources are allocated

It is worth being honest about what these signals cannot tell you. Employee engagement scores can look positive while real adoption is still shallow. People often say what they think is expected of them, particularly in the early stages. The more useful question is not “do people support this change?” but “is this change visible in how we actually work?”

For organisations working within a broader purpose and culture framework, this is also a moment to check whether the change is genuinely aligned with the organisation’s values, or whether it is creating tension that has not yet been named.

What should happen at the 90-day mark to sustain momentum?

At the 90-day mark, the most important thing is an honest, structured review, not a celebration of the launch, but a genuine assessment of what has changed, what has not, and what needs to shift to sustain momentum. This review should involve people at multiple levels of the organisation, not just the project team or senior leadership.

A useful 90-day review addresses three things:

What is working and why. Understanding what has genuinely taken hold, and what made that possible, helps you reinforce and replicate those conditions elsewhere.
Where adoption is lagging and what is driving that. Lagging adoption is rarely about unwillingness. It usually points to a structural barrier, a gap in capability, or a misalignment between the change and how the organisation actually operates.
What the next phase of the journey looks like. Sustained change requires continued attention. The 90-day mark is a natural point to reset expectations, recommit to the process, and make any necessary adjustments to the approach.

This is also the moment to be honest about whether the change has been embedded in the systems and structures that shape daily behaviour: performance conversations, decision-making processes, onboarding, and team rituals. If the change only lives in a set of principles or a communication campaign, it will not last.

For senior leaders and change managers, the 90-day review is not a sign-off. It is a signal that the real work of change management, building genuine change adoption across the organisation, is ongoing. The first 90 days after a change rollout are not the end of the story. They are where the story actually begins.

The pressures aren’t slowing down: disengaged teams, tightening regulations like the CSRD, and AI that amplifies every crack in a weak foundation. The companies that thrive won’t be those who wait: they’ll be the ones who build a stronger foundation across purpose, leadership, culture, stakeholders, and business model before they’re forced to. The good news is you can see exactly where you stand, and where your biggest opportunities lie, in just a few minutes. Take the Conscious Business Scan here.

Conscious Business | Get in touch

Frequently Asked Questions

How do we get middle managers on board when they weren't involved in designing the change?

Start by acknowledging the gap honestly — if middle managers weren’t part of the design process, they need a different kind of onboarding than the rest of the organisation. Give them dedicated space to ask hard questions, understand the reasoning behind decisions, and shape how the change lands in their specific teams. Managers who feel like messengers rather than owners will unintentionally undermine adoption, even when they’re trying to support it. Equipping them with context, tools, and genuine autonomy over implementation is one of the highest-leverage investments you can make in the post-rollout period.

What's the difference between resistance to change and a legitimate signal that something needs adjusting?

Resistance and signal can look identical on the surface — both show up as pushback, disengagement, or slow adoption. The distinction lies in what’s driving the behaviour. Resistance is typically rooted in fear, uncertainty, or a lack of trust in the process; a legitimate signal points to a real flaw in the change design, a structural misalignment, or an unintended consequence that leadership hasn’t yet seen. The most effective way to tell the difference is to listen with genuine curiosity rather than a defensive posture. If the same concern is surfacing independently across different teams or levels, it’s almost certainly a signal worth taking seriously.

How do we prevent change fatigue when our organisation is running multiple initiatives at the same time?

Change fatigue is rarely about the volume of change itself — it’s about the absence of coherence and prioritisation. When people can’t see how different initiatives connect, or when they’re asked to absorb new ways of working without anything being simplified or removed, exhaustion sets in quickly. The most practical antidote is ruthless clarity about what matters most right now, communicated consistently by senior leaders. Where possible, integrate overlapping initiatives rather than running them in parallel, and be honest with your teams about sequencing — people can handle a lot when they trust that leadership has a clear and considered plan.

What are the most common mistakes organisations make when conducting a 90-day review?

The most common mistake is treating the 90-day review as a performance report rather than a learning conversation — presenting data that confirms the change is on track rather than genuinely interrogating what’s working and what isn’t. A close second is limiting the review to the project team or senior leadership, which produces a partial picture at best. The most useful 90-day reviews include honest input from frontline teams, surface uncomfortable truths without blame, and result in concrete adjustments to the approach rather than a reaffirmation of the original plan.

How do we know if the change has been embedded in our culture, or just in our communications?

The clearest test is whether the change shows up in decisions and behaviours when no one is watching or measuring it. If the new ways of working only appear in formal contexts — town halls, performance reviews, or when leadership is present — it’s living in your communications, not your culture. Look for whether the language and values of the change are being used naturally in everyday conversations, whether people at all levels can explain why it matters in their own words, and whether it’s influencing how resources, recognition, and opportunities are actually allocated day to day.

Is there a point at which it makes more sense to pause or reset a change initiative rather than push through?

Yes — and recognising that moment early is a sign of strong leadership, not failure. A reset is worth considering when adoption signals are consistently poor across multiple teams, when the change is creating more friction than it’s resolving, or when the organisational context has shifted significantly since the initiative was designed. The key is to distinguish between a change that needs more time and support, and one that needs to be fundamentally rethought. A structured 90-day review is often the right moment to make that call honestly, with input from across the organisation rather than from the top down.

How does the Conscious Business framework connect to sustaining organisational change?

The Conscious Business framework provides the foundation that makes change sustainable rather than episodic. When an organisation has genuine clarity of purpose, aligned leadership, and a culture built on trust and accountability, change initiatives land differently — they’re understood as part of a coherent direction rather than isolated interventions. Without that foundation, even well-designed change programmes tend to fade because there’s no deeper organisational identity for them to attach to. If your change efforts keep stalling, it’s worth asking whether the issue is the change programme itself, or the organisational conditions it’s being asked to take root in.