Key Takeaways
- Digitalization projects rarely fail because of software – usually because the human factor was skipped.
- Resistance is not a disturbance but valuable feedback about real pain points.
- Successful change needs three ingredients: orientation, participation and quick visible wins.
- An external impulse at the kick-off achieves what internal newsletters cannot: attention and momentum.
Between “We are introducing a new system” and “Our team enjoys working with it” lies the actual project – and it has little to do with technology. Digital change management decides whether investments work or vanish into drawers.
Why Do People Resist New Systems?
They rarely resist the technology – they resist loss of control, extra work during the transition and the feeling of not having been asked. Those who worked excellently with a tool for twenty years lose a piece of status along with the tool. Change must take these losses seriously, otherwise you negotiate with the wrong arguments.
What Do Successful Change Projects Do Differently?
- They explain the why before the how – from the perspective of those affected, not of management.
- They involve early: key users co-design before decisions are set in stone.
- They deliver quick wins: within the first two weeks, everyone must experience a personal benefit.
- They persevere: after the euphoria comes the valley – those who reinforce there, win.
What Role Does a Keynote Play in the Change Process?
It sets the rhythm for the departure: a good kick-off impulse removes fears, creates curiosity and gives the project a positive face – precisely because it comes from outside. Having been responsible for system rollouts as a managing director myself, I speak both languages: that of decision-makers and that of users.
Which Roles Decide Change Success?
Change rarely fails because of the software and almost always because of unclear roles. Staff these four before the first system goes live:
- A visible sponsor from top management who explains the why – not the features.
- Multipliers from the business units who help decide early and help colleagues later.
- Leaders as translators: they answer what changes for their specific team.
- Works council and data protection – an accelerator when involved early, a brake when involved late.
The sequence matters: clarify roles first, communicate second. An announcement without a contact person creates exactly what you want to avoid – rumours.
What Does a Realistic Change Roadmap Look Like?
Across many projects a simple rhythm has proven itself, and it works without a large consulting apparatus:
- Twelve weeks ahead: a target picture in three sentences every employee can repeat.
- Eight weeks ahead: name your multipliers and let them work on it themselves.
- Four weeks ahead: a shared impulse for everyone – why the company is taking this step.
- Launch: deliberately small, with one unit that actually wants it.
- After 30 and 90 days: an honest interim review with visible corrections.
What Does Missing Change Management Cost?
The invoice rarely appears in a spreadsheet, yet it is real: paid licences nobody uses. Duplicate work, because the old procedure quietly continues. Shadow IT, because teams help themselves. And the most expensive item: people who will not follow the next project because nobody listened during the last one.
Planning an event? As a keynote speaker for artificial intelligence, digitalization and Microsoft 365, I bring technology topics to the stage in a way that sticks – hands-on, entertaining and immediately actionable. Book a digital transformation keynote: content, formats and fee at a glance.
Frequently Asked Questions (FAQ)
When should the change impulse happen – before or after the rollout?
Ideally before the rollout, when the workforce first officially hears about the project. This way the news pairs with confidence instead of grapevine rumors.
How do we deal with loud critics?
Involve instead of exclude: critics are often the most precise observers of weaknesses. Making them test pilots wins you the most credible advocates.
Can change success be measured?
Yes: usage rates, support tickets, cycle times – and the simplest metric of all: how many people voluntarily work with the new system after 90 days?
How many multipliers does a rollout need?
As a rule of thumb one person per 20 to 30 employees – more important than the number is that they volunteer and get real time for the task.
What should we do if the project is already going wrong?
Schedule a reset meeting, name honestly what is not working and make one visible decision. People forgive mistakes, but rarely the sitting out of problems.
