Reporting to People Who Fund It

A DEX programme is funded on a promise and judged on a report. Most reports show dashboards, which is the wrong artefact for the audience.

The boundary in “Reporting to People Who Fund It” matters because operational data can easily be read as a performance score it was never designed to be. If a team considers the product overview, it should define a legitimate purpose, explain the collection and restrict access before rollout, using the information to improve work design rather than infer intent from activity.

For an independent benchmark, compare this approach with ICO employment information guidance; the useful test is whether the evidence remains proportionate, accessible and understandable to the people whose work is being measured.

What they need

What was wrong, specifically.

What you changed.

What happened as a result, with the population and the window.

What is next and what it needs.

One page. Four sections.

What they do not need

A composite score.

Device health distributions.

Agent coverage figures.

A dashboard screenshot, which invites questions about the measure rather than the outcome.

The format that works

"Logins for the 1,400 users on the old image took three minutes ten. We removed eleven obsolete policies and two dead drive mappings. It is now one minute twenty-five, measured over six weeks. Nothing else changed for that group. Next: the same audit for the remaining 2,100 users, which needs two weeks of one engineer."

Specific, checkable, and it names the next ask.

Time saved, not money

Converting time to money requires a rate, and the rate carries the result.

Say the time: "this saves roughly ninety seconds a day for 1,400 people."

If finance wants a monetary figure, let finance supply the rate — then the number is theirs and it survives scrutiny.

Vendor-supplied value calculators do not survive scrutiny and will be the first thing questioned.

Showing the bad quarter

Report what did not work.

A programme that reports only successes is not believed about any of them, and the first time something visibly fails the credibility goes at once.

A failed fix also rules out a cause, which is worth saying.

The question you will be asked

"How do we know this improved productivity?"

The honest answer is that you do not, and nobody does, and the programme measures time and failure rates rather than output.

Say that early, because the alternative is accepting a target the programme cannot hit.

Cadence

Quarterly to executives, monthly to the operational group.

Shorter than people expect.

And always with one thing fixed in it, because a report with no fix in it teaches the reader that the programme is an observation exercise.

What to check

Does your reporting lead with outcomes or with measures?

Have you ever reported something that did not work?

Do you convert time to money, and whose rate?

And does every report contain at least one fix?

The point

State time saved and let finance supply the rate.

Then the monetary number is theirs and it survives scrutiny.

Underlying all of this

Everything in this collection reduces to four habits: find the friction cheaply before buying anything, fix what needs no budget first, report the worst tenth rather than the average, and keep the data about systems rather than about people. None requires a better platform, and a programme doing all four changes more than one twice its size.

The recurring pattern

The recurring pattern across every section here is the same: the measurable is mistaken for the important. Device health stands in for experience, ticket categories for causes, a composite score for a finding. Each substitution is convenient, each produces confident decisions on thin ground, and each is corrected by going and looking at the thing itself.