Change management refers to the structured approach to planning, steering, and supporting change processes in organizations. In its classical form — from Kotter to ADKAR to Prosci — it operates under a central assumption: change can be planned and steered as a transition from a defined current state to a defined target state. This assumption holds for complicated challenges. For complex ones, it does not. The distinction determines whether change management works as an instrument or fails as a cargo cult.

Strategic Relevance

Change management has its place in defined, bounded change projects — IT migrations, process conversions, reorganizations with a clear target. The problem begins where change management is applied to challenges for which it was not designed. Digital transformation, business model change, cultural realignment — these endeavors have no stable target state.

For C-level executives, the strategic relevance lies in precise classification: change management is a tool, not a paradigm. The decision of where to deploy it and where not is itself a strategic decision — one that presupposes understanding of the Cynefin Framework.

Common Misconceptions

The most widespread misconception: change management fails due to insufficient execution discipline. In truth, it frequently fails due to a wrong problem diagnosis. Second misconception: resistance is the main problem. In many cases, what is labeled resistance is a signal of lacking connectivity. Third misconception: a good change plan replaces good decision architecture.

Decision Architecture Perspective

From the perspective of decision architecture, change management is a downstream instrument. It designs the implementation of changes already decided. It does not design the conditions under which these decisions are made.

Distinction

Change management is not the same as transformation. Transformation refers to fundamental change of structures, culture, and business model. Change management refers to the steered implementation of defined changes. The confusion of both terms is one of the most frequent causes of transformation failure.

What begins as change management frequently reveals in implementation architectural deficits that cannot be fixed with change methods alone.

If this concept plays a role in your context — Schedule an initial conversation

Was ist neu

v1.0.0 Webflow Launch 2025-09-01
  • Erster Launch auf Webflow
v2.0.0 Astro Relaunch 2026-02-24
  • Komplett neue Website
  • Insights & Glossar mit Compass-Dimensionen
  • Blindspot-Report & Sparring-Anfrage
  • Englische Version (DE/EN)
v2.1.0 Dark Mode & Tooling 2026-03-01
  • Dark Mode mit System-Erkennung
  • Newsletter-Anmeldung
  • Lesezeit-Anzeige bei Insights
v2.2.0 Compass & Polish 2026-03-03
  • Interaktiver Compass im Hero
  • Optimiert fuer alle Bildschirmgroessen
v2.3.0 Content & UX 2026-03-05
  • 15 interaktive Diagnose-Tools in der Toolbox
  • In a Nutshell: Kompakte Uebersicht
  • Volltextsuche (⌘K)
  • Schnellere Ladezeiten
v2.4.0 Insights & Muster-Serie 2026-03-10
  • 12 neue Insights zur Transformations-Muster-Serie
  • Self-Check: 4 neue Muster + Multi-Pattern-Ergebnis
v2.5.0 Neue Tools & Features 2026-03-15
  • Neue Tools: Delegation Map + Agile Suitability Canvas
  • Hilfreich-Button bei allen Tools
v2.6.0 Zusammenarbeit im Fokus 2026-03-21
  • HTW-Studie zur Transformation Readiness jetzt verfuegbar
v3.0.0 AI Launch Geplant
  • Transformation Diagnostic (Claude AI)
  • Self-Check mit Radar Chart