What Leaders/Managers Can Learn from Factfulness
Daniel Voss ran the weekly review for twenty branch managers, and after one branch reported a rough quarter, he caught himself mentally sorting the whole division into branches "carrying us" and branches "dragging us down." When he finally plotted every branch's numbers on one chart, he saw a long, unremarkable line of branches doing reasonably, with only two outliers at either end. The story he had been telling his own boss had been about two camps that barely existed. He also noticed his review agenda was built almost entirely around whichever branch had produced the most dramatic number that week, while branches quietly improving month over month never came up. When a process failure hit one branch, his instinct was to find the one manager responsible rather than trace the shared system every branch used. Rebuilding the review around trend lines took weeks, but it changed which conversations happened in the room.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Sorting teams into winners and losers instead of seeing the range
Daniel's instinct to divide branches into two camps is the gap instinct at organizational scale: a handful of standout cases get treated as representative of two opposite groups, when most teams actually sit in an unremarkable middle the story never mentions.
Some teams truly are outliers, and treating a genuinely exceptional case as ordinary wastes a chance to learn from it. Practice: before a review meeting, plot every team's core metric on one chart rather than listing standout wins and losses from memory.
Before a review meeting, plot every team's core metric on one chart rather than listing standout wins and losses from memory.
Why one bad week outshouts a quarter of gradual gains
A single dramatic incident, like one team's rough quarter, captures attention far more than a slow, steady improvement elsewhere, so agendas and worry both drift toward whatever is loudest rather than whatever matters most.
A quiet trend can still be an early sign of real trouble, and dismissing every dramatic incident as noise misses genuine warnings. Practice: pair every incident report in a review with the relevant metric's twelve-month trend line before discussing it.
Pair every incident report in a review with the relevant metric's twelve-month trend line before discussing it.
The push to name someone responsible before the data is in
Under pressure, leaders reach for a single accountable person faster than they trace the shared processes or incentives that actually produced a failure, protecting the system from scrutiny while one manager takes the blame for a problem larger than any one role.
Individual accountability is sometimes exactly correct, and diffusing blame across a system can let real negligence go unaddressed. Practice: when investigating a failure, list every contributing system before naming any individual.
When investigating a failure, list every contributing system before naming any individual.
Leading two truths at once
Factfulness for a leader means holding both that current performance has real weaknesses and that the organization is, on balance, improving, without letting either truth cancel the other out in front of the team. Treating a leader's own first alarmed or triumphant reaction to a report as an invitation to check the underlying numbers, rather than as a verdict to announce, keeps the whole reporting chain calmer and more accurate.
The blame instinct and the urgency instinct reinforce each other in a crisis: a leader under pressure to respond publicly often names a cause faster than the evidence supports, simply to be seen acting. The workable move is to separate the two decisions, making a fast containment response immediately while deferring any causal judgment until a proper review, and saying so out loud so speed is not mistaken for certainty.
Name one thing, honestly
- Which direct reports have I quietly filed into a "strong" or "weak" bucket without checking whether the data supports two camps? - What is the most recent report I reacted to before checking its trend line? - When did I last assign blame to move faster, and was the underlying cause actually that simple?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
When investigating a failure, list every contributing system before naming any individual.