Six Thinking Hats

---
name: six-thinking-hats
description: Parallel thinking method using six colored hats to systematically explore problems from six distinct perspectives in sequence
---

# Six Thinking Hats

## Overview

Six Thinking Hats is a structured parallel thinking technique developed by Edward de Bono (physician, psychologist, philosopher) for exploring problems from six distinct cognitive modes represented by colored hats. The method eliminates adversarial debate by having all participants "wear the same hat" simultaneously, focusing collective attention on one thinking style at a time.

The genius of the approach: traditional meetings devolve into ego battles where individuals defend positions. Six Hats separates the ego from thinking by making hat-switching explicit—everyone adopts the same perspective simultaneously, transforming argument into exploration. You're not "the pessimist" (Black Hat); you're simply wearing the Black Hat for this phase, as is everyone else.

Each hat has a specific function: White (data/facts), Red (emotions/intuition), Black (caution/risk), Yellow (benefits/optimism), Green (creativity/alternatives), Blue (process control). By sequencing hats deliberately, teams extract maximum value from each thinking mode without cognitive interference or conflict.

## When to Use

- Decision-making with diverse stakeholders (avoid groupthink or conflict)
- Strategic planning sessions requiring multiple perspectives
- Risk assessment that balances optimism and caution
- Innovation workshops needing structured creativity
- Post-mortem analysis of projects or failures
- Conflict resolution by depersonalizing viewpoints
- Complex problems requiring thorough exploration before deciding

## The Process

### Step 1: Blue Hat - Set the Agenda (2-5 minutes)

Define the problem, desired outcome, and hat sequence. The Blue Hat manages the thinking process throughout.

**Questions:** What are we solving? What's our goal? What hat order will serve us best?
**Example:** "We're deciding whether to enter the Asian market. Start White → Red → Yellow → Black → Green → Blue."

### Step 2: White Hat - Gather Facts (5-15 minutes)

Focus solely on available data, information gaps, and where to find missing information. No opinions, no interpretations—only facts.

**Questions:** What do we know? What don't we know? What information is missing? Where can we get it?
**Example:** "Current revenue: $50M. Asian market size: $2B. Our market research shows 37% brand awareness in Tokyo."

### Step 3: Red Hat - Express Emotions (30 seconds - 2 minutes)

Quick gut-check for intuition and feelings. No justification required—this is instinctive reaction, not analysis.

**Questions:** How do I feel about this? What's my gut reaction? What emotions arise?
**Example:** "I feel excited but anxious. My gut says timing is premature. I'm worried about execution risk."

### Step 4: Yellow Hat - Identify Benefits (5-10 minutes)

Explore positive outcomes, benefits, and value. Adopt the most optimistic lens possible—what's the best-case scenario?

**Questions:** What are the benefits? What value could this create? Why might this work brilliantly?
**Example:** "Access to 500M new customers. First-mover advantage. Diversifies revenue away from saturated US market."

### Step 5: Black Hat - Assess Risks (5-10 minutes)

Critical judgment: What could go wrong? What are the risks, downsides, and weaknesses? Employ rigorous caution.

**Questions:** What are the risks? What could fail? Why might this not work? What am I missing?
**Example:** "Regulatory barriers in 3 countries. $20M upfront investment. Team lacks Asia expertise. Currency fluctuation risk."

### Step 6: Green Hat - Generate Alternatives (10-15 minutes)

Creativity mode: brainstorm new ideas, alternatives, modifications. Push boundaries. Explore unconventional approaches.

**Questions:** What are alternative approaches? How could we modify this? What new ideas emerge?
**Example:** "Joint venture with local partner? Start with just Japan? Pilot program with 3 customers first? Licensing model?"

### Step 7: Blue Hat - Summarize and Decide (5-10 minutes)

Return to process control. Summarize insights from each hat. Make a decision or define next steps.

**Questions:** What did we learn? What's our decision? What are the next actions?
**Example:** "Decision: Pilot program in Japan only. Mitigates Black Hat risks while testing Yellow Hat benefits. Team: draft JV proposals (Green Hat idea)."

## Example Application

**Situation (Tech Startup):** Deciding whether to build a mobile app or focus on web-only product.

**Application:**
1. **Blue:** Goal is platform decision. Sequence: White → Red → Yellow → Black → Green → Blue.
2. **White:** 70% of users access via mobile browser. Development: mobile app = 6 months, web = 3 months. Budget: $200K available.
3. **Red:** Gut says mobile is "the future," but feel anxious about resource drain. Excitement about app store presence.
4. **Yellow:** Mobile app enables push notifications, offline mode, app store discovery, better user retention (industry: +40%).
5. **Black:** 6-month delay means competitor launches first. $200K could fund 3 web features instead. App store approval risk. Ongoing maintenance for iOS + Android.
6. **Green:** Progressive Web App (PWA)? Hybrid framework (React Native)? Mobile-optimized web first, app later?
7. **Blue:** Decision: Build PWA first (Green Hat idea). Delivers 80% of mobile benefits at web speed/cost. Revisit native app in Q3 if metrics justify.

**Outcome:** PWA launched in 3 months, achieved 35% retention boost (Yellow Hat benefit), avoided 6-month delay (Black Hat risk). Structured thinking prevented common trap of "mobile app because everyone has one."

## Anti-Patterns

- ❌ Allowing multiple hats simultaneously (defeats the purpose—everyone must wear same hat)
- ❌ Making Red Hat into justification session (should be instinctive 30-60 second gut check, not analysis)
- ❌ Skipping Black Hat to "stay positive" (pessimism phase is critical for risk identification)
- ❌ Using hats as labels for people ("John is so Black Hat"—depersonalization is the point)
- ❌ Rigid timing that cuts off valuable discussion (2-minute guideline is flexible)
- ❌ Starting with Red/Yellow before White (emotional reactions without data foundation)
- ❌ No Blue Hat facilitation (process drifts without conductor)

## Related

- pre-mortem (imagining failure—Black Hat on steroids)
- inversion (pessimistic thinking to identify risks)
- devils-advocate (designated critic role)
- second-order-thinking (Yellow + Black Hat: trace consequences)
- lateral-thinking (Green Hat creativity techniques by de Bono)
- red-team-blue-team (adversarial perspective-taking)