Transformation & Change

Change Management: What Makes Large Change Programs Succeed

Marin Niehues31 July 202510 min read

Large group in a bright room

Large change programs succeed when the target picture and accountability are set early and line managers demand the change in daily work. Change management is the discipline that turns an executive decision into changed behavior in line and business functions. From a delivery perspective, success comes down to one question: do employees work differently after go-live than before? This article sets out the models and success factors, presents a steering framework and names the warning signals by which executives recognize early whether a program is landing.

What distinguishes large programs from small changes

A change within one team can be implemented with good preparation and a clear mandate. A program that touches several divisions and locations follows different rules. The number of dependencies grows, responsibilities overlap, and every level interprets the goals in its own way. The change then becomes a task that someone has to deliver, with named owners and deadlines. How structure, roles and delivery interact is set out in the article characteristics and metrics of a high-performing organization.

Two models have proved their worth as frameworks. In 1995, John Kotter described eight steps for large change efforts in a widely cited article. Jeff Hiatt developed the ADKAR model at Prosci, which describes the journey of the individual employee. Kotter orders the program, ADKAR orders the person. Both views belong together, because a program only takes effect once employees have made the change individually.

Kotter's eight steps are:

  1. Establish a sense of urgency.
  2. Form a powerful guiding coalition.
  3. Create a vision.
  4. Communicate the vision.
  5. Empower others to act on the vision.
  6. Plan for and create short-term wins.
  7. Consolidate improvements and produce further change.
  8. Institutionalize new approaches in the culture.

The five stages of ADKAR are:

  • Awareness of the need for change
  • Desire to take part
  • Knowledge of how the work changes
  • Ability to apply the new way of working day to day
  • Reinforcement, so that the old way does not return

In practice, you use Kotter for the program plan and ADKAR to diagnose individual groups. When a division stalls, its ADKAR stage shows where it stands: if awareness is missing, more explanation from leadership helps. If ability is missing, training on the job helps, and further communication has no effect.

Why do so many change programs fail?

Change programs fail mainly because of unclear accountability, leaders who do not model the change themselves, and a lack of reinforcement in roles and processes. Kotter derived his eight steps explicitly from errors he had observed in companies: too little urgency, a guiding coalition that is too weak, a vision that is missing or poorly communicated, obstacles nobody removes, a lack of short-term wins, victory declared too soon and a change that never reaches the culture.

The frequently quoted claim that around 70 percent of all change programs fail, by contrast, has no empirical basis. A review of the sources in a specialist change management journal concluded in 2011 that no valid empirical evidence supports such a fixed rate. For executives this is a useful correction, because the known causes of failure can be checked and fixed before the start.

Five success factors from a delivery perspective

Programs that reach their goals differ from those that stall in five respects. The factors apply across sectors, and they can be checked before the start.

The second and third factors are underestimated most often. A sponsor who has the program on the agenda only occasionally loses decisions to the divisions whose interests are affected. A project organization that communicates the change in place of the line creates spectators. The line manager is the person from whom employees read whether a change is meant seriously.

How do you steer a large change program?

You steer a large change program through two fixed rhythms, a few behavioral metrics and an escalation rule with a deadline. The steering must be simple enough to be used. A weekly rhythm in the program team and a monthly rhythm with the sponsor have proved effective. In the weekly rhythm, obstacles are removed; in the monthly rhythm, the decisions are taken that a team cannot make alone.

A rule of thumb applies to metrics: three to five measures that capture changes in behavior are enough for each program. A manager tracks, for example, which share of the affected teams uses the new process and how long a decision takes in the new process. Activity metrics such as the number of training sessions say little about success.

Escalation needs rules. An obstacle that the program management does not resolve within an agreed period goes to the sponsor, and the sponsor decides within a defined time. Without this rule, conflicts between divisions stay open for months and the program loses pace.

Warning signals and dealing with resistance

Four signals show early that a program is at risk of stalling. Managers' participation falls from meeting to meeting. The metrics show activity but no change in behavior. Divisions adopt the new vocabulary but work in the old process. Decisions are postponed because the sponsor does not take them.

Resistance belongs to every large program and delivers information. It shows where a goal is unclear, where employees expect disadvantages or where a process does not work in daily practice. Managers who evaluate these signals and refine the change progress faster than those who treat resistance as a disturbance.

The same rules apply to changes with a technology component, such as the introduction of AI. One factor is added there: employees must understand which tasks change.

A partner for change programs: Niehues Consulting

Niehues Consulting steers large change programs from a delivery perspective. The central question is what an organization must do for a change to land in daily business. As delivery manager, project manager or product owner, Niehues Consulting takes over the steering of the initiative. In organization design, structures and decision paths emerge that secure the new behavior.

The approach follows the Niehues Delivery Model with its phases of understanding, building and introducing. Three of its review questions matter most for change programs. Which business outcome should change measurably? Are users enabled and processes adapted? Which metric shows after 90 days that the solution is landing? Where a program contains an AI component, Niehues Consulting connects the proof of value in the real workflow with adoption by the business functions. The entry point is a free initial consultation of 30 minutes: book an initial consultation.

Frequently asked questions

What is change management?

Change management is the steering of the human side of a change, the path from the decision to changed behavior in daily work. It covers the target picture and communication, the enablement of employees and the adjustment of roles and processes. It is measured by whether those affected work differently after go-live.

What is the difference between change management and project management?

Project management delivers a result in time, scope and quality, while change management ensures that employees use the result and change their behavior. Large programs need both. Both should come together in one steering structure with a single sponsor.

What are Kotter's 8 steps of change?

Kotter's eight steps are creating urgency, forming a guiding coalition, creating and communicating a vision, empowering others to act, generating short-term wins, consolidating improvements and anchoring the new approach in the culture. Kotter published them in 1995. The model orders a program from the top and works as a scaffold for the program plan.

What is the ADKAR model?

The ADKAR model by Jeff Hiatt describes in five stages how an individual makes a change: Awareness, Desire, Knowledge, Ability and Reinforcement. It shows at which stage a group is stuck, and therefore which measure helps next. Kotter and ADKAR complement each other, because one orders the program and the other the person.

How long does a large change program take?

Plan a program across several divisions for one to three years, with visible stage results after three to six months. If the change affects a single division with one process, six to twelve months are usually enough. Kotter warns that declaring victory too soon endangers reinforcement, so the program ends only once the metric stays stable.

Which metrics show whether change management is working?

Change management is working when behavioral metrics rise: the share of teams using the new process, the cycle time in the new process and the satisfaction of users. Activity figures such as training attendance complement the picture but do not replace it. Every metric needs a baseline before the start.

Who should be accountable for a change program?

A member of the executive team is accountable as sponsor, a program lead steers, and the managers of the affected divisions implement on site. Unclear accountability and leaders who do not model the change themselves slow programs down the most. The allocation of roles is therefore fixed before the first meeting.

How much does change management consulting cost?

External change support in Germany is typically billed at around 1,000 to 2,500 euros per consultant day, according to the fee study of the industry association. The total effort depends on the number of divisions and the duration of the support.

Let’s talk about your initiative.

In 30 minutes we clarify where your organization stands and which step will pay off most now.

Request a consultation

30 minutes · free · no obligation