What are 'principles' in the Ray Dalio sense?

The idea popularised by investor Ray Dalio in his book Principles is simpler than its reputation suggests, and you do not need to read the book to use it. Stripped to its core it is this: you meet the same kinds of situations over and over, so write down explicit rules for handling them, apply the rules, watch what happens, and revise them. That is the whole engine. Everything else is elaboration.

We have no affiliation with Ray Dalio or his publisher; what follows is our own plain description of a widely discussed public idea, not a summary of or substitute for the book.

The three-part loop

1. Situations repeat, and you can recognise the type

The claim is that most of what happens to you is "another one of those" — another underperforming collaborator, another opportunity that looks great but arrives at a terrible time, another argument about the same thing in a new costume. If you treat every instance as unprecedented, you re-solve solved problems and pay the full cost of learning each time.

2. So write the rule down explicitly

Once you notice a repeating type, write the rule you want to apply, in words, in advance. Writing does two things that thinking does not. It forces specificity — vague policies do not survive being written as sentences. And it creates an artefact separate from your mood, so the rule you set calmly still exists when you are furious.

3. Then treat the rule as testable

This is the part most often lost. The rules are explicitly provisional. You apply one, observe whether it produced good outcomes, and rewrite it when it did not. A principle you refuse to revise has stopped being a principle in this sense and has become a belief.

Where the idea is genuinely strong

It converts pain into a written asset. The prompt "pain plus reflection equals progress" is not motivational fluff; it is a filing instruction. Something goes badly, you write the rule that would have prevented it, and the episode now has a residue that outlives your memory of it.

It makes disagreement productive. When two people argue from written rules, the argument becomes about the rule rather than about who is smarter. In your own head the same thing happens: you can disagree with your past self without it being a personal failure.

It separates decision quality from outcome quality. Because the rule is written before the result, you can ask whether the rule was sound independently of whether this instance worked out. That distinction is the foundation of learning in anything probabilistic, and it pairs naturally with a decision journal.

Where it does not transfer

The book's system was built inside a hedge fund with unusual institutional machinery: radical transparency, recorded meetings, believability weighting, extensive tooling and a workforce that signed up for it. Three honest caveats for an individual:

• You have no sample size in most of your life. Markets give thousands of resolved bets. You will change careers perhaps four times. In low-sample domains, rules written from personal experience are drawn from very few points, so hold them loosely.
• Radical transparency is an organisational norm, not a personal one. Adopting blunt candour without the surrounding structure — a shared agreement, a culture that reciprocates — usually just damages relationships, and people who try it in ordinary workplaces tend to discover this the hard way.
• Volume is not the point. A published list of hundreds of principles is a lifetime's accumulation and a reference work, not a target. Copying someone else's list wholesale gives you rules extracted from a life that is not yours, and borrowed rules do not survive contact with a real trade-off.

How to use the core loop yourself

1. Wait for the second occurrence. Do not write a principle after one bad experience; you will be encoding an anecdote. Write it when you notice the repeat.
2. Write it as an if-then. "If a project is late and the client has not asked, I tell them the same day." Conditional rules fire when the condition appears; abstract virtues do not.
3. Date it and record the case. One line on the situation that generated it. Without the case you cannot later judge whether it still applies.
4. Revisit quarterly and delete freely. A rule that has not fired in six months is either about a situation you no longer face, or it was never a real pattern. Deleting is the maintenance that keeps the list credible.

Two dozen honest, tested rules of your own are worth more than any published collection. The value was never in the specific principles someone else arrived at — it is in the loop that produced them.