Your Change Is on Schedule. But Are Your People?

Project teams know how to track progress. Milestones are completed. Systems are configured. Training is scheduled. Risks are logged. As launch approaches, leaders can look at the project plan and see reassuring evidence that the change is moving forward.

But the people expected to work differently may be somewhere else entirely. Employees may still be trying to understand why the change is necessary. Managers may not feel prepared to answer questions from their teams. Training may be complete without people feeling confident applying what they learned.

A change can be on schedule without its people being ready to move with it.

Project Progress Is Not People Progress

Project plans are designed to track activity: what has been completed, delivered, approved, or implemented. Those measures matter, but they don't necessarily tell us whether people are progressing through the change.

A communication can be delivered without creating understanding. Training can be completed without creating capability. A new process can go live without employees adopting it. When we treat completion as evidence of readiness, we create an illusion of progress.

The better question isn't simply, “Did we complete the activity?” It's “What changed for the people because we completed it?”

Look for Different Evidence

Human transition doesn't follow a project calendar. We cannot assign a date by which everyone will understand, believe, feel capable, or adopt a new behavior. But we can look for evidence that people are moving toward the Future State.

Do employees understand why the change is happening and what it means for them? Do they know what they will need to do differently? Are managers prepared to support their teams? What concerns continue to surface? Are sponsors still visibly reinforcing why the change matters?

Those signals tell us something a milestone cannot: whether the organization is actually moving with the project.

When the Timelines Separate

The gap often becomes most visible at implementation. The system launches, but employees find workarounds. The new process is available, but teams continue using the old one. Training is complete, but managers are fielding questions they cannot answer.

It's easy to label what happens next as resistance. A better question may be whether the project moved forward faster than the people did. That distinction changes the response. Instead of simply pushing harder, communicating more, or demanding compliance, leaders can investigate what is preventing progress and address the actual barrier.

LaMarsh Perspective

Successful change requires visibility into both project progress and people progress. Milestones tell us whether implementation is advancing; they do not tell us whether people understand the change, are prepared to work differently, or are moving toward sustained adoption.

When those two timelines begin to separate, identifying the gap early gives leaders an opportunity to understand what's getting in the way and respond before implementation exposes the problem.

Leadership Reflection

Think about a significant change underway in your organization. You probably know whether the project is on schedule. Do you know whether the people are?

What evidence tells you they are ready? Where are managers struggling? What concerns continue to surface? What will people need to stop, start, or do differently in the Future State?

A green project dashboard can tell you implementation is progressing. It cannot tell you whether your people are progressing with it.