Five-Step Process for Getting What You Want
Turn goals, problems, and reflection into repeatable progress
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 99%
The process treats progress as a recurring loop rather than a straight path. Begin by identifying the goal you genuinely want, then surface the problems obstructing it instead of ignoring or tolerating them. Diagnose each problem deeply enough to distinguish symptoms from root causes, including weaknesses in your own behavior. Next, design a concrete way to handle the same class of problem differently and execute that design with determination. Pain becomes useful when paired with quality reflection: the experience reveals a lesson, which can be written as a principle and reused. Repeating this cycle gradually improves decisions, capabilities, and results while changing failure from a source of shame into actionable information.
Origin
Dalio developed the process through painful mistakes while building Bridgewater, recording the lessons and decision principles that eventually became Principles.
Core principles
- 01Treat problems as signals rather than obstacles
- 02Diagnose root causes before prescribing solutions
- 03Convert painful experiences into reusable principles
- 04Design changes before taking action
- 05Repeat the cycle until results improve
How to run it
- 1
Clarify the Goal
Define the dream or result you are pursuing. A clear destination makes it possible to distinguish meaningful problems from irrelevant discomfort.
Pro tip Choose goals based on your own nature and motivations rather than borrowed expectations.
Watch out Competing goals can consume the same resources and make progress ambiguous.
- 2
Identify the Problems
Notice the obstacles appearing between your current reality and the goal. Refuse to normalize recurring problems merely because confronting them is uncomfortable.
Pro tip Treat each painful result as evidence that something in the current approach needs attention.
Watch out Ignoring a problem prevents the learning cycle from beginning.
- 3
Diagnose Root Causes
Determine why the problem occurred and separate underlying causes from visible symptoms. Examine whether your own habits, abilities, or decisions contributed.
Pro tip Ask what would have needed to be different for the outcome to change.
Watch out Jumping directly to solutions often produces a fix for the symptom rather than the cause.
- 4
Design a Better Approach
Create a specific response that will prevent or navigate the same problem in the future. Convert the lesson into a principle or decision rule that can travel across situations.
Pro tip Write the design down so it can be reviewed, shared, and refined.
Watch out A vague intention such as trying harder is not an operational design.
- 5
Execute and Repeat
Carry out the design with enough determination to produce results. Use new problems and failures as inputs for another cycle.
Pro tip Review the principle when a similar situation appears instead of starting from scratch.
Watch out Insight without execution does not change the outcome.
In the wild
Dalio correctly anticipated a sovereign debt crisis but incorrectly predicted its market consequences. The resulting losses forced him to dismiss his staff and borrow money from his father. He diagnosed overconfidence as a root cause, redesigned his decision process around humility and thoughtful disagreement, and sought intelligent people who could challenge his conclusions.
→ The failure changed his approach from assuming he was right to asking how he could know he was right.
A team misses its launch target and resists blaming effort alone. It defines the intended outcome, identifies late customer validation as the central problem, diagnoses an approval bottleneck, designs weekly customer tests with a named decision owner, and applies the new procedure to the next release.
→ The next launch exposes weak assumptions earlier and avoids the same delay.
Common mistakes
Tolerating Recurring Problems
Accepting a recurring obstacle as normal eliminates the pressure to understand and redesign the system causing it.
Confusing Symptoms with Causes
A fast explanation may describe what happened without revealing the behavior or mechanism that repeatedly produces it.
Reflecting Without Executing
A lesson creates no progress unless it becomes a design that is actually carried through to results.
Is it for you?
Best for
It is best for people pursuing ambitious goals who are willing to examine mistakes honestly and change their behavior.
Not ideal for
It is not ideal for situations requiring an immediate emergency response before reflection and diagnosis are possible.
From the transcript
“So I was saying pain plus reflection equals progress.”
“Third step, you have to diagnose those problems to get at the root causes.”
“Number five, do those things pushed through the results. You keep doing this over and over and over again, you're going to be successful.”
From the episode
Ray Dalio on Failure, Meaningful Work and Relationships