Outcomes Hide the Conditions That Created Them

Category: Why This Was Never an Accident Rewarding results alone erases the behaviours and systems that produced them.

For eleven years, an old church hall ran a soup kitchen on Thursday nights, and for eleven years it never once ran short, never turned anyone away, and never had a single complaint logged with the council. The numbers were impeccable. Meals served, on budget, no incidents — a clean line in the annual report that the trustees pointed to with quiet pride. When a regional charity decided to study what made some food projects resilient, the church hall was held up as a model. Replicate this, the report said. Here is what good looks like.

What the report measured was the result: meals out, no gaps, no fuss. What it did not measure, because it could not see it, was a woman called Brenda.

Brenda was not on any rota. She had simply taken it upon herself, years earlier, to drive round to the wholesaler late on a Wednesday and read the reduced-to-clear shelf, so that the kitchen always had a buffer of stock nobody had ordered. She kept a private list of which regulars hadn’t shown up lately and rang round to check on them, which was why nobody ever fell through a gap — the gaps were caught before they became gaps. She knew which volunteer could be relied on in a crisis and which one needed gently steering away from the hot pans, and she arranged the shifts in her head accordingly, without ever writing it down or calling it a rota. The kitchen’s flawless record was not a property of the kitchen. It was Brenda, doing forty quiet things a week that no measure captured and no report named.

When Brenda’s knees finally gave out and she stopped coming, the trustees thanked her warmly and replaced her with the system they could see: the rota, the budget, the supplier list. None of which contained any of what she had actually been doing. The record stayed flawless for about five weeks. Then a Thursday came when the stock ran short and twenty people went home with nothing, and a regular who hadn’t shown up in a fortnight turned out to have been ill alone the whole time, and a volunteer scalded her wrist on a pan she should never have been near. The trustees were baffled. Nothing had changed. The system was exactly as it had always been — the system that the regional report had so admired. They had banked the result for eleven years and never once asked what was actually producing it, and so when the thing producing it walked out of the door on two bad knees, they didn’t even know to mourn it.

The Principle

A result is the visible tip of something much larger. Underneath it sits the machinery that produced it — judgement, slack, trust, careful people, good process — almost all of which is invisible. If you reward, measure, and credit only the result, you stop seeing the machinery, which means you stop funding and protecting it, which means it quietly erodes until the results vanish “inexplicably.” The skill is to look through a good outcome to the conditions beneath it, and to protect those.

The trap is a sort of optical illusion. An outcome is concrete, countable, and sitting right there in front of you — meals served, deals closed, defects avoided, deadlines met. The conditions that produced it are none of those things. They are diffuse, often unrecorded, frequently embodied in particular people doing particular things that never appear in any account of the work. So when you go looking for what caused the good result, the result itself is the loudest thing in the room, and the machinery beneath it is more or less silent. The natural conclusion — that the result is the thing, that you should reward and replicate the result — is exactly backwards. The result is the evidence. The thing to understand, credit, and defend is whatever produced it. Reading through the outcome to its conditions is the entire discipline, and it runs against every instinct that points you at the number instead.

Why It Is Inevitable

This isn’t a refinement that careful organisations bolt on for tidiness. It’s a correction they’re forced into, because the default — crediting the outcome and ignoring the conditions — is not neutral. It actively destroys the thing it depends on, and it does so invisibly, which is the worst possible combination.

It’s inevitable first because conditions don’t show up in any account of the work. The meals served are in the report. Brenda’s Wednesday drive is not. There is no line for “slack that absorbed the shock nobody saw coming,” no column for “the judgement that quietly rerouted around a problem before it became one,” no entry for “the trust that meant people flagged things early instead of hiding them.” These conditions do their work precisely by preventing visible events — the crisis that never happened, the error caught while small, the gap closed before it opened. A condition that works leaves no trace, because its whole function is to stop things from happening. So the better the machinery, the more invisible it is, and the more completely the credit flows to the bare result instead.

It compounds because what gets measured gets funded, and what gets funded survives. An organisation directs its attention, its budget, and its gratitude toward what it can see. If it can only see outcomes, it will, with complete sincerity, reward outcomes — and the conditions beneath them, being unmeasured, get nothing. Not because anyone decided they didn’t matter, but because nobody could see them to value them. The slack looks like inefficiency and gets trimmed. The careful person looks expensive and gets stretched. The good process looks like overhead and gets streamlined. Every one of those decisions improves the visible numbers in the short run, which is exactly why they get made — and every one of them is quietly cutting a strut out of the structure holding the result up.

And it is self-concealing, which is the dangerous part. Because the conditions erode slowly and the results hold steady right up until they don’t, there is no warning. The structure keeps delivering the same outcome on less and less actual support, like a bridge losing rivets one by one while the traffic flows fine — until the load that would have been absorbed easily a year ago is the load that brings it down. By then the connection between the long-ago erosion and the sudden collapse is invisible, so the failure looks like bad luck or a freak event rather than the slow consequence of having banked a result without ever protecting what produced it. Any organisation that wants its good results to keep coming is forced, eventually, to learn to see the machinery — usually the hard way, after the first inexplicable failure of something that “had always worked.”

How It Shows Up

