Sign inGet started
Skills / Thinking-frameworks

Six Thinking Hats

The need to be right all the time is the biggest bar to new ideas.

Six Thinking Hats is Edward de Bono's structured parallel-thinking framework that eliminates circular debate by guiding you through six distinct cognitive modes in sequence — facts, emotions, caution, optimism, creativity, and process control — before reaching a conclusion. Rather than everyone arguing from mixed motives simultaneously, all thinking focuses in the same direction at once: one hat at a time, until every angle is fully mapped. The result is a complete, documented analysis that separates what you know from what you feel from what could go wrong — and turns muddled discussions into clear, committed decisions.

By Edward de Bono · Free
Specimen 01 · Live diagnosisSix Thinking Hats
Input

“We're deciding whether to replace our human customer support team with an AI chatbot. It would save a lot of money but my team is split on it and I…”

Diagnosis
Blue Hat — let's frame this before we begin.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

Stop arguing in circles — think in parallel, one hat at a time

Six Thinking Hats operates on the principle of parallel thinking: instead of adversarial debate where everyone argues from different positions simultaneously, all participants explore the same cognitive dimension together before shifting to the next. Each hat is color-coded with a strictly defined, non-overlapping role: White Hat (objective facts and data gaps only), Red Hat (emotions and gut reactions, no justification required), Black Hat (critical judgment and risk identification), Yellow Hat (optimistic benefits and best-case feasibility), Green Hat (new ideas, lateral alternatives, creative possibilities), and Blue Hat (meta-process, facilitation, session framing, and synthesis). The Blue Hat opens and closes every session. De Bono prescribes distinct hat sequences for different goals: full exploration begins White→Red→Yellow→Black→Green→Blue; quick decisions follow White→Yellow→Black→Red→Blue; creative generation sessions open Blue→White→Green→Red→Yellow→Black→Blue. The sequence — not just the hats — is the core intellectual technology, ensuring no dimension is skipped and no cognitive mode contaminates another.

The problem

Most decisions fail not because people lack information, but because all modes of thinking — facts, feelings, risks, optimism, creativity — collide simultaneously. The loudest voice dominates, gut reactions go unvoiced or distort the logic, and meetings end with everyone defending positions rather than exploring the full picture. Six Thinking Hats solves this by separating the modes entirely: facts have their own protected space, emotions are explicitly welcomed rather than leaking into supposedly rational debate, and risks and benefits are examined one at a time instead of canceling each other out in real time.

The solution

Work through any decision, idea, or problem across all six cognitive dimensions — one focused mode at a time — and end with a structured analysis map that captures what you know, what you feel, what could go wrong, what the upside is, what alternatives exist, and what to do next.

You bring
  • A specific decision, problem, idea, or proposal you want to think through — the sharper the question, the sharper the session
  • Your genuine feelings, gut reactions, and hunches (especially for the Red Hat — no justification needed)
  • Domain knowledge about the facts, risks, and possibilities relevant to your situation
  • Willingness to stay inside each hat's defined mode before moving on to the next
You get
  • A recommended hat sequence matched to your stated goal — exploration, quick decision, or creative generation
  • A guided session through each hat with targeted questions calibrated to that hat's cognitive mode
  • Real-time redirection when your thinking bleeds into the wrong hat, keeping the analysis clean and trustworthy
  • A complete Six Hats Analysis Map — structured outputs from all six perspectives, plus a Blue Hat summary with conclusions and next actions
In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01The same situation, two ways
Specimens A · B
Specimen AVague
Unaided

“You're three meetings deep into a decision about restructuring your support team. Every conversation covers the same ground: your operations lead argues cost, your customer success lead argues loyalty, your CEO wants a recommendation, and you're surfacing new concerns each time without reaching any conclusion. You have data, you have opinions, you have strong feelings — all tangled together, and the meeting ends with more action items to 'gather more data' instead of a decision.”

×Vague — nothing concrete to act on.
Specimen BCalibrated
With Six Thinking Hats

“You've worked through all six hats in sequence. The White Hat revealed one critical data gap — the routine vs. complex ticket ratio — that you need before deciding, saving you from either a premature 'yes' or a premature 'no.' The Red Hat surfaced the loyalty and brand concerns that were quietly distorting every logic debate. The Black Hat named the real failure mode: not the switch itself, but making it without knowing if the AI can handle your specific ticket mix. The Yellow Hat built the full upside case. The Green Hat generated a phased pilot idea no one had proposed. The Blue Hat summary is a one-page document with the decision framing, the six-perspective map, and three concrete next actions — shareable with your board today.”

