A few years ago, a specialist we worked with asked a question that has stayed with me: why are people so afraid to put a face to data?
And he answered it himself: without a face, data lacks emotion and humanity. Without that connection, analysis becomes superficial and fails to generate real action.
The same is true of transformation. Companies invest in technology, hire consultants, and define roadmaps. And yet something fails. Not in the system. In the people who are supposed to adopt it.
According to an NTT Data report, 78% of executives believe that a poor organizational culture is obstructing their innovation efforts. Not a lack of budget. Not the absence of tools. Culture. And yet, when a transformation project begins, technology is the first thing defined and the last thing considered is how the people who will live that change every day are going to react to it.
After accompanying hundreds of transformation processes alongside our clients, we've found that resistance variables are more closely tied to organizational culture than to individual characteristics. People don't resist change. They resist uncertainty. It's not fear of learning something new — it's fear of doing so blindly, without understanding the why or the what for.
There are three reasons that repeat themselves with a consistency that no longer surprises us. The first is the misalignment between training programs and employees' real expectations: people are trained on the system, but nobody explains how that system changes their work, their role, and their place in the organization. The second is phased implementation without clear communication, which generates distrust and rumors before the change has even arrived. And the third — perhaps the most costly — is the disconnect between organizational policies and the actual work culture: what the manual says and what happens in practice are two different things, and everyone knows it.
In this context, change management is not a support component of the technology project. It is the condition that determines whether the project will work at all.
Change management is a structured approach to facilitating the successful transition of individuals and teams through organizational change. It focuses on preparing, training, and supporting people so they adopt change effectively, with the goal of maximizing their participation and the return on investment of initiatives. But beyond the definition, it implies something more demanding: understanding the real complexities of the organization, anticipating how its employees will react, and defining a purpose that excites them rather than one that simply instructs them.
Mustafa Suleyman, co-founder of Inflection AI, said with a clarity rarely heard in corporate settings: this is going to be the moment of greatest transformation — not only technological, but cultural and political — of our entire lives. And yet most organizations continue approaching transformation as if it were exclusively a systems problem.
More than 85% of organizations identify the adoption of new technologies as the trend most likely to drive their transformation over the next five years. The figure is revealing not for what it says, but for what it leaves out: adopting technology is not the same as transforming. An organization can implement the best ERP on the market and still operate with the same silo logic, the same bottlenecks, and the same silent resistance as always.
Real transformation happens when behaviors change. And behaviors don't change by decree or through training. They change when people understand the purpose behind what they're being asked to do, when they feel part of the process, and when their environment gives them genuine permission to learn — even at the cost of making mistakes. That is the difference between managing change and simply announcing it.
By Irene Marqués, Partner at Olivia Mexico.