Dan Heath — ’s Reset Strategy | How to Change What’s Not Working

In one sentence

The core of the "Reset" strategy is recognizing that when a system produces a consistently mediocre result, it is not a crisis but a signal that the system is perfectly designed to produce that exact outcome.

Why read this (and who it's for)

This is for leaders, managers, and individuals who feel "stuck" in a loop of mediocrity—where there is no immediate fire to put out, but the current trajectory is clearly wrong. It solves the problem of "analysis paralysis" by providing a framework to identify leverage points and restack resources when you are constrained by a lack of time, money, or people. After reading, you will be able to distinguish between a "crisis" (which requires reaction) and a "systemic stall" (which requires a reset).

The big idea

Most people wait for a crisis to justify a change in direction. However, Dan Heath argues that the most dangerous problems are often "underwhelming but steady" examples of performance. If a system consistently produces a result you aren't happy with, it means the system is working exactly as designed; you simply don't like the design.

To change what isn't working, you must move beyond "downstream" reactions—fixing the symptoms of a problem—and move "upstream" to the root cause. This requires identifying leverage points (the specific places where a small change can yield a large result) and then restacking resources. Because most people are resource-constrained (lacking extra cash or staff), the "reset" is often about finding new ways to deploy existing resources, which requires a shift in internal motivation and a willingness to break old patterns.

Key ideas

The "Absurd Equilibrium" of Systems

• What it is — A system is often perfectly designed to get the results it currently produces. If you are getting a mediocre result, the system is doing its job perfectly.
• Why it matters — It shifts your perspective from "Why is this failing?" to "What is this system designed to do?" This allows you to see the "stuckness" as a structural reality rather than a personal or temporary failure.
• In the book — Heath uses the example of a hospital receiving area where packages (medications, gloves) take an average of three days to be deployed. It isn't a crisis; it's an "absurd equilibrium" where the system has settled into a slow, inefficient rhythm that everyone just accepts as "the way it is."

Upstream vs. Downstream Thinking

• What it is — Downstream thinking is reacting to the consequences of a problem; Upstream thinking is identifying and solving the root cause before the consequences manifest.
• Why it matters — Downstream fixes are often temporary and can lead to unintended consequences. Upstream thinking addresses the source, though it requires a higher level of systemic awareness.
• In the book — Heath discusses how banning thin plastic bags led to people buying thicker bags, which increased the total amount of plastic in the environment. This is a "downstream" consequence of a "midstream" policy change that failed to account for the system's function.

The Resource Constraint of Resetting

• What it is — Most organizations don't have "satchels full of free cash" or extra employees to hire to fix a problem.
• Why it matters — Because you are usually resource-constrained, a "reset" isn't about adding more; it's about restacking what you already have. This is often painful because it requires taking resources away from one area to put into another.
• In the book — Heath argues that when things aren't working, you often lack the "marketing dollars" or "extra people" to fix them, so you must find ways to recycle existing work in a new direction.

The Power of Motivation as a Resource

• What it is — The most neglected resource in organizational change is motivation.
• Why it matters — Leaders often assume that a "change conceit" (a new vision) is enough to move a team. However, without a strategy to generate and sustain motivation, the plan will fail to gain traction.
• In the book — Heath notes that leaders often focus on the "analytical" part of a plan (the shortest line between two points) but fail to account for the human element of buy-in and the motivation required to actually move the team.

The "Grant" Principle of Persistence

• What it is — Success in a reset often depends on a leader's willingness to "fight it out" when the system is under extreme pressure.
• Why it matters — When a system is being reset, there will be periods of "getting your ass kicked" (initial failure) before the new system takes hold.
• In the book — Heath cites Ulysses S. Grant during the Civil War. Grant understood that the North had the resources to win, but they weren't winning because the system of leadership was failing. He was willing to endure the brutal "Battle of the Wilderness" to break the old pattern of retreating and regrouping.

Frameworks & tools

The Reset Framework

When you find yourself in a "stuck" situation where there is no immediate fire but the results are underwhelming, follow these steps:

1. Identify the Equilibrium: Look at the data. What is the current "average" result? Accept that the system is currently designed to produce that specific result.
2. Find the Leverage Points: Identify the specific variables that, if changed, would alter the output of the system.
3. Audit Resources: Determine what you actually have (time, people, money, motivation). Do not assume you can "buy" your way out of the problem.
4. Restack Resources: Decide what current activities will be stopped or reduced to provide the "fuel" for the new direction.
5. Build the New System: Implement the change in iterations (inspired by the Agile Methodology) to get quick feedback and maintain momentum.

Memorable examples & stories

The Hospital Receiving Area

A hospital system for processing packages (medications, etc.) resulted in a three-day average delivery time. Because there was no "crisis," people just worked around it, leading to over-buying and spoiled meds. Lesson: A lack of urgency doesn't mean a lack of problem; it means a system has settled into a bad equilibrium.

The "Duct Tape" Cover of Made to Stick

Heath describes how the physical texture of the book's cover—feeling like actual duct tape—created a "sticky" experience because it exceeded expectations and provided a tactile surprise. Lesson: To make something "stick," it must offer a sense of differentiation and surprise.

The "Upstream" Plastic Bag Ban

A city banned thin plastic bags, but people began buying thicker bags for other uses, actually increasing the total plastic in the environment. Lesson: When you remove a variable from a system, something else will substitute for it; you must understand the function of the thing you are removing.

The Y2K "Success"

The "Millennium Bug" was a massive undertaking where billions were spent to prevent a collapse. Because the collapse didn't happen, the public viewed the work as a "scam." Lesson: The success of preventative work (going upstream) is often invisible, which can lead to the removal of the very systems that prevented the disaster.

Key quotes

"Every system is perfectly designed to get the results it gets." Why it matters: This is the foundational realization for any reset. It removes the "why" of the failure and focuses on the "how" of the design.

"The most neglected resource is motivation." Why it matters: It reminds leaders that a plan is just a map; motivation is the fuel that actually moves the vehicle.

"When you're doing something new, you first look backwards and then you look forwards." Why it matters: You must understand the history of the old system before you can successfully architect the new one.

How to apply it

This week

• Identify one "Underwhelming Equilibrium": Find a process in your work or life that isn't a "crisis" but is consistently disappointing (e.g., a slow-moving project, a messy filing system).
• The "Audit" Exercise: List the resources (time, energy, money) you currently spend on that "underwhelming" process.
• Identify a Leverage Point: Ask: "If I could only change one thing about how this works, what would it be?"

Ongoing

• Upstream Thinking: Before starting any new project, spend 15 minutes identifying the "downstream" consequences of the actions you are about to take.
• The Agile Reset: Instead of trying to overhaul a system in one giant leap, break the "reset" into 2-week "sprints" to ensure you are getting feedback and maintaining momentum.

Common pitfalls

• The "Crisis" Trap: Waiting for a disaster to happen before attempting a reset. Heath argues that the most dangerous problems are the ones that don't cause a crisis, but rather a slow erosion of performance.
• The "Addition" Fallacy: Assuming you can fix a system by adding more resources (more money, more people). In reality, most resets require restacking—taking resources from one thing to give to another.
• The "Reaction" Bias: Thinking that a "reaction" to a symptom is the same as a "solution." Reaction is downstream; solution is upstream.

Connects to

• Getting Things Done (David Allen): Allen's work on "mind like water" and externalizing memory complements Heath's ideas on building systems to handle complexity.
• Upstream (Dan Heath): This provides the foundational theory for why we must look at the roots of problems rather than the symptoms.

If you remember only three things

• Systems are designed to produce their current results; if you don't like the results, change the design.
• Most resets are about restacking resources, not adding new ones.
• Success in a reset requires identifying leverage points and moving upstream to the root cause.

Internalize it

• Reflection questions
  • What is a "boring" problem in my organization that we have simply accepted as "the way things are"?
  • If I were to "restack" my current weekly schedule, what would I stop doing to create more resources for my highest-leverage goal?
  • In what areas of my life am I reacting to "downstream" symptoms rather than fixing "upstream" causes?
• Flashcards
  • Q: What does it mean when a system is "perfectly designed" to get a result?
  • A: It means the system is functioning exactly as it was built, even if the result is a mediocre or "stuck" outcome.
  • Q: What is the difference between a "crisis" and an "underwhelming equilibrium"?
  • A: A crisis is an emergency; an underwhelming equilibrium is a steady, mediocre performance that has become the accepted norm.
  • Q: Why is "restacking" resources important in a reset?
  • A: Because most people are resource-constrained and cannot simply add more money or people to a problem; they must redistribute what they already have.
  • Q: What is "Upstream" thinking?
  • A: Identifying and solving the root cause of a problem before the consequences (downstream) manifest.
  • Q: What is the most neglected resource in organizational change?
  • A: Motivation.

Fidelity note

This summary is based strictly on the provided transcript of the interview between Ryan and Dan Heath. The summary captures Heath's specific arguments regarding "Reset," "Upstream" thinking, and the "Restacking" of resources. The "Agile" and "Grant" examples were explicitly mentioned by Heath as inspirations or historical parallels for his work. The "Plastic Bag" and "Y2K" examples were provided by the host/guest as illustrations of downstream consequences.