solving-problems

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Solving Problems

问题解决

Purpose

目标

Apply a systematic 5-phase framework for complex problems:

Define problem boundaries clearly before investigating
Generate multiple hypotheses before testing any
Test hypotheses efficiently with time-boxing
Fix root causes, not just symptoms
Prevent recurrence with process improvements

为复杂问题应用系统化的5阶段框架：

调查前明确界定问题边界
在测试任何假设前先提出多个假设
用时间盒高效测试假设
修复根本原因，而非仅解决表面症状
通过流程改进防止问题复发

Quick Start

快速上手

Define (5-10 min) - Clarify what IS and IS NOT the problem, set success criteria
Hypothesize (10-15 min) - Generate 3+ hypotheses BEFORE testing any
Test (time-boxed) - Test cheapest hypothesis first, mark confirmed/eliminated
Solve - Fix root cause, verify fix, add regression test
Prevent - Analyze why it happened, implement preventive measures

界定（5-10分钟）- 明确问题的“是”与“非”，设定成功标准
假设（10-15分钟）- 在测试任何假设前先提出3个以上假设
测试（时间盒限制）- 先测试成本最低的假设，标记已确认/已排除
解决 - 修复根本原因，验证修复效果，添加回归测试
预防 - 分析问题发生原因，实施预防措施

Features

特性

Feature	Description	Guide
Problem Boundary	Define what IS vs IS NOT the problem	List symptoms, affected scope, working parts
Hypothesis Generation	Create 3+ theories before testing	Include evidence for/against, test cost
Prioritized Testing	Test highest-value hypotheses first	Score = evidence x (1/cost)
Root Cause Fix	Address underlying cause, not symptoms	Verify fix prevents recurrence
Prevention Plan	Stop future occurrences	Code, process, monitoring changes
Escalation Criteria	Know when to ask for help	Time-boxed out, all hypotheses eliminated

特性	描述	指南
问题边界	明确界定问题的“是”与“非”	列出症状、影响范围、正常工作的部分
假设生成	在测试前创建3个以上理论	包含支持/反对的证据、测试成本
优先级测试	先测试最高价值的假设	评分 = 证据 × (1/成本)
根本原因修复	解决潜在原因，而非表面症状	验证修复可防止问题复发
预防计划	阻止未来问题发生	代码、流程、监控变更
升级标准	了解何时寻求帮助	超出时间盒、所有假设均已排除

Common Patterns

通用模板

undefined

undefined

Define Phase

界定阶段

BOUNDARY DEFINITION What IS the problem:

Specific error: [error message]
Steps to reproduce: [steps]
When started: [date/commit]

What is NOT the problem:

What still works: [list]
Red herrings eliminated: [list]

Success criteria:

What does "solved" look like?

边界定义问题的“是”：

具体错误：[error message]
复现步骤：[steps]
开始时间：[date/commit]

问题的“非”：

仍正常工作的部分：[list]
已排除的干扰项：[list]

成功标准：

“解决”的定义是什么？

Hypothesize Phase

假设阶段

H1: [Most likely] - Evidence: ___ - Test cost: Low H2: [Second likely] - Evidence: ___ - Test cost: Medium H3: [Less likely] - Evidence: ___ - Test cost: High

RULE: Generate hypotheses BEFORE testing any.

H1: [最可能] - 证据：___ - 测试成本：低 H2: [次可能] - 证据：___ - 测试成本：中 H3: [可能性较低] - 证据：___ - 测试成本：高

规则：先生成假设再进行测试。

Test Phase

测试阶段

Test H1: [15 min box] Action: ___ Result: CONFIRMED / ELIMINATED / INCONCLUSIVE

undefined

测试H1: [15分钟时间盒] 操作：___ 结果：已确认 / 已排除 / 不确定

undefined

Risk Assessment Matrix

风险评估矩阵

Hypothesis	Probability	Impact	Test Effort	Priority
H1	High	High	Low	1st
H2	Medium	High	Medium	2nd

undefined

假设	概率	影响	测试工作量	优先级
H1	高	高	低	1st
H2	中	高	中	2nd

undefined

Use Cases

适用场景

Debugging complex bugs when conventional approaches fail
Troubleshooting production incidents with unknown root causes
Analyzing intermittent failures or race conditions
Investigating performance regressions
Resolving integration issues between systems

当常规方法失效时调试复杂bug
排查根本原因未知的生产事故
分析间歇性故障或竞态条件
调查性能退化问题
解决系统间的集成问题

Best Practices

最佳实践

Do	Avoid
Generate multiple hypotheses before testing	Testing first idea that comes to mind
Test cheapest hypothesis first when evidence equal	Spending 4 hours on 1 hypothesis
Time-box each phase	Rabbit holes without progress
Document failed approaches (valuable data)	Discarding hypotheses without testing
Verify root cause, not just symptoms	Fixing symptoms without understanding cause
Escalate when time-boxed out	Hero-coding beyond time limits
Add regression tests for every fix	Skipping prevention phase

建议做法	避免事项
测试前先提出多个假设	想到第一个想法就直接测试
当证据相同时先测试成本最低的假设	在单个假设上花费4小时
为每个阶段设置时间盒	无进展地钻牛角尖
记录失败的方法（有价值的数据）	未测试就丢弃假设
验证根本原因，而非仅表面症状	不理解原因就修复症状
超出时间盒时升级求助	超时硬扛独自解决
为每个修复添加回归测试	跳过预防阶段