Resources / Managing change

How to approach change management: where to start concretely?

What driving change really involves

Project managementChange management
Manage tasks, deadlines, deliverablesAccompanying behaviours and perceptions
Measurable and technical objectivesOften human and intangible results
Rational approachSensitive, adaptable approach
Downward communicationActive listening, continuous adjustments
Focus on the WhatFocus on the comment and the Why

Before acting: preparing for change management

Identify concrete human impacts

Let's take two examples:

  • A new business software? This can call into question skills, well-established routines, or a sense of effectiveness.
  • A team reorganisation? This directly affects interpersonal relationships, the meaning of work, and sometimes even psychological safety.

Celebrating progress, even imperfect

Several key profiles are generally identified:

  • Sponsors : those who carry the vision, actively support change and give it political weight.
  • The relays : influential figures or local managers, essential for translating strategy into daily action.
  • The engines : enthusiastic and willing collaborators, invaluable for sparking momentum in the early stages.
  • Those who wait : neither for nor against. Their position can tip either way depending on the quality of the support.
  • The Resistance : people who disagree or withdraw, often due to fear, overload, or lack of clarity.

Clarify the internal “why” of the change

A change, however strategically justified, will not be convincing if it is perceived as abstract, brutal, or disconnected from the realities on the ground.

This is why it is essential to formulate a “The ”why" of change who speaks as much to management as to the teams.

This “why” rests on three pillars:

  1. Vision : driven by the company: Where are we going? What ambition guides this change?
  2. Internal stakes : what signals, tensions or misalignments make this change necessary here and now?
  3. The organisation's history : how does this transformation fit into the continuity (or break) with our culture and values?

During the transformation: the right reflexes to support

When the deployment phase begins, the hardest part isn't always doing... but rather to last.

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

This is the stage where change management takes on its full human dimension: it's about supporting, pacing, and adjusting – without letting up.

Advance in clear, visible steps

A successful change is a readable change.
Rather than a comprehensive plan imposed in one go, it’s more effective to proceed by phased milestones, valuing small victories and feedback.

This step-by-step approach allows:

  • to anchor the transformations sustainably
  • to maintain team energy
  • to reassure about the direction being taken
  • avoid wear and tear or confusion related to uncertainty

Examples of change management steps

  1. Shared diagnostics : identify irritants, expectations, points of convergence, and sensitive areas, by actively involving the stakeholders concerned.
  2. Clarification of the “why” and the stakes : give meaning to the approach, link it to internal realities, the company's vision, and local needs.
  3. Pilot roll-out : experiment on a small scale, secure initial successes, gather feedback to refine the next steps.
  4. Regular communication and listening rituals : maintain a clear flow of information, open spaces for expression and adjustment.
  5. Phased rollout and continuous adjustments : progressively roll out changes, whilst adapting to feedback from the ground and operational constraints.
  6. Anchoring and consolidation : integrate new practices into habits, processes, tools, and management culture.

Maintain open and continuous communication

In any change management, what is left unsaid becomes a rumour.
And what is said once... is often forgotten the next day.

Effective communication during transformation doesn't rely on “big moments”, but on a continuous, embodied, bidirectional presence. It should be:

  • frequent : not necessarily long, but regular. It's better to have 5 short messages than one long email that's forgotten.
  • clear and honest : to say what we know, what we don't yet know, and what is in progress
  • open to feedback To create spaces for sincere expression (rituals, barometers, short polls, inverted meetings…)

The manager's role is central:

It becomes the primary vector of meaning, the one who re-explains locally, translates decisions and reassures with their stance.
He is also the one who can pick up on subtle signals.

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

But be careful: wanting to “eradicate” resistance risks stifling useful signals.

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

To resist is often...

  • protect its landmarks
  • to express a loss of meaning or trust
  • to refuse a brutal method
  • to remind you of a blind spot in the project

Leave room for discussion

Create times for to understand what's holding back, without judgment, is often a lever for personal transformation. This allows to:

  • reduce emotional pressure (anger, fear, fatigue),
  • come up with concrete proposals adjustment,
  • avoid the encapsulation of a silent opposition, which is much more dangerous.

Listening does not mean giving up.
But this allows for intelligent readjustment – and to show that change is being built with, not against.

After the transformation: best practices

It's often after deployment everything is at stake: habits are re-establishing themselves, automatisms are returning, tensions are rising.

Listening for weak signals from teams.

The weak signals these small alerts, often invisible in reports but revealing:

  • A speech that changes (“we'll wait a bit...”)
  • a team that stops asking questions
  • a meeting where we return to old methods
  • a new tool used... but bypassed

Adjust what needs to be adjusted

Adjusting doesn't mean improvising.
This could mean:

  • simplify a misunderstood procedure
  • reschedule a tight schedule
  • strengthen forgotten support
  • or reintroduce markers that were deleted too quickly

Celebrate and evolve

To recognise what has changed – even partially – is strengthen the dynamic continuous transformation.
It's also about installing the idea that change is not a final state, but a evolving posture.

To celebrate is to:

  • recognise the efforts made
  • create positive rituals (feedback, storytelling, team moments...)
  • stabilise the anchoring while maintaining a margin for adjustment

3 questions to ask yourself after deployment

  1. What has actually changed in the practices

“What concrete daily behaviours have evolved?”

  1. What the teams have understood and integrated

“What do they make of the meaning of change? What do they say about it?”

  1. What remains fragile or needs support

To summarise: what is successful change?

Driving effective change means not revolutionise the organisation from floor to ceiling.
First and foremost to develop what needs to be developed, while respecting what works, what structures, what connects.

A successful change is one that:

  • who transforms practices without damaging culture
  • who creates clarity without generating rigidity
  • who is taking people on board without forcing them

It's not about changing everything. But about create the conditions for the movement to be made with meaning, with intelligence, and with the people involved.

It is in this stance – 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 (UK)