Business Central
Ina Rogalev
6. May 2026
Many companies start digitalization projects with a clear expectation: processes should become faster, coordination should become smoother, and information should finally reach the places where it is needed. What sounds simple on paper often becomes far more complex in reality.
The real challenge begins with a different question: what exactly is supposed to change in the company, why that change is necessary, and whether the people who will later work with new processes or systems have been considered from the very beginning.
This is exactly where many digitalization projects begin to stall. In many cases, the root cause is not the technology itself. It is the fact that change is being viewed too narrowly as a technical issue. Change management in digitalization projects is not a side topic. It is the prerequisite for turning a project into real change.
What does Change management mean?
Change management describes the structured support of change within a company. In digitalization projects, this is not just about new systems or processes. It is also about providing orientation, taking concerns seriously, clarifying responsibilities, and making change sustainable in day-to-day work.
Many companies know they need to digitalize. Processes are too slow, coordination is too time-consuming, information is spread across too many places, or it depends too heavily on individual people. At the same time, it is often unclear where to start in a meaningful way.
That is when familiar statements appear:
The problem is not that these assessments are wrong. The problem is that they do not yet amount to a robust project foundation.
As long as digitalization remains abstract, agreement is easy. It becomes critical the moment existing workflows are examined in concrete terms: Which steps are actually necessary? Which routines make sense, and which ones still exist only because they have been embedded for years?
This is the point at which it becomes clear that many digitalization projects do not fail because of technology. They fail because there is no clear picture of the current state and no real understanding of what actually needs to change in everyday operations.
That is why change management does not begin with rollout. It begins where companies are willing to question routines and turn a vague desire for change into a viable target picture.
The more deeply a digitalization project affects day-to-day work, the more it also becomes a human issue. New processes do not just change interfaces or responsibilities. They change security, habits, established routines, and sometimes even the self-image of people who have worked with a certain system for many years.
Behind resistance there is often neither blanket rejection nor hostility toward technology, but very concrete concerns:
Resistance is not automatically problematic behavior. It is often a signal that people were involved too late or that their pain points were not sufficiently considered throughout the project.
Good change management therefore does not mean smoothing over criticism. It means making concerns visible early enough, interpreting them correctly, and taking them seriously. That also includes involving leadership. Change only becomes sustainable in a company when it is not communicated solely from within the project team, but is supported by leaders who provide orientation, trust, and clarity.
Good change management is not an add-on at the end of a project. It starts at the beginning. Not only during implementation. Not only during training. And not only when the first signs of resistance appear.
In practice, four things matter most:
Anyone who wants to digitalize must first be able to define what exactly is meant to improve. Without clear goals, a project quickly turns into actionism.
Change cannot be understood from a bird’s-eye view alone. You need to see how people actually work, where friction occurs, and which dependencies exist in the background.
Digitalization must not simply preserve old workflows in a new format. It must examine what still makes sense and what only continues to exist because it has never been seriously questioned.
Acceptance does not emerge shortly before go-live. It emerges where people notice early on that their working reality has been understood and that their perspective is part of the change.
That is exactly the difference between a solution that has been introduced and a change that is truly effective. Only when companies are prepared to question routines, bring people along, and think about change not only in technical terms but also in organizational terms does digitalization create a sustainable new reality.
STEFAN SCHADE
Senior Project Manager
INA ROGALEV
Junior Marketing Manager
Other articles that might be interesting for you
