Resources / Managing change

Change management: where to start?

What "driving change" really means

Project managementChange management
Manages tasks, deadlines and deliverablesSupports behaviors and perceptions
Measurable and technical objectivesResults often human and intangible
Rational approachSensitive, adaptive approach
Downstream communicationActive listening, continuous adjustments
Focus on whatFocus on how and why

Before taking action: preparing for change management

Identify concrete human impacts

Let's take two examples:

  • New business software? It can call into question skills, well-established routines or a sense of efficiency.
  • Team reorganization? This directly affects interpersonal relations, the meaning of work and sometimes even psychological safety.

Celebrating evolution, even imperfect evolution

Several key profiles can be identified:

  • Sponsors Those who carry the vision, actively support change and give it political weight.
  • Relays These include influential figures and local managers, who are essential for translating strategy into action on a day-to-day basis.
  • The engines Our team: enthusiastic, willing employees, invaluable for building momentum right from the start.
  • The wait-and-see crowd Neither for nor against. Their position can change depending on the quality of the support provided.
  • Resistance fighters People who disagree or withdraw, often because of fear, overload or lack of clarity.

Clarify the internal "why" of change

A change, however strategically justified, will not convince if it is perceived as abstract, brutal or disconnected from the field.

That's why it's essential to formulate a the "why" of change that speaks to management and teams alike.

This "why" rests on three pillars:

  1. The vision Where are we going? What ambition guides this change?
  2. Internal issues What signals, tensions or misalignments make change necessary here and now?
  3. History of the organization How does this transformation fit in with the continuity (or rupture) of our culture and values?

During the transformation: the right reflexes for support

When the deployment phase begins, the hardest thing is not always to do... but to make it last.

The first few weeks can generate enthusiasm, but also confusion and fatigue if nothing is structured.

It's during this phase that change management takes on its full human dimension: you have to support, pace and adjust - without letting up.

Move forward in clear, visible stages

Successful change is readable change.
Rather than a global plan imposed from a single block, it's more effective to move forward in stages. progressive milestonesby highlighting small victories and feedback.

This step-by-step approach makes it possible to :

  • d'anchoring transformations for the long term
  • keep teams energized
  • to reassure people about the direction
  • andavoid wear and tear or confusion linked to uncertainty

Examples of change management stages

  1. Shared diagnosis
    → Identify irritants, expectations, points of convergence and sensitive areas, actively involving the players concerned.
  2. Clarifying the "why" and what's at stake
    → Give meaning to the approach, linking it to internal realities, the company's vision and local needs.
  3. Launching pilot actions
    → Experiment on a small scale, secure initial successes, gather feedback to fine-tune the follow-up.
  4. Regular communication and listening rituals
    → Maintain a clear flow of information, opening up spaces for expression and adjustment.
  5. Progressive deployment and ongoing adjustments
    → Gradually roll out the changes, while adapting to feedback from the field and operational constraints.

Anchoring and consolidation
→ Integrate new practices into habits, processes, tools and managerial culture.

Maintain open and continuous communication

In all change management, what's left unsaid becomes a rumor.
And what's said once... is often forgotten the next day.

Effective communication during the transformation process is not based on "great moments", but rather on a "good communication". continuous, embodied, two-way presence. It must be :

  • frequent : not necessarily long, but regular. Better 5 short points than one long, forgotten e-mail.
  • clear and honest : say what we know, what we don't know yet, and what's in progress
  • open to feedback Create spaces for sincere expression (rituals, barometers, short surveys, reverse meetings, etc.).

The manager's role is central:

It becomes the first direction vectorHe's the one who explains things locally, translates decisions and reassures through his posture.
He's also the one who can point out weak signals.

In any change, the resistance is not an anomaly... it's a normal reaction.
It can take the form of doubt, slowing down, withdrawal, passive disengagement... or more outspoken opposition.

But beware: trying to "eradicate" resistance means running the risk of stifling useful signals.

The right reflex: welcome resistance as an indicator of what needs to be clarified, supported or adapted.

Resistance often means...

  • protect your bearings,
  • express a loss of meaning or confidence,
  • refuse a brutal method,
  • or recall a blind spot in the project.

Leaving room for speech

Creating time for hear what's holding you backA non-judgmental approach is often a lever for self-transformation. It enables :

  • of reduce emotional pressure (anger, fear, fatigue),
  • of generate concrete proposals adjustment,
  • and avoid the encystment of a much more dangerous silent opposition.

Listening doesn't mean giving up.
But it does allow for intelligent readjustment - and shows that change is a work in progress. withnot against.

During the transformation: the right reflexes for support

It's often after deployment that everything comes into play: habits are re-established, automatisms return, tensions rise again.

Listening to teams' weak signals

The weak signals are those small alerts that are often invisible in reporting, but which can be very revealing:

  • a changing discourse ("we'll wait a bit...")
  • a team that stops asking questions
  • a back-to-basics meeting
  • a new tool used... but circumvented

Adapting what needs to be adapted

Adjusting doesn't mean improvising.
This can mean :

  • simplifying a misunderstood procedure
  • shift a tight schedule
  • reinforcing forgotten support
  • or reintroduce markers that were removed too quickly

Adapting what needs to be adapted

Recognizing what has changed - even partially - means strengthening the momentum continuous transformation.
It also means installing the idea that change is not a final statebut a evolving posture.

To celebrate is :

  • give recognition to efforts made
  • create positive rituals (feedback, storytelling, team moments, etc.)
  • stabilize anchoring while retaining a margin for adjustment

3 questions to ask yourself after deployment

  1. What has really changed in practice

"What concrete behaviors have changed on a daily basis?"

  1. What the teams have understood and integrated

"What do they retain about the meaning of change? What are they saying?"

  1. What's still fragile or needs support

During the transformation: the right reflexes for support

Driving effective change does not mean revolutionizing floor-to-ceiling organization.
First and foremost improving what needs to be improvedwhile respecting what works, what structures, what connects.

A successful change is one that :

  • that transforms practices without damaging culture
  • that creates clarity without rigidity
  • that takes people on board without forcing them

It's not about changing everything.
But from create the conditions to ensure that the movement is carried out sensibly, intelligently and with the people concerned.

It is in this posture - both ambitious and realistic - that true change management is built.

Article written with the help of artificial intelligence

Are you really ready to tackle change management?

English