Design improvements to your machine to get around your problems

Sometimes the right change is automation; sometimes it is a training loop; sometimes it is removing a step that creates confusion.

Design must consider trade-offs. Fixing one problem can create another if incentives shift or complexity increases. So the design should be tested against reality: run it, observe results, adjust.

This is where principles become operational. Values like honesty and learning turn into protocols: how debates run, how decisions are recorded, how errors are tracked until fixed.

With a real diagnosis in hand, Dalio turns to design — building a machine that gets around the problem rather than heroically pushing through it each time. He tells managers to visualize the outcome they want as a story, then work backward to the sequence of tasks, roles, and people that would reliably produce it, the way an architect designs a building before anyone pours concrete.

A core design principle is that people and design are two sides of the same coin: a task is only well-designed once you've also identified who is wired to do it well. Dalio warns against designing around a specific individual's quirks (which breaks when they leave) versus designing roles and then staffing them with people whose tested traits fit — the Baseball Cards feed directly into this matching.

He stresses designing for the reality that things go wrong: build in the diagnosis-and-improvement loop itself, so the machine surfaces its own problems (via the Issue Log and metrics) and evolves. A good design is not a static org chart but a system that keeps producing feedback about where it's failing and channels that feedback into the next redesign — the machine improving the machine.

The chapter's usable move is to stop treating recurring problems as bad luck or as things to willpower through, and to treat them as design defects to engineer out. Ask 'what would have to be true, in roles and process, for this class of problem never to reach me again?' — then build that. Dalio's whole system rewards the person who redesigns over the person who merely re-exerts.

He also warns against designing in anger or haste right after a failure: the best designs come from calm, believability-weighted reflection on the diagnosed root, not from the urge to be seen doing something. And a design should be tested against reality and revised — Dalio treats every machine as a draft that its own feedback loops will keep improving, never a finished blueprint.