Change and Projects: Two Sides of the Same Coin
Not long ago, I found myself in a meeting where two teams—one leading a transformation project, the other handling the change management—were debating who should “own the adoption plan.”
Each had good intentions, sharp minds, and detailed slide decks. But what struck me most was that they were treating adoption as a handoff. As something that happened after delivery. It felt like watching a relay race where the baton was dropped mid-sprint—and everyone blamed the handover.
This wasn’t a one-off. I’ve seen it play out in industry after industry, country after country. Project teams focused on outputs. Change teams focused on people. But rarely working as one.
In theory, this separation made sense. In practice, it’s costing us outcomes, value, and trust.
We’ve spent the past few decades treating project delivery and change management as parallel disciplines—cousins who rarely talk, but always show up at the same family events. We now know that’s not enough. In today’s environment, change and projects aren’t just related—they are two sides of the same coin. And it’s time we start leading them as one.
Why have we treated them separately?
Historically, organizations often treated project management and change management as parallel but distinct disciplines:
- On one side:
Please log in or sign up below to read the rest of the article.
|
"The most exciting phrase to hear in science, the one that heralds new discoveries, is not Eureka! (I found it!) but rather, 'hmm.... that's funny...'" - Isaac Asimov |




