Understanding Change, Innovation and Complexity

Most change and transformation programmes do not fail because they are badly designed or poorly managed. Many of them are thoughtful, carefully scoped, well resourced, and run by capable people. They fail because they are built on an assumption that is quietly wrong.

The assumption is that change is something you can design up front and then implement into an organisation.
In reality, organisations are not machines that can be reconfigured by pulling the right levers. They are living systems made up of people, relationships, habits, incentives, power dynamics, histories, and unspoken norms. When you introduce change into such a system, the system responds. It adapts, resists, reinterprets, reshapes, and sometimes absorbs the change in ways no plan can fully predict.

A plan can tell you what you intend to do. It cannot tell you how the system will meet it.
Most change programmes are strong on intent and weak on interaction. They focus on what will be delivered, by when, and by whom. They are often much less attentive to how people will experience the change, what it will threaten, what it will disrupt, what it will ask people to let go of, and what informal structures it will collide with.
As a result, change is treated as a rollout rather than a relational process.

This creates several common failure patterns.

One is that people comply on the surface while disengaging underneath. They attend the workshops, complete the training, and say the right things, but their behaviour does not shift because the change does not make sense in their lived reality, or because it conflicts with incentives, pressures, or identity.

Another is that early resistance is interpreted as a problem to be managed rather than as information about the system. When people push back, raise concerns, or fail to engage, this is often a signal that something important has been missed. Instead of listening, programmes often double down on communication, persuasion, or enforcement, which deepens the disconnection.

A third is that complexity is mistaken for complication. Leaders expect linear progress through milestones, but complex systems do not move in straight lines. New issues emerge. Priorities shift. Political or regulatory forces intervene. What looked sensible in the planning phase no longer fits the reality on the ground. Without the capacity to adapt, the programme either stalls or becomes increasingly fragile.

Finally, many programmes aim for delivery rather than for capability. They focus on implementing the change rather than on helping the system learn to change. This creates dependency on external consultants, programme teams, or heroic leaders, and once they leave, the organisation quietly drifts back to old patterns.

In short, change programmes fail when they try to impose change on a system instead of working with it.

What makes change more likely to succeed is not better planning, but better sensemaking, better dialogue, better feedback, and better adaptation. It is the ability to notice how the system is responding and to reshape the change accordingly. It is the willingness to treat resistance as data, not as obstruction. It is the humility to accept that you do not know everything at the start, and the discipline to keep learning as you go.
This is why systemic approaches to change focus less on controlling outcomes and more on cultivating the conditions for change. Conditions such as trust, psychological safety, shared purpose, meaningful participation, and fast feedback. When these are present, change does not have to be forced. It begins to emerge.

Change fails when it is treated as a project. It succeeds when it is treated as a relationship.

Because most organisations are built to run on checklists.

That is not a criticism. It is how large, complex organisations create reliability, safety, and consistency. Processes are standardised. Work is broken into tasks. Plans are created. Progress is tracked. This makes simple and complicated work possible at scale.
And much of that work should be tick box.

Continuous improvement, lean processes, compliance, quality management, and operational delivery all benefit from clarity, structure, and closure. When you are improving an existing process, reducing waste, or rolling out something well understood, ticking boxes is not a failure. It is how work gets done.

The problem arises when this same logic is applied to complexity.

Innovation and transformational change are not linear, predictable, or decomposable in the same way. They involve uncertainty, ambiguity, human difference, and emergence. They require exploration, learning, reframing, and iteration. They do not move neatly from step one to step two.

When organisations try to manage innovation using the same Chronos logic they use for delivery, it becomes a plan rather than a practice. It becomes a sequence of activities to complete rather than a process of discovery to live through.
So innovation becomes a phase in the project plan.

Run the workshop. Build the prototype. Launch the pilot. Capture the learning. Tick the box.

At that point the energy drains out of it, not because people are lazy or cynical, but because humans naturally follow the path of least resistance. In NLP we would say the unconscious mind is designed to conserve energy and seek ease. If the task is framed as something to complete rather than something to care about, most people will complete it and move on.

This is not a moral failing. It is how people are wired.

Innovation requires something different.

It requires Kairos rather than just Chronos. Time to think. Time to notice. Time to play with ideas. Time to walk around the block and ask, what if we tried this instead. It requires psychological permission to not know, to get things wrong, and to learn.
This is why mindsets matter so much.

