Back to Details

meta-structured-problem

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Structured Problem Solving

结构化问题解决

Framework

框架

IRON LAW: MECE or It's Not Structured

Every decomposition must be MECE:
- Mutually Exclusive: No overlap between categories
- Collectively Exhaustive: No gaps — all possibilities covered

"Revenue = New customers + Existing customers" is MECE ✓
"Revenue = Online + Enterprise + Growth" is NOT MECE ✗ (overlapping)
IRON LAW: MECE or It's Not Structured

Every decomposition must be MECE:
- Mutually Exclusive: No overlap between categories
- Collectively Exhaustive: No gaps — all possibilities covered

"Revenue = New customers + Existing customers" is MECE ✓
"Revenue = Online + Enterprise + Growth" is NOT MECE ✗ (overlapping)

Core Tools

核心工具

Issue Tree: Decompose a question into sub-questions, MECE at each level
"Why is profit declining?"
├── Revenue declining?
│   ├── Volume down?
│   │   ├── New customer acquisition down?
│   │   └── Existing customer churn up?
│   └── Price down?
│       ├── Discounting increased?
│       └── Mix shift to lower-priced products?
└── Costs increasing?
    ├── COGS up?
    └── OpEx up?
Hypothesis-Driven Approach: Instead of exploring everything, state a hypothesis and test it
  1. Form an initial hypothesis ("Profit declined because churn increased")
  2. Identify what evidence would prove/disprove it
  3. Gather that specific evidence
  4. Refine or reject the hypothesis
  5. Repeat
Pyramid Principle (Barbara Minto): Structure communication top-down
  1. Lead with the answer: Start with the recommendation, not the analysis
  2. Group supporting arguments: 3-5 supporting points, MECE
  3. Order logically: By argument strength, chronologically, or structurally
  4. Detail only when asked: Each level provides more detail for those who want it
80/20 Rule: Focus on the 20% of analysis that drives 80% of the answer. Don't over-analyze secondary branches of the issue tree.
议题树（Issue Tree）：将问题拆解为子问题，每一层都需符合MECE原则
"Why is profit declining?"
├── Revenue declining?
│   ├── Volume down?
│   │   ├── New customer acquisition down?
│   │   └── Existing customer churn up?
│   └── Price down?
│       ├── Discounting increased?
│       └── Mix shift to lower-priced products?
└── Costs increasing?
    ├── COGS up?
    └── OpEx up?
假设驱动法（Hypothesis-Driven Approach）：不盲目探索所有方向，而是先提出假设再进行验证
  1. 形成初始假设（例如："利润下滑是因为客户流失率上升"）
  2. 明确能够证明/推翻该假设的证据
  3. 收集针对性证据
  4. 修正或推翻假设
  5. 重复上述步骤
金字塔原理（Pyramid Principle，Barbara Minto提出）：采用自上而下的沟通结构
  1. 结论先行：从建议开始，而非分析过程
  2. 分组支撑论点：3-5个支撑论点，需符合MECE原则
  3. 逻辑排序：可按论点强度、时间顺序或结构顺序排列
  4. 按需提供细节：仅在对方需要时补充更底层的细节
80/20法则：聚焦能影响80%结果的20%分析内容。不要过度分析议题树中的次要分支。

Problem Solving Process

问题解决流程

  1. Define the problem: "The client's profit has declined 15% YoY. Why, and what should they do?"
  2. Structure with an issue tree: MECE decomposition of possible causes
  3. Prioritize branches: Which branches are most likely to contain the answer? (80/20)
  4. Form hypotheses: "I believe the primary cause is..."
  5. Gather evidence: Test each hypothesis with data
  6. Synthesize findings: What does the evidence say?
  7. Recommend: Present using the Pyramid Principle (answer first)
  1. 定义问题：例如"客户利润同比下滑15%，原因是什么？该如何解决？"
  2. 用议题树构建结构：将可能的原因按MECE原则拆解
  3. 优先处理分支：哪些分支最有可能找到答案？（遵循80/20法则）
  4. 形成假设："我认为主要原因是……"
  5. 收集证据：用数据验证每个假设
  6. 整合发现：证据说明了什么？
  7. 提出建议：用金字塔原理呈现（结论先行）

Output Format

输出格式

markdown
undefined
markdown
undefined

Structured Analysis: {Problem}

结构化分析：{问题}

Problem Statement

问题陈述

{One sentence, specific and measurable}
{一句话，具体且可衡量}

Issue Tree

议题树

{MECE decomposition — text or visual}
{符合MECE原则的拆解——文字或可视化形式}

Hypothesis

假设

{Initial hypothesis with rationale}
{初始假设及依据}

Evidence

证据

