I see this across all kinds of work, especially HR systems and tech stack transformations. HCM, HRIS, payroll, time & attendance, ATS, LMS, Finance/ERP.

Good intentions. Big budgets. Tight timelines. Under-resourced teams. High expectations.

And then… surprise.

Surprised managers. Surprised team members. Surprised leaders wondering why adoption is lagging, trust is fraying, and training isn't sticking — because no one talked to the front lines early enough. Because it was assumed this could be run off the side of the desk.

Most of these programs and projects don't fail because the technology is wrong. They fail because the work starts before needs are validated, before anyone is meaningfully enrolled, and before the organization's change capacity and pace are understood.

Layer on overlapping initiatives, and change fatigue is inevitable.

The pattern I see, over and over

None of this is on purpose. It's just rushed.

Real change work requires more than a project plan

It requires someone whose job is to:

That's not something you do between meetings.

This is why organizations stall or fail

When no one is operating at a program level, orchestrating the work and owning the messy middle where real change lives.

When I'm brought into these transformations, it's not to support the project. It's to run it properly — with governance, accountability, and ownership that hold under pressure.

If your current system or transformation project already feels heavier than expected, that's usually the signal.

Project feeling heavier than it should? Let's talk.

Book a 30-min fit call → Read: HR operating models