The space between a familiar system and an emerging one can feel disorganised. It is also a phase in which important transformation work can take place.
During change, organisations often try to move forward while protecting daily operations. Existing roles still need to function, new expectations are introduced and decisions must be made before every answer is available. The result can look like resistance; in some situations, a lack of shared clarity is part of the issue: people do not yet know what has changed, what has not, or what they are responsible for now.
A useful architecture for change does not attempt to remove all uncertainty. It creates enough structure for people to orient themselves, make sound choices and learn as the situation develops.
Name the reality before designing the answer
Movement starts with an honest diagnosis. What is creating pressure today? Which processes are no longer serving the organisation? Where do responsibilities overlap, and where is ownership missing? What must remain stable while other elements evolve?
This first step is not a search for blame. It separates symptoms from structural causes. A workload problem may be rooted in unclear decision rights. Repeated delays may reveal an approval process that no longer fits the pace of the organisation. Tension between teams may come from competing priorities rather than difficult personalities.
Create a shared direction
A vision only becomes useful when people can translate it into choices. Teams need a clear answer to a small set of practical questions:
- What are we trying to achieve, and why does it matter now?
- Which priorities guide trade-offs when everything feels urgent?
- Who decides, who contributes and who needs to be informed?
- What will we stop, protect or test during the transition?
- How will we recognise meaningful progress?
These questions can turn an abstract ambition into reference points. They can also reduce the hidden effort people spend interpreting mixed signals or recreating decisions that were never anchored.
Build a workable sequence
Large transformations become more manageable when they are organised into visible movements. Instead of launching every initiative at once, identify what needs to happen first so that the next step becomes possible. Clarify dependencies, assign ownership and keep the number of immediate priorities realistic.
A practical sequence often begins with one stabilising action, one structural decision and one learning cycle. The stabilising action can help protect the operation. The structural decision can reduce ambiguity. The learning cycle can create room to test assumptions and adjust without treating every adjustment as failure.
Support the human rhythm of change
People rarely experience change at the same speed. Some are already working towards the new model; others are still making sense of what is being left behind. Leadership presence matters here. Listening, repeating the direction and acknowledging what is genuinely difficult are operational acts, not soft additions.
Regular moments of coordination can help teams bring tensions into the open before they become bottlenecks. Short feedback loops can also help leaders distinguish temporary discomfort from a structural issue that needs intervention.
Anchor what should last
Change is not complete when a new process is announced. It becomes real when responsibilities, routines and decisions consistently reflect the intended direction. Review what is working, simplify what is not and transfer ownership to the people who will carry the work forward.
The goal is not permanent dependence on external support. It is an organisation that understands its own choices, can adjust with confidence and retains enough breathing room to keep moving.
A useful place to begin
If your organisation is between two ways of working, begin with one question: what do people need to understand today in order to make a sound decision tomorrow? The answer often reveals the first piece of structure that is missing.
