The Human Side of Change and What We've Learned About Implementations

Oct 2026 — Manage it Pros

When organizations decide to introduce a new tool, process, or way of working, there's usually a good reason. The current approach has become difficult to manage. Work has become harder to track. Communication feels fragmented. The team has outgrown the systems that once served them well.

By the time an implementation begins, most people are hoping (maybe even desperate) for improvement. They're ready for something that will create more clarity, reduce friction, or help the team work together more effectively.

Then the learning begins.

If you've ever been a  part of an implementation, the wave of feelings over the next few weeks may sound a bit familiar. There is usually a mix of optimism, confusion, great questions, second-guessing, and at least one moment where someone wonders why you couldn't have just left things the way they were.

Implementations have a funny way of humbling all of us. It doesn't matter whether you've been in your role for six months or sixteen years. Learning something new usually feels a little uncomfortable before it feels empowering.

We've supported enough implementations to know that adoption is rarely a straight line. People don't simply decide whether they're "good at change." Instead, they move through different phases as they build confidence, often in ways that surprise both themselves and the people around them.

One of the biggest lessons we've learned is this: where someone starts during an implementation tells you very little about where they'll end up.

Hope

Implementations often begin with optimism. People see the opportunity to solve long-standing frustrations. Maybe work has been scattered across spreadsheets, email, Slack, and meetings. Maybe requests have been inconsistent or ownership hasn't always been clear. There's often a sense of relief: "Finally, this should make things easier."

That optimism creates momentum, but it's only the beginning.

Uncertainty

Once people begin using a new process or platform, reality sets in. The things that used to take five minutes now take fifteen. Buttons aren't where you expect them to be. The shortcuts you've relied on for years no longer exist, and even simple tasks require more thought than they used to. There's almost always a moment where someone says, "I could have finished this already in the old system." They're usually right. Learning something new almost always feels slower before it feels easier.

This is a completely normal part of learning, but it can feel discouraging when people compare their confidence using the new process with how comfortable they were using the old one.

Frustration

This is the phase that often receives the most attention, and it's also the one that's most likely to be misunderstood.

Some people become quieter because they don't want to ask another question. Others become more vocal because they're frustrated by the learning curve. Sometimes that frustration gets directed at the new process, the platform, or the implementation itself. That's understandable. When we're frustrated, it's much easier to see the friction in the process than it is to recognize that we're still building new habits.

These reactions are easy to interpret as resistance. In our experience, they're often signs that people are working through uncertainty while trying to build confidence. They aren't rejecting the new way of working—they're still learning it.

Confidence

Eventually, something begins to shift. Nobody announces it.

People stop second-guessing every action. They’re less worried about clicking the wrong thing, putting something in the wrong place, or accidentally disrupting the process. They start navigating the system more naturally and making decisions without needing reassurance at every step.

The questions change too. Instead of focusing on where to click or what comes next, people start asking how to handle more complex situations. They begin connecting the process to their day-to-day work instead of thinking about every individual step.

The tool is starting to feel less like something they’re learning and more like something they know how to use.

Ownership

This is one of our favorite phases to watch.

The person who kept apologizing for asking “one more question” is now answering someone else’s. The teammate who was skeptical is suggesting ways to improve the workflow. Conversations become less about learning the process and more about strengthening it.

At this point, the implementation no longer belongs to the project team. It belongs to the organization. People begin taking ownership, helping one another, and identifying opportunities to make the system even better.

Leadership plays an important role here, too. When leaders use the system themselves, reinforce it in conversations, and look to it for visibility into the work, it sends a powerful signal to the rest of the team: this is how we work now. That kind of ownership at the top creates reassurance and makes it much easier for adoption to take hold throughout the team.

That's when real adoption begins.

What this Means for Project Leaders

Supporting an implementation isn't just about configuring software or documenting a process. It's about helping people navigate change.

That requires patience, empathy, and an environment where people feel comfortable asking questions, making mistakes, and learning together. We've found that some of the strongest advocates for a new way of working are the people who struggled the most at the beginning. Given enough time, support, and encouragement, they're often the ones helping others build confidence too.

At Manage it Pros, we don't measure the success of an implementation by the day a system goes live. We measure it by the day the team no longer has to think about the process because it has become part of how they naturally work.

In the Manage it Method™, we call this the METABOLIZE phase. It's the point where nobody refers to it as "the new process" anymore. It has simply become how the team works. That doesn't happen because a project is complete or a training session has ended. It happens because people have had the time, support, and confidence to make the process their own.

Final Thoughts

Every implementation is different. Every team is different. Every person experiences change differently. Some phases last longer than others, some people skip phases entirely, and others move back and forth before finding their footing.

What stays remarkably consistent is that confidence doesn't happen on day one. It grows through support, experience, and the opportunity to practice.

The most successful implementations aren't the ones where everyone embraces change immediately. They're the ones where people are given the time, guidance, and encouragement to make the new way of working their own. 

And throughout all of these phases, it helps to keep reminding people why you're making the change in the first place. When you're in the frustrating part of an implementation, it's easy to focus on what's harder right now and forget what you're working toward: a way of working that makes things clearer, easier, and less frustrating for the team.

There is relief on the other side of the learning curve. Sometimes people just need to be reminded that they're getting there.