Specific, grounded, and ends with one clear next step.
Fig.02A real session, unedited
In-app · assistant
Six Thinking HatsClaude
Six Thinking Hats
Blue Hat — let's frame this before we begin. I'll start every session by putting on the process hat: its job is to define the question, set the sequence, and eventually synthesize what we find.
What is the specific decision, problem, or proposal you want to think through? The sharper the framing, the sharper the analysis. And briefly: is this a full exploration, a time-pressured decision, or a creative generation exercise? That tells me which hat sequence to recommend.
We're deciding whether to replace our human customer support team with an AI chatbot. It would save a lot of money but my team is split on it and I keep going back and forth.
Blue Hat framing: 'Should we replace our human customer support team with an AI chatbot?'
Given that the team is divided and the decision carries real stakes, I'd recommend the full exploration sequence: White → Red → Yellow → Black → Green → Blue. This is not a quick-decision situation — you need every angle before concluding.
Starting with White Hat now — pure facts and data only, no opinions, no feelings, no predictions. What do you actually know? Support volume, response times, team cost, AI tool pricing, CSAT scores. And where are the data gaps — what do you need to know that you don't yet?
We handle about 800 tickets a month. Average response time is 4 hours. Team costs $12k per month. The AI tool is $800 per month. Our CSAT is 78%. We don't actually know what percentage of tickets are routine versus complex.
White Hat captured: $11,200/month potential savings, 4-hour response baseline, 78% CSAT. One significant data gap flagged: the routine vs. complex ticket ratio is unknown — and that ratio will determine whether the AI can actually handle the volume without degrading CSAT.
Moving to Red Hat — this one works differently. No justification required here. When you imagine making this switch, what do you feel? Not the business case, not the logic — your gut reaction, your hunches, what your instincts say. What emotions have surfaced in those team conversations?
Honestly, I feel uneasy. Like we'd be abandoning customers to a machine. And there's a real loyalty concern — two of the support staff have been with us for four years.
Red Hat received — and these are important signals, not noise to override. The 'abandoning customers' feeling is telling you something about how this will land with your brand. The loyalty concern is a real execution risk: leaders who feel this way often delay or bungle the transition, which makes outcomes worse than the decision itself.
Yellow Hat now — make the strongest possible case for doing this. Best-case scenario only: what is the genuine upside if it works well?
Instant 24/7 responses, $11k per month freed up for product development, and the team could potentially move into higher-value roles rather than handling the same questions every day.
Yellow Hat: instant response, $130k/year reinvested, and a possible path to redeployment rather than elimination — which also addresses some of the Red Hat loyalty concern.
Black Hat now — rigorous caution, devil's advocate. What can realistically go wrong? Don't balance it with upside yet; this hat's job is to find the failure modes. We already know the routine/complex ratio is unknown — that's one. What else?
If the AI can't handle complex cases, customers hit a wall and escalate frustrated — possibly leaving. And we'd be giving up 78% CSAT without knowing what we'd replace it with. That number could drop badly.
Reply to Six Thinking Hats
What the skill is doing
01Hat Sequence Selection
02Guided Hat-by-Hat Facilitation
03Hat Bleed Correction
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
STSix Thinking Hatstyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
We're deciding whether to replace our human customer support team with an AI chatbot. It would save a lot of money but my team is split on it and I ke…9:14✓✓
Blue Hat — let's frame this before we begin.9:14
I'll start every session by putting on the process hat: its job is to define the question, set the sequence, and eventually synthe…9:15
What is the specific decision, problem, or proposal you want to think through?9:15
Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

Reads the situation, names the pattern, returns one concrete next move.
Delivered in seconds, inside a conversation that already exists.
Specimen · WhatsApp Business API · live
Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Hat Sequence Selection

Before the session begins, the skill identifies the right hat sequence for your goal — full exploration, quick decision, or creative generation — rather than defaulting to a one-size-fits-all order. The sequence determines which hats you visit and in what order, and it matters: evaluating risks before building the optimistic case leads to premature elimination of good ideas.

