Who Owns Experimentation Governance

There is a conversation that happens in most organisations with an experimentation programme. A senior leader is asked how quality is maintained across the programme, and the answer is some version of: the analytics and product teams decide that. It sounds like empowerment. It is abdication. Governance fails most often not because nobody cares but because everybody assumes it is someone else's job. Practitioners assume leadership will set standards. Leadership assumes the people closest to the work will govern it. The result is a framework that belongs to nobody, which is the same as not having one. Governance has three distinct jobs, held by three distinct roles. Programmes that work keep them separate.

Executives issue the mandate

The executive job is not to design the framework. It is to make the framework matter. That means three things. Issue the mandate: a clear, written statement that evidence standards apply to the programme and who owns them. Hold team leads accountable to it: the mandate appears in reviews, not just in the announcement. Provide air cover: when the framework says no to someone senior, the executive backs the framework.

What is not the executive job: passing the decision down. "You decide" from a senior leader does not empower a team to govern. It strands them with responsibility and no authority, and the framework they build will be routed around the first time it inconveniences someone above them.

A senior owner finalises the framework

Somewhere between the executive and the practitioners sits the role that actually owns the framework: a centre of excellence, a programme lead, a head of experimentation. The title matters less than the seniority. This person finalises the framework, oversees how it is applied, and feeds back on quality continuously.

Finalises is the important word. Practitioners contribute to the framework, and should, because they know where the work actually strains. But contribution is not ownership. A framework finalised by committee is a framework nobody defends.

What is not this role's job: enforcing without a mandate. An owner asked to uphold standards that leadership has never formally backed is being set up to fail. If you have given someone this role without the executive mandate behind it, you have given them a title, not a job.

Practitioners contribute and operate

The practitioner job is to bring expertise into the framework, operate within it day to day, and surface what is broken or missing. Governance improves by being used, and practitioners are the only people who know where it chafes.

What is not the practitioner job: owning or finalising the framework. Not because practitioners lack the skill, but because a framework owned at the practitioner level has no authority above the practitioner level, and evidence standards that stop at the team boundary are hope, not governance.

The test

Ask three questions of your own programme. Who issued the mandate, and can anyone produce it? Who finalised the framework, by name? What happened the last time the framework said no to someone senior?

If the answers are nobody, a committee, and it has never said no, the programme does not have governance. It has an assumption that someone else is doing it.