• A good result is treated as a question — what is actually producing this? — rather than simply a number to record and move on from.
• The invisible conditions get named out loud: the slack, the trust, the particular judgement, the careful person, the bit of process that quietly absorbs shocks. They are spoken about as real and as load-bearing, not taken for granted.
• Credit flows to the machinery, not only the tip. The person who prevented the crisis nobody saw is valued as highly as the person who visibly resolved one.
• Before anything is trimmed in the name of efficiency, someone asks what it was actually doing — on the assumption that a long-standing condition is probably holding something up, even if it isn’t obvious what.
• A flawless record is regarded with a degree of curiosity rather than pure satisfaction: why is it flawless, and what would happen to it if one particular person left?
• Slack, redundancy, and “spare” judgement are protected on purpose, because the organisation understands they are the buffer that makes the good results robust rather than merely lucky.

Why It Causes Benefit

When an organisation learns to read through its outcomes to the conditions beneath them, it gains something rare and quietly decisive: its good results become durable instead of fragile, because the thing producing them is finally being seen and defended.

The first benefit is that the machinery stops eroding by neglect. Once the slack, the trust, and the careful people are named as the cause of the result rather than treated as incidental to it, they get funded and protected like the assets they are. The condition that would otherwise have been trimmed for looking inefficient is recognised as the buffer it is and left in place. The person doing the forty invisible things a week is identified, credited, and — crucially — understood well enough that the organisation knows what it would lose if they left, and can prepare for it. The structure keeps its rivets, because someone is finally counting them.

The second benefit is that the organisation stops fooling itself about why it succeeds. An outcome banked without understanding is a result you cannot reliably reproduce, because you don’t actually know what caused it — you just know it happened. Read the conditions instead, and a good result becomes genuine knowledge: this is what produced it, these are the behaviours and structures that matter, and so this is what we protect and replicate. The church hall’s eleven-year record, properly understood, was a manual for how to run a resilient kitchen — the buffer stock, the quiet welfare calls, the judgement about who works where. Banked as a bare number, it taught the trustees nothing, which is why they could not save it. Understood, it would have been the most valuable thing they owned.

And the third benefit is the compounding one: good results stop being mysterious, in either direction. An organisation that sees the machinery knows why its wins happen and why its failures happen, because it understands the conditions that drive both. It is not blindsided by the slow collapse of something that “always worked,” because it was watching the supports, not just the output. It can tell the difference between a result that is robust and one that is running on borrowed time, which means it can act on the second before it fails rather than after. That is the whole basis of staying good rather than merely having been good once: an organisation that protects its conditions keeps producing the outcome, while one that banks only the tip eventually watches the iceberg melt beneath it and calls the disappearance bad luck.

How To Cultivate It

• Treat every good result as evidence to investigate, not just a number to bank. The discipline is a question asked at the moment of success rather than the moment of failure: what is actually producing this, and would it survive losing one person, one budget line, or one quiet bit of slack? Asked while things are going well, that question is cheap. Asked after the collapse, it’s an autopsy.
• Hunt for the invisible work deliberately, because it will not announce itself. Find the Brendas — the people doing the unrostered, uncounted things that prevent the crises nobody ever sees. Name them, credit them, and understand what they do well enough to know what you’d be losing. Work that prevents events leaves no trace, so you have to go looking for it on purpose.
• Before trimming anything for efficiency, establish what it was doing. A long-standing condition that looks like waste is, more often than not, a buffer holding something up. The burden of proof should sit with the cutter: show that nothing depends on this before removing it, rather than assuming nothing does because nothing visible has failed yet.
• Be suspicious of a flawless record in the right way — curious rather than complacent. A perfect run is not, by itself, reassuring; it might mean the system is robust, or it might mean one person is quietly carrying it and you haven’t noticed. The only way to tell is to look beneath the result at what’s actually producing it.
• Protect slack and redundancy as deliberate assets, not as fat to be rendered. The spare capacity, the second opinion, the unhurried judgement, the stock nobody ordered — these are precisely what absorb the shocks that would otherwise turn into visible failures. They look like inefficiency exactly because they are working.
• Credit the conditions out loud, repeatedly, especially the ones that prevented something. Praise the crisis that didn’t happen as warmly as the one that got solved. What gets credited gets protected, and the whole point is to make the machinery visible enough that it survives.

What Good Looks Like

An environment where a good result is the beginning of a question rather than the end of one. Where the slack, the trust, the careful people, and the quiet processes that actually produce the outcomes are seen, named, and defended as the load-bearing things they are — not trimmed away the moment they look like inefficiency, because the organisation has learned that they look like inefficiency precisely when they are doing their job. Where the people doing the invisible, event-preventing work are found and credited rather than discovered only by their absence. Where a flawless record prompts someone to ask why, and to understand the answer well enough that the record survives the departure of any one person who was holding it up.

In a place like that, good outcomes are durable instead of fragile, because the machinery beneath them is being protected rather than quietly cannibalised. The organisation knows why it succeeds, which means it can reproduce its successes on purpose rather than hoping they recur. It is rarely blindsided, because it watches its supports and not only its output, so it sees the slow erosion before the sudden collapse. And when something does finally fail, it understands the failure as the loss of a condition rather than as inexplicable bad luck — which means it can do something about it. None of this is pessimism about results. It is simply what it looks like to take success seriously enough to ask what produced it, and then to defend the answer. The church hall’s eleven good years were never an accident. They were Brenda. The only mistake was never seeing her until she was gone.

A Reflective Question

Think of something in your environment that has worked reliably for so long that nobody really thinks about it any more. Do you actually know what is producing that result — or only that it keeps arriving? And if the one person, the bit of slack, or the quiet process holding it up walked out tomorrow, would you find out by having noticed it in time, or by watching the result vanish for reasons you could no longer explain?