Change Management

When a company changes something fundamental, an announcement is rarely enough. A new computer program, a new process in the warehouse, a merger of departments: all of this requires hundreds of people to change their habits. Change management is the deliberate steering of exactly this transition. It encompasses everything that happens between the decision and the new everyday routine: informing, training, taking resistance seriously, measuring interim progress. The English term has also become established in German usage; literally it simply means steering of change. The direction of focus matters: it’s not about the technology, but about the people who are supposed to work with it.

Why projects don’t fail because of the technology

Major transformations fail astonishingly often. Consulting firms have cited figures for decades suggesting that roughly half of all initiatives miss their goals. The reason is almost never broken software. It lies in the fact that employees circumvent the new system, use it half-heartedly, or secretly stick to the old way.

One example: a corporation spends millions on customer management software. Yet the sales team continues to maintain its contacts in its own spreadsheets because it’s faster. Technically, everything works. Economically, the project is nevertheless a complete failure, because the data isn’t where it’s supposed to be.

With artificial intelligence, this point is particularly visible. Many companies introduce AI assistants without addressing the fear of job cuts. Anyone who fears making themselves redundant will not enthusiastically use a tool. That is exactly why change management budgets now appear in almost every larger AI project.

From the announcement to the new habit

It starts with an analysis: who is affected by the change, and what does this group lose or gain? In technical jargon, these people are called stakeholders, meaning parties with an interest in the matter. Afterward, it is clarified why the change is necessary in the first place. This rationale must be simple enough that everyone can pass it on in a single sentence.

Then comes the actual implementation. Typical building blocks are training sessions, test runs in a small department, and so-called multipliers: colleagues who are involved early on and later spread their knowledge within the team. Feedback channels are also important, through which problems can be reported without anyone being labeled a naysayer.

At the end comes the anchoring. As long as the old solution is still available, many will fall back on it. That’s why legacy systems are deliberately shut down and new processes are incorporated into performance targets and key metrics. A well-known model by the psychologist Kurt Lewin describes the three phases as unfreezing, changing, and refreezing. It is highly simplified, but it captures the essence: without the last step, an organization slips back into old patterns.

Where the term appears in business news

In quarterly reports and press releases, change management is a standard term. When an executive board announces a corporate restructuring, it’s almost always accompanied by a mention of supporting measures for the workforce. Consulting firms earn a significant portion of their revenue from such programs. It’s also central to mergers, because two different work cultures need to grow together there.

But you also encounter this principle outside of corporations. When a school switches from paper notebooks to tablets, the same mechanisms play out: pilot classes, training for teachers, parent-teacher evenings, complaints. The distinction from project management is important here. Project management deals with deadlines, costs, and outcomes. Change management deals with whether those affected are on board.

A common misconception is to regard the whole thing as pure communication. A mass email and a motivational video are not enough. If a change brings real disadvantages for individual departments, the only solution is to name them openly and offer compensation. Glossed-over upheavals create distrust, and distrust is the most expensive line item in any change project.