Projects move more slowly than expected. Decisions keep being reopened. Tasks remain unfinished, or results fall short of what was originally intended. When implementation starts to hesitate, I see it as an important red flag, whether the issue is meeting invitations, decision-making or approvals.
When I notice this, my first question is what sits behind it. Slow or difficult implementation is a symptom. Very often, the underlying cause lies somewhere in the structure.
That does not necessarily mean there is no structure. Most initiatives already contain the beginnings of one in three simple questions: What are we trying to achieve? Why does it matter? And how are we going to get there?
The answers shape objectives, responsibilities, processes and actions. They often originate at a higher level, for example in company objectives, and are then translated step by step through the organization. Each level takes what it has been given, makes it more specific and develops it further.
But not everyone involved necessarily has the full picture of the What, Why and How. And even when they do, they will not necessarily interpret it in the same way. Different functions and individuals look at the same direction through different lenses, shaped by their expertise, prior knowledge and the practical requirements of their work.
As the initiative moves closer to implementation, decisions become more specific, processes are added and solutions are adapted to particular working contexts. The structure changes along the way, and sometimes it changes to the point where it no longer works equally well across the organization.
The objective may no longer mean quite the same thing to everyone. The rationale behind a decision may be obvious to the people who made it, while only part of it reaches those responsible for putting it into practice. One function solves a problem one way, another develops a different solution to the same issue. Additional requirements are added, temporary workarounds become permanent and individual processes gradually develop a logic of their own.
Every one of those steps may make perfect sense on its own. Yet taken together, they can move the overall structure further and further away from what it was originally designed to achieve. Eventually, it stops working.
When things start taking longer, responsibilities become unclear or decisions require repeated alignment, the cause often lies somewhere in this drift. Different parts of the organization may all be working hard, but they are no longer necessarily working in the same direction.
The response at that point is often to demand more speed. But pushing harder does not fix the underlying problem. First, you need to understand where the structure has stopped working and why.
I usually go back to the beginning and ask those three seemingly simple questions again: What were we actually trying to achieve? Why did it matter? And how was the chosen approach supposed to get us there?
Those questions often reveal quite quickly whether there is still a shared understanding or whether different parts of the organization have drifted apart. Perhaps the objective is still clear, but the approach no longer fits. Perhaps a process is working exactly as designed, but no longer serves its original purpose. And it is not unusual for different stakeholders to have developed different ideas over time about what they are actually trying to achieve.
Seeing this requires moving between different levels. Sometimes the problem sits in a very small detail: an unclear handover, a decision right that was never properly defined, or a piece of information missing at a crucial point. But sometimes that detail only makes sense once you step back and look at the wider system.
Because problems often do not originate at the same level where they become visible. A communication problem may actually stem from an unclear decision. Resistance to change may indicate that people have understood something differently or have encountered an issue during implementation that was invisible during planning. A project that appears to be moving too slowly may be held back by dependencies between functions that, viewed individually, are all operating perfectly reasonably.
For me, the real work is therefore to trace the visible problem back to the point where the underlying structure stopped serving its purpose. Only then does it make sense to decide whether something needs to be clarified, realigned or genuinely changed.
It also means that even a structure that works cannot simply be designed once and then rolled out unchanged. In complex initiatives, implementation is often the point at which we discover which assumptions hold, which consequences could not have been anticipated and where people with more detailed knowledge encounter problems that could never have been fully visible from a higher planning level.
Feedback and adaptation loops are therefore not a concession to poor planning. They are a necessary part of good planning. Insights and objections from implementation need to feed back into the process and be assessed on their merits. Perhaps the original decision is confirmed. Perhaps it needs to be adjusted. What does not work, in my view, is to dismiss resistance on the assumption that people simply do not like change and then continue with the original plan regardless of what is being learned during implementation.
In complex initiatives, failing to build in these feedback mechanisms is fundamentally unsound. Planning cannot anticipate every piece of detailed knowledge that will only become relevant once implementation is underway.
Creating order in complex situations therefore does not mean simplifying everything as quickly as possible. It means making the underlying structure visible again: understanding why it was created, how it evolved and where it stopped doing what it was meant to do. Only then can you decide what should remain, what needs to be adapted and what needs to be rebuilt.
Complexity does not disappear but chaos becomes something you can work with again.