The work nobody counts

A backup that has never been restored is a claim about a file. The claim is usually true. It fails on the one property nobody checks, which is whether what comes back out is what went in, and the day you find out is chosen for you.

So I restore them somewhere safe, on a schedule, and the result of a good one is that a Tuesday in six months is unremarkable. No ticket. No thread anybody remembers. Nothing to put in a report except a sentence that reads like an excuse.

The same shape covers most of what I actually do. Moving a service off a version that stops getting patches in the spring. Reading the dependency list and updating the four that matter. Deleting a subsystem that two people still half understand. Writing down how the thing works. Handing a system over properly, so that it survives the handover.

A failure leaves a timestamp.
A recovery leaves a story.
Prevention leaves an ordinary week.

Every organisation gets good at the thing it can see.

That is the whole mechanism, and no manager is being accused of anything by it. Attention follows evidence, and an incident produces evidence in enormous quantity: a start time, a page, a channel full of people, a postmortem, a named person who stayed up. Prevention produces a calendar with nothing in it. Run that difference across enough quarters and an organisation converts its preventive capacity into response capacity without deciding to, and experiences the change as getting better at incidents.

Which is the exact inverse of the counter under the photograph. A number pointed at the thing it measures produces more of that thing. Work that no number points at produces less of itself, year after year, and the decline stays invisible for as long as the luck holds.

The only method I have found is to make the invisible work produce an artifact on purpose. Not for a dashboard. Because otherwise there is nothing to hold in the conversation six months later. A restore with a date, a duration and a row count. A migration with a written record of what moved and what was left behind deliberately. A deletion whose commit message says which failure it was carrying. Small, slightly artificial, and the difference between a thing that happened and a thing nobody can prove happened.

This is also what I sell, which makes for an odd pricing conversation. What a customer buys is a year in which the infrastructure does not interrupt them, and from their side of the wall that year is indistinguishable from a year in which nothing needed doing. The invoice arrives either way.
So does the work.

Nothing happened last quarter.
That was the deliverable.