Rules for Effectively Justifying Change
Antonio Gramsci. Financial Advisor and contributor at IT Business Solutions DEF
Frequently, when an organization launches a new strategy, implements a technology, or redefines a process, change management is reduced to communication sessions, training plans, or support materials.
All of these are important, but reducing change management to these actions means overlooking an essential part of the problem.
After participating in numerous transformation processes, I have observed that many initiatives fail not because of technological issues or a lack of resources, but because of basic mistakes in the way change is approached.
If I had to summarize the keys to effective change management, I would do so in three rules.
- Decide to Manage the Change
It may seem obvious, but it is not. Many organizations decide to transform processes, operating models, or technologies, yet never make an explicit decision about how they will manage the impact that transformation will have on people, both employees and customers.
Change management is taken for granted. It is assumed that once the new solution has been implemented, teams will naturally adapt. However, reality is often very different.
People need to understand what is happening, why it is happening, what is expected of them, and how the transformation will affect them. When these questions go unanswered, uncertainty, rumors, and resistance emerge.
Change management is not a complementary project activity. It is part of the project.
In fact, the more significant the transformation, the more important it becomes to dedicate time, resources, and leadership to managing its human dimension.
Change is not improvised. It is designed, planned, and managed.
- Make the Impact of Change Visible and Involve Those Who Will Experience It
People rarely resist change simply because it is change. What generates resistance is uncertainty.
That is why it is essential to clearly explain what problem is being solved, what benefits are expected, and how the transformation will affect people’s daily work.
Too often, projects are communicated using corporate terms such as efficiency, digitalization, productivity, or simplification. These are important concepts, but most people need much more concrete answers:
- What is going to change in my job?
- What problem will I be able to solve better?
- What effort will be required from me?
- Why is it worth it?
Making the impact of the change visible helps answer these questions and significantly reduces uncertainty and potential resistance.
However, there is a second element that is equally important: participation.
One of the most common mistakes is designing change for people instead of designing it with people.
Those who perform an activity every day know better than anyone else the problems, limitations, and opportunities for improvement associated with it.
Including those affected in the design of the change plan helps identify barriers that are not visible from management levels, improves the quality of solutions, and significantly increases commitment to the transformation.
There is one reality that rarely fails:
People are more likely to support what they have helped build.
When the impact is visible and those affected participate in the process, change stops being perceived as an imposition and begins to be understood as an opportunity.
- Measure Impact, Not Just Adoption
This is probably one of the most common mistakes.
Many organizations invest significant effort in measuring change adoption. They track how many people have been trained, how many users are using a new tool, how many processes have been migrated, or how many communications have been sent.
All of these indicators may be useful, but none answers the most important question:
Has the objective that justified the change actually been achieved?
An organization does not drive transformation to increase the number of users of an application or to complete a training plan.
It drives transformation to improve something: customer experience, productivity, quality, revenue, or costs.
When this distinction is lost, there is a risk of declaring a project successful while results remain exactly the same as before it began.
I have seen projects with large budgets, excellent technologies, and highly qualified teams fail to generate the expected results.
And I have seen much more modest transformations produce extraordinary changes.
The difference was almost never the technology.
It was the ability to consciously manage change, make its impact visible, involve people, and measure the outcomes that truly mattered.
Because transformation does not happen when a technology is installed, a process is redesigned, or a new strategy is presented.
Transformation happens when behaviors change and those new behaviors generate better results.
And that never happens by chance.
