run-six-thinking-hats

Run Six Thinking Hats

Structure group thinking by having everyone wear the same "hat" simultaneously, separating facts, emotions, risks, benefits, creativity, and process into distinct rounds.

Why This Is Best Practice

Adopted by: IBM, Siemens, Federal Express, British Airways, ABB, Prudential, and thousands of Fortune 500 teams. de Bono's methods were formally adopted in the national curricula of the UK, Australia, and Singapore. Used by McKinsey and BCG facilitators for structured client workshops. Impact: IBM reported 75% reduction in meeting time on decisions after adopting parallel thinking. Separating thinking modes eliminates the adversarial dynamic of traditional debate — ego, status, and seniority stop corrupting the reasoning. Why best: Traditional debate is a zero-sum contest — whoever argues hardest wins, regardless of correctness. Six Hats makes every thinking role temporary and shared; no one "owns" the critical or optimistic position. The Black Hat critic and the Yellow Hat optimist are roles, not personalities — removing the identity threat that shuts down honest analysis.

Sources: Edward de Bono, "Six Thinking Hats" (1985); de Bono Group case studies (IBM, Siemens, Federal Express); adoption in national education curricula (UK, AU, SG)

The Six Hats

Hat	Mode	Question it answers
White	Facts	What do we know? What data is missing?
Red	Emotions	What is our gut feeling? What do we fear or love about this?
Black	Caution	What could go wrong? What are the risks and flaws?
Yellow	Optimism	What is the best case? What value does this create?
Green	Creativity	What alternatives exist? What new angles haven't we tried?
Blue	Process	What hat do we use next? What is the summary?

Steps

1. Assign the Blue Hat facilitator

One person wears the Blue Hat for the session. Their role:

• Define the thinking sequence before the session
• Keep each round time-boxed
• Summarize at the end and call the decision

The Blue Hat facilitator does not contribute content — only manages the process.

2. Define the question

State the decision or problem in one sentence before the session begins. Everyone must agree on the question — ambiguity here wastes every subsequent round.

Bad:  "Let's discuss the new pricing strategy."
Good: "Should we raise the enterprise tier price by 20% in Q3?"

3. Choose a hat sequence

Don't use all six hats in every session. Match the sequence to the situation:

Decision evaluation (most common): Blue → White → Yellow → Black → Green → Red → Blue

Creative problem-solving: Blue → White → Green → Yellow → Black → Red → Blue

Quick risk check (15-min version): Blue → Black → Green → Blue

Emotionally charged topic: Blue → Red (clear the air first) → White → Yellow → Black → Blue

4. Run each round in parallel

Everyone wears the same hat simultaneously — this is the core rule. No one is allowed to argue from a different hat during a round.

• White Hat round: State only facts and data. No opinions. If data is missing, note it.
• Red Hat round: Each person states their feeling in one sentence. No justification required or allowed.
• Black Hat round: List every risk, flaw, and reason it could fail. No softening.
• Yellow Hat round: List every benefit and reason it could succeed. No hedging.
• Green Hat round: Generate alternatives without judgment. Wild ideas are welcome.
• Blue Hat round (close): Facilitator summarizes, calls the decision or next action.

Time-box each round: 5–10 min for most; 3 min for Red Hat.

5. Blue Hat close — summary and decision

The facilitator summarizes each hat's output in 1–2 sentences and states:

• The decision reached, OR
• The next action required before a decision is possible

Write the summary where the team can see it. Do not leave the room without a documented output.

Rules

• Parallel, not sequential: Everyone wears the same hat at the same time. Never let one person argue from Black while another argues from Yellow — that's traditional debate.
• Red Hat needs no justification: The rule "no justification required" is not optional. Requiring people to defend their intuition kills the Red Hat's diagnostic value.
• Black Hat is not pessimism: Black Hat is caution — it evaluates risk objectively. A good Black Hat round is not an attack on the idea; it is a stress test.
• Facilitator stays neutral: The Blue Hat facilitator does not contribute content opinions. If they have a view, they must explicitly remove the Blue Hat, contribute, then put it back.
• Don't use all six hats every time: A full six-hat session takes 60–90 min. Use abbreviated sequences (2–3 hats) for smaller decisions.

Common Mistakes

Mixing hats mid-round. Someone in a Yellow Hat round says "but what about the risk of…" — this is Black Hat thinking. Redirect immediately: "Black Hat concerns go in the Black Hat round."

Skipping Red Hat. Teams skip it because it feels soft. Red Hat surfaces the emotional undercurrent that will kill implementation even if the logic is sound. Don't skip it.

Using Black Hat as veto power. Black Hat identifies risks — it does not decide. A long Black Hat list does not automatically reject the proposal; Green Hat generates mitigations.

No Blue Hat close. The session produces rich input but no decision. Always end with a documented Blue Hat summary. Input without output is just a meeting.

When NOT to Use

• Individual decisions: Six Hats is a group tool. For solo thinking, use the hats as a personal checklist, not a facilitated session.
• Crisis requiring immediate action: No time for structured rounds — decide and act, debrief later.
• Already-decided topics: If leadership has already decided and is seeking buy-in, Six Hats surfaces honest dissent that may not be actionable. Be transparent about whether the decision is genuinely open.
• Teams unfamiliar with the method: Run a 20-min orientation first — cold introduction during a high-stakes decision fails.