The argument has been won. The operating room has not.

The impact revolution has been extraordinarily successful at the thing it set out to do. Twenty years ago, arguing that a business should account for its social and environmental effects made you an activist. Today it makes you compliant. Reporting standards exist. Frameworks proliferate. Boards ask for impact data. Investors screen on it. Regulators mandate it.

The argument is over. We won.

And yet walk into almost any mission-driven organisation and ask a simple question — name a decision your last impact report changed — and watch what happens. People look at the ceiling. Someone mentions a funder conversation. Someone else says the report "informed thinking". Eventually somebody is honest and says: none.

This is the reporting problem at the centre of the impact revolution. Impact is measured everywhere. It is operated almost nowhere.

What actually happened

The revolution optimised for a specific fight. The fight was legitimacy: proving that impact was real, that it could be evidenced, that it deserved a place in serious conversation. Winning that fight required standardisation, comparability and disclosure. So that is what the movement built — an accounting apparatus.

An accounting apparatus is designed to produce a statement. It is not designed to produce a decision. Those are different machines with different outputs, and we built the first one while assuming the second would follow.

It did not follow. What followed instead was a reporting function: a team, usually small, usually under-powered, usually sitting somewhere adjacent to communications or compliance, producing an annual document for an external audience. The document is often excellent. It arrives after the decisions it might have shaped have already been taken.

The tell

There is a quick diagnostic for whether an organisation has an impact function or an impact reporting function. Ask when the evidence arrives relative to when the decision is made.

In a reporting function, evidence arrives afterwards, for a funder, at a fixed point in the calendar. Its purpose is accountability — showing what happened. That is a real purpose and it matters. But it is retrospective by construction, and nothing retrospective can change the thing it describes.

In an operating function, evidence arrives before, for a named person, at the moment a course correction is still possible. Its purpose is the decision itself.

Most organisations have built the first and believe they have built the second. The belief is sincere. It is also expensive: you are paying for measurement infrastructure and receiving documentation.

Why more measurement will not fix it

The instinctive response to "our impact data does not change anything" is to improve the data. Better indicators. Better dashboards. A new platform. More frequent collection.

This almost never works, because the constraint is not the quality of the evidence. It is that no part of the organisation is structurally obliged to act on it. There is no body whose agenda requires it, no role whose objectives depend on it, no decision that cannot proceed without it. Evidence with no destination does not become more useful when there is more of it. It becomes a larger pile in the same corner.

This is an organisational design problem wearing a measurement costume. It responds to design intervention and it is almost entirely immune to measurement intervention.

What the next phase looks like

If the first phase of the impact revolution was about proving impact could be measured, the second is about making the measurement operationally consequential. That means answering questions the reporting frameworks deliberately leave open:

  • Where do impact decisions get made? Not where they get discussed — where they get made, escalated and owned. If that body is not the same one reviewing financial and operational performance, impact is running beside the organisation rather than through it.
  • Who is accountable for the decision, not the report? Producing evidence and acting on it are different accountabilities. Most organisations have assigned the first and left the second unowned.
  • What is the cadence? An annual report can only inform annual decisions. Most consequential decisions are not annual.
  • What may each body actually decide? A committee that can advise but not allocate will produce advice, indefinitely.
  • What infrastructure is required underneath? Systems and data, sized to the decisions they serve rather than to the report they populate.

Those five questions are the five layers of the operating model we designed and published. We did not adopt a framework for this. There was not one to adopt: the frameworks answer what to count, and this is the layer beneath that, about who decides and when.

The uncomfortable part

The reason this is difficult has nothing to do with methodology. It is that fixing it moves authority. Deciding that a body must review impact evidence before approving a programme takes something away from whoever currently approves it unencumbered. Giving the impact lead decision rights takes rights from someone else.

Measurement is popular because it is additive — a new dashboard costs nobody any power. Operating design is unpopular because it is redistributive. That is precisely why the revolution stalled at measurement, and precisely why the organisations that push through get results the measurement-only organisations never see.

The impact revolution did not fail. It succeeded at its first task and stopped, one layer short of the thing that would have made it matter.