Systems Often Reward Rescue More Than Prevention

A colleague once told me that his daughter wanted Louis Vuitton luggage. Outrageous, he said.

He was much too frugal to approve of that, although he admitted that her bland, generic suitcases must have given her grief on a recent excursion from her semester at Harvard Law.

He was prudent by temperament, the sort of man who looked at luxury branding with suspicion and viewed expensive luggage as completely irrational. The suitcases she already owned seemed perfectly functional to him, even if they were generic enough to disappear into every airport carousel on earth.

He held the line. No Louis Vuitton luggage, even though he had the means for it.

A month later, she called him from Mexico. Stolen luggage. Tears. Crisis. I heard him reassure her on the phone, "I've got you, baby girl. Use Daddy's card for whatever is needed." He wiped his brow as the call ended, visibly shaken.

Overhearing the call, I remember thinking "Daddy?" His reversion to the diminutive term from her childhood showed me the intensity of how moved he had been by her situation. He talked to me about imagining how frightened she must have been, stranded abroad on an international class trip with her belongings missing.

I listened for a moment and smiled with tenderness.

“Oh,” I replied. “You’ve been had. In the best way. Masterful, in fact.”

The reason I said this had a bit to do with luggage, of course, and even more to do with his daughter's interpretation of his internal emotional system. The final cost of repairing her trip to Mexico experience ended up approximately equal to her original Louis Vuitton request, plus replacement clothing and other necessities for the items she had supposedly lost.

You see, my friend wore a white cowboy hat to work every day, an actual white hat (really!). He stood tall, enjoyed being the rock others depended on, and loved stepping in when things went sideways. She read him as only daughters can do. His hero desire had been played like a fiddle. White hat to the rescue.

His daughter understood all of this perfectly. She had not argued with his frugality because his frugality was not the deepest force in the system. It was merely the visible policy shell-layer. Underneath it sat something stronger: his identity as a provider and rescuer.

He did not want to buy luxury luggage when that was the only question at play. He did, though, immediately want to save his daughter in a moment of distress. So she routed through the stronger pathway.

White hat to the rescue.

Organizations Skew Toward Heroics

The more experience I get, the more convinced I become that organizations work the same way.

Every institution claims to value prevention. Annual reports praise foresight and resilience. Reports cover risk management, continuity, preparedness, and operational excellence. Executives speak reverently about avoiding disruption. Then budget season arrives, and prevention begins to look expensive.

People trying to reduce volatility acquire reputations, and not good ones. They become known as cautious, procedural, a little obsessive, always worried about edge cases. The language used to describe them darkens, and the character labels change first. Eye rolling begins shortly afterward.

Preventive competence has a perception problem: its success appears as nothingness, vaporware. Inevitably, when nothing happens, as is the usual case with sound preventive actions, executives ask, "Did we really need them? Nothing happened, after all."

The cybersecurity team that prevents a breach did not create a memorable event. The procurement office that quietly closes fraud pathways did not generate any applause. The facilities group that prevented catastrophic infrastructure failure mostly gets labeled as expensive.

Human beings are surprisingly poor at emotionally valuing calm, uninterrupted Tuesdays. Especially in the workforce.

We could all use a bit of advice from the famous adage often attributed to French military leader Napoleon Bonaparte: "I would rather have lucky generals than good ones." Lucky generals often are lucky because of preventive action. Rewarding "luck" sometimes serves as proxy for seeing this.

Corporate Measures of Competence

The irony is that these same organizations often become intensely emotional about heroic actions, equating heroics with competence the moment the boredom of operational continuity fails.

Take the exact same employee. Let the predictable outage or system failure actually happen. Allow the missed shipment, the compliance breakdown, the security incident, the hazardous-material problem, the inventory collapse, the server catastrophe, the public fiasco cause actual organizational embarrassment. Then let that employee step in with a prepared solution.

Suddenly the organization sees leadership. Calm under pressure. Decisive. A fixer. A hero.

Even if the exact same person could have prevented the entire sequence months earlier and didn't.

I have watched this pattern repeat for decades across industries. Units which run smoothly because they anticipate problems often fade into the organizational wallpaper. Nearby departments that repeatedly stumble into preventable chaos become seen as heroes, because visible recovery produces emotional theater that prevention doesn’t.

And organizations, despite all their procedural language, are still after all profoundly emotional and very human systems.

Beef Stew, Golf Courses, and a Boss’s Advice

I saw this play out in my own life this year while making one of my traditional meal baselines: beef stew.

A few cuts of beef from a butchered quarter steer in my freezer, in this case a large bone-in sirloin steak, some short ribs, and a piece of cut liver. Black beans and pintos cooked on the stove got added. Onions, garlic, celery tops, and whatever seasonings were on hand, as well. All of it went into a crock pot. Yes, some people still use them.