Presuppositions like “there is no such thing as failure, only learning” or “fail fast” or “screw it, let’s do it” are not slogans. They are cultural signals that experimentation is safe, that curiosity is valued, and that learning is more important than looking good.
Without those signals, people will protect themselves by playing it safe. They will do what is asked, produce what is required, and avoid risk. Innovation then becomes performative rather than exploratory.

There is also a loss of purpose that often happens inside plans.

When work is reduced to tasks without context, without meaning, and without a felt sense of why it matters, people stop relating to it as change and start relating to it as admin. A task without purpose invites compliance. A purpose without a task invites dreaming. Innovation needs both.

It needs structure and energy.

When either is missing, the system defaults to what it knows best, which is ticking boxes.

So innovation becomes tick box not because organisations do not care, but because the structures, time logic, and psychological conditions needed for real innovation have not been created.

Systemic innovation works differently.

It distinguishes between where checklists help and where they harm. It makes space for Kairos inside Chronos. It treats innovation as a living process rather than a project phase. It reconnects work to purpose, meaning, and consequence. It creates permission to learn, to iterate, and to evolve.

When those conditions are present, innovation stops feeling like something to complete and starts feeling like something to care about.

That is when it becomes real.

Innovation sprints, pilots, and MVPs often produce good ideas. They can be energising, creative, and genuinely insightful. Teams come away feeling hopeful, aligned, and motivated. Something new has been born.
And then, very often, nothing happens.
The idea sits in a deck. The prototype is admired but not adopted. The pilot runs once and quietly fades away. The energy dissipates and the system returns to business as usual.
This does not happen because the ideas were poor. It happens because the system was never prepared to receive them.
Most innovation activity is designed to produce novelty, not to carry novelty into the existing organisation. Sprints are optimised for speed, creativity, and divergence. Organisations, however, are optimised for stability, efficiency, risk management, and predictability. When the output of a sprint meets the reality of the organisation, the two logics often collide.
The innovation makes sense in the room. It does not yet make sense in the system.
There are several reasons for this.
One is that pilots are treated as experiments in isolation rather than as probes into a living system. Teams test whether something works technically or conceptually, but they do not test how it interacts with incentives, governance, power, compliance, budget cycles, roles, and identities. The pilot may succeed on its own terms, but fail in relation to the wider system it must live inside.
Another is that ownership is unclear. The sprint team creates the idea, but no one inside the organisation feels responsible for carrying it forward. Sponsors move on. Champions lack authority. Delivery teams were not involved early enough to feel invested. The idea becomes everyone’s responsibility and therefore no one’s responsibility.
A third is that embedding is treated as a later phase rather than as something that must be designed from the start. Questions of governance, funding, operational fit, risk, capability, and long term stewardship are postponed until after the pilot. By the time they surface, momentum has been lost and the organisational immune system has kicked in.
There is also a deeper psychological dynamic at play. Innovation work is often exciting because it is safe. It happens in workshops, labs, and sandboxes that are deliberately separate from the pressures of everyday work. Embedding means bringing the idea into contact with those pressures. It means changing routines, renegotiating priorities, and sometimes challenging existing power structures. This is where innovation stops being inspiring and starts being disruptive in the emotional sense of the word. Without support, many organisations unconsciously avoid that moment.
From a systemic perspective, this is entirely predictable. New ideas are disturbances to a system. If the system does not have the capacity, permission, or motivation to adapt, it will either neutralise the disturbance or eject it.
This is why systemic innovation treats embedding not as a final step, but as a design challenge in its own right. It asks early questions. Who will own this in six months. What will this replace or displace. What capabilities will be needed to sustain it. What governance will hold it. What tensions will it create. What will people have to stop doing for this to live.
When these questions are explored alongside ideation, pilots become bridges rather than islands. They are shaped in dialogue with the system that must absorb them. They evolve not just to be clever, but to be viable, legitimate, and meaningful in context.
Ideas fail to scale not because they are too radical, but because they are not relational enough.
Innovation sticks when it is woven into the fabric of the organisation, not dropped onto it.

