The Blame Instinct

Core idea

The blame instinct is the urge to find a single, identifiable person responsible whenever something goes wrong — and, just as automatically, a single hero to credit when something goes right. It feels like analysis. It is actually the moment analysis stops.

Rosling's argument: Once we have decided who to punch in the face, we stop looking for explanations elsewhere. The bad outcome stays unchanged, because the system that produced it is still running.

The corrective: resist pointing your finger.

Why it matters

"Punch the boss" hides who actually owns the choice

Rosling asks students why Big Pharma underinvests in malaria. Punch the CEO? The CEO answers to the board. The board answers to the shareholders. The shareholders are pension funds. The pension funds answer to retirees — many of whom, indirectly, are the students' own grandparents. There is no villain to hit. The system is the answer, and the system is everyone.

Blame freezes the investigation

When a plane crashes, blaming "a sleepy pilot" ends inquiry. Asking why the pilot was sleepy — scheduling, fatigue regulation, training, fatigue-detection systems — is the only line of questioning that prevents the next crash. The blame instinct rewards the wrong stopping rule.

Our favorite villains say more about us than about the world

Rosling assumed a Swiss family pharma firm had to be ripping off UNICEF when it bid below the cost of raw materials. He flew out expecting fraud. The truth was financial innovation — robotic pill-making, 30-day supplier credit, four-day customer payment, interest on the float. The "scam" was a small business beating the giants on logistics. The villain template had blinded him to a perfectly legal, perfectly admirable answer.

Journalists make the same template error about reality. Rosling tested groups of BBC, PBS, National Geographic, and Discovery producers on his factual questions. They scored no better than the public — about as well as chimps. They are not deliberately lying; they are themselves misled, and incentivized to compete for attention. Demonizing them is wrong on the facts and useless as a strategy.

Mediterranean drownings: the villain template misdirects again

Refugees in 2015 paid 1,000 euros for a place in a rubber dinghy when a regular flight cost 50. Why? Not smugglers' greed but a 2001 EU Council Directive making airlines pay full repatriation costs for any undocumented passenger they board. The airline staff at check-in cannot decide in 45 seconds whether someone qualifies under the Geneva Convention. So they refuse to board anyone. EU policy also confiscates the boats on arrival, so the only economic route is one-trip rubber dinghies. The "smuggler villain" is downstream of European policy that nobody wants to look at.

Heroes are the same trick in reverse

Mao's one-child policy gets credited with China's fertility collapse. But fertility was already falling from six children to three in the decade before the policy. Countries without enforcement — Ukraine, Thailand, South Korea — fell faster. Hong Kong, with no one-child rule, dropped below 1.0. The papal condemnation of contraception sits beside a 60 percent contraception rate in Catholic-majority countries — versus 58 percent in the rest of the world. "Powerful leader caused this" is a story; the data says institutions, technology, and the boring work of plumbers, nurses, teachers, and accountants do most of the lifting.

Key takeaways

Mental model

Copy sourceZoom

Practical application

1. Trace the chain of agency. When you nominate a villain, ask one more level: who do they answer to? Boss → board → shareholders → retirees. The chain almost always lands somewhere uncomfortable for the accuser.
2. Mirror-check your blame. Ask: does my villain belong to a group I already dislike? If yes, raise the bar of evidence by an order of magnitude. The blame instinct loves confirming a prior.
3. Replace heroes with systems too. When something works, ask whether it would have happened anyway. Ebola in Liberia was beaten less by famous organizations and more by anonymous government staff and contact tracers. Give the system its credit.
4. Demand the second question. A good incident review answers two questions, not one: who did this, then what made it possible. Without the second, the first is theater.
5. Look for plumbers. When you're grateful for an outcome, name the unsung infrastructure: civil servants, nurses, teachers, accountants, electricians. They are the answer to "how did this society function?" — not the headlines.

Example

A startup ships a buggy release and customers churn. The blame instinct picks the engineer who pushed the bad commit. Fire them, problem solved. The system view asks: was there a code review? Was the test suite running? Did CI block deploy on red? Did anyone have time to write the test? Who set the deadline? Why did QA shrink last quarter? Within an hour the actual answer surfaces — a release schedule three weeks too short, no rollback procedure, and a culture that rewards merging fast over merging safe. Firing the engineer leaves all four problems intact and guarantees the same bug a quarter later. Fixing the system removes the conditions that produced the bug in the first place.

Related lessons