Six Thinking Hats Retrospective: Explore Issues from Every Angle

The Six Thinking Hats retrospective applies Edward de Bono’s famous lateral thinking framework to team reflection. By systematically wearing different “thinking hats,” teams explore issues from multiple perspectives—uncovering insights that single-perspective analysis misses.

This guide shows you how to run an effective Six Thinking Hats retrospective, including when to use this powerful but time-intensive format.

What Is the Six Thinking Hats Retrospective?

The Six Thinking Hats method structures discussion by having everyone adopt the same thinking mode simultaneously. Instead of people arguing from different perspectives, everyone explores together through each lens.

Origin

Developed by Edward de Bono in 1985, the Six Thinking Hats framework was designed for decision-making and problem-solving. It works exceptionally well for retrospectives because it ensures comprehensive exploration of any topic.

Why It Works

Traditional discussions allow people to stick to their preferred thinking style:

Optimists always see the bright side
Critics always spot problems
Creatives jump to solutions
Analysts want more data

Six Hats forces everyone through all modes, creating richer, more balanced discussions.

The Six Hats Explained

Each hat represents a distinct thinking mode:

🎩 White Hat: Facts and Information

Focus: Objective data, facts, figures

In retrospectives:

What actually happened?
What are the metrics?
What do we know for certain?
What information is missing?

Example contributions:

“We completed 8 of 10 story points”
“There were 3 production incidents”
“Customer feedback score was 4.2/5”
“We don’t have data on deployment time”

❤️ Red Hat: Emotions and Feelings

Focus: Gut feelings, emotions, intuitions

In retrospectives:

How do we feel about the sprint?
What’s our intuition telling us?
What emotional reactions emerged?

Example contributions:

“I felt frustrated with the changing requirements”
“I’m proud of how we handled the incident”
“Something feels off about our velocity, but I can’t pinpoint it”
“I’m excited about the new architecture”

💡 Key insight: The Red Hat gives permission to share feelings without justification. “I feel anxious” doesn’t need data to back it up.

⚫ Black Hat: Caution and Risks

Focus: Critical thinking, potential problems, risks

In retrospectives:

What could go wrong?
What are the risks ahead?
What weaknesses exist?
Why might something fail?

Example contributions:

“Our test coverage is low in the new module”
“We might miss the deadline if requirements change again”
“The dependency on Team X is a single point of failure”
“Technical debt will slow us down eventually”

💛 Yellow Hat: Optimism and Benefits

Focus: Positive aspects, opportunities, value

In retrospectives:

What worked well?
What opportunities exist?
What value did we create?
What are the benefits of our approach?

Example contributions:

“The new CI pipeline saves hours each week”
“Customer feedback validates our direction”
“Team collaboration has never been better”
“This sprint’s learnings will help future projects”

💚 Green Hat: Creativity and Alternatives

Focus: New ideas, alternatives, possibilities

In retrospectives:

What else could we try?
What alternatives exist?
How might we do this differently?
What creative solutions come to mind?

Example contributions:

“What if we paired on all complex tasks?”
“We could try mob programming for the tricky parts”
“Maybe we should flip our sprint structure”
“Has anyone considered async standups?”

💙 Blue Hat: Process and Control

Focus: Meta-thinking, facilitation, next steps

In retrospectives:

What should we discuss?
How should we proceed?
What decisions do we need to make?
What are our action items?

Example contributions:

“Let’s spend more time on the Yellow Hat”
“We need to decide on testing strategy”
“Our action item is to create a tech debt sprint”
“Let’s revisit this topic next retrospective”

When to Use Six Thinking Hats

Best Use Cases

Complex Issues When a topic has many dimensions and simple formats don’t do it justice.

Stuck Discussions When the team keeps arguing in circles, hats force new perspectives.

Important Decisions When you need thorough analysis before deciding.

Experienced Teams Teams comfortable with retrospectives can handle this complexity.

Conflict Situations Hats depersonalize disagreements—you’re critiquing ideas (Black Hat), not people.

Best For

Attribute	Recommendation
Team size	4-10 people
Experience level	Intermediate to Advanced
Duration	60-90 minutes
Best timing	Quarterly reviews, complex issues, major decisions

When NOT to Use Six Hats

Quick sprint retros (too time-intensive)
New teams unfamiliar with retrospectives
Simple issues that don’t need deep analysis
Teams without strong facilitation

How to Run a Six Thinking Hats Retrospective

Before the Meeting

Schedule 60-90 minutes - This format takes time
Choose the topic - What will you analyze? (The sprint, a specific issue, a decision)
Prepare visuals - Display hat colors and meanings
Explain in advance - Share the framework with the team beforehand

Step-by-Step Facilitation

Step 1: Introduction (5 minutes)

Explain the framework:

“Today we’re using Six Thinking Hats. We’ll all wear the same hat at the same time, exploring our sprint from six different perspectives. This helps us think more completely and avoid getting stuck in our usual viewpoints.”

Display the hat meanings for reference throughout.

Step 2: Blue Hat Opening (5 minutes)

Start with Blue (process):

“Let’s begin with the Blue Hat. What should we focus on today? What’s most important to explore?”

Define the scope and priorities for the session.

Step 3: White Hat - Facts (10 minutes)

“Now put on your White Hat. What are the facts? What do we objectively know happened?”

Gather data and facts
Note what information is missing
No opinions yet—just facts

Step 4: Red Hat - Feelings (8 minutes)

“Switch to the Red Hat. How do you feel about the sprint? No justification needed—just feelings.”

