thinking-second-order

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Second-Order Thinking

二阶思维

Overview

概述

Second-order thinking, articulated by Howard Marks, moves beyond immediate effects to consider what happens next, and what that leads to. First-order thinking is simplistic ("This action solves the problem"); second-order thinking asks "And then what?" repeatedly.

Core Principle: The obvious answer to "What should I do?" is often wrong because it ignores downstream effects.

二阶思维由Howard Marks提出，它跳出直接影响，思考接下来会发生什么，以及后续连锁反应。一阶思维较为简单（“这个行动能解决问题”）；而二阶思维会反复追问“然后呢？”

核心原则： “我该怎么做？”的显而易见的答案往往是错误的，因为它忽略了后续连锁影响。

When to Use

适用场景

Making strategic or architectural decisions
Evaluating policy or process changes
Considering incentive structures
Planning features that change user behavior
Decisions with long-term consequences
When the "obvious" solution feels too easy

Decision flow:

Decision with consequences beyond immediate? → yes → APPLY SECOND-ORDER THINKING
                                            ↘ no → First-order may suffice

制定战略或架构决策
评估政策或流程变更
考量激励机制
规划会改变用户行为的功能
具有长期影响的决策
当“显而易见”的解决方案看起来过于简单时

决策流程：

Decision with consequences beyond immediate? → yes → APPLY SECOND-ORDER THINKING
                                            ↘ no → First-order may suffice

First vs Second-Order Thinking

一阶思维 vs 二阶思维

Situation	First-Order	Second-Order
Team is slow	Add more engineers	More engineers → more coordination → slower decisions → may get slower
Users complain	Add the feature they request	Feature → complexity → more support load → less time for core work
Costs too high	Cut spending	Cuts → reduced quality → customer churn → revenue drop → worse situation
Bug in prod	Hotfix immediately	Hotfix → skip testing → more bugs → trust erosion → slower deployments

场景	一阶思维	二阶思维
团队效率低下	增加工程师数量	增加工程师 → 协作成本上升 → 决策变慢 → 效率可能更低
用户抱怨	添加用户要求的功能	新增功能 → 系统复杂度提升 → 支持负担加重 → 核心工作时间减少
成本过高	削减开支	削减开支 → 质量下降 → 客户流失 → 收入减少 → 情况恶化
生产环境出现Bug	立即热修复	热修复 → 跳过测试 → 更多Bug出现 → 信任受损 → 部署速度变慢

The Process

实施步骤

Step 1: Identify the Decision and First-Order Effect

步骤1：明确决策与一阶影响

Decision: Add a feature flag system
First-order: Teams can ship features independently ✓

Decision: Add a feature flag system
First-order: Teams can ship features independently ✓

Step 2: Ask "And Then What?"

步骤2：追问“然后呢？”

Chain the consequences:

Feature flags → More flags created → Flag debt accumulates
             → Teams don't clean up → Combinatorial testing complexity
             → Bugs from flag interactions → "Turn it off" becomes risky
             → Flags become permanent → Codebase complexity explodes

连锁推导后果：

Feature flags → More flags created → Flag debt accumulates
             → Teams don't clean up → Combinatorial testing complexity
             → Bugs from flag interactions → "Turn it off" becomes risky
             → Flags become permanent → Codebase complexity explodes

Step 3: Apply the 10/10/10 Framework

步骤3：应用10/10/10框架

Evaluate impact across time horizons:

Timeframe	Question	Analysis
10 minutes	How will I feel right after?	Relief—problem solved
10 months	How will this affect things in 10 months?	Flag sprawl emerging
10 years	What's the long-term trajectory?	Technical debt crisis

从不同时间维度评估影响：

时间范围	问题	分析
10分钟后	行动后我会有什么感受？	释然——问题解决了
10个月后	这会对10个月后的情况产生什么影响？	标志系统混乱开始显现
10年后	长期发展趋势如何？	技术债务危机

Step 4: Consider Systemic Effects

步骤4：考量系统性影响

Ask: "What if everyone did this?"

Decision: Skip code review for urgent fixes
If everyone: All urgent fixes skip review
Result: Definition of "urgent" expands → most things skip review
Outcome: Quality collapses, more urgent fixes needed

追问：“如果所有人都这么做会怎样？”

Decision: Skip code review for urgent fixes
If everyone: All urgent fixes skip review
Result: Definition of "urgent" expands → most things skip review
Outcome: Quality collapses, more urgent fixes needed

Step 5: Map the Consequence Chain

步骤5：绘制连锁影响链

┌─────────────────┐
│ Decision: X     │
└────────┬────────┘
         ▼
