---

Most change efforts begin with a logical assumption.

If a problem is identified, a solution can be designed.

If a solution is designed, it can be implemented.

If it is implemented, the desired outcome should follow.

At first glance, the logic appears sound.

A challenge is identified.

A strategy is developed.

Actions are taken.

Results are achieved.

This sequence forms the foundation of many strategic plans, reform agendas, transformation programs, and policy initiatives.

In its simplest form, it assumes a pathway that looks something like this:


Problem  →  Solution  →  Implementation  →  Outcome


For certain types of challenges, this approach can be highly effective.

Where conditions are stable, variables are limited, and the environment remains predictable, linear planning often performs exactly as intended.

The difficulty emerges when these same assumptions are applied to complex systems.

Institutions, communities, economies, and societies rarely operate in a straight line.

They are shaped by thousands of interconnected relationships, competing priorities, evolving behaviours, and continuous feedback.

What appears straightforward on paper can behave very differently once it encounters reality.

This is one of the reasons many strategies appear logical, well considered, and entirely reasonable, yet still struggle to produce the outcomes they were designed to achieve.

The issue is often not the quality of the strategy itself.

The issue is the assumption that change will occur in a linear way.

Linear models of change persist for a simple reason.

They are intuitive.

They provide a clear beginning, a clear destination, and a sequence of actions intended to connect the two.

They create the impression that change can be understood, planned, and managed through a series of deliberate steps.

For many operational challenges, this is entirely appropriate.

If a process is inefficient, it can be redesigned.

If a capability is missing, it can be developed.

If a resource is unavailable, it can be acquired.

In environments where relationships are predictable and the factors influencing outcomes can be reasonably controlled, linear approaches can produce reliable results.

The challenge is that institutions rarely exist in these conditions.

Every decision made within a complex system interacts with other parts of the system.

A policy change may alter behaviour.

Behaviour may influence culture.

Culture may affect adoption.

Adoption may impact performance.

Performance may create new pressures that alter decision making.

The outcome is not a straight line.

It is a dynamic system of interactions.

This is where many change efforts begin to encounter difficulty.

The strategy itself may be logical.

The objectives may be reasonable.

The intended outcome may be desirable.

Yet the system responds in ways that were never anticipated because the system is not simply executing a plan.

It is adapting to it.

Each response creates new conditions, influences subsequent decisions, and alters how the change itself is experienced throughout the system.

Complex systems do not remain static while change is introduced.

They respond to change.

They absorb it.

They resist it.

They reshape it.

And in some cases, they produce outcomes entirely different from those originally intended.

One of the most common assumptions within change efforts is that implementation and transition are the same thing.

They are not.

Implementation refers to the introduction of change.

Transition refers to the adoption of change.

The distinction may appear subtle, but its implications are significant.

A strategy can be approved.

A policy can be introduced.

A reform agenda can be launched.

New processes can be documented.

New structures can be established.

New responsibilities can be assigned.

From an implementation perspective, each of these actions may represent progress.

Yet none of them guarantee that the system itself has transitioned.

People may continue making decisions in the same way.

Teams may continue operating according to old assumptions.

Incentives may remain unchanged.

Informal behaviours may continue to override formal processes.

The system may appear different on paper while functioning much as it did before.

This is one of the reasons many change initiatives create substantial activity without producing substantial change.

The implementation occurred.

The transition did not.

Within simple environments, implementation and transition often happen together.

Within complex systems, they frequently diverge.

The greater the complexity of the system, the greater the likelihood that introducing change and embedding change become two very different challenges.

Part of the challenge is that implementation is often easier to observe than transition.

Implementation produces visible activity.

Plans are approved.

Projects are launched.

Training is delivered.

Policies are released.

Governance structures are updated.

Progress can be measured against milestones, timelines, and deliverables.

Transition is different.

Transition occurs within behaviours, relationships, decision making, and operating patterns.

It is reflected not in what has been introduced, but in how the system functions once those changes have been introduced.

As a result, implementation can create the appearance of progress long before meaningful transition has occurred.

An organisation may successfully complete every action outlined within a transformation plan.

A reform agenda may meet every scheduled milestone.

A program may be delivered exactly as intended.

Yet the underlying system may continue producing many of the same outcomes it produced before.

This is one of the reasons implementation success and change success should not automatically be considered the same thing.

One measures whether activities occurred.

The other measures whether the system itself changed.

The distinction becomes increasingly important as complexity increases.

Within complex systems, change is rarely achieved simply because a set of actions has been completed.

Change emerges through the interaction between those actions and the system receiving them.

The more interconnected the system, the less likely it is that implementation alone will be sufficient to produce transition.

This does not mean that strategy is unimportant.

Nor does it suggest that planning, governance, or implementation lack value.

Each plays an essential role within successful change efforts.

The challenge is that many traditional change models assume that implementation is the primary mechanism through which change occurs.

Once the strategy is developed and the implementation plan is executed, the desired outcome is expected to follow.

Within complex systems, the relationship is rarely that direct.

Between implementation and outcome sits a dynamic environment of interactions, adaptations, dependencies, incentives, behaviours, and responses.

Each of these influences how change moves through the system.

Some may accelerate adoption.

Others may slow it.

Some may reinforce the intended direction of change.

Others may redirect it entirely.

This means that the path between action and outcome is rarely fixed.

It evolves as the system responds.

The challenge is not simply that outcomes become difficult to predict.

It is that the assumptions used to design the change effort may no longer reflect the reality through which the change must travel.

What appeared to be a straightforward pathway can quickly become a series of adjustments, reactions, unintended consequences, and competing influences.

The further a change effort moves into complexity, the more visible this becomes.

Strategies that appeared robust encounter unexpected resistance.

Reforms that seemed comprehensive fail to gain traction.

Initiatives that were carefully planned struggle to achieve lasting adoption.

Not necessarily because the ideas were flawed.

But because the assumptions governing how change was expected to occur were incomplete.

This may help explain why many change efforts produce a familiar pattern.

The problem is recognised.

A solution is developed.

Resources are allocated.

Implementation begins.

Activity increases.

Progress is reported.

Yet months or years later, many of the underlying challenges remain.

In some cases, the intended outcome was never achieved.

In others, the outcome may have improved temporarily before gradually returning to previous patterns.

And in many instances, substantial effort, investment, and commitment were applied throughout the process.

The challenge is rarely a lack of intention.

Nor is it always a lack of capability.

Often, the challenge lies in the assumption that introducing change and achieving change are fundamentally the same thing.

Within complex systems, they are not.

A change effort may be implemented successfully without producing meaningful transition.

A reform may be introduced without fundamentally altering how the system operates.

A strategy may be executed without creating the conditions required for lasting change.

This raises an important question.

If implementation alone is often insufficient, what enables a system to move from one state of operation to another?

What allows change to become embedded rather than merely introduced?

And what exists between the decision to change and the reality of sustained transformation?

These questions become increasingly important as institutions, communities, economies, and societies confront challenges that are growing in complexity, scale, and interdependence.

Because if traditional models of change struggle to explain how transition occurs, it may be necessary to reconsider whether something essential is missing from the way change itself is understood.

Continue the Series
Structural Transition Systems
​
Publication II →
​
The Missing Design Problem : Institutional Transition Architecture 

​Shaping How the Future is Built
© Jamie Meyer Enterprises
Structural Transition Systems | Publication II
July 2026