Leading Change
Successfully.

For us, resistance is a signal, not a disruption — it usually points to an unanswered question or an unclear impact on someone's daily work. During the stakeholder analysis we identify resistance and its causes early and address it with targeted communication rather than pressure. We explicitly coach leaders to address resistance openly instead of ignoring or waiting it out.

As soon as an IT rollout noticeably changes the daily work of several teams or departments, structured change management pays off — regardless of the pure project budget. For smaller projects, a focused stakeholder analysis and a clear communication plan are often enough, without the full programme. We deliberately scale our approach to the actual depth of change, not to project size alone.

At the start of a project we define concrete change KPIs — such as adoption rates of the new system, training attendance or pulse-check results — and track them throughout the project. Regular surveys show where acceptance is still lacking, so we can adjust course instead of only finding out at the end that something didn't land. We keep monitoring these metrics after go-live too, to ensure the change is sustainably anchored.

We draw on established models such as Kotter or ADKAR, but we don't apply them dogmatically — our four-phase approach, from stakeholder analysis through communication and enablement to stabilization, picks up the core principles of these models and adapts them to the actual project reality. What matters to us is not the label of the model, but that every phase leads to measurable acceptance within the team.

No — go-live is often where it becomes clear whether a change really sticks. We support the stabilization phase with hypercare, gather feedback from day-to-day operations and run a structured lessons-learned workshop. Only once the new processes have become second nature in everyday work do we consider the change sustainably anchored.