Major reforms begin with an ambition: more competition, stronger passenger rights, better integration, lower costs or greater capacity for innovation. Legislation and policy can redistribute roles and establish new rules. The real system emerges later, through thousands of decisions made by the organisations expected to implement them.
A decision creates permission for change
Political and regulatory decisions matter. They remove barriers, define responsibilities and establish the direction in which a market or public system should develop. Without that formal mandate, many structural changes would remain impossible.
The decision itself leaves important questions open. Actors must interpret new roles, adapt commercial relationships, build processes and exchange information. Existing services need to continue while new arrangements take shape. Customers expect the whole system to work throughout the transition.
Implementation is therefore more than executing a finished design. It is the period in which the practical design of the reformed system is completed.
Every reform creates a transition system
Reform discussions often compare the present state with the intended future state. Organisations experience a third system between them: the transition.
During this period, old and new responsibilities coexist. Legacy technology remains in operation. Contracts reflect different points in time. Some actors invest early while others wait. Temporary solutions accumulate because essential services cannot pause until the final architecture is ready.
This transition system can last for years. Treating it as a short technical phase creates hidden dependencies and growing complexity. Treating it as a system in its own right makes sequencing, responsibilities and customer protection visible from the start.
Incentives translate intention into behaviour
New rules describe what actors may or must do. Incentives shape what they actually prioritise. An organisation will interpret the reform through its own mandate, economics, risk and accountability.
A reform may ask organisations to collaborate while rewarding them mainly for local performance. It may introduce competition while depending on shared infrastructure and coordinated customer processes. It may promise innovation while making every deviation from established practice difficult or risky.
These tensions are part of the system rather than evidence of bad intent. Effective implementation makes them explicit and aligns enough of the incentives for the desired behaviour to become rational for the actors involved.
“A reform becomes real when the intended behaviour is possible, rational and governable for the actors expected to deliver it.”
The user experiences the implementation
Institutions experience a reform through responsibilities, contracts and systems. Users experience it through information, prices, availability, reliability and the response they receive when something goes wrong.
A problem may be caused by one actor and presented to the customer by another. From the user’s perspective, the distinction offers little comfort. Fragmented responsibility remains a real service failure even when every organisation can explain why its own part was handled correctly.
Following the complete user journey provides an essential test of the reform. It reveals where formal responsibilities connect, where they leave gaps and whether the new system creates a coherent result across organisational boundaries.
Governance must support learning
Complex reforms cannot anticipate every interaction in advance. New behaviours emerge, technology changes and unintended consequences become visible only after implementation begins.
Governance gives the system a way to learn without losing direction. It creates places where evidence can be shared, dependencies can be addressed and decisions can be revised. It distinguishes between problems that require clearer compliance, better coordination or an adjustment to the underlying design.
This adaptive capacity is especially important in markets where public obligations, commercial freedom and shared infrastructure meet. The reform needs sufficient stability for actors to invest and sufficient flexibility for the system to improve.
Leadership holds the whole transition
Individual workstreams naturally focus on legislation, procurement, technology, operations or communications. Reform leadership must keep those perspectives connected to the intended system outcome.
That includes maintaining a shared view of the destination, making trade-offs visible and deciding which issues can be solved locally and which require collective action. It also means protecting the long-term logic of the reform when short-term pressures encourage isolated fixes.
Questions before implementation begins
A credible implementation logic can be tested through a small set of system questions:
- Which behaviours must change for the reform to achieve its purpose?
- Do mandates, incentives and risks support those behaviours?
- How will the old and new systems coexist during the transition?
- Which outcomes depend on coordination across several organisations?
- How will user problems reveal gaps in the emerging system?
- Where can the reform learn and adapt without losing predictability?
The strength of a reform is ultimately measured in the system that people experience, not in the elegance of the original decision. Implementation logic connects ambition to behaviour, organisations to shared outcomes and formal change to practical value. That is where a reform earns its legitimacy—and where its lasting results are created.