Dan Heath on resetting broken systems and solving problems upstream

Executive overview

Most teams and organizations stay stuck in underwhelming performance — not in crisis, but not improving either. Dan Heath's framework in Reset explains how to identify leverage points in a system, find resources to push on them, and build team motivation into the change process rather than bolting it on afterward.

Every system is perfectly designed to get the results it gets — change the system, not just the people.

Knowing when to reset versus rebuild

• A reset targets systems and processes; a rebuild acknowledges missing talent or resources.
• Ask: is the gap doable and worth fixing with what you currently have?
• Most organizations confuse a systems problem with a personnel problem — and apply the wrong fix.
• Leverage points are nodes in a system where a small investment yields a disproportionate return; find these before acting.

Finding resources when you're constrained

• Most change efforts fail because teams try to push in a new direction without reallocating existing resources.
• Motivation is the most neglected resource in organizational change.
• Start with the overlap between what change requires and what team members actually want right now.
• Leaders who lead with the plan and then seek buy-in have it backwards — desired behavior needs to precede the plan.
• Ask team members for their pain points first; fixing small frustrations signals genuine listening.

The progress principle

• Teresa Amabile and Steven Kramer's research: the top motivator at work is the feeling of progress on meaningful work.
• Managers consistently rank progress last when asked what motivates their teams — a direct contradiction of the data.
• Early in a project, people look backward (celebrating distance covered); later they look forward (closing the gap to the goal).
• Break large goals into small milestones to create measurable momentum; the confidence from early wins compounds.
• Grant's decision to march south after the Battle of the Wilderness — rather than retreat — is a model for reframing setbacks as progress.

Upstream thinking and its limits

• Upstream work means solving problems before they occur; it produces less visible glory than heroic downstream reaction.
• The prevention paradox: the more effective the upstream intervention, the less evidence remains that the problem ever existed (Y2K is the clearest example).
• Removing a bad element from a system doesn't guarantee improvement — something worse can replace it (Chicago's plastic bag ban increased total plastic use by switching to thicker bags).
• Unintended downstream consequences are often invisible in advance; intellectual humility is required but cannot become an excuse for inaction.
• Upstream wins that compound over generations — clean water, vaccines, maternal care — added roughly 30 years to average human lifespan across the 20th century.

Iteration as a change method

• Traditional book or project cycles allow one or two feedback rounds; Heath used six rounds on Reset, inspired by agile software methodology.
• Working in short sprints forces confrontation with underbaked ideas early, when changes are cheap.
• Sharing crude early drafts feels uncomfortable but keeps work aligned with what readers or users actually need.
• Getting less precious about early output removes paralysis and accelerates the path to quality.