Developed by Edward de Bono (Six Thinking Hats, 1985).
A group thinks in one mode at a time (facts, feelings, risks, benefits, new ideas, and process), each marked by a colored hat, so argument gives way to parallel thinking.
One proposal to close a branch office, thought through one hat at a time
The six hats in the order the group wore them, everyone in the same hat at once. Select a hat to see the only kind of thinking it allowed, what went on the board, and what that hat caught that the others would have missed. Illustrative.
White hat
- Thinks only about
- Facts and gaps
- What went on the board
- The branch brings in $2.1 million a year, its lease ends in March, nine of its twelve staff live nearer the branch than the main office, and about a third of its clients visit in person each year.
- What this hat caught
- A hole in the data: no one knew how many walk-in clients would follow the staff to the main office.
Red hat
- Thinks only about
- Feelings, unexplained
- What went on the board
- Two managers felt the decision had already been made. The branch head felt it as a verdict on her team. One partner felt relief.
- What this hat caught
- The sense that the meeting was for show, which would have turned every later point into a fight.
Yellow hat
- Thinks only about
- Benefits
- What went on the board
- It saves $310,000 a year in rent and puts the branch's two farm specialists next to the commercial team.
- What this hat caught
- A gain no one had counted: the specialists and the commercial team sell to many of the same farm owners.
Black hat
- Thinks only about
- Risks
- What went on the board
- Long-standing farm clients may move to a local rival, and three staff may leave over a forty-minute commute.
- What this hat caught
- That the risk sits in one group of clients, the farm accounts, and not across the whole book.
Green hat
- Thinks only about
- New ideas
- What went on the board
- Keep a desk two days a week in the town library. Let the three longest commuters work from home. Call the top forty farm clients before any announcement.
- What this hat caught
- A middle course that keeps the face-to-face visits without keeping the lease.
Blue hat
- Thinks only about
- The process
- What went on the board
- Close the branch in March, open the part-time desk, have the branch head call the top forty farm clients first, and check client retention in six months.
- What this hat caught
- The decision, an owner for each step, and the date to look again.
An example
The partners of a regional insurance broker had argued twice about closing their smallest branch, and both meetings ended the same way: the finance partner listing savings, the branch head defending her team, and nobody moving. The managing partner ran the third meeting under the hats, with everyone in the same hat at the same time and ten minutes per hat.
Under the white hat the group listed facts and found a gap: nobody knew how many walk-in clients would follow. Under the red hat two managers said they felt the decision was already made, which explained the earlier stalemates. Yellow found a benefit nobody had counted, putting the farm specialists next to the commercial team. Black placed the risk in one group, the long-standing farm accounts. Green produced a middle course, a desk two days a week in the town library. The blue hat closed the meeting with a decision: close the branch in March, open the part-time desk, call the top forty farm clients first, and check retention in six months.
Why it works
Most meetings ask people to do several kinds of thinking at once, and they sort themselves into roles: one person attacks, another defends, another worries out loud. Each then argues to protect a position, and the group spends its time on the contest. Putting everyone in the same mode at the same time removes the contest. When the whole room looks for risks together, the critic has nothing to win, and when the whole room looks for benefits, the skeptic has to find some too. Each mode also gets its own turn, so the kinds of thinking a group tends to skip, such as feelings stated without justification or ideas nobody has tested, get heard instead of leaking into the argument. The blue hat keeps the session pointed at a decision.
The thinking behind it
Edward de Bono Edward de Bono, a Maltese physician and writer who coined the term lateral thinking, set out the method in Six Thinking Hats (1985). Each colored hat stands for one kind of thinking, and a group wears one hat at a time, which he called parallel thinking. His tools, among them the CoRT lessons, were built for schools and business and were more concerned with usefulness than with tests of their effect. A review of 42 thinking frameworks by Moseley and colleagues found sparse evidence that training in Six Thinking Hats improves thinking in general; its case rests on usefulness in the room.
How to run it
- Frame one question. Write the decision as a single question everyone can see, such as whether to close the branch in March.
- Set the order of hats. Start with blue to agree on the order, then pick a sequence that suits the question; a decision often runs white, red, yellow, black, green, blue.
- Put everyone in the same hat. For each hat, the whole group thinks only in that mode, including the people who usually play the opposite part.
- Keep each hat short. Give each hat a set time, two minutes for red and ten or so for the others, so no mode turns into a debate.
- Write each hat's output separately. Record the facts, feelings, benefits, risks, and ideas in their own columns on the board.
- Close with the blue hat. Sum up what each hat produced, make the decision or name what is missing, and assign the next steps.
Where it goes wrong
The first failure is hats as labels for people. When the finance partner is always the black hat, the meeting is the old argument with costumes, so rotate the whole group through every hat. The second is skipping the red hat because feelings seem unprofessional. Unspoken feelings still steer the outcome; two minutes of them, stated without justification, costs less than a meeting derailed by them later. The third is running the hats and deciding nothing. If the session ends without a blue-hat summary, owners, and a date, it was a well-mannered discussion, so reserve the last ten minutes for blue before starting.
When to use something else
- Plus, Minus, Interesting. When one person needs a quick, structured look at an idea's pluses, minuses, and open questions.
- Red Teaming. When the stakes are high enough to give a separate team the job of breaking the plan.
- Nominal Group Technique. When the problem is that a few voices dominate and the group needs ideas written and ranked in silence.
Where it sits in SOLVE eX
Go to the source
- Six Thinking Hats, Little, Brown, 1985