What I'd do differently if I rolled it out again

Here's the part I don't usually put on LinkedIn. The program worked. It launched, people adopted it, and by most measures it was a success. But "it worked" and "I got it right the first time" are two different things, and I want to be honest about the gap between them.

I underestimated how much of this was change management, not project management

I walked in thinking the job was a plan. Clear milestones, a solid timeline, the right stakeholders in the room. That part mattered, but it wasn't the hard part. The hard part was everything that happens underneath a good plan: whether people trust the change, whether they believe leadership actually stands behind it, whether they're quietly worried about what it means for them.

I spent most of my early effort on the plan itself. I should have spent more of it upfront, on the trust and the resistance, before a single milestone hit.

I waited too long to talk to the skeptics

It's tempting to build momentum around the people already on board. They're easy to work with, and their enthusiasm feels like progress. But they were never the group that determined whether this actually stuck.

The skeptics had real, specific reasons for holding back, and most of those reasons were reasonable once I actually heard them. I got there eventually, but later than I should have. Next time, the skeptics are some of my first conversations, not a group I circle back to once the early wins are already banked.

I measured too much of the wrong thing early on

Milestones hit and tasks closed were easy to track, so that's what I tracked first. It took longer than it should have to shift toward measuring whether the change was actually holding, whether people were still doing things the new way a month later, without someone checking in on them.

A closed task tells you the work got done. It doesn't tell you if anything actually changed. I got there, but I'd build that measurement in from day one next time, not add it once the project status started looking green enough to feel comfortable.

I didn't build enough space for people to say it wasn't working for them

Status updates tend to get polite answers, especially from people further from the decision. What I actually needed was an ongoing, low pressure way for people to say "this isn't working for me" without it feeling like a complaint on the record. I built that channel eventually. It should have existed from the start, not gotten added once I noticed people quietly reverting to the old way instead of saying so.

What I'd keep exactly the same

Not everything needs fixing. Tying the plan to real stakeholder input instead of a timeline built in a vacuum was right, and I'd do that again immediately. So was resisting the pressure to call it done after launch. Change isn't an event, it's a slope, and treating it that way instead of a finish line is part of why it actually held instead of quietly unwinding a few months later.

The bottom line

The version of this rollout that people saw looked clean. The real version had false starts, a few conversations I should have had earlier, and a slower start with the resistant stakeholders than I'd like to admit. I think that's true of most change efforts that end up working. The finished version just doesn't show the part where you were still figuring it out.

If you're in the middle of a rollout right now and it doesn't feel as smooth as everyone else's looks online, that's probably not a sign you're doing it wrong. It might just be the part nobody posts about.

Happy Learning,

KP