AFTER NOT GUILTY · SYSTEMS SATIRE
The Sir Humphrey Moment
When the paperwork is impeccable, but the outcome is absurd.
Public administration can perform every prescribed step and still fail the person it was intended to serve. These short fictional exchanges expose the gap between following a process and verifying an outcome.
How to read this series: Each entry separates a real-world systems question from an original satirical dialogue and a practical improvement. The sketches are fictional, not transcripts of officials, organisations or events. They are an independent affectionate tribute to the administrative satire of Yes Minister; they are not affiliated with its creators or rights holders.
1. The Orphaned Outcome
The systems question. A criminal case can end with a Not Guilty verdict while records, restrictions, reputation and practical consequences remain unresolved. Who is responsible for checking what happens next?
Hacker: The case has finished, Humphrey. Has the matter been resolved?
Sir Humphrey: Entirely, Minister. Every department has completed its part.
Bernard: Except the part where somebody checks whether the person’s life has returned to normal.
Sir Humphrey: Bernard, that would require us to define what we mean by “completed”.
Closing the loop: Give the overall outcome a named owner. Reconcile records, check continuing consequences and independently verify whether restoration has happened. Explore the Orphaned Outcome.
2. The Seven-Pence Principle
The systems question. A bank letter about seven pence illustrates how automated administration can faithfully execute a rule without anyone assessing proportionality or purpose. The example concerns process design, not artificial intelligence.
Hacker: We sent a letter to recover seven pence? How much did the letter cost?
Sir Humphrey: The cost is recorded under correspondence, Minister. The seven pence is recorded under recoveries.
Bernard: So we can report both figures correctly without ever comparing them?
Sir Humphrey: Precisely. One must not confuse accurate accounting with an inconvenient conclusion.
Closing the loop: Add proportionality checks, exception handling and a human review of recurring low-value actions. The computer completed its task; nobody had asked whether the task was worth completing.
3. The Missing Evidence
The systems question. Records that are filed, transferred or marked complete are not necessarily reconciled with the evidence or with each other.
Hacker: Was the record verified?
Sir Humphrey: It was submitted in the correct format.
Bernard: Formatting tells us it looks like a verified record. It doesn’t tell us whether it is true.
Sir Humphrey: Bernard, you are bringing evidence into an administrative discussion.
Closing the loop: Trace each significant conclusion to its source, identify missing or conflicting records, preserve contrary evidence and record who corrected what.
4. The Mechanical Clock
The systems question. An ageing clock may have polished brass, complete maintenance logs and a stopped mechanism. Public services can display the same divide between procedural health and actual performance.
Hacker: The clock has stopped. Why does every department say it is working?
Sir Humphrey: Because the winding, cleaning and inspection schedules are all up to date.
Bernard: But the hands haven’t moved, Sir Humphrey.
Sir Humphrey: We may need a new box on the form.
Closing the loop: Measure the outcome the mechanism exists to produce—not merely the completion of maintenance tasks.
5. The Google Verification Paradox
The systems question. While setting up this website, Google displayed a DNS verification record it had found but still reported that ownership verification had failed. This can happen when the record found is not the token currently expected, or when verification systems have yet to update. The underlying technical reason has not been established.
Hacker: Google says it cannot find the evidence, Humphrey.
Bernard: But it has printed the evidence on the screen, Minister.
Sir Humphrey: An exemplary transparency measure. It allows the applicant to see exactly what the system has declined to accept.
Hacker: And how do we resolve it?
Sir Humphrey: By repeating the procedure until the outcome becomes administratively convenient.
Closing the loop: Distinguish evidence discovery from validation; explain the precise reason for rejection and show a recoverable route to correction.
A serious point beneath the laughter
“The paperwork may be complete. The failure may still be present.” The purpose of these sketches is not to mock individuals or victims. It is to ask a simple question of every public-facing system: Who checks that the intended outcome actually happened?
This series will grow alongside the wider work of After Not Guilty and Rewiring the Public Sector. For comments, examples or corrections, send Simon a message.