If you have lots of ideas and nothing is moving, the problem is almost never a lack of creativity. It is a lack of connection between the ideas and the system they need to live inside.
This can feel deeply frustrating, especially when people have invested time, energy, and care into generating those ideas. It can start to feel as if the organisation is resistant, slow, or simply not serious about innovation. In reality, what is usually happening is that the ideas have not yet found a pathway into the existing structures, incentives, and rhythms of the organisation.
An idea on its own has no power. It only becomes powerful when it becomes connected.
The first thing to do, therefore, is to stop trying to push ideas forward and start trying to understand what they are bumping into.
Every organisation has invisible constraints. Budget cycles. Governance rules. Risk thresholds. Informal power structures. Cultural norms about what is acceptable to try and what is not. Competing priorities that are not written down anywhere but are felt by everyone. When ideas stall, it is often because they are colliding with one or more of these forces.
Instead of asking, how do we get people to adopt these ideas, a more useful question is, what would need to be true in this system for these ideas to be able to move.
That shift changes everything.
It turns the problem from one of persuasion into one of sensemaking. It invites you to explore the system rather than fight it.
Practically, this means bringing the ideas back into dialogue with the people and parts of the organisation they affect. Not to sell them, but to learn from them. What feels risky about this. What feels misaligned. What would this disrupt. What would this make harder. What would it make easier. What would have to stop for this to start.
These questions often surface tensions that were invisible in the ideation phase. That is not a sign of failure. It is a sign that the work is becoming real.
It is also important to notice that not all ideas deserve to move forward in their current form. Some are early sketches. Some are symptoms of deeper needs. Some are valuable precisely because they reveal what the system is not ready for yet. Letting ideas evolve, combine, or even dissolve is part of a healthy innovation process.
This is where explicit reframing and ideation techniques are powerful. They allow teams to reshape ideas so that they fit the system better, or to reshape the system just enough to make space for the ideas. Sometimes the right move is not to push harder, but to redesign the idea so it meets the organisation where it is.
Finally, it helps to shift focus from ideas to pathways. Ask not just what is the idea, but what is the smallest meaningful step that could move this into practice. A conversation. A micro experiment. A change in policy language. A new role. A small shift in governance. Innovation rarely moves as a leap. It moves as a series of small, relational steps.
When ideas are sitting on the shelf, they are not dead. They are waiting for the system to be ready.
Your task is not to force them into action, but to help the system become able to carry them.

When a change or innovation programme stalls, the instinct is often to try to restart it by adding more energy. A new plan. A new sponsor. A new set of workshops. A new deadline. A fresh round of communication.
Sometimes that helps. More often, it simply layers new activity on top of unresolved tension.
A stalled programme is rarely a sign that people do not care. It is more often a sign that something important is not being spoken about, not being seen, or not being worked with.
Before you try to restart anything, it is worth pausing and asking a different kind of question. Not how do we get this moving again, but what caused it to slow down in the first place.
Momentum does not disappear randomly. It is lost when people become uncertain, disconnected, overloaded, misaligned, or quietly disillusioned. It is lost when the work no longer feels meaningful, safe, possible, or worth the effort it requires. It is lost when the programme stops fitting the system around it.
So the first act of restarting is sensemaking, not mobilisation.
This means creating a space where the people involved can step back from delivery and reflect together. What has changed since we started. What feels stuck. What feels risky. What feels unclear. What feels pointless. What feels politically difficult. What feels personally costly. What assumptions are no longer true.
These are not comfortable questions, especially in organisations that value confidence and progress. But they are the questions that restore honesty to the work.
Very often what emerges is not a technical problem but a relational or psychological one. Trust may have been lost. A key stakeholder may have disengaged. A conflict may have gone underground. A decision may have been made elsewhere that changed the context. A quiet sense of futility may have crept in.
You cannot restart a programme without working with whatever has taken the life out of it.
Once this has been surfaced, the second move is to reconnect the work to something that feels real and meaningful again. Many programmes stall because they drift away from lived experience into abstraction. They become about frameworks, deliverables, or targets rather than about the human or organisational need they were created to serve.
Regrounding the work in that original need, or in the current version of it, often restores energy more effectively than any motivational speech.
The third move is to reduce the scale of what you are asking for.
Stalled programmes are often burdened with too much ambition and too little capacity. Restarting does not mean recommitting to the entire roadmap. It means finding a small, coherent next step that people can genuinely take. Something that restores a sense of agency and progress. Something that creates a little evidence that movement is possible again.
From a systemic perspective, momentum is an emergent property. It cannot be commanded. It arises when people feel safe enough, clear enough, connected enough, and hopeful enough to act.
So restarting is less about pushing and more about tending.
Tending to clarity. Tending to relationships. Tending to meaning. Tending to the small signals that tell you whether the system is ready to move.
When those conditions are restored, momentum often returns on its own.
Not because you forced it, but because the system once again has somewhere it wants to go.

