Complex change processes rarely begin with a sharp picture of the problem. There is a sense that something no longer works, a result that falls short, a structure that pinches, or a collaboration that stalls. But what exactly is going on, and for whom, often proves harder to formulate than expected. In that uncertainty, opinions quickly take over. Loud voices get plenty of airtime, quiet voices barely get heard, and before it is truly clear what needs to be solved, the process has already begun. Building, planning and deciding all happen without a clear, jointly agreed picture of the problem.
That is not a sign of incompetence. It is inherent to the nature of these kinds of processes. Multiple departments are involved, multiple interests, multiple ways in which people view the same situation. External parties often play a role too: suppliers, customers, citizens, regulators, or laws and regulations that set limits on what is possible. Everyone carries their own version of what is happening and what needs to be done. Those versions overlap in part, but rarely align completely.
It is precisely at this stage that the wrong move is often made. Because uncertainty is uncomfortable, there is a tendency to shift quickly into action: a plan of approach, a project group, a point on the horizon. That feels like progress. In reality, it often means tackling a problem that has not yet been shared.
Decisiveness does not resolve uncertainty
Decisiveness is valuable, but it only works when there is something to steer decisively toward. When the problem itself has not yet been articulated, and the expectations of those involved have not yet been laid on the table, action shifts the tension rather than removing it.
That is why it matters to define in advance what the solution actually is. What exactly do you want to achieve, and what does that look like in concrete terms? There should be no room for ambiguity here. As soon as this is negotiated away, as soon as the answer stays vague or shifts from conversation to conversation, it becomes impossible for the process to succeed quickly and effectively. Clarity of purpose is the precondition for speed in execution.
This shows up in a familiar pattern. Hard work goes into a solution, working groups are set up, reports are written and adjustments are made, and yet the sense remains that the process is not really moving forward. Not because people are not putting in the effort, but because the energy is directed at a problem for which no shared picture yet exists.
Whoever slows down at this stage to first understand, ultimately gains time. Whoever pushes ahead without that picture, pays that time back later, often with interest, in the form of resistance, delay, or a process that has to start over.
Looking at the problem from vision
A problem only becomes manageable once a vision underlies it. Not as an abstract image of the future, but as an answer to a concrete question: what do we really want to achieve here, and for whom must this process ultimately deliver something?
Without that vision, a change process quickly becomes a sum of loose bottlenecks. Every part of the organisation brings its own irritation, its own wish, its own interpretation. The process grows, but it does not sharpen. More and more themes get added, and it becomes increasingly difficult to point out where the core actually lies.
Vision acts here as a kind of filter. It helps determine what genuinely contributes to the intended result, and what may feel relevant but mainly makes the process heavier. That filtering is uncomfortable, because it means that not everything that feels like a problem gets included in the approach. But that very choice is what makes a process workable.
Keeping the problem small and clear
A common pitfall in complex processes is that the problem grows along the way. What starts as a concrete challenge gradually turns into a broad theme under which almost everything seems to fall. Culture, structure, leadership, systems, history. Everything connects to everything, and so the process keeps expanding.
This rarely happens deliberately. It arises because every person involved adds their own experience to the picture of the problem, with the best intentions. The result is a problem that becomes intellectually more complete, but practically more unworkable.
A problem that must remain solvable needs boundaries. Not because the broader context does not matter, but because a process only moves forward when it is clear what it is actually about at this moment. That boundary is one of the most important benefits of gaining early insight into motives, approach and expectations: the distinction between what forms the core of the issue and what hangs around it becomes visible before the process gets stuck in it.
Why involvement makes the difference
A change process that is shaped only top-down misses an important source of information: the people who have to deliver the result day to day. They see bottlenecks that are not visible from a higher position, and they experience the consequences of decisions most directly.
When these people are involved only late in the process, the result is an approach that has been thought through but not lived through. The approach can be strong in content and still get stuck, simply because those who have to carry it out never felt ownership of it.
Early involvement of all relevant parties does something different from merely creating support. It surfaces expectations that would otherwise have remained unspoken, it exposes assumptions before they start steering the process, and it gives people the chance to think along about a solution instead of only being confronted with it. That not only increases the quality of the approach, but also the performance of the team that has to carry it.
What actually stands in the way of solutions
It is tempting to assume that a change process gets stuck because of the complexity of the problem itself. In practice, the delay rarely lies there. Most issues, reduced to their core, are clearer and smaller than they appear at first glance. What actually makes a process heavy is what happens around it.
Alongside the interests already mentioned, there is the multitude of opinions, and the way people communicate with each other about what is going on. Some voices become loud and are repeated often, others remain unspoken because someone does not consider them appropriate to share. Decision-making becomes vulnerable as a result: decisions get made based on who speaks loudest or has the most influence, not on what the process actually needs. And leadership that does not see through this dynamic often intervenes at the wrong level: on the content, while the problem lies in the undercurrent.
All these elements together form the dynamic of an organisation. That dynamic is not neutral. When it is not consciously channelled, delay arises because decisions keep getting reopened for discussion. Confusion arises because people carry different versions of the process with them. Dropout arises because those involved disengage the moment they no longer feel heard or seen. And budget overruns arise because a process that gets stuck in people and opinions, by definition, takes longer and costs more than planned.
The greatest risk in all of this is not the delay or the budget. The greatest risk is that the original problem, despite all the effort, ultimately does not get solved.
The moment when insight delivers the most
Insight into motives, approach and expectations is often applied only after a process has gotten stuck, as a repair after the fact. Yet that same insight has the most value right at the start, when the picture of the problem still needs to take shape and the pull toward quick action is strongest.
At that stage, it helps to see what expectations exist among the people the process affects, which assumptions are being carried along without ever being voiced, and which interpretations of the problem exist side by side without anyone noticing. This does not prevent a process from being complex, because complex issues remain complex. What it does prevent is that complexity becoming unmanageable.
Beyond that, you want to keep the energy in your team to move forward high, and the dynamic positive and solution-focused. A process that takes a long time asks a great deal of people, and setbacks along the way are unavoidable. That is why it is so wise to know the motives of the participants. What drives them, and what do they assume? A team that knows this about each other can actually help one another through setbacks and grumbling, instead of getting stuck on it internally.
A change process that begins this way gains direction. A shared picture forms of what truly needs to happen, who is needed for it, and what everyone's contribution to it is. That shared picture is ultimately what makes the difference between a process that moves and a process that gets stuck in good intentions.
The right moment to start with this is not when the problem is fully clear. The right moment is when you notice that it is not yet clear, and still feel the pressure to already start acting.
That is why, in complex change processes, we always choose to deploy CIRCYOULAR®, right from the start. Not as an extra step alongside the process, but as the foundation beneath it. It brings to light early what would otherwise only surface after months of delay: which interests are at play, which expectations exist, and which dynamic will carry the process forward or hold it back. That insight takes time upfront. It saves considerably more time, money and frustration further down the line, and it is precisely what makes the difference between a process that gets stuck in good intentions and a process that actually solves the problem.