The most common mistake in action is jumping from a problem directly to a proposed solution in a nanosecond — without spending the hours required to properly diagnose and design a solution. Dalio calls this the primary source of bad decisions that don't actually address the problem. ## The Anti-Pattern "It is a very common mistake for people to move directly from identifying a tough problem to a proposed solution in a nanosecond without spending the hours required to properly diagnose and design a solution." Jumping to solutions feels like action — it relieves the discomfort of uncertainty. But it is false action: it consumes resources on the wrong problem. ## The Discipline: Thinking as Action Dalio: "Take at least a few hours to think through your plan. Those hours will be virtually nothing in relation to the amount of time that will be spent doing, and they will make the doing radically more effective." Thinking is not a delay before action — it is a form of action. Before any significant campaign, run the planning questions: what am I trying to achieve, why, how will I know I'm successful, likely pitfalls, and the conditions under which I'd abandon the plan. ## Cross-Domain Applications **Software architecture**: the pull request that changes the database schema without diagnosing the query bottleneck first. Symptoms → immediate fix → root cause untouched. **Client work**: proposing a Rails upgrade before auditing what's actually breaking — the diagnosis must precede the design. ## Related Concepts - [[Deliberateness as Anti-Chance Strategy]] — the broader principle; diagnosis-design is its application to problem-solving - [[Reflective Control]] — the state required to think through diagnosis without autopilot taking over - [[Simple Disciplined Thinking]] — related discipline in this topic *Source: Sebastian Marshall, Gateless, "The Cognitive Lever" — via [[Conative Knowledge]]*