Resistance to change is often treated as a problem to be overcome. Something to manage, reduce, or bypass. People who resist are labelled as blockers, laggards, or obstacles to progress.
From a systemic and human perspective, this framing is almost always wrong.
Resistance is information.
It tells you something about how the change is being experienced, what it threatens, what it disrupts, and what it asks people to give up. When people resist, they are rarely resisting change in the abstract. They are resisting a perceived loss of control, competence, identity, security, status, or meaning.
There is also a more ordinary and often overlooked reason for resistance.
Many change initiatives are delegated. People pick them up because they are tasked to do so, not because they feel any intrinsic connection to them. They may not understand why the organisation cares so much about this change, whether it is the right change, or whether those higher up fully understand its impact on people lower down. They may privately doubt the ethics, the fairness, or the wisdom of what they are being asked to implement.
In that situation, resistance is not a character flaw. It is a moral and motivational signal.
If you are asked to deliver something you do not believe in, or do not understand, or quietly feel is harmful, your system will resist. Even if your conscious mind tries to comply.
This is why we place so much emphasis on sponsor discovery and on creating a meaningful mission brief at the start of change. Not as a formality, but as a way of answering two essential questions.
Why does this matter to the organisation.
Why should this matter to me.
If those questions have never been answered, or have only been answered in abstract corporate language, then it is often worth pausing to do that work, even mid programme. Reconnecting the change to its real purpose, its real stakes, and its real human impact often does more to restore engagement than any amount of motivation or pressure.
Engagement begins when you stop trying to convince and start trying to understand.
This means creating spaces where people can speak honestly without being judged or corrected. Where concerns are not immediately reframed into positivity. Where scepticism is allowed. Where doubt is treated as a legitimate response to uncertainty rather than as a defect of attitude.
This requires psychological safety. And psychological safety does not arise from telling people they are safe. It arises when they see that speaking truth does not lead to punishment, marginalisation, or subtle exclusion.
In global organisations this becomes especially important. Changes designed at headquarters often collide with very different realities in regional offices. What looks elegant and sensible at the centre can feel clumsy, unfair, or even damaging at the edges. If those voices are not heard, resistance will grow quietly until it becomes visible, usually when it is much harder to work with.
This is why listening is not a soft skill. It is a core systemic intervention.
There is a simple but demanding question that sits underneath all of this.
Am I willing to hear the truth of how this change is experienced, even if it is uncomfortable.
Am I willing to create the conditions for that truth to emerge.
If the answer is no, engagement will remain superficial.
Practices from psychology and sensemaking, including NLP, add real value here because they help people surface what is often implicit, unspoken, or difficult to articulate. They help people notice their own assumptions, emotional responses, and internal conflicts, and to express them in ways that can be worked with rather than acted out.
Engaging people who did not choose the change is not about selling them a vision. It is about inviting them into a relationship with uncertainty, meaning, and responsibility.
Resistance is not the enemy of change.
It is one of its most valuable teachers.

