six-thinking-hats
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSix Thinking Hats
六顶思考帽（Six Thinking Hats）
Apply Edward de Bono's parallel thinking framework (1985) to make better decisions by examining ideas from six distinct perspectives systematically.
运用爱德华·德博诺（Edward de Bono）1985年提出的平行思考框架，通过从六个不同视角系统性地审视想法来做出更优决策。
When to Use This Skill
此技能的适用场景
- Making complex decisions that require multiple perspectives
- Evaluating new products, offers, or strategies before launch
- Breaking out of analysis paralysis with structured thinking
- Running productive meetings where everyone thinks in the same direction
- Balancing optimism with caution in strategic planning
- Generating creative alternatives when stuck on a problem
- 制定需要多视角考量的复杂决策
- 在推出前评估新产品、方案或战略
- 借助结构化思维打破分析瘫痪
- 开展全员思路统一的高效会议
- 在战略规划中平衡乐观与谨慎
- 陷入困境时生成创造性替代方案
Methodology Foundation
方法学基础
| Aspect | Details |
|---|---|
| Source | Six Thinking Hats (1985) |
| Expert | Edward de Bono - Coined "lateral thinking", advisor to IBM, Shell, NASA |
| Core Principle | "Parallel thinking" - Instead of adversarial debate, everyone thinks in the same direction at the same time, switching perspectives together |
| 维度 | 详情 |
|---|---|
| 来源 | 《六顶思考帽》（Six Thinking Hats, 1985） |
| 提出者 | 爱德华·德博诺（Edward de Bono）——提出“横向思维”（lateral thinking），曾为IBM、壳牌、NASA提供咨询 |
| 核心原则 | “平行思考”——取代对抗性辩论，让所有人在同一时间朝同一方向思考，共同切换视角 |
What Claude Does vs What You Decide
Claude的职责 vs 你的决策
| Claude Does | You Decide |
|---|---|
| Structures content frameworks | Final messaging |
| Suggests persuasion techniques | Brand voice |
| Creates draft variations | Version selection |
| Identifies optimization opportunities | Publication timing |
| Analyzes competitor approaches | Strategic direction |
| Claude的职责 | 你的决策 |
|---|---|
| 构建内容框架 | 最终信息传递 |
| 建议说服技巧 | 品牌调性 |
| 创建草稿变体 | 版本选择 |
| 识别优化机会 | 发布时机 |
| 分析竞品策略 | 战略方向 |
What This Skill Does
此技能的作用
This skill replaces chaotic brainstorming and unproductive debates with structured parallel thinking.
Instead of people defending positions and attacking others, everyone:
- Examines facts together (White)
- Shares feelings together (Red)
- Explores risks together (Black)
- Discovers benefits together (Yellow)
- Generates alternatives together (Green)
- Manages the process together (Blue)
The result: Faster decisions, better buy-in, more creative solutions, and reduced conflict.
此技能用结构化平行思考取代混乱的头脑风暴和低效的辩论。
不再是人们各执己见、互相攻击，而是所有人共同：
- 审视事实（白帽/White Hat）
- 分享感受（红帽/Red Hat）
- 探索风险（黑帽/Black Hat）
- 发现收益（黄帽/Yellow Hat）
- 生成替代方案（绿帽/Green Hat）
- 管理流程（蓝帽/Blue Hat）
结果：更快的决策、更高的认可度、更具创造性的解决方案，以及更少的冲突。
How to Use
使用方法
Analyze a Decision or Strategy
分析决策或战略
Apply the Six Thinking Hats to analyze:
[describe decision, product, strategy, or problem]
Go through each hat systematically and provide insights.运用六顶思考帽（Six Thinking Hats）分析：
[描述决策、产品、战略或问题]
系统地逐一梳理每顶帽子并提供见解。Run a Structured Evaluation
开展结构化评估
I need to decide whether to [decision].
Walk me through Six Thinking Hats analysis with specific questions for each hat.我需要决定是否[决策内容]。
带我完成六顶思考帽分析，为每顶帽子提供具体问题。Generate Creative Alternatives
生成创造性替代方案
Use Six Thinking Hats (focusing on Green Hat) to generate alternatives for:
[current approach or problem]
First establish context with White and Red, then expand with Green.运用六顶思考帽（重点为绿帽/Green Hat）为以下内容生成替代方案：
[当前方法或问题]
首先用白帽和红帽确立背景，再用绿帽拓展思路。Instructions
操作指南
The Six Hats Overview
六顶思考帽概览
┌─────────────────────────────────────────────────────────────────┐
│ THE SIX THINKING HATS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 🎩 BLUE HAT - Process & Control │
│ "What hat should we use now?" │
│ │
│ ⬜ WHITE HAT - Facts & Information │
│ "What do we know? What don't we know?" │
│ │
│ ❤️ RED HAT - Emotions & Intuition │
│ "What does my gut say? How do I feel?" │
│ │
│ ⚫ BLACK HAT - Caution & Risks │
│ "What could go wrong? What are the dangers?" │
│ │
│ 💛 YELLOW HAT - Benefits & Value │
│ "What are the benefits? Why will this work?" │
│ │
│ 💚 GREEN HAT - Creativity & Alternatives │
│ "What else could we do? What's a new approach?" │
│ │
└─────────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────────┐
│ THE SIX THINKING HATS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 🎩 BLUE HAT - Process & Control │
│ "What hat should we use now?" │
│ │
│ ⬜ WHITE HAT - Facts & Information │
│ "What do we know? What don't we know?" │
│ │
│ ❤️ RED HAT - Emotions & Intuition │
│ "What does my gut say? How do I feel?" │
│ │
│ ⚫ BLACK HAT - Caution & Risks │
│ "What could go wrong? What are the dangers?" │
│ │
│ 💛 YELLOW HAT - Benefits & Value │
│ "What are the benefits? Why will this work?" │
│ │
│ 💚 GREEN HAT - Creativity & Alternatives │
│ "What else could we do? What's a new approach?" │
│ │
└─────────────────────────────────────────────────────────────────┘Hat 1: BLUE HAT (Process Control)
帽子1：蓝帽（Blue Hat）——流程与控制
undefinedundefined🎩 BLUE HAT - The Conductor
🎩 蓝帽（Blue Hat）——指挥者
Focus: Managing the thinking process itself
Role: The Blue Hat is the "meta" hat - it controls which hat is used
when, keeps the group focused, and summarizes conclusions.
When to Use:
- At the START: Define the problem and set the agenda
- DURING: Switch hats, refocus discussion
- At the END: Summarize findings and next steps
Blue Hat Questions:
- What is the problem we're trying to solve?
- What outcome do we want from this thinking session?
- Which hat should we use next?
- Have we spent enough time on this perspective?
- What have we concluded so far?
- What are the next steps?
Blue Hat Outputs:
- Clear problem definition
- Thinking agenda (hat sequence)
- Time allocation per hat
- Summary of insights
- Action items and decisions
Tip: Start and end every session with Blue Hat.
---核心聚焦： 管理思考流程本身
角色： 蓝帽是“元思考”帽——它控制何时使用哪顶帽子，让团队保持专注，并总结结论。
适用时机：
- 开始时：定义问题并设定议程
- 进行中：切换帽子，重新聚焦讨论
- 结束时：总结发现并确定下一步行动
蓝帽问题：
- 我们要解决的问题是什么？
- 我们希望本次思考会议达成什么结果？
- 我们接下来应该用哪顶帽子？
- 我们在这个视角上花的时间足够吗？
- 到目前为止我们得出了什么结论？
- 下一步行动是什么？
蓝帽输出：
- 清晰的问题定义
- 思考议程（帽子顺序）
- 每顶帽子的时间分配
- 见解总结
- 行动项与决策
提示： 每次会议都以蓝帽开始和结束。
---Hat 2: WHITE HAT (Facts & Information)
帽子2：白帽（White Hat）——事实与信息
undefinedundefined⬜ WHITE HAT - The Scientist
⬜ 白帽（White Hat）——科学家
Focus: Objective facts, data, and information
Role: Neutral, factual thinking. No interpretations, no opinions.
Just "what do we know?" and "what do we need to find out?"
When to Use:
- Early in the process to establish baseline
- When debate gets heated (return to facts)
- Before making final decisions
White Hat Questions:
- What data do we have?
- What are the facts?
- What information is missing?
- How reliable is this information?
- What do the numbers say?
- What has happened in similar situations?
White Hat Outputs:
- List of known facts
- Data points and metrics
- Gaps in information
- Sources and reliability assessment
- Historical precedents
Rules:
- NO opinions ("I think..." = Red Hat)
- NO judgments ("That's bad..." = Black Hat)
- Just facts: "Sales were 10,000 units" ✓
- Flag uncertainty: "We believe X, but haven't verified"
Example:
❌ "The market is too competitive" (opinion)
✅ "There are 47 competitors. Top 3 have 60% market share." (fact)
---核心聚焦： 客观事实、数据与信息
角色： 中立、基于事实的思考。不做解读，不发表观点。只关注“我们知道什么？”和“我们需要查明什么？”
适用时机：
- 流程早期：确立基础背景
- 辩论激烈时：回归事实
- 做出最终决策前
白帽问题：
- 我们有哪些数据？
- 事实是什么？
- 我们缺失哪些信息？
- 这些信息的可靠性如何？
- 数据显示了什么？
- 类似情况下发生过什么？
白帽输出：
- 已知事实列表
- 数据点与指标
- 信息缺口
- 信息来源与可靠性评估
- 历史先例
规则：
- 禁止发表观点（“我认为……”属于红帽范畴）
- 禁止做出评判（“这很糟糕……”属于黑帽范畴）
- 只陈述事实：“销量为10000台” ✓
- 标注不确定性：“我们认为X，但尚未验证”
示例：
❌ “市场竞争太激烈了”（观点）
✅ “现有47家竞争对手，头部3家占据60%的市场份额”（事实）
---Hat 3: RED HAT (Emotions & Intuition)
帽子3：红帽（Red Hat）——情感与直觉
undefinedundefined❤️ RED HAT - The Heart
❤️ 红帽（Red Hat）——心灵
Focus: Feelings, intuition, gut reactions
Role: Express emotions WITHOUT justification. No need to explain
why you feel something - just state the feeling.
When to Use:
- After establishing facts (gauge emotional response)
- When something "feels off" but can't be articulated
- To surface hidden concerns or excitement
- Before final decisions (gut check)
Red Hat Questions:
- How do you feel about this?
- What's your gut reaction?
- What excites you about this?
- What worries you (emotionally)?
- If you had to decide right now, what would you choose?
- What's your intuition saying?
Red Hat Outputs:
- Emotional reactions (positive and negative)
- Intuitive hunches
- Excitement levels
- Concern levels
- Gut-based preferences
Rules:
- NO justification required
- "I don't like it" is valid (no need for why)
- Feelings are data points, not arguments
- Everyone's feelings are legitimate
- Brief expressions (not long explanations)
Example:
✅ "I feel excited about this"
✅ "Something feels off, I'm not sure what"
✅ "My gut says we should wait"
❌ "I feel this won't work because the market is saturated" (that's Black Hat)
---核心聚焦： 感受、直觉、本能反应
角色： 表达情感，无需证明理由。无需解释你为何有这种感受——只需说出感受即可。
适用时机：
- 确立事实后：评估情感反应
- 感觉“不对劲”但无法明确表达时
- 挖掘隐藏的担忧或兴奋点时
- 做出最终决策前：本能检查
红帽问题：
- 你对此有何感受？
- 你的本能反应是什么？
- 这件事让你兴奋的点是什么？
- （情感上）你担心什么？
- 如果你现在必须做决定，你会选什么？
- 你的直觉告诉你什么？
红帽输出：
- 情感反应（积极与消极）
- 直觉预感
- 兴奋程度
- 担忧程度
- 基于本能的偏好
规则：
- 无需证明理由
- “我不喜欢它”是有效的（无需解释原因）
- 感受是数据点，而非论据
- 每个人的感受都是合理的
- 简洁表达（无需长篇大论）
示例：
✅ “我对这件事感到兴奋”
✅ “总觉得哪里不对，但不确定是什么”
✅ “我的本能告诉我应该等等”
❌ “我觉得这行不通，因为市场已经饱和了”（这属于黑帽范畴）
---Hat 4: BLACK HAT (Caution & Risks)
帽子4：黑帽（Black Hat）——谨慎与风险
undefinedundefined⚫ BLACK HAT - The Judge
⚫ 黑帽（Black Hat）——法官
Focus: Caution, risks, problems, what could go wrong
Role: Critical thinking - identify weaknesses, dangers, and flaws.
This is NOT negativity for its own sake, but protective thinking.
When to Use:
- After Yellow Hat (balance optimism with caution)
- Before committing resources
- To stress-test ideas
- To identify what needs mitigation
Black Hat Questions:
- What could go wrong?
- What are the risks?
- What are the weaknesses?
- Why might this fail?
- What obstacles will we face?
- What are the costs and downsides?
- Does this fit with our resources/capabilities?
- What have we overlooked?
Black Hat Outputs:
- List of risks and dangers
- Potential failure modes
- Resource constraints
- Logical flaws in the plan
- External threats
- Implementation challenges
Rules:
- Must be LOGICAL (not just feelings - that's Red)
- Point to specific risks, not vague negativity
- "This could fail because X" ✓
- "I just don't like it" ✗ (that's Red Hat)
The Black Hat is VALUABLE:
- Prevents disasters
- Identifies what needs fixing
- Ensures realistic planning
- Required before any major decision
Example:
✅ "If competitors copy this in 3 months, we lose first-mover advantage"
✅ "Our team has never done X before - execution risk is high"
❌ "This will never work" (too vague)
---核心聚焦： 谨慎、风险、问题、可能出错的地方
角色： 批判性思考——识别弱点、危险与缺陷。这并非为了消极而消极，而是保护性思考。
适用时机：
- 黄帽之后：平衡乐观与谨慎
- 投入资源前
- 压力测试想法时
- 识别需要缓解的问题时
黑帽问题：
- 可能会出什么问题？
- 风险有哪些？
- 弱点是什么？
- 为什么这可能会失败？
- 我们会面临哪些障碍？
- 成本与弊端是什么？
- 这符合我们的资源/能力吗？
- 我们忽略了什么？
黑帽输出：
- 风险与危险列表
- 潜在失败模式
- 资源限制
- 计划中的逻辑缺陷
- 外部威胁
- 实施挑战
规则：
- 必须有逻辑依据（不能只是感觉——那属于红帽范畴）
- “这可能会失败，因为X” ✓
- “我就是不喜欢它” ✗（那属于红帽范畴）
黑帽的价值：
- 预防灾难
- 识别需要修正的问题
- 确保规划务实
- 任何重大决策前都必不可少
示例：
✅ “如果竞争对手在3个月内抄袭此方案，我们将失去先发优势”
✅ “我们团队从未做过X——执行风险很高”
❌ “这绝对行不通”（过于模糊）
---Hat 5: YELLOW HAT (Benefits & Value)
帽子5：黄帽（Yellow Hat）——收益与价值
undefinedundefined💛 YELLOW HAT - The Optimist
💛 黄帽（Yellow Hat）——乐观者
Focus: Benefits, value, why it will work
Role: Constructive, positive thinking. Find the value and benefits.
Look for what's good about an idea.
When to Use:
- To explore the upside of ideas
- When team is too negative
- To build enthusiasm and motivation
- To find value in unexpected places
Yellow Hat Questions:
- What are the benefits?
- Why will this work?
- What's the best-case scenario?
- Who gains from this and how?
- What opportunities does this create?
- What's valuable about this idea?
- How can we make this succeed?
Yellow Hat Outputs:
- List of benefits
- Value propositions
- Success scenarios
- Opportunity identification
- Reasons for optimism
- Supporting evidence for success
Rules:
- Must have LOGICAL basis (not just hope)
- "This will work because X" ✓
- "I hope it works" ✗ (that's Red Hat)
- Find genuine benefits, not forced positivity
Balance with Black Hat:
Yellow without Black = naive optimism
Black without Yellow = paralysis
Both together = realistic assessment
Example:
✅ "If we capture 5% of the market, that's $2M revenue"
✅ "This positions us as thought leaders in an emerging space"
❌ "It'll be great!" (no substance)
---核心聚焦： 收益、价值、可行原因
角色： 建设性、积极的思考。寻找想法的价值与收益。关注想法的优点。
适用时机：
- 探索想法的优势时
- 团队过于消极时
- 建立热情与动力时
- 在意想不到的地方寻找价值时
黄帽问题：
- 收益有哪些？
- 为什么这会可行？
- 最佳场景是什么？
- 谁会从中受益，如何受益？
- 这会创造哪些机会？
- 这个想法的价值是什么？
- 我们如何能让它成功？
黄帽输出：
- 收益列表
- 价值主张
- 成功场景
- 机会识别
- 乐观的理由
- 支持成功的证据
规则：
- 必须有逻辑依据（不能只是希望——那属于红帽范畴）
- “这会成功，因为X” ✓
- “我希望它能成功” ✗（那属于红帽范畴）
- 寻找真正的收益，而非强行 positivity
与黑帽平衡：
只有黄帽没有黑帽=天真乐观
只有黑帽没有黄帽=分析瘫痪
两者结合=务实评估
示例：
✅ “如果我们占据5%的市场份额，那将带来200万美元的收入”
✅ “这将使我们成为新兴领域的思想领袖”
❌ “一定会很棒！”（没有实质内容）
---Hat 6: GREEN HAT (Creativity & Alternatives)
帽子6：绿帽（Green Hat）——创造力与替代方案
undefinedundefined💚 GREEN HAT - The Creator
💚 绿帽（Green Hat）——创造者
Focus: New ideas, alternatives, creative solutions
Role: Generate possibilities without judgment. Explore "what if?"
Think beyond obvious solutions.
When to Use:
- When stuck on a problem
- After Black Hat identifies problems (find solutions)
- To generate options before deciding
- When current approach isn't working
Green Hat Questions:
- What alternatives exist?
- What if we did the opposite?
- How might we approach this differently?
- What would [successful company/person] do?
- What's a completely new way to solve this?
- How can we overcome the Black Hat concerns?
- What assumptions can we challenge?
Green Hat Techniques:
- Random Entry: Pick random word, connect to problem
- Reversal: What's the opposite approach?
- Analogy: How do other industries solve this?
- Exaggeration: What if we 10x'd this element?
- Combination: Merge two different approaches
Green Hat Outputs:
- List of alternative approaches
- Creative solutions
- New ideas to explore
- Modifications to existing ideas
- "What if" scenarios
Rules:
- NO judgment during Green Hat (judgment = Black)
- Quantity over quality initially
- Build on others' ideas ("Yes, and...")
- Suspend disbelief temporarily
- Wild ideas welcome (can be refined later)
Example:
✅ "What if we gave it away free and monetized differently?"
✅ "What if we partnered with competitors instead of fighting them?"
✅ "What if we targeted the opposite customer segment?"
---核心聚焦： 新想法、替代方案、创造性解决方案
角色： 不受评判地生成可能性。探索“如果……会怎样？”超越显而易见的解决方案。
适用时机：
- 陷入问题困境时
- 黑帽识别出问题后（寻找解决方案）
- 决策前生成选项时
- 当前方法行不通时
绿帽问题：
- 有哪些替代方案？
- 如果我们反过来做会怎样？
- 我们可以用哪些不同的方式处理这件事？
- [成功公司/人士]会怎么做？
- 有什么全新的解决方法？
- 我们如何解决黑帽提出的担忧？
- 我们可以挑战哪些假设？
绿帽技巧：
- 随机切入： 挑选随机词汇，与问题建立关联
- 反转： 相反的方法是什么？
- 类比： 其他行业如何解决这个问题？
- 夸张： 如果我们将这个元素放大10倍会怎样？
- 组合： 合并两种不同的方法
绿帽输出：
- 替代方法列表
- 创造性解决方案
- 待探索的新想法
- 对现有想法的修改
- “如果……”场景
规则：
- 绿帽阶段禁止评判（评判属于黑帽范畴）
- 初期追求数量而非质量
- 基于他人的想法拓展（“是的，而且……”）
- 暂时搁置怀疑
- 欢迎疯狂的想法（后续可完善）
示例：
✅ “如果我们免费提供，通过其他方式盈利会怎样？”
✅ “如果我们与竞争对手合作而非对抗会怎样？”
✅ “如果我们瞄准相反的客户群体会怎样？”
---Recommended Hat Sequences
推荐的帽子使用顺序
undefinedundefinedCommon Hat Sequences
常见帽子使用顺序
For EVALUATING an Idea:
评估想法时：
- 🎩 Blue - Define what we're evaluating
- ⬜ White - Gather facts about the idea
- ❤️ Red - Initial gut reactions
- 💛 Yellow - Explore benefits
- ⚫ Black - Identify risks
- 💚 Green - Generate improvements/alternatives
- ❤️ Red - Final gut check
- 🎩 Blue - Summarize and decide
- 🎩 蓝帽 - 定义评估对象
- ⬜ 白帽 - 收集关于想法的事实
- ❤️ 红帽 - 初始本能反应
- 💛 黄帽 - 探索收益
- ⚫ 黑帽 - 识别风险
- 💚 绿帽 - 生成改进方案/替代方案
- ❤️ 红帽 - 最终本能检查
- 🎩 蓝帽 - 总结并决策
For SOLVING a Problem:
解决问题时：
- 🎩 Blue - Define the problem clearly
- ⬜ White - Understand the facts
- 💚 Green - Generate solutions (many options)
- 💛 Yellow - Evaluate benefits of each
- ⚫ Black - Evaluate risks of each
- ❤️ Red - Which feels right?
- 🎩 Blue - Choose and plan next steps
- 🎩 蓝帽 - 清晰定义问题
- ⬜ 白帽 - 了解事实
- 💚 绿帽 - 生成解决方案（多种选项）
- 💛 黄帽 - 评估每个方案的收益
- ⚫ 黑帽 - 评估每个方案的风险
- ❤️ 红帽 - 哪个感觉更合适？
- 🎩 蓝帽 - 选择并规划下一步
For QUICK Decisions:
快速决策时：
- ⬜ White - Key facts only (2 min)
- ❤️ Red - Gut reaction (1 min)
- 💛 Yellow - Main benefit (1 min)
- ⚫ Black - Main risk (1 min)
- 🎩 Blue - Decide (1 min)
- ⬜ 白帽 - 仅核心事实（2分钟）
- ❤️ 红帽 - 本能反应（1分钟）
- 💛 黄帽 - 主要收益（1分钟）
- ⚫ 黑帽 - 主要风险（1分钟）
- 🎩 蓝帽 - 决策（1分钟）
For CREATIVE Sessions:
创造性会议时：
- 🎩 Blue - Set creative challenge
- 💚 Green - Generate ideas freely (bulk)
- 💛 Yellow - Find value in each idea
- ⚫ Black - Identify issues to solve
- 💚 Green - Modify and improve
- 🎩 Blue - Select ideas to develop
---- 🎩 蓝帽 - 设定创意挑战
- 💚 绿帽 - 自由生成大量想法
- 💛 黄帽 - 寻找每个想法的价值
- ⚫ 黑帽 - 识别需要解决的问题
- 💚 绿帽 - 修改并完善想法
- 🎩 蓝帽 - 选择待发展的想法
---Examples
示例
Example 1: Evaluating a New Product Launch
示例1：评估新产品发布
Context: SaaS company considering launching a mobile app
🎩 Blue Hat (Setup):
We're evaluating whether to launch a mobile app for our project management tool. We want to decide: build, don't build, or build later. Let's spend 5 minutes per hat.
⬜ White Hat (Facts):
- 34% of our users access via mobile browser
- Competitors X and Y have apps (4.2 and 3.8 star ratings)
- Development estimate: 4-6 months, $120K
- Our NPS is 47 (desktop users)
- Mobile browser bounce rate: 67% (vs 23% desktop)
- We have 2 mobile developers available
❤️ Red Hat (Feelings):
- "Excited - this could unlock new use cases"
- "Nervous about the investment"
- "Frustrated we haven't done this sooner"
- "Gut says our users want this"
💛 Yellow Hat (Benefits):
- Reduces friction for mobile users (67% bounce → potential wins)
- Competitive parity with X and Y
- Push notifications = higher engagement
- New positioning as "work anywhere" tool
- If 20% of mobile bouncers convert, that's 400 new users/month
⚫ Black Hat (Risks):
- 6-month dev = opportunity cost (what else could we build?)
- Mobile apps need ongoing maintenance (15-20% of dev time)
- App store reviews are public - bad launch = reputation damage
- Our mobile developers have never shipped an app
- Desktop feature requests are piling up
💚 Green Hat (Alternatives):
- Progressive Web App (PWA) instead of native?
- Partner with app development agency?
- Launch MVP with 3 core features only?
- Build for one platform first (iOS or Android)?
- Buy a smaller competitor with existing app?
🎩 Blue Hat (Conclusion):
Decision: Build PWA first (lower risk, faster). If adoption exceeds 1,000 weekly users in 3 months, greenlight native app development.
背景： SaaS公司考虑推出移动端应用
🎩 蓝帽（准备阶段）：
我们正在评估是否为项目管理工具推出移动端应用。我们需要决定：开发、不开发，还是延后开发。每顶帽子分配5分钟时间。
⬜ 白帽（事实）：
- 34%的用户通过移动浏览器访问
- 竞争对手X和Y拥有应用（评分分别为4.2和3.8星）
- 开发预估：4-6个月，12万美元
- 我们的NPS为47（桌面用户）
- 移动浏览器跳出率：67%（桌面为23%）
- 我们有2名移动开发人员可用
❤️ 红帽（感受）：
- “很兴奋——这能解锁新的使用场景”
- “对投资感到紧张”
- “很懊恼我们之前没做这件事”
- “本能告诉我用户需要这个”
💛 黄帽（收益）：
- 降低移动用户的使用门槛（67%的跳出率→潜在转化机会）
- 与X和Y达到竞争对等
- 推送通知→更高的用户参与度
- 打造“随时随地工作”的工具定位
- 如果20%的移动跳出用户转化，每月新增400名用户
⚫ 黑帽（风险）：
- 6个月的开发周期=机会成本（我们本可以开发其他功能？）
- 移动应用需要持续维护（占开发时间的15-20%）
- 应用商店评论公开——糟糕的发布会损害声誉
- 我们的移动开发人员从未发布过应用
- 桌面功能的需求堆积如山
💚 绿帽（替代方案）：
- 用渐进式Web应用（PWA）替代原生应用？
- 与应用开发机构合作？
- 仅发布包含3个核心功能的MVP？
- 先为一个平台开发（iOS或Android）？
- 收购拥有现有应用的小型竞争对手？
🎩 蓝帽（结论）：
决策：先开发PWA（风险更低、速度更快）。如果3个月内周活用户超过1000，再批准原生应用开发。
Example 2: Quick Decision on Pricing
示例2：定价快速决策
Context: Should we raise prices by 20%?
⬜ White (30 sec): Current price $99. Competitors range $79-$149. Last increase was 18 months ago. Churn is 4.2% monthly.
❤️ Red (30 sec): "Nervous about customer backlash." "Feels overdue though."
💛 Yellow (30 sec): 20% more revenue on existing customers. Positions us as premium. Funds product improvements.
⚫ Black (30 sec): Some customers will leave. Acquisition might suffer. Timing during economic uncertainty.
🎩 Blue (30 sec): Decision: Raise prices 15% for new customers only. Grandfather existing for 6 months. Re-evaluate.
背景： 我们是否应该提价20%？
⬜ 白帽（30秒）： 当前价格99美元。竞争对手价格范围79-149美元。上次提价是18个月前。月度流失率4.2%。
❤️ 红帽（30秒）： “担心客户反弹。”“不过感觉早就该提价了。”
💛 黄帽（30秒）： 现有客户收入增加20%。定位为高端产品。为产品改进提供资金。
⚫ 黑帽（30秒）： 部分客户会流失。获客可能受影响。当前经济不稳定时期的时机问题。
🎩 蓝帽（30秒）： 决策：仅对新客户提价15%。现有客户6个月内保持原价。后续重新评估。
Checklists & Templates
检查表与模板
Six Hats Analysis Template
六顶思考帽分析模板
markdown
undefinedmarkdown
undefinedSix Thinking Hats Analysis
六顶思考帽（Six Thinking Hats）分析
Subject: [What are we analyzing?]
Date: [Date]
Participants: [Who's involved?]
主题： [我们要分析的内容]
日期： [日期]
参与者： [参与人员]
🎩 BLUE HAT - Setup
🎩 蓝帽（Blue Hat）——准备阶段
Problem/Question:
Desired Outcome:
Time per Hat:
问题/议题：
期望结果：
每顶帽子时间分配：
⬜ WHITE HAT - Facts
⬜ 白帽（White Hat）——事实
What we know:
What we don't know:
Data sources:
我们知道的：
我们不知道的：
数据来源：
❤️ RED HAT - Feelings
❤️ 红帽（Red Hat）——感受
Positive feelings:
Concerns/negative feelings:
Gut instinct:
积极感受：
担忧/消极感受：
本能直觉：
💛 YELLOW HAT - Benefits
💛 黄帽（Yellow Hat）——收益
Key benefits:
Best-case scenario:
Who gains and how:
核心收益：
最佳场景：
受益方及方式：
⚫ BLACK HAT - Risks
⚫ 黑帽（Black Hat）——风险
Key risks:
What could go wrong:
Obstacles:
核心风险：
可能出现的问题：
障碍：
💚 GREEN HAT - Alternatives
💚 绿帽（Green Hat）——替代方案
Alternative approaches:
Modifications to improve:
Wild ideas:
替代方法：
改进建议：
疯狂想法：
🎩 BLUE HAT - Conclusion
🎩 蓝帽（Blue Hat）——结论
Summary of insights:
Decision:
Next steps:
1.
2.
3.
---见解总结：
决策：
下一步行动：
1.
2.
3.
---Meeting Facilitation Guide
会议引导指南
markdown
undefinedmarkdown
undefinedRunning a Six Hats Meeting
运行六顶思考帽会议
Preparation
准备工作
- Define the topic/decision clearly
- Prepare White Hat data in advance
- Allocate time per hat (typically 5-10 min each)
- Brief participants on the method
- 清晰定义议题/决策
- 提前准备白帽数据
- 为每顶帽子分配时间（通常5-10分钟）
- 向参与者介绍此方法
Rules to Establish
确立规则
- Everyone wears the same hat at the same time
- No criticism during Green Hat
- Red Hat feelings need no justification
- Black Hat must be specific, not vague
- Blue Hat facilitator controls hat switches
- 所有人同一时间佩戴同一顶帽子
- 绿帽阶段禁止批评
- 红帽感受无需证明理由
- 黑帽必须具体，不能模糊
- 蓝帽引导者控制帽子切换
Facilitation Tips
引导技巧
- Use physical props (colored cards/hats) if in person
- Announce hat switches clearly
- Redirect off-hat comments ("Let's save that for Black Hat")
- Keep time visible
- Capture outputs for each hat
- End with clear next steps
- 线下会议可使用实物道具（彩色卡片/帽子）
- 清晰宣布帽子切换
- 偏离当前帽子的评论要引导回正轨（“我们把这个留到黑帽阶段讨论”）
- 显示时间进度
- 记录每顶帽子的输出
- 会议结束时明确下一步行动
Common Pitfalls
常见陷阱
- Skipping Red Hat (emotions surface anyway, better explicit)
- Too much time on Black Hat (negativity spiral)
- Not enough time on Green Hat (settling for obvious)
- Mixing hats (debating during White Hat)
---- 跳过红帽（情绪总会显现，不如明确表达）
- 黑帽时间过长（陷入消极螺旋）
- 绿帽时间不足（满足于显而易见的方案）
- 混合帽子（白帽阶段进行辩论）
---Skill Boundaries
技能边界
What This Skill Does Well
此技能擅长的领域
- Structuring persuasive content
- Applying copywriting frameworks
- Creating draft variations
- Analyzing competitor approaches
- 构建有说服力的内容
- 应用文案框架
- 创建草稿变体
- 分析竞品策略
What This Skill Cannot Do
此技能不擅长的领域
- Guarantee conversion rates
- Replace brand voice development
- Know your specific audience
- Make final approval decisions
- 保证转化率
- 替代品牌调性开发
- 了解你的特定受众
- 做出最终审批决策
References
参考资料
- de Bono, Edward. "Six Thinking Hats" (1985)
- de Bono, Edward. "Lateral Thinking" (1967)
- de Bono Group - Official training materials
- Harvard Business Review - "Six Thinking Hats" application studies
- de Bono, Edward. 《Six Thinking Hats》(1985)
- de Bono, Edward. 《Lateral Thinking》(1967)
- de Bono Group - 官方培训材料
- 哈佛商业评论 - 《Six Thinking Hats》应用研究
Related Skills
相关技能
- first-principles - Deep analysis for White Hat facts
- inversion - Structured approach for Black Hat risks
- pre-mortem - Extended Black Hat failure analysis
- eisenhower-matrix - Prioritize actions from Blue Hat conclusions
- first-principles - 为白帽事实提供深度分析
- inversion - 为黑帽风险提供结构化方法
- pre-mortem - 黑帽失败分析的延伸
- eisenhower-matrix - 优先处理蓝帽结论中的行动项
Skill Metadata (Internal Use)
技能元数据（内部使用）
yaml
name: six-thinking-hats
category: strategy
subcategory: decision-making
version: 1.0
author: MKTG Skills
source_expert: Edward de Bono
source_work: Six Thinking Hats (1985)
difficulty: beginner
estimated_value: $500 workshop
tags: [decision-making, creativity, meetings, problem-solving, de Bono]
created: 2025-01-25
updated: 2025-01-25yaml
name: six-thinking-hats
category: strategy
subcategory: decision-making
version: 1.0
author: MKTG Skills
source_expert: Edward de Bono
source_work: Six Thinking Hats (1985)
difficulty: beginner
estimated_value: $500 workshop
tags: [decision-making, creativity, meetings, problem-solving, de Bono]
created: 2025-01-25
updated: 2025-01-25