Why Project Managers and Change Managers Need to Stop Running on Parallel Tracks

• September 16, 2026

By Jahzeel A. Ormeno

There’s a moment most project managers and change practitioners know well. The system goes live. The budget closes clean. The project is declared a success. And then, six months later, someone asks: Is anyone actually using it?

The silence that follows that question is expensive.

The space between delivery and adoption—between a project that finished and a change that stuck—exists not because project managers aren’t doing their jobs, or because change managers aren’t doing theirs. It exists because, in most organizations, they’re doing their jobs on entirely separate tracks.

If you’ve ever arrived at a stakeholder meeting where scope was already frozen and the go-live date was already set, and been handed a change management plan to build around decisions that were never yours to shape, you know exactly what this gap feels like from the other side.

When I work with project teams, I ask them to distinguish between three things that often get collapsed into one:

1) Delivery. Project management traditionally measures whether the project hits the go-live target, on time, on budget. When the system is live, requirements are met and the budget is closed, that’s considered a success by every traditional project metric.

2) Adoption. This is what change management measures. Are people actually using the tool? A change practitioner can check every box on their plan and still hand off to an organization that quietly reverts to old habits within a quarter.

3) Sustained value. This is what the organization actually needs: Did it stick and did it matter? Were outcomes realized at 90 or 180 days? Did the return on investment (ROI) materialize? Did the culture shift the way the business case assumed it would?

Most organizations measure delivery first. Some measure the second and very few deliberately measure the third, because by the time sustained value can be assessed, the project is closed, the team has disbanded and no one has been named as the owner of what comes next.

When project management and change management run independently, delivery is optimized at the expense of everything that comes after it. Both disciplines are doing valuable work, but without deliberate integration, they are optimizing for different finish lines and the organization ends up crossing neither.

The solution isn’t to make project management and change management sit in the same room more often. It’s to give them shared anchors that force integration as a structural reality rather than a goodwill gesture.

Here are five principles to facilitate integration:

1) Change at the charter stage. Involve both teams as co-authors of the plan before the scope hardens.

2) Define adoption metrics before the go-live day. What does 80% adoption look like? Who measures it and when? These questions need answers at planning, not retrospectively.

3) Integrate the risk register. Combine and jointly maintain a way of measuring both technical risk and people risk in the same view.

4) Share status reporting. For example, a dashboard should serve as a single source of truth for leadership on delivery progress and adoption readiness.

5) Plan reinforcement. Reinforcement planning starts during the execution. Name the owner. Budget for it. Calendar it.

Jahzeel A. Ormeno is founder of Simplexity PM.