Where Transformations Succeed or Fail: The Day After the Announcement

There is a moment that happens in almost every transformation.

The announcement has been made. The communications have been sent. Roadmaps shared and trainings delivered. Leadership breathes a collective sigh of relief and believes "We're finally moving."

If we're honest, that's usually the moment I become the most concerned. Announcements create awareness. They don't create adoption.

I believe every transformation really has two launch dates:

• The first is the day leadership makes the announcement,

• The second is the first ordinary Tuesday morning, when people sit down at their desks and have to figure out how this new way of working fits into the reality of their jobs and day-to-day.

We spend months preparing for the first launch. We rarely prepare for the second.

And somewhere between launch day and "business as usual", many transformations quietly begin losing momentum. Not because the strategy was wrong, but because everyone assumes the hardest part is already behind them.

In reality... the hardest part has only just begun.

And that's where I believe many leaders unintentionally fall into what I'd call the illusion of progress.

I've watched incredibly thoughtful leaders spend months preparing for a transformation. They build the strategy, align stakeholders, create communication plans, develop training, anticipate risks and launch successfully.

Then. Everyone moves on. Not intentionally but simply because another priority appears. Another deadline. Another initiative. Another customer. Another board meeting.

The transformation becomes yesterday's news long before it becomes today's habit.

Momentum quietly fades; not because people rejected the change, but because they were expected to figure it out on their own.

People don't adopt change during the announcement. They adopt it while trying to do their work differently. One conversation, one decision, and one new habit at a time.

The more transformations I've been a part of, the more convinced I've become that adoption doesn't happen in a meeting. We like to think it does because meetings are visible. They're measurable. Attend the training, complete the communication can be put on a project plan. It provides the ability to 'check the box'.

But people don't build confidence during a one-hour session. They build confidence while attempting something for the third, tenth, or twentieth time when the training slides are closed and they need to rely on their own judgement.

That's when the real questions emerge:

• Am I doing this correctly?

• This process takes longer than before

• What if my situation doesn't fit the example

• Is everyone else struggling too?

Unfortunately, by the time those questions appear the office hours have ended, the project team has been redeployed, leadership has shifted its attention elsewhere, and support often disappears just as people are needing it most.

We ask people if they have questions long before they've had enough experience to know what questions they should be asking.

Week one sounds something like this: Any questions. Silence. Leadership assumes everything is going well.

Three or four weeks later: people suddenly have hundreds of questions. Now they've encountered exceptions, unexpected customer situations, workarounds, and moments where the process doesn't fit quite as neatly as it did in training.

Now they know what they don't know. But many organizations have already stopped creating space for those conversations. It isn't that leaders failed to provide support, it's that the support was designed around the announcement instead of the adoption.

And then there's measurement. Or maybe more accurately, the lack of it.

This is another challenge that quietly appears after launch because nobody had clearly defined what success actually looks like.

Was success:

1. Finishing training?

2. Logging into the new system?

3. Using the new process correctly?

4. Improving the cycle time?

5. Better customer outcomes?

6. Higher employee confidence?

Without defining success before launch, organizations often default to measuring activity instead of adoption.

Completion isn't committment. Attendance isn't behavior change. Usage isn't proficiency.

If we don't decide what "success" actually looks like before we begin, it's incredibly difficult to know whether the change is truly becoming part of how people work.

Interestingly, I think we're watching this lesson play out all over again as organizations begin adopting AI.

Not because people don't see the value or because the technology isn't capable. Introducing AI is relatively easy.

Helping people build new habits, and new mindsets, around it is much harder. The technology isn't the transformation, human adoption is.

The same lesson applies whether you're introducing a new operating model, implementing a new system, reorganizing a team, or asking people to incorporate AI into their daily work.

The challenge has never been introducing something new. The challenge is helping it become part of how people naturally work.

What this means for leaders is we need to stop asking "how do we launch successfully?" and start asking "what will our team need sixty or ninety days after launch?".

That single question changes the role of a leader. Instead of asking did we launch, you start asking are people actually beginning to work differently.

Suddenly, the focus shifts.

From communication to reinforcement. From implementation to integration. From activity to adoption.

It reminds us that learning isn't linear. People need time to experiment. To struggle, to ask better questions, to hear how others are approach the same challenges and to slowly build confidence until the new way of working no longer feels new.

This might mean:

• Extending office hours well beyond launch

• Scheduling conversations at 30, 60, and 90 days. Not to report status but to understand where work is actually getting harder

• Measuring confidence alongside completion

We need to protect the space needed for people to integrate one change before introducing the next. People don't simply absorb change, they practice it. Question it. Adjust to it and eventually, it becomes part of who they are as a tea.

Maybe that's the biggest lesson I've learned over the years. Transformation rarely fails because of a bad announcment. It struggles because we confuse communication with adoption.

The day after the announcement is when people begin deciding whether this change is worth investing themselves in. That's the work that deserves our attention. Not because the strategy depends on it, but because the people do.

And when people succeed, transformation finally has a chance to succeed alongside them.