Constantly train, test, evaluate, and sort people
A chapter summary from Principles by Ray Dalio.
You have the gist — now hear the whole argument. Free with a 30-day Audible trial, cancel anytime.
“The aim is to get the right people in the right seats — and, when the fit isn't there, to move them rather than pretend.”
If expectations are clear, evaluation becomes information. The goal is to match responsibilities to capability.
Sorting sounds harsh until you see the alternative: keeping people in roles that don’t fit, where they feel constant failure and the organization absorbs constant cost. Honest sorting can move someone into a better match—or out of a system where mismatch will only grow.
The loop must be continuous. People change, roles change, and new pressures expose new strengths and weaknesses. When the loop is constant, growth becomes normal and stagnation becomes visible.
Dalio treats people development as an ongoing engineering loop, not a once-a-year review: continuously train, test, evaluate, and sort. Training and evaluation, he argues, are really the same activity — you learn what someone can do by giving them real responsibility and watching how they handle it, then feed that back honestly so both of you see their trajectory clearly.
He is unsentimental about the hardest part, sorting. Caring about people and holding high standards are not in conflict; keeping someone in a role they're wired to fail at is a cruelty disguised as kindness, to them and to everyone who depends on them. The aim is to get the right people in the right seats — and, when the fit isn't there, to move them rather than pretend. 'You can't teach someone who doesn't want to learn,' he notes, so willingness matters as much as capacity.
Evaluation at Bridgewater is radically transparent and continuous, captured in tools like the Baseball Cards and the Dot Collector so a person's demonstrated strengths and weaknesses are visible and accumulate over time rather than resetting each review cycle. Dalio argues that ongoing, specific, believability-weighted feedback is far more useful — and ultimately kinder — than an annual verdict delivered in vague generalities.
The chapter's principle for any leader: your people are the most important part of your machine, so know them at least as well as you know your numbers. Assess honestly, communicate the assessment clearly, invest in those who can grow, and have the discipline to reassign or part with those who can't — always separating the judgment of a fit from a judgment of a person's worth.
One chapter a week — curated, not algorithm-picked.
If this resonated, the free weekly Read Stacks email sends one curated 4-book stack with the chapter we'd open first. No spam, unsubscribe anytime.
More from Principles
Principles sits in a curated reading path — each pairing it with other books that sharpen the same idea. Three nearest peers:
- Outliersby Malcolm GladwellFrom Think clearly
Malcolm Gladwell breaks the myth of pure innate talent and replaces it with the more uncomfortable claim: skill is the visible part of a stack of advantages — cultural, generational, circumstantial. Reading Outliers after the first two books rewires how you think about your own decisions and the decisions you judge other people for.
Read first chapter - Thinking, Fast and Slowby Daniel KahnemanFrom Think clearly
Daniel Kahneman's career-summary book is the unavoidable starting point. System 1 (fast, automatic, error-prone) versus System 2 (slow, effortful, lazy). Once you can name which system is firing, you can interrupt it — but you can only interrupt what you can see.
Read first chapter - Mindsetby Carol S. DweckFrom Think clearly
Carol Dweck's research provides the bridge between Outliers' contextual debunking of pure talent and the practical question of what to do about it. The fixed-vs-growth mindset distinction is the single most actionable lever in this stack: most learning behaviors are downstream of the underlying belief about whether ability can grow. Read after Outliers, Mindset is the operator's manual for the talent-is-contextual claim.
Read first chapter
From Read Stacks · Learn
If you just read a chapter summary…
You're using the navigation tool the way it was designed to be used. Two short essays on the meta-skill — what summaries actually preserve, and the six retention techniques that decide whether what you just read is still useful six months from now.
- Are book summaries actually useful, or am I just cheating?
Chapter summaries are a navigation tool, not a substitute. Used right, they help you read more books fully — by helping you avoid the wrong ones. Used wrong, they're a comfort blanket that lets you feel like you're reading without engaging with the material.
6 min read
- I read a lot of books but can't remember anything. What works?
Forgetting most of what you read is normal, not a personal failing — your brain wasn't designed to retain prose at the rate modern readers consume it. The practices that DO work share one thing: they force you to USE the material instead of just consuming it. Six specific techniques, each tested across decades.
7 min read