Leadership and execution

Change management: when the solution is right but the approach needs to change

A technically sound change led to resistance and complaints. The lesson was to involve the people responsible for making the transformation work.

I implemented a technically sound change and almost had to reverse it. My manager was direct: either I stabilized the operation or we would return to the previous model.

I was convinced the idea was good. I drove the change from the top down, at my pace, expecting the team to understand its value along the way. Internal dissatisfaction followed, along with complaints from customers and representatives.

The quality of the solution had not resolved the adoption problem. I needed to reconsider how I was leading the transformation.

Stabilizing the operation also had a cost

I reassigned responsibilities to stabilize the operation. It worked, but it was painful. Some of that cost could have been avoided if I had involved people more effectively before implementation.

My attention had been focused on designing and executing the solution. I had not sufficiently built a shared understanding of why the change was needed and what it was meant to achieve.

Understanding the reason comes before learning the procedure

Later, I encountered Prosci's ADKAR model. It organizes individual change around five elements: awareness, desire, knowledge, ability and reinforcement. What struck me most was the distinction between understanding why to change, wanting to participate, and learning how to do it.

In the experience I described, I had started with the how before developing the why and the purpose with the people who would make the change happen.

I use this framework to interpret that learning. The account does not imply that I formally applied the model in that episode or that a specific methodology caused the outcome.

Another opportunity to lead differently

At the same company, when automating another process, I began by mapping the operation with the area leader and some team members before proposing a change. They helped design the new process and took ownership of it. Resistance was much lower.

Their participation brought knowledge of the actual work and room to influence what would change. My leadership responsibility included creating those conditions.

What I would check before another transformation

The experience leads me to four preparation questions:

  • Whose routine will change, and who needs to help understand the problem?
  • Is the reason for the change clear to those people?
  • What operational knowledge is still missing from the design?
  • How can adoption difficulties be recognized before they compromise delivery?

Involving the team does not remove conflict or difficulty. It helps uncover what a solution viewed only from the top may have missed.

Authority increases the responsibility to listen and involve the people who must work through the change.

Reference

The ADKAR Model, Prosci. Prosci is the model's source and also sells related training and services.

Adapted from a LinkedIn post by Leandro Oliveira: LinkedIn · 2026-09-15.

Leandro Oliveira

Executive with experience in B2B sales, marketing, services and operations. Shares lessons from his professional career across different sales rhythms and markets.

Ready to develop your commercial operation?

Let us discuss the decisions, processes and capabilities that need to evolve.

Contact ProduBiz