When work is delegated, it is easy for people to feel as if it does not really belong to them. They become implementers of someone else’s thinking rather than authors of something meaningful. The work turns into a task to be completed rather than a change to be shaped.
In that state, people may still perform, but they rarely care deeply. Energy becomes compliance. Creativity gives way to caution. Responsibility narrows to doing what is asked rather than doing what is needed.
This is not a failure of attitude. It is a predictable human response to loss of agency.
People care about what they feel connected to, what they have some influence over, and what aligns with their sense of purpose, values, or professional identity. When those conditions are absent, motivation thins out.
So the way to help a team care is not to motivate them harder, but to reconnect them to authorship.
This starts by bringing the team back into the “why” of the work. Not the polished narrative, but the real one. Why does this matter to the organisation. What problem is it trying to solve. What happens if it fails. Who is affected and how. What tensions is it trying to navigate. What trade-offs are involved.
Very often, teams have only been given the “what” and the “when”. They are told what needs to be delivered and by when, but not what it is in service of. Without that context, it is hard to care. With it, something often shifts. The work becomes intelligible rather than arbitrary.
The second move is to invite the team into shaping the work rather than just executing it.
This does not mean reopening every decision or dissolving all constraints. It means creating space for the team to influence how the work is done, what is prioritised, what risks are taken, and what assumptions are challenged.
This is where systemic and design practices matter. They give teams structured ways to explore the system they are working in, surface tensions, generate options, and make sense of complexity together. Through that process, the work becomes something the team is in relationship with, not just responsible for.
It also matters to name the emotional and ethical dimensions of the work.
Teams often carry unspoken doubts. Is this actually the right thing to be doing. Who benefits from this. Who might be harmed. What values are we enacting here. What compromises are we making.
When these questions are not acknowledged, they leak out as disengagement, cynicism, or resistance. When they are made discussable, they can be worked with. Even when people do not fully agree, they are more likely to care when they feel the moral and human dimensions of their work have been taken seriously.
Another important shift is from task ownership to stewardship.
Rather than asking people to own deliverables, invite them to steward a part of the system. A stakeholder group. A capability. A risk. A learning loop. A relationship. Stewardship creates a different quality of connection. It positions people as caretakers of something that matters, not just as executors of instructions.
Finally, it helps to recognise that care grows through feedback.
When teams see the impact of their work, hear from people it has helped, or notice small shifts in the system as a result of what they are doing, motivation deepens. When work disappears into reports and governance layers, motivation evaporates.
So if you want people to care, make the impact visible. Make learning visible. Make progress visible, even when it is partial or messy.
Care is not something you inject into a team.
It is something that emerges when people feel connected, trusted, and able to make a difference.
That is the work of leadership in complex change.

Leaders rarely disagree because they are irrational or uncooperative. They disagree because they are accountable for different parts of the system, they bring different perspectives and styles, and they are motivated by different things.
They also disagree because they are human.
They have personal ambitions, fears, loyalties, reputations to protect, and careers to navigate. They care about different outcomes. They stand to gain or lose different things from the same change. All of this is always present, even when it is not spoken about.
So conflict is not an anomaly in leadership teams. It is the normal expression of a complex system trying to coordinate itself.
Alignment, in this context, is not about getting everyone to agree or think the same way. It is about creating enough shared understanding, trust, and honesty that these differences can be seen, named, and worked with rather than acted out indirectly.
This begins with making the system visible.
Leaders need ways to surface how their priorities, incentives, pressures, and assumptions interact. How what looks sensible from one role creates problems in another. How local optimisation leads to global friction. How decisions ripple across boundaries and time.
This is why systemic mapping and structured dialogue are so important at leadership level. They create a shared surface on which different realities can be placed side by side. They allow leaders to say, this is what I am accountable for, this is what I am worried about, this is what I am protecting, and this is what I need, and to have that heard without it immediately turning into debate.
Just as important is making personal motivation discussable.
What do I actually want from this. What do I fear losing. What feels risky for me. What feels ethically uncomfortable. What feels career limiting or career enhancing.
These questions are always in the room. When they are not spoken, they distort behaviour. When they are spoken, they become something the system can work with.
This requires psychological safety. Leaders need to believe that telling the truth will not be punished, used against them later, or quietly remembered at promotion time. Without that, alignment will always be superficial.
It also helps to have a skilled external voice in the room. Someone who is not caught in the internal politics, who can listen deeply, reflect what is being said and not said, and gently challenge inconsistencies, blind spots, and untested assumptions. This is often what allows the real conversation to begin.
Another important principle is timing.
In systems thinking we talk about sensitive dependence on initial conditions. Small misalignments early on can become large failures later. This is why having the difficult conversations early is not a risk. It is a form of risk management.
It is far better to surface disagreement, doubt, and tension at the start than to pretend alignment and discover the cracks later when there is sunk cost, public commitment, and political pressure to continue.
Sometimes this leads to a hard but wise outcome.
The decision not to proceed.
Or the decision to radically reshape the ambition so that it fits the system more honestly.
Or the decision to narrow the scope to what is actually within the organisation’s capacity to do well.
These are not failures. They are forms of success.
Fail fast, in this deeper sense, does not mean act carelessly. It means learn early enough to avoid doing harm.
Finally, alignment is not a one off event.
It is not something you achieve in a workshop and then tick off. It is a living practice of returning to purpose, revisiting assumptions, renegotiating trade-offs, and staying in relationship as conditions change.
Alignment is not about eliminating difference. It is about creating enough coherence that difference becomes a resource rather than a source of fragmentation.
That is what alignment looks like in living systems.