After many hours, when the beef was soft enough to separate and the bones had cooled enough to give to the dog, I broke the stew down slightly with a covered hand blender, leaving it thick and a bit chunky.

That stew became a base, not a single meal.

It could become enchilada filling, a mushroom-and-wine stew over rice, a pasta sauce finished with cheese, or something else entirely. I frequently make a similar chicken version too, with navy beans, northern beans, roasted salsa verde, and the same basic logic: prepare the hard part once, the base, then preserve future variety.

This mattered in January, when I was ill much of the month. Too sick to visit the store, and wanting to protect others from getting sick, I made it through without ordering takeout or grocery delivery. The frozen bases carried me, along with shelf-stable accompaniments: rice, pasta, tortillas, dried peppers.

Preparation often looks excessive until the day it quietly saves you.

Clubhouse Boss

My first boss, at a golf course clubhouse where I worked when I was fourteen, understood this. One of her sayings was, “Always prepare.” She lived that way. At the top and bottom of the clubhouse stairs, she kept baskets for anything that needed to go up or down. The next person using the stairs was expected to carry the items with them.

She also taught us to think two hours, two days, and two weeks ahead. Sometimes she added "also remember to consider two months and two years from now, too."

She would stop us in the kitchen and ask, “What time is it?”

We would check our watches or the kitchen clock.

“Right,” she would say. “That whole group who went out earlier will be finishing the back nine soon. Are we ready for the rush?”

That was prevention in its ordinary form. No drama or heroics, just the small discipline of seeing to the mechanics of the rush before it arrived.

The Danger of Rewarding Only Catastrophe Repair

When organizations instead reward only catastrophe repair, it creates a dangerous asymmetry: systems reward heroics and visible rescue more consistently than their invisible cousin, prevention.

Once you see it, you begin to notice how deeply this logic shapes institutional behavior. The employee who says, quietly and months in advance, “this process is unstable,” often sounds irritating. The employee who says, during a visible emergency, “leave it with me,” sounds indispensable.

What is memorable

The distinction has less to do with competence than with narrative structure. Rescue produces a story. Prevention produces only bland operational continuity. Stories are emotionally legible, while continuity is mostly silent.

A successful rescue contains tension, witnesses, summons into the inner sanctum of executive conference rooms, visible agency under pressure, relief afterward, and often gratitude. A successful prevention leaves behind something more difficult to metabolize: an ordinary day in which the system kept functioning. Yawn.

That asymmetry distorts organizational incentives. Over time, institutions begin rewarding the emotional appearance of competence more than competence itself.

This does not usually happen because leaders prefer chaos, of course. Most executives sincerely want stable operations. The distortion emerges because human beings naturally anchor attention around events rather than absences of events. We remember the fire more vividly than the inspection that prevented one. We remember the late-night scramble more readily than the boring control that made the scramble altogether unnecessary.

What is measurable

This is one reason mature operational people often develop a strange relationship with praise. The best operations professionals I have known rarely produce emotionally satisfying narratives. Their victories occur upstream in the unmeasurable fog of daily operations.

The shipment arrived because they anticipated the customs issue three months earlier. The inventory remained accurate because they redesigned the controls to make any shrinkage visible. The hazardous material did not injure anyone because someone internally irritating insisted on segregation of duties nobody wanted to think about. The fraud pathway quietly closed because somebody spent six tedious months redesigning chain-of-custody procedures while everyone around, in other departments, only complained about the inconvenience.

These prevention-oriented people frequently acquire reputations as difficult personalities precisely because they create friction before the organization emotionally understands why the friction matters. Prevention isn't measurable. Reaction is. This explains a lot about why organizations skew toward heroics rather than safety, prevention, and actual risk management.

Heroics rule

There inevitably comes a moment when yet another unit, system, or product fails publicly. Suddenly executives gather around the visible fire. Emergency solution budgets suddenly appear. Attention. Admiration. Breath held as the corporate white hat rescuer enters the room, metaphorically tipping his hat.

The preventive person may still be quietly maintaining the conditions preventing five other disasters from occurring simultaneously. Nobody notices because nothing exploded.

Recognition Failure

In Convivial Systems Theory, this is a recognition failure.

Human systems struggle to assign value to preserved continuity because continuity of normal operations lacks spectacle. Healthy systems therefore require deliberate cultural mechanisms capable of recognizing invisible load-bearing work before failure occurs. Otherwise, institutions drift again and again toward recoverable instability: enough dysfunction to create visible heroes, enough recurring volatility to generate stories, enough preventable crisis to keep rescue identities socially rewarded with career trajectory.

People optimizing for career growth learn to prepare a solution in advance, then let the problem happen and step in to play hero when all inevitably goes sideways.

Family Systems and Romance

