I have noticed over the past few years that my attitude towards transformation is changing. Perhaps it is because I have increasingly worked with organisations, teams and people facing complex challenges. Or perhaps it is because I have become more sceptical of a logic that is deeply familiar in consulting (even in my own work), politics and organisations: we identify a problem, make its urgency visible, explain its causes, and then bring in expert knowledge and solutions. From there, we develop measures, responsibilities, timelines and KPIs. It is a rational and professional approach, and it has become almost second nature in many projects.
And yet I increasingly wonder whether this logic is still sufficient for the major challenges we are facing today. Many of these challenges are no longer clearly defined problems with identifiable causes and known solutions. Climate change, biodiversity loss, labour shortages, social polarisation or organisational transformation are expressions of complex systems. They emerge from an interplay of relationships, structures, decisions, habits and ways of thinking that have developed over time and continuously influence one another. That is why I believe it is not enough to look at visible symptoms and then search for the most effective measures to address them.
My own shift begins with the question of what we actually do when we define something as a problem. The familiar storyline often goes something like this: problem → urgency → need for action. We show what is not working, demonstrate how serious the challenge is, and derive from this the conclusion that something must be done. This is understandable and sometimes necessary. But problem awareness does not automatically create ownership or the energy for change. In fact, when a problem appears sufficiently large and complex, our sense of agency can become smaller rather than larger. We may understand the problem better without necessarily feeling more connected to changing it.
That is why I am increasingly interested in a different movement: we begin with perception, seek to understand relationships and patterns, and from there explore possibilities together. This does not mean downplaying problems or denying their urgency. It means approaching them differently. Rather than only asking what is not working and how we can reduce the pressure created by it, we look at the patterns and relationships that produce the problem in the first place, the assumptions behind them, and what we may have overlooked. From this perspective, the problem does not become the starting point for a predefined solution. It becomes the starting point for a shared exploration.
This also changes the role we ourselves play in such a process. When dealing with complex challenges, we are not standing outside the problem, observing a system from a distance. We are part of the system we are trying to change. This makes the traditional distinction between problem owner and problem solver much more questionable. The external expert analyses the system, identifies the causes and recommends measures, while the organisation is then responsible for implementation. But who actually decides what the problem is in the first place? Which perspective is being considered? Which relationships become visible, and which remain invisible? And what assumptions about the future are already embedded in the proposed solution?
These questions have fundamentally changed the way I understand my own role as a consultant and facilitator. I increasingly want to move away from entering a room and saying: “I understand your problem, I know its causes, and I have a model that can help you solve it.” Of course I bring knowledge, experience, methods and perspectives, and that is still an important part of my contribution. But I increasingly see my role as bringing this knowledge into a shared process of inquiry rather than presenting it as a finished answer. For me, it is less about transferring knowledge and more about bringing different forms of knowledge into relationship with each other.
People within an organisation possess knowledge that no external consultant can ever fully access. They know the history of the system, its informal rules, its relationships and its contradictions. External people, on the other hand, bring different experiences, models and perspectives. Both are valuable. But meaningful change often emerges where these different forms of knowledge meet and something new is created. The relationship is no longer “we know and you implement”. It becomes an attempt to understand together what is actually happening and what possibilities might emerge from that understanding.
This also shifts the starting point of transformation. For me, transformation does not begin only when a new strategy is approved or a measure is implemented. It can begin much earlier: in the moment when people start to perceive their own system differently. When a relationship becomes visible that nobody had considered before. When an unquestioned pattern is suddenly questioned. When someone realises that a decision is not repeatedly made because it is necessarily the best decision, but simply because it is the way things have always been done. Or when something that was previously seen as a weakness suddenly becomes visible as a resource. These moments cannot be fully planned, but we can create spaces in which they are more likely to emerge.
This leads me to a different understanding of the future. In many transformation processes, we define a target state first and then plan the path towards it. That can be useful. At the same time, there is a danger that we describe the future too early through the assumptions and possibilities of the present. Especially in complex systems, we often do not know at the beginning of a transformation what possibilities might actually emerge. That is why I increasingly prefer to think in terms of possibilities rather than finished solutions. A solution closes a search process. A possibility opens one. It invites us to try something, observe what happens, reflect on what we learn and choose the next step based on that experience.
Transformation then becomes a learning journey. Not a linear process in which we already know at the beginning what the end result should look like, but an iterative process of perceiving, experimenting, observing, reflecting and changing. This does not mean abandoning strategy or planning. It means acknowledging that insight does not only emerge before we act; it also emerges through action itself. We learn by trying something, and we adjust our assumptions when reality shows us something different.
This also changes the meaning of ownership for me. Ownership does not automatically emerge because people are given responsibility for implementing a project. An organisation can have a perfect project plan and still generate very little genuine energy for change. Ownership is more likely to emerge when people experience themselves as authors of the transformation. When the task is not to implement a concept developed somewhere else, but to shape their own organisation, their own place or their own system. That is why I am increasingly interested in the question of how we can help people move from being implementers to becoming shapers of change.
Perhaps this does not require more expert knowledge, but a different relationship with expertise. Expertise does not become less important. Quite the opposite. But its function changes. The expert does not necessarily have to provide the answer. Their role can be to introduce new perspectives, make relationships visible, ask better questions and open up possibilities. Perhaps the most valuable form of expertise is not the one that already knows the way, but the one that helps people discover a way together.
The longer I work with transformation, the less convinced I am that complex change primarily requires better answers. Perhaps what we need are better shared processes of inquiry. Processes in which we allow ourselves to look more closely before deciding what the problem is, who or what is responsible for it, and which solution should be implemented. How did this situation come about? Which patterns keep it in place? Which relationships matter? Which perspectives are missing? What possibilities for change are already present? Where is there energy, capacity or an experiment we could build on? And what could we try in order to learn more?
For me, this changes the fundamental distinction between implementation and transformation. Implementation asks how we can bring a known solution into an existing system. Transformation begins earlier and asks what we need to perceive and understand together so that new possibilities for change can emerge within that system.
Perhaps this is also the shift I feel most strongly in my own role. I increasingly want to be less of an expert in the solution and more of a facilitator of a shared process of inquiry and change. Not because I believe I know less, but because I have learned that knowledge alone rarely transforms complex systems. What makes change possible is the connection between knowledge, experience, perception, relationships and the willingness to experiment together with something whose outcome is not yet fully known.
And perhaps genuine transformation begins exactly there: not with the perfect answer, but with the shared willingness to look more closely and discover where change might actually come from.ne transformation begins exactly there: not with the perfect answer, but with the shared willingness to look more closely and discover where change might actually come from.