The first thing to say is that you cannot measure complex change in the same way you measure delivery.
If you try to do so, you will end up measuring activity rather than impact, outputs rather than outcomes, and compliance rather than learning. You will get lots of data and very little insight.
This does not mean you should not measure change and innovation. It means you need to measure different things, in different ways, at different times.
In simple and complicated work, you can define success in advance and track progress against a plan. In complex change, you often do not know what success will look like until the system begins to respond. So measurement has to be developmental rather than evaluative.
It has to help you learn, not just judge.
One way to think about this is in terms of three layers.
There is the layer of observable change. Are people behaving differently. Are decisions being made differently. Are new practices actually being used. Are old practices being let go of. These are often more reliable signals than formal metrics because they show whether the system is genuinely shifting.
There is the layer of relational and cultural change. Is trust increasing or decreasing. Are conversations becoming more open or more guarded. Are people willing to speak honestly about problems. Are different parts of the organisation collaborating more or less easily. These are harder to quantify, but they are often the leading indicators of whether change will stick.
There is the layer of systemic impact. Are feedback loops working better. Are bottlenecks easing. Are unintended consequences reducing. Is the system becoming more resilient, more adaptive, or more capable of learning. These are signs that the system itself is becoming healthier, not just that a particular initiative has been delivered.
Alongside this, there are of course commercial and operational measures. Cost, revenue, performance, quality, safety, customer experience, and so on. These matter, but in complex change they tend to lag behind reality. By the time they move, the change has already either taken root or failed.
So you use these measures, but you do not rely on them alone.
Another important shift is from measuring success to measuring learning.
In innovation especially, early work is not about being right. It is about discovering what works, what does not, and why. A prototype that fails but teaches you something valuable is often a success. A pilot that succeeds technically but teaches you nothing about the system may be a dead end.
So good measures of innovation include questions like: What did we learn. What surprised us. What assumptions were challenged. What became clearer. What became more complex. What new questions emerged.
These are not soft questions. They are the questions that tell you whether the system is actually changing how it thinks and acts.
It is also important to ask who is doing the measuring.
If measurement is done only from the centre, it will miss local reality. If it is done only through surveys and dashboards, it will miss meaning and context. In systemic work, measurement is a participatory activity. People are invited into noticing what is changing, what is working, and what is not. This turns measurement into another form of sensemaking.
There is also a longer-term dimension.
Finishing an innovation project does not complete the work. It releases it into the system. What happens next depends on whether the system can nurture, adapt, and refresh what has been created.
This is why structural sensemaking matters over time.
In the Viable System Model, this is often associated with what is called System 3 star. Traditionally this is described as audit, but in a living system it is better understood as listening. It is the organisation’s way of staying in touch with what is actually happening, not through reports alone, but through ongoing contact with reality.
Tom Peters famously described this as management by walking about. In systemic terms, this is a series of Kairos moments. Leaders and stewards staying in relationship with the system, noticing how work is really being done, how people are really experiencing change, and how the system is quietly adapting.
This kind of listening cannot be reduced to a dashboard. It is relational, embodied, and contextual.
And it is essential.
Because innovation is not a goal you reach.
It is a living system you cultivate.
If you stop listening, it withers.
If you keep listening, responding, and learning, it evolves.
So measuring whether change and innovation are working is less about proving success and more about stewarding emergence.
It is about staying close enough to the system to notice what is becoming possible, what is becoming fragile, and what is becoming ready.
That is what allows change to remain alive rather than collapse back into habit.
This now carries your voice very clearly, and it places VSM, Kairos, listening, and nurturing exactly where they belong.