This dynamic appears in families as much as corporations. Some parents unconsciously reward children more during crisis than during stable competence. So the straight A student might be ignored while the D student gets taken to a theme park if they bring it up to a C by end of the semester.

Some romantic relationships also become organized around recurring emotional emergencies because repair receives more intensity than maintenance. This mechanism partially explains why we have a conception of people choosing to date the "bad boy or bad girl" rather than the stable romantic alternative.

Why Leaders Love Heroics

Some leaders build their own identities around perpetual firefighting because stable systems leave them feeling psychologically underutilized.

This gives them a selection bias toward similar heroics when measuring the performance of their reporting line staff. In calibration meetings, they love to bring up the manager who saved the day after disaster. Promotions, accolades, raises and bonuses then go that person's way.

Organizations become dangerous when they reward these hero-identity structures so consistently that they weaken the subtler forms of competence required for long-term stability.

The operational person who prevents ten disasters may remain invisible. The charismatic fixer who resolves one visible catastrophe which should never have happened becomes legend. The result is that competent people quietly learn an uncomfortable lesson: if they want recognition, they may need to allow more visible failures, and then ride in on a metaphorical horse to save the day.

Some resist this incentive structure toward heroism and continue preventing problems anyway. Others drift toward strategic rescue behavior without quite admitting it, even to themselves. They stop solving issues fully upstream. They allow manageable instability to persist, so that they can preserve the possibility of future heroics.

Most do not think of themselves as manipulative. They are adapting to the emotional reward structures surrounding them.

That, in fact, was the deeper brilliance of my colleague’s daughter. She understood that her father’s stated values and his emotionally load-bearing values were not identical. His spoken philosophy was frugality. His governing emotional identity was rescue. The stronger system won. It always does.

What makes the story charming rather than cynical is that she gave him something he genuinely wanted. He got to become the hero of his daughter’s story. The emotional reward was real. They both more or less won in that situation.

Organization risks of hero-based selection bias

Once organizations emotionally reward visible recovery more than stable continuity, they begin training themselves into fragility. The system loses respect for the people carrying the invisible load. One day those people leave.

That is usually the moment institutions discover how much unseen stabilization had been occurring all along. Outages multiply. The inventory drifts. Near misses become real misses. The heroic rescuers suddenly face disasters too large to theatrically resolve and they, too, leave. The organization is then stuck with a mess and without any available heroes to save it.

How to Stop Rewarding Heroics Over Prevention

Organizations cannot fix recognition failure by telling people to “value prevention” when they themselves value heroics. They have to instead make prevention visible before the crisis.

1. Name preventive actions in meetings.
   When a team prevents a failure, say so explicitly. “This did not become a customer issue because the team caught it upstream” is a different sentence from “nothing happened.”
2. Attach anticipatory value to prevention.
   Estimate the avoided failure load in hard numbers: this solution predictably avoids 300 customer complaints, one press incident, two weeks of rework, a regulatory finding, a safety event, a supplier disruption. The estimate will be imperfect, but the act of naming avoided harm helps the organization see continuity as produced rather than hidden value.
3. Interview for prevention, not only rescue.
   When candidates describe a major problem they solved, follow the thread backward. What early signals did they miss in retrospect? What controls did they put in place afterward? What would prevent the same class of failure from recurring? Hero stories are easy to tell. Prevention stories reveal deeper discipline.
4. Give prevention a shared technical language.
   Disciplines like FMEA, 8D, control plans, pre-mortems, and after-action TGR /TGW reviews help organizations discuss risk before it becomes drama. The point is not paperwork. The point is making weak signals discussable while there is still time to act.
5. Reward stable systems before they break.
   Promotion and compensation systems should notice teams whose domains run quietly because they are well-governed. If only crisis response earns status, the organization will keep producing crises.

The cure is not to eliminate rescue, because we know every system eventually needs repair under pressure. The cure is to stop confusing rescue with the highest form of competence.

Healthy Systems

Healthy systems are usually built less by heroes than by people willing to look peculiar six months before everyone else understands the core problems. They are built by people who notice weak signals, reinforce the bridge before it visibly sags, insist on tedious controls, quietly lower volatility, and preserve continuity so successfully that others forget that continuity requires any labor at all.

Those people rarely get cowboy hats.

Mostly, they get ordinary Tuesdays.

Which, in a functioning civilization, should probably be regarded as one of the highest achievements available to us.

— Madonna Demir, founder of Convivial Systems Theory and author of Systems & Soul

KPI Kingdoms and How They Fall

From social platforms to public companies to universities, KPIs shape what leaders choose to build. Portable KPIs travel through institutions like a mental map. Over time, the map becomes policy, and the institution begins to confuse the dashboard for reality. That is legibility capture.

Systems. Soul. And the space between.Madonna Demir