Based on de Bono's three prescribed sequences: exploration (White→Red→Yellow→Black→Green→Blue), quick decision (White→Yellow→Black→Red→Blue), and creative generation (Blue→White→Green→Red→Yellow→Black→Blue) — each optimized for a different cognitive goal.
CapabilityC-02

Guided Hat-by-Hat Facilitation

For each hat, the skill asks targeted elicitation questions calibrated to that hat's specific cognitive mode — not generic open-ended prompts, but questions designed to extract facts without opinion (White), surface gut reactions without demanding logic (Red), or generate alternatives without judgment (Green).

Mirrors the de Bono Group's facilitation training, which specifies that each hat requires a different question style to activate the correct thinking mode and prevent cognitive contamination between the six modes.
CapabilityC-03

Hat Bleed Correction

When a response drifts into the wrong cognitive mode — judgment creeping into White Hat facts, optimism undermining Black Hat rigor, new ideas surfacing during evaluation — the skill identifies the bleed and redirects it to the correct hat, naming exactly where that thought belongs.

De Bono explicitly identifies 'hat mixing' as the primary failure mode of the framework: the entire value of parallel thinking collapses if modes blur, because the point is to give each dimension its own uncontaminated space before synthesis.
CapabilityC-04

Red Hat Emotion Elicitation

The Red Hat is the most powerful and most frequently skipped mode in practice. It explicitly makes emotional reactions, hunches, and gut instincts into legitimate analytical inputs — with no justification required. The skill creates a structured space where feelings are welcomed as valid data, not overridden by logic or suppressed out of professionalism.

De Bono argues that unacknowledged emotions are the primary source of muddled thinking. The Red Hat rule is explicit: 'You do not have to give any reason or justification for your feelings.' Surfacing them legitimately prevents them from distorting the other five hats covertly.
CapabilityC-05

Six-Perspective Synthesis

At the close of the session, the Blue Hat produces a structured synthesis: a summary of what each hat surfaced, an integrated picture of the full analysis, and a recommended decision direction or next actions. This becomes a shareable, reviewable document — not just a conclusion, but a map of the reasoning that reached it.

The Blue Hat as session opener and closer is a defining architectural feature of the framework. De Bono specifies it as the 'thinking about thinking' meta-hat that owns the agenda, the pacing, and the final synthesis — the only hat that appears twice in every sequence.
Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces
OutputD-01

Six Hats Analysis Map

A structured document capturing the outputs from all six thinking perspectives in sequence — what is known (White), what is felt (Red), what the risks are (Black), what the benefits are (Yellow), what alternatives exist (Green), and the final synthesis (Blue). Reviewable, shareable, and designed to document the reasoning behind a decision, not just the outcome.

OutputD-02

Hat Session Agenda

A recommended hat sequence with framing for each mode, tailored to your specific goal — exploration, quick decision, or creative generation. Used as a pre-session orientation for yourself or shared with a team before a facilitated workshop to align everyone on the process before the content.

OutputD-03

Blue Hat Decision Summary

The closing synthesis from the Blue Hat: a concise, one-page summary of what the full session revealed, the overall picture across all six modes, what was concluded, what remains unresolved, and a clear statement of recommended next actions. Designed to be shared with stakeholders who weren't in the session.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Edward de Bono

Edward de Bono (1933–2021) was a Maltese physician, psychologist, and author who coined the term 'lateral thinking' in 1967 and wrote more than 80 books translated into 46 languages across 150 countries. He lectured at Cambridge, Oxford, London, and Harvard universities, and founded the de Bono Group to certify facilitators worldwide. Six Thinking Hats (1985) became one of the most widely deployed corporate thinking frameworks in history, adopted by IBM, Boeing, British Airways, and Siemens, and taught in executive programs across 150+ countries.

Status · Inspired by Edward de Bono’s work — not yet claimed. Are you Edward de Bono?
Primary sourceS-01

Six Thinking Hats (1985)

by Edward de Bono

Creator of 'lateral thinking'; 80+ books in 46 languages; lecturer at Cambridge, Oxford, and Harvard; Six Thinking Hats adopted by IBM, Boeing, British Airways, and Siemens.

Read the original ↗
Citationedwdebono.com
In the build queue

Be first to run it.

Six Thinking Hats is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail
At launchI have a decision my team has been debating in circles for two weeks and I want to stop arguing and actually think it through properly. Can we run a full Six Hats session?