BranchHypothesisEvidenceVerdict
{branch}{sub-hypothesis}{data found}Confirmed/Rejected
分支子假设证据结论
{分支}{子假设}{找到的数据}已确认/已推翻

Synthesis (Pyramid Structure)

整合内容（金字塔结构）

Recommendation: {answer first}
Supporting Arguments:
  1. {argument 1 with evidence}
  2. {argument 2 with evidence}
  3. {argument 3 with evidence}
建议：{结论先行}
支撑论点：
  1. {带证据的论点1}
  2. {带证据的论点2}
  3. {带证据的论点3}

Next Steps

后续步骤

  1. {action item}
undefined
  1. {行动项}
undefined

Examples

示例

Correct Application

正确应用

Scenario: "Why is our food delivery app losing market share?"
Issue tree (MECE):
Market share declining
├── Our growth slowing?
│   ├── New user acquisition down?
│   │   ├── Marketing spend reduced?
│   │   └── Conversion rate dropped?
│   └── Existing user activity down?
│       ├── Order frequency declining?
│       └── Users churning?
└── Competitors growing faster?
    ├── New entrant capturing share?
    └── Existing competitor accelerating?
Hypothesis: "Existing user activity is down because order frequency declined after the delivery fee increase." Evidence: Order frequency dropped 22% in the month after fee increase. ✓
Pyramid: "Reverse the delivery fee increase for high-frequency users. Order frequency dropped 22% post-increase, and 60% of lost orders came from users who ordered 3+/week. A loyalty tier with waived fees for frequent users would recover an estimated 15% of lost share at a cost of NT$X/month."
场景："为什么我们的外卖应用市场份额在流失？"
议题树（符合MECE原则）：
Market share declining
├── Our growth slowing?
│   ├── New user acquisition down?
│   │   ├── Marketing spend reduced?
│   │   └── Conversion rate dropped?
│   └── Existing user activity down?
│       ├── Order frequency declining?
│       └── Users churning?
└── Competitors growing faster?
    ├── New entrant capturing share?
    └── Existing competitor accelerating?
假设："现有用户活跃度下降是因为配送费上涨后下单频次降低。" 证据：配送费上涨当月，下单频次下降22%。✓
金字塔式呈现："建议为高频用户恢复原配送费。配送费上涨后下单频次下降22%，且60%的订单流失来自每周下单3次及以上的用户。为高频用户设置免配送费的忠诚度等级，预计可挽回15%的流失份额，每月成本约为NT$X。"

Incorrect Application

错误应用

  • Issue tree: "Revenue problem: Online, Marketing, Customer Service" → Not MECE (overlapping categories, not exhaustive). Violates Iron Law.
  • 议题树："营收问题：线上、营销、客户服务" → 不符合MECE原则（分类重叠、不全面）。违反铁律。

Gotchas

注意事项

  • MECE is hard in practice: Perfect MECE is aspirational. Get as close as possible and note where categories blur. "Good enough MECE" beats "perfect but took 3 days."
  • Hypothesis-driven ≠ confirmation bias: The hypothesis is a starting point to guide investigation, not a conclusion to defend. If evidence contradicts it, change the hypothesis.
  • The Pyramid Principle feels counterintuitive: People naturally want to tell the story chronologically (problem → analysis → conclusion). Audiences want the answer FIRST, then the supporting evidence. Lead with the recommendation.
  • Structured ≠ slow: Spending 30 minutes structuring the problem saves hours of unfocused analysis. The structure IS the speed.
  • Know when to stop: Analysis has diminishing returns. If you have enough evidence to make a confident recommendation, stop analyzing and recommend.
  • MECE原则实践难度大：完美的MECE是理想状态。尽量接近即可，并标注分类模糊的地方。"足够好的MECE"胜过"完美但耗时3天的MECE"。
  • 假设驱动≠确认偏差：假设是指导调查的起点，而非需要捍卫的结论。如果证据与假设矛盾，就修改假设。
  • 金字塔原理违反直觉：人们自然倾向于按时间顺序讲故事（问题→分析→结论），但听众希望先得到答案，再看支撑证据。所以要先提出建议。
  • 结构化≠低效：花30分钟构建问题结构，能节省数小时无重点的分析时间。结构本身就是效率的关键。
  • 知道何时停止：分析的收益会递减。如果已有足够证据得出有信心的建议，就停止分析并提出建议。

References

参考资料

  • For issue tree templates by problem type, see 
    references/issue-tree-templates.md
  • For Pyramid Principle writing guide, see 
    references/pyramid-principle.md
  • 按问题类型划分的议题树模板，请查看
    references/issue-tree-templates.md
  • 金字塔原理写作指南，请查看
    references/pyramid-principle.md