Back to Details

consulting-issue-tree-mece

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MECE Issue Tree

MECE问题树

Use $ARGUMENTS as initial context.
使用$ARGUMENTS作为初始上下文。

When to use this skill

何时使用该技能

  • Diagnosing root causes in performance decline or execution failures.
  • Structuring strategic questions into mutually exclusive branches.
  • Creating a prioritized analysis plan before data deep-dives.
  • Aligning teams on problem scope and ownership.
  • 诊断性能下降或执行故障的根本原因。
  • 将战略问题拆解为互斥的分支。
  • 在深入分析数据前制定优先级明确的分析计划。
  • 让团队就问题范围和职责达成一致。

Required inputs

所需输入

  • Problem statement, metric, and baseline.
  • Scope boundaries (segment, geography, time horizon).
  • Available data and decision deadline.
  • 问题陈述、指标和基准线。
  • 范围边界（细分领域、地域、时间范围）。
  • 可用数据和决策截止日期。

Workflow

工作流程

  1. Convert the request into one decision-oriented problem statement.
  2. Select tree type: driver, process, option, or hypothesis tree.
  3. Build 2-3 levels of MECE branches with parallel labels.
  4. Run formal checks for overlap, gaps, and level-mixing.
  5. Prioritize branches by impact, controllability, and learning speed.
  6. Translate top branches into an analysis backlog with owners and timing.
  1. 将需求转换为一个以决策为导向的问题陈述。
  2. 选择树类型：驱动因素树、流程树、选项树或假设树。
  3. 构建2-3层MECE分支，分支标签平行对应。
  4. 对重叠、缺口和层级混淆问题进行正式检查。
  5. 根据影响程度、可控性和学习速度对分支进行优先级排序。
  6. 将顶级分支转化为包含负责人和时间安排的分析待办事项。

Ask-first questions

前置询问问题

Ask up to 3 questions before building the tree:
  1. Which metric and baseline define the problem severity?
  2. What scope is explicitly in or out?
  3. What decision must this tree support?
在构建树之前，最多询问3个问题：
  1. 哪些指标和基准线定义了问题的严重程度？
  2. 明确包含或排除的范围是什么？
  3. 该树需要支持哪项决策？

Assumption policy

假设原则

  • Proceed if data is incomplete, but list assumptions in a dedicated section.
  • Tag assumptions with confidence and validation path.
  • Do not invent branch evidence; flag unknowns explicitly.
  • 若数据不完整仍可继续，但需在专门章节列出假设。
  • 为假设标记置信度和验证路径。
  • 不得编造分支证据；需明确标记未知项。

Output contract

输出约定

Always produce these sections in order:
  1. Context
  2. Decision or Recommendation
  3. Analysis
  4. Risks
  5. Next Actions
  6. Assumptions
始终按以下顺序生成这些部分：
  1. 上下文
  2. 决策或建议
  3. 分析
  4. 风险
  5. 后续行动
  6. 假设

Guardrails

约束规则

  • No branch overlap at the same level.
  • No mixing causes and outcomes in one branch layer.
  • No "other" bucket unless unavoidable and quantified.
  • Keep branch naming at equivalent abstraction depth.
  • 同一层级的分支不得重叠。
  • 同一分支层级不得混合原因和结果。
  • 除非不可避免且可量化，否则不得使用“其他”类别。
  • 分支命名需保持相同的抽象深度。

Resources

资源

  • references/issue-tree-patterns.md
    - Tree patterns and branch design rules.
  • references/mece-checks.md
    - Validation gates and failure diagnostics.
  • templates/issue-tree.md
    - Decision-ready tree template.
  • examples/issue-tree-example.md
    - Golden example with partial information.
  • references/issue-tree-patterns.md
    - 问题树模式和分支设计规则。
  • references/mece-checks.md
    - 验证关口和故障诊断方法。
  • templates/issue-tree.md
    - 可用于决策的问题树模板。
  • examples/issue-tree-example.md
    - 包含部分信息的优秀示例。

Keywords

关键词

issue tree, MECE, root cause, problem structuring, analysis backlog, driver tree
问题树, MECE, 根本原因, 问题结构化, 分析待办事项, 驱动因素树