Why reforms stall after they are adopted

An adopted reform is not a delivered reform. Between the text voted through, the decree signed or the strategy approved in cabinet, and real change in the lives of users, there lies a territory that few public organisations have learnt to cross. It is there, and almost never at the moment of decision, that reforms stall.

The conventional diagnosis blames a “lack of political will”. Experience of public programmes suggests something else: the will exists at the moment of decision, but it finds no organised relay over time. Three breaks occur, almost always the same ones.

First break: governance stops at the decision

A political decision names an objective; it rarely names an owner. Once the reform is adopted, the questions that matter remain without an owner: who settles matters when two administrations contradict each other? Who reports on progress, to whom, how often? Who has the authority to say that a workstream is behind and to act on it?

When these questions have no institutional answer, every disagreement rises to the top, where it waits. Political sponsorship, which was meant to be a scarce resource reserved for major deadlocks, becomes the ordinary way of working. It runs out.

Second break: the trade-offs are not made

Every reform competes with the existing: the same teams, the same budgets, the same systems must carry both day-to-day operations and change. Without explicit sequencing, day-to-day operations win, because they are urgent and the reform never quite is.

Trade-offs that are not made take discreet forms: funding released in tranches with no link to the real pace of the programme, priorities that pile up without ever being ranked, schedules kept up for show while the resources have changed. None of these decisions killed the reform; their accumulation brings it to a standstill.

Third break: execution has no organ

This is the most structural break. Administrations are organised to manage the existing: to process, to control, to produce official acts. Driving change, holding an inter-ministerial schedule, integrating a system, managing dependencies between workstreams belong to another profession, one that requires profiles, methods and tools that the ordinary structure does not have and has no reason to have.

Entrusting the execution of a reform to an organisation designed for day-to-day administration is asking a structure to do what it does not exist to do. The failure that follows is not a fault; it is a predictable result.

What a delivery model changes

The answer to these three breaks is not another study. It is a delivery model: a dedicated, small and well-equipped team, placed close enough to the top to force trade-offs to be made, and close enough to the field to see the reality of progress.

Such a delivery model holds four functions. It gives the reform permanent governance: bodies that actually meet, decisions on record, named owners. It prepares trade-offs rather than suffering them: every deadlock comes up framed, costed, with options. It steers by the facts: a progress picture grounded in verifiable data, not in the declarations of the workstreams. And from day one it organises the transfer of its own methods to the permanent teams, because a delivery model that becomes indispensable has failed in its turn.

This last point is decisive. The temptation exists, for structures of this kind, to become a parallel administration, better paid and better heard than the services it is meant to strengthen. The measure of success must be the opposite: the delivery model succeeds when the functions it performs are taken over, one by one, by the administration itself.

Reforms do not stall because they are poorly designed. They stall because the crossing between decision and result is entrusted to no one. This missing link can be built: governance that lasts, trade-offs that are made, an execution capability that is set up and then handed on. It is on these three conditions that a decided reform becomes an executed reform.