┌─────────────────┐
│ 1st Order: A    │ ← Obvious, intended
└────────┬────────┘
         ▼
┌─────────────────┐
│ 2nd Order: B    │ ← Less obvious
└────────┬────────┘
         ▼
┌─────────────────┐
│ 3rd Order: C    │ ← Often counterintuitive
└────────┬────────┘
         ▼
┌─────────────────┐
│ Feedback Loop   │ ← May reinforce or counteract
└─────────────────┘

┌─────────────────┐
│ Decision: X     │
└────────┬────────┘
         ▼
┌─────────────────┐
│ 1st Order: A    │ ← Obvious, intended
└────────┬────────┘
         ▼
┌─────────────────┐
│ 2nd Order: B    │ ← Less obvious
└────────┬────────┘
         ▼
┌─────────────────┐
│ 3rd Order: C    │ ← Often counterintuitive
└────────┬────────┘
         ▼
┌─────────────────┐
│ Feedback Loop   │ ← May reinforce or counteract
└─────────────────┘

Common Second-Order Effects in Software

软件开发中常见的二阶影响

Optimization

优化

1st: Optimize critical path → Faster
2nd: Team focuses on optimization → Less feature work
3rd: Premature optimization spreads → Complexity increases
4th: Maintenance burden grows → Slower overall

1st: Optimize critical path → Faster
2nd: Team focuses on optimization → Less feature work
3rd: Premature optimization spreads → Complexity increases
4th: Maintenance burden grows → Slower overall

Hiring

招聘

1st: Hire senior engineers → More capacity
2nd: Salary expectations rise → Budget pressure
3rd: Junior engineers feel stuck → Attrition
4th: Knowledge concentrated in seniors → Bus factor risk

1st: Hire senior engineers → More capacity
2nd: Salary expectations rise → Budget pressure
3rd: Junior engineers feel stuck → Attrition
4th: Knowledge concentrated in seniors → Bus factor risk

Process Addition

流程新增

1st: Add approval process → More oversight
2nd: Approvals create bottleneck → Slower delivery
3rd: People route around process → Shadow processes
4th: Formal process becomes theater → Worst of both worlds

1st: Add approval process → More oversight
2nd: Approvals create bottleneck → Slower delivery
3rd: People route around process → Shadow processes
4th: Formal process becomes theater → Worst of both worlds

Technical Shortcuts

技术捷径

1st: Skip tests to ship faster → Feature delivered
2nd: Bugs emerge → Support load increases
3rd: Team fights fires → Less time for features
4th: More shortcuts taken → Quality death spiral

1st: Skip tests to ship faster → Feature delivered
2nd: Bugs emerge → Support load increases
3rd: Team fights fires → Less time for features
4th: More shortcuts taken → Quality death spiral

Application Framework

应用框架

For any significant decision, fill out:

markdown

undefined

对于任何重要决策，填写以下内容：

markdown

undefined

Second-Order Analysis: [Decision]

Immediate Effect (1st Order)

[What happens right away]

Near-Term Consequences (2nd Order)

[What does the immediate effect cause? 1-3 months]

Medium-Term Consequences (3rd Order)

[What do the near-term effects cause? 3-12 months]

Long-Term Trajectory

[Where does this path lead? 1+ years]

Feedback Loops

[Does this create reinforcing or balancing dynamics?]

If Scaled

[What happens if this becomes standard practice?]

Revised Decision

[Given analysis, what should we actually do?]

undefined

[Given analysis, what should we actually do?]

undefined

Questions to Surface Second-Order Effects

挖掘二阶影响的问题清单

"And then what?"
"Who else is affected, and how will they respond?"
"What incentives does this create?"
"What behavior does this encourage/discourage?"
"If this works, what problems does success create?"
"What will we wish we had done differently in a year?"
"What does this look like if everyone does it?"

“然后呢？”
“还有谁会受到影响，他们会如何反应？”
“这会创造什么样的激励机制？”
“这会鼓励/抑制什么样的行为？”
“如果这个方案成功了，成功会带来什么新问题？”
“一年后，我们会后悔哪些决策？”
“如果所有人都这么做，会是什么结果？”

Verification Checklist

验证清单

Marks' Warning

Marks的警示

"First-level thinking is simplistic and superficial, and just about everyone can do it. Second-level thinking is deep, complex, and convoluted."

The crowd uses first-order thinking. Competitive advantage comes from thinking one level deeper—seeing what happens after the obvious effect.

“一阶思维简单肤浅，几乎人人都能做到。二阶思维则深刻、复杂且层层递进。”

大众都在用一阶思维。竞争优势来自于更深入的思考——看到显而易见的影响之后会发生什么。