Go around the room
Accept all feelings without debate
Look for emotional patterns

Step 5: Black Hat - Risks (10 minutes)

“Now the Black Hat. What are the risks? What could go wrong? Where are the weaknesses?”

Critical analysis
Identify problems and risks
Thorough but not personal

Step 6: Yellow Hat - Benefits (10 minutes)

“Put on the Yellow Hat. What’s working? What value have we created? What are the benefits?”

Balance the Black Hat critique
Identify positives and opportunities
Celebrate successes

Step 7: Green Hat - Ideas (12 minutes)

“Time for the Green Hat. What new ideas do you have? What alternatives should we consider?”

Creative thinking
No criticism of ideas (save for later)
Build on each other’s suggestions

Step 8: Blue Hat Closing (10 minutes)

“Back to Blue Hat. Given everything we’ve discussed, what should we do? What are our decisions and actions?”

Summarize insights from each hat
Create action items
Decide next steps

Facilitation Tips

1. Enforce Hat Discipline

If someone offers critique during Yellow Hat:

“That’s a Black Hat thought—let’s save it. Right now, we’re focusing on positives.”

2. Time-Box Strictly

Six Hats can run long. Use a timer and keep moving.

3. Make Hats Visible

Display current hat prominently. Some teams use physical colored hats or cards.

4. Sequence Matters

The suggested order works well, but you can adapt:

Start with Red Hat if emotions are high
Spend more time on Green if you need solutions
Return to hats if needed

5. Everyone Wears the Same Hat

The power comes from parallel thinking. Don’t let people stay in their comfort zone.

Six Thinking Hats Template

┌─────────────────────────────────────────────────────────────────────┐
│                    SIX THINKING HATS RETROSPECTIVE                  │
│                    Topic: [Sprint X / Issue / Decision]             │
├───────────────────┬───────────────────┬─────────────────────────────┤
│ 🎩 WHITE - Facts  │ ❤️ RED - Feelings │ ⚫ BLACK - Risks            │
│                   │                   │                             │
│ • Completed 8/10  │ • Frustrated with │ • Test coverage low         │
│   story points    │   scope changes   │ • Single point of failure   │
│ • 3 incidents     │ • Proud of launch │ • Tech debt growing         │
│ • NPS: 4.2        │ • Anxious about   │ • Team X dependency         │
│                   │   next sprint     │                             │
├───────────────────┼───────────────────┼─────────────────────────────┤
│ 💛 YELLOW - Value │ 💚 GREEN - Ideas  │ 💙 BLUE - Actions           │
│                   │                   │                             │
│ • CI pipeline     │ • Pair on complex │ • Create tech debt sprint   │
│   saves time      │   tasks           │ • Trial async standups      │
│ • Customer        │ • Try async       │ • Review in 2 weeks         │
│   feedback good   │   standups        │ • Owner: [Name]             │
│ • Team collab     │ • Mob programming │                             │
│   excellent       │                   │                             │
└───────────────────┴───────────────────┴─────────────────────────────┘

For discussion prompts that pair well with this format, see our retrospective questions guide.

Common Mistakes to Avoid

Mixing Hats

When someone offers Black Hat critique during Yellow Hat time, redirect immediately. The value comes from focused, parallel thinking.

Rushing Through

Six Hats needs time. Don’t compress it into 30 minutes—you’ll get shallow results.

Skipping Red Hat

Teams sometimes skip or minimize emotions. The Red Hat surfaces important intuitions that other hats miss.

Black Hat Dominance

Some teams spend too long on risks. Balance with equal Yellow Hat time.

No Blue Hat Closure

Without clear action items at the end, the rich discussion doesn’t translate into change.

Six Thinking Hats Variations

Focused Hats

Don’t have 90 minutes? Use only 3-4 hats relevant to your situation:

Problem exploration: White, Black, Green
Decision making: Yellow, Black, Blue
Team check-in: Red, Yellow, Blue

Hat Per Group

For larger teams:

Split into groups
Each group takes a hat
Groups present findings
Full team discusses

Written Hats

Async variation:

Assign hat timeframes (e.g., Red Hat until 2pm)
Everyone contributes to that hat’s board
Sync call to discuss and create actions

Six Thinking Hats vs Other Formats

Six Hats vs 4Ls

Aspect	Six Thinking Hats	4Ls
Perspectives	6 thinking modes	4 categories
Depth	Very deep	Moderate
Time needed	60-90 min	45-60 min
Best for	Complex issues	Regular sprints

Six Hats for complex analysis; 4Ls for regular retrospectives.

Six Hats vs Sailboat

Aspect	Six Thinking Hats	Sailboat
Metaphor	Thinking modes	Journey
Structure	Sequential phases	Parallel categories
Depth	Very thorough	Moderate
Best for	Complex decisions	Visual teams

Sailboat is simpler and more visual; Six Hats is more rigorous.

If you find Six Thinking Hats valuable, try:

Futurespective - Forward-looking analysis
Lean Coffee - Democratic deep dives
4Ls Retrospective - Simpler multi-dimensional format
Pre-Mortem Retrospective - Risk-focused (like Black Hat)

See our complete sprint retrospective formats guide for 30+ options.

Run Six Thinking Hats with RetroFlow

Most retro tools charge per user or cap free boards at 3. RetroFlow doesn’t — every feature is free, no account needed. Share a link and your team starts contributing in seconds.

Start Free Retrospective →

Retrospective Formats Retrospectives Facilitation