Upstream
Dan Heath · 2020
Editorial rating
- Evidence
- 7/10
- Actionability
- 8/10
- Originality
- 7/10
The thesis
We're trapped in cycles of reaction - putting out fires, treating symptoms, handling emergencies. Upstream thinking means preventing problems before they happen by addressing root causes, changing systems, and intervening earlier. It requires overcoming psychological barriers: problem blindness, lack of ownership, and tunneling.
Who this is for
Leaders frustrated by recurring problems that never seem to get solved. Operations managers tired of firefighting. Anyone who suspects their organization is treating symptoms rather than causes. Executives looking to shift from reactive to proactive strategies.
My favorite quote
Every system is perfectly designed to get the results it gets.
Why it matters
This reveals that chronic problems aren't accidents - they're the predictable output of how things are currently structured.
Do this
Identify one recurring problem in your work. Ask: "What system is producing this outcome?" rather than "Who's failing?"
Start here
Ask seven upstream questions before any intervention: (1) How will you unite the right people? (2) How will you change the system? (3) Where can you find leverage? (4) How will you get early warning? (5) How will you know you're succeeding? (6) How will you avoid doing harm? (7) Who will pay for prevention while someone else benefits? These questions expose whether an effort is truly upstream or just more sophisticated downstream work.
Critical summary
Dan Heath, co-author of Switch and Made to Stick, examines why organizations and societies default to reaction rather than prevention. Using examples from healthcare, education, technology, and public policy, he identifies barriers to upstream thinking and provides a framework for overcoming them.
The book opens with the famous parable of children drowning in a river - do you keep pulling them out, or go upstream to stop whoever is throwing them in? Heath shows this choice pervades organizational life, with powerful forces pushing us downstream.
Three barriers to upstream thinking
- Problem blindness: We don't see problems as problems - they feel inevitable
- Lack of ownership: When everyone's problem is no one's problem
- Tunneling: Scarcity mindset forces focus on immediate crises
What it gets right
- Expedia example is brilliant - they eliminated 20 million customer service calls by simply fixing the itinerary email process
- Framework is practical and applicable across domains
- Addresses the measurement challenge - how do you measure problems that didn't happen?
- Acknowledges unintended consequences of upstream interventions
- Tackles the payment problem - who funds prevention when someone else captures the benefit?
What it misses
- Some examples repeat across chapters
- Lighter on "how" than "why" - framework questions are good but implementation guidance is thin
- Political applications may alienate readers who disagree with implied policy positions
- Doesn't fully address organizational incentives that reward downstream heroics over upstream prevention
Evidence is primarily case studies, but they're well-researched and cross-validated. Heath draws on established psychology research for the barrier framework.
Key concepts
Upstream vs. Downstream
Downstream work is reactive (treating illness); upstream work is preventive (promoting health). Categorize your team's activities.
Problem Blindness
Believing negative outcomes are inevitable. Ask: "What if this problem simply didn't exist?"
Tunneling
When overwhelmed, we can only address what's immediately in front of us. Create slack to think upstream.
Data for Learning vs. Data for Inspection
Inspection data punishes; learning data improves. Shift your metrics to enable improvement.
Surrogate Measures
Proxy metrics that can be gamed. Identify where you're measuring the wrong thing.
Leverage Points
Where small interventions create disproportionate impact. Find the acupuncture points in your system.
Core insights
-
Downstream work is demanded; upstream work is chosen
No one asks permission to save a drowning child, but preventing drowning requires proactive initiative - and is often optional.
-
Paying for prevention is structurally hard
The person who pays for prevention often isn't the person who benefits. This misalignment requires deliberate organizational design to fix.
-
Heroism is downstream
We celebrate firefighters, not building inspectors. This cultural bias makes upstream work thankless.
-
Early warning requires proximity
The people closest to problems see them first. Create feedback loops from frontline to decision-makers.
-
Systems change outlasts individual heroics
Individual downstream effort scales linearly; system change scales exponentially.
Implementation steps
Today
- List three recurring problems that consume significant team time
- For each, ask: "Who's responsible for preventing this?" If the answer is unclear, that's the problem
- Identify one problem where early warning signs exist but aren't being captured
This week
- Map the system producing your most annoying recurring problem
- Identify who benefits from prevention vs. who would pay for it
- Find one "canary in the coal mine" metric that predicts problems before they explode
This month
- Convene cross-functional group around one upstream problem (unite the right people)
- Design one preventive intervention, including how you'll measure success
- Build in feedback mechanism to detect unintended consequences
Ongoing
- Protect time for upstream thinking - it gets crowded out by downstream emergencies
- Celebrate prevention, even though it's invisible - make upstream wins visible
- Regularly audit: "What percentage of our effort is reactive vs. preventive?"
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Audit current work - categorize activities as upstream or downstream
- Day 2
Select one high-impact recurring problem for upstream intervention
- Day 3
Map the system - what inputs produce this outcome?
- Day 7
Identify leverage points and early warning indicators
- Day 14
Design intervention with clear ownership and success metrics
- Day 21
Implement first preventive measure, track leading indicators
- Day 30
Review results, document learnings, select next upstream project
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
