The Sobering Reality
In recent years, “transformation” has become one of the most overused terms in business, politics, and society. Hardly any organization refrains from talking about “driving digital transformation,” “becoming more agile,” or “strategically repositioning” in strategy meetings or annual reports. The ambition sounds impressive — the reality, however, is often sobering.
The numbers speak clearly: Studies show that 60-70% of all transformation initiatives fail to achieve their originally stated goals. Many stall, lose direction, or fizzle out entirely amid day-to-day operations. Billions in investment evaporate, teams become frustrated, and in the end comes the realization: “Well, that didn’t work.”
But why? Why do so many well-intentioned, often even well-funded transformation initiatives fail?
The Central Thinking Error: Transformation as a Project
A key reason for failure lies in a misconception that pervades nearly all transformation efforts: Transformation is treated like a project. The process follows a familiar pattern:
- Set a start date
- Define an end date
- Create a detailed action plan
- Track progress in percentages
- Define milestones and check them off
This may work for building a production facility or implementing an IT system. Transformation, however, is not a linear execution process but a complex social phenomenon — shaped by interdependencies, feedback loops, and emergent developments.
What Happens When Project Thinking Meets Transformation
Those who try to tame this dynamic with the tools of classical project management quickly hit limits:
- Plans become outdated — before the first steps are even implemented
- Target visions shift — because conditions change
- Resistance emerges — people are not variables in a plan
New influences from markets, technology, or society surface while target visions shift because conditions change. At the same time, resistance builds because people don’t function as variables in a plan.
What Is Transformation, Actually? A Necessary Clarification
The widespread misunderstanding is also fueled by a lack of terminological precision. In many organizations, “change” and “transformation” are used synonymously — often in the same breath as topics like digitalization or innovation.
Change vs. Transformation: The Crucial Difference
| Change Management | Transformation |
|---|---|
| Clearly defined, often one-time changes | Fundamentally alters thinking and operating logic |
| Linearly planned with a clear beginning and end | Affects values, decision mechanisms, self-understanding |
| Example: Implementing a new CRM system | Not just structures or processes |
| The organization remains the same at its core | The organization thinks, decides, and acts differently |
Placing Related Terms in Context
Digital transformation is primarily triggered by technologies and data-driven business models.
Agile transformation targets the adaptability of structures and leadership models in complex markets.
Innovation can be part of or trigger transformation, but must be embedded within a broader framework of change.
Understanding the Three Dimensions of Transformation
Transformation cannot be grasped one-dimensionally. It always unfolds simultaneously across multiple levels, drawing its dynamic precisely from the interactions between them. Three analytical lenses help clarify the framework:
Content Level: The “What”
This addresses all elements that are concretely supposed to change:
- Business models and value propositions
- Technologies and digital platforms
- Processes and workflows
- Leadership structures and decision pathways
- Cultural norms and values
Depth of Impact: The “How Deep”
Not every change is equally radical:
- Incremental changes: Small optimizations that don’t touch existing logic (e.g., process improvements)
- Transitions: Significant changes within existing logic (e.g., from analog to digital)
- Fundamental changes: Complete transformation of identity, business logic, and culture (e.g., from product manufacturer to platform)
Systemic Level: The “Where”
Transformation never operates in isolation but simultaneously affects:
- Individuals: New competencies, mindsets, and ways of working
- Teams: Different collaboration, decision processes, and roles
- Organization: Changed structures, culture, and strategies
- Ecosystem: New partnerships, customer relationships, and market dynamics
Why Classical Assessment Models Fail
Many organizations rely on the same instruments for transformation initiatives that they use in projects or change initiatives: KPI sets, maturity models, progress dashboards. The problem: These tools are based on a logic of linear predictability.
The Assumptions of Classical Models
They presuppose that:
- Goals can be precisely defined in advance
- Actions are plannable and controllable
- Results emerge linearly from activities
- Progress is measurable and can be expressed in percentages
These assumptions rarely hold true in complex, dynamic systems.
The Reality of Transformation
| Classical Assumptions | The Reality of Transformation |
|---|---|
| Goals can be precisely defined | Emergent: Structures and ways of working emerge in the process, not on the drawing board |
| Actions are plannable and controllable | Dynamic: What serves as a critical lever today may be a brake tomorrow |
| Results emerge linearly from activities | Nonlinear: Progress often comes in leaps, with detours, setbacks, and sudden breakthroughs |
| Progress is measurable in percentages | Context-dependent: What works in one organization may be completely ineffective in another |
The Way Out: A Systemic Approach
Anyone who truly wants to steer transformation must learn to regularly pause and examine:
- Do we understand the conditions shaping our actions?
- Where are the systemic levers that create lasting impact?
- What interactions between different areas are we observing?
Instead of linear progress indicators, what’s needed is an assessment mindset that places reflection, learning loops, and context sensitivity at the center.
What Characterizes Systemic Transformation
| Classical Approach | Systemic Approach |
|---|---|
| Works with fixed plans | Works with hypotheses instead of fixed plans |
| Considers isolated measures | Considers interactions instead of isolated measures |
| Relies on large-scale projects | Uses experiments instead of large-scale projects |
| Focuses on control | Focuses on learning cycles instead of control |
| Attempts to shape outcomes | Shapes conditions instead of outcomes |
Transformation demands a different understanding: less the precise execution of a plan, more the continuous orientation and adjustment within a changing environment.
Organizations that grasp this difference work iteratively, leverage feedback systems, and create spaces for experimentation — without losing sight of strategic alignment.
The Alternative: A Compass Instead of a Map
What organizations truly need in complex transformation efforts is not a detailed plan (a map), but a reliable orientation instrument (a compass).
Map vs. Compass
| The Map | The Compass |
|---|---|
| Shows exactly where we want to go and which path to take | Shows direction even when the terrain is unknown |
| Works in known, stable territory | Works in dynamic, unpredictable environments |
| Perfect for predictable environments with clearly defined paths | Enables navigation in complex, evolving systems |
What Makes a Good Transformation Compass?
An effective transformation compass:
- Orients around principles rather than detailed steps
- Makes systemic connections visible instead of examining isolated problems
- Asks the right questions instead of delivering prefabricated answers
- Enables continuous adaptation instead of rigid plans
- Considers interactions between different domains
A New Path: Interconnected Dimensions Instead of Isolated Measures
The solution lies in an approach that views transformation through interconnected fields of action. Instead of launching isolated measures in different areas, what’s needed is a systematic understanding of how different aspects of the organization interact.
The Problem with Isolated Measures
A typical example: Many organizations introduce agile methods (structural level) without adapting leadership culture (cultural level) or rethinking strategy (strategic level). The result: The new methods remain superficial because the systemic conditions are wrong.
The Power of Interactions
When different areas of the organization are consciously aligned with one another, reinforcing effects emerge:
- Leadership — New leadership approaches enable more effective teams
- Teams — More effective teams drive innovation forward
- Innovation — Innovation influences strategic direction
- Strategy — Strategic clarity creates better leadership
This cycle reinforces itself — and that’s precisely where the power of systemic transformation lies.
The network is stronger than the sum of its parts. Those who work on only one dimension will quickly find that impact remains limited. Those who understand and deliberately shape the interplay, however, can trigger system-wide change with comparatively little effort.
What Changes for You
A systemic approach means a fundamental shift in how transformation is pursued. Here are the most important differences:
Instead of project planning, systemic understanding. The first step is not creating a project plan, but collectively understanding the current system dynamics:
- What patterns shape our actions?
- Where do blockages and friction losses occur?
- What interactions do we observe?
Instead of action catalogs, targeted experiments. Rather than working through a comprehensive catalog of measures, small, targeted experiments are launched:
- What happens if we change something here?
- What effects do we observe in other areas?
- What do we learn from this for the next steps?
Instead of progress reports, continuous reflection. Rather than producing monthly progress reports, there is continuous reflection:
- What is working better than expected?
- Where have new obstacles emerged?
- Which assumptions do we need to rethink?
The First Step: An Honest Assessment
Before you launch the next transformation program, an honest assessment is worthwhile:
On the starting point: Do we truly understand the problem we’re trying to solve? Or are we mainly treating symptoms? It is essential to go deeper and identify the systemic causes, not just the visible effects.
On the approach: Are we thinking in projects or in systems? Are we planning linearly or iteratively? The choice of approach fundamentally determines whether we can handle the complexity of transformation or will fail at it.
On the interactions: Are we looking at isolated areas or interconnected dimensions? Are we considering how different changes influence one another? Often the greatest impact lies in the interactions, not in individual measures.
On the mindset: Do we want to control or to navigate? Are we prepared to learn and adapt along the way? The inner mindset often determines success or failure more than the methods chosen.
Conclusion: From the Illusion of Control to the Art of Navigation
The failure of many transformation initiatives is not coincidental — it is the logical consequence of an approach that treats complex, dynamic changes like simple, predictable projects.
There is a way out. Organizations that learn to think and act systemically, that work with hypotheses instead of certainties, and that consciously shape interactions are not only more successful in their transformation efforts — they also become more resilient and adaptable for future challenges.
The decisive difference lies not in better plans or more sophisticated control. It lies in the willingness to understand transformation for what it is: a continuous process of learning and shaping within a living, changing system.
The question is not whether your environment is changing — the question is whether you are prepared to adapt your way of thinking and acting accordingly.
Transformation is not a project you complete. It is a capability you develop.