How to Turn an Issued Mandate into an Enforced One

Most experimentation mandates die quietly. They are announced with conviction, referenced for a quarter, and then absorbed into the category of things everyone agrees with and nobody checks. The programme continues, the standards drift, and two years later somebody asks why the results cannot be trusted. The distinction that matters is between an issued mandate and an enforced one. A mandate is issued once. It is enforced continuously, or it decays.

Buy-in is not a mandate

Stakeholder buy-in is sentiment: people agree the programme matters. A mandate is authority: evidence standards apply, someone owns them, and there are consequences for bypassing them. Programmes with enthusiastic buy-in and no mandate are common, and they are the programmes where quality depends entirely on who happens to be in the room.

If your programme's authority rests on everyone continuing to feel positive about it, it does not have authority.

What issuing actually looks like

An issued mandate is written, scoped, and named. Written, because a mandate that exists only in a town hall recording does not survive the first reorganisation. Scoped, because "we believe in experimentation" mandates nothing; "significant product changes are tested before rollout, and results are verified before they are reported upward" mandates something specific. Named, because the mandate must designate who owns the framework that carries it. A mandate without a named owner is a wish.

What enforcement actually looks like

Enforcement is not surveillance. It is three habits.

A cadence: the mandate appears in the rhythm of the organisation. Team leads answer for evidence quality in reviews the way they answer for delivery. What gets asked about regularly gets done; what was announced once gets forgotten.

Consequences: something happens when the mandate is bypassed. Not punishment theatre, but visibility. A change shipped without testing gets asked about. A win reported without verification gets sent back.

Air cover: this is the one leaders most often miss. Sooner or later the framework will say no to someone senior. A test plan from a favoured team fails review. A claimed win from an executive's pet project does not survive verification. In that moment, the framework's owner is watching to see whether the mandate is real. Back the framework once in a contested moment and it gains authority for a year. Undercut it once and every gate becomes optional.

The decay curve

An issued mandate that is not enforced does not fail loudly. It decays. First the standards apply to everyone except the busiest team. Then the review becomes a formality that has never rejected anything. Then documentation becomes the goal rather than quality. The end state is a programme with all the artefacts of governance and none of its function, which is worse than nothing, because it looks fine from above.

The test

One question tells you which side of the line your programme is on. What happened the last time someone shipped without meeting the standard? If there is a concrete recent answer, the mandate is enforced. If the honest answer is that nothing happened, or that it has never come up, the mandate was issued and has been decaying ever since it was announced.