Six thinking hats: a practical guide for workplace decisions

Some meetings get stuck because people are doing different kinds of thinking at the same time. One colleague offers an idea, another raises a risk, someone else asks for data and a fourth explains why the proposal feels wrong. Each contribution may matter, but the conversation becomes an argument about whose approach is most legitimate.

Edward de Bono's Six Thinking Hats offers a way to separate these modes. Rather than dividing the team into optimists, critics and creative people, the group deliberately looks at the same question through one lens at a time.

This guide explains the six hats, how to facilitate a session and how to turn the discussion into a practical next step. It is an independent introduction, not official de Bono training or an endorsement of WorkplaceHero by the method's owners.

What are the six thinking hats?

The hats are six prompts for different kinds of thinking. You do not need physical hats. A written agenda or a visible label is enough to identify the current mode.

According to the official Six Thinking Hats summary, the six modes are:

The colours describe thinking modes, not personality types, job roles or competence. Calling someone "the black hat person" misses the point. Everyone should have an opportunity to contribute information, possibilities, concerns and reactions.

What does parallel thinking mean?

In a typical debate, people defend different positions. Parallel thinking asks participants to explore the same aspect together before moving to the next.

During a green-hat section, everyone helps generate alternatives. They do not immediately reject an idea because it may be expensive. That concern is captured for the later black-hat discussion. During black-hat thinking, even the strongest supporter of an idea helps identify weaknesses.

This does not mean avoiding disagreement. It changes the sequence so that criticism, evidence and creativity each receive deliberate attention. Participants can still reach different conclusions at the end.

There is no universal sequence that fits every problem. The blue-hat role chooses the process and adjusts it when the group needs clarification. A meeting focused on an urgent incident will need a different structure from one exploring a new service.

The white hat: establish information and gaps

White-hat thinking separates evidence from interpretation. Ask what happened, what was measured, where the information came from and what remains unknown.

For example, "The new process is frustrating" is a judgement. "Eight of the twelve people interviewed said they entered the same information twice" is information about reported experience. "The process causes all delays" is a causal claim that needs investigation.

Keep a visible distinction between confirmed facts, estimates and unanswered questions. It is acceptable to say that something important is not yet known.

Useful prompts include: What would change our understanding? Whose experience have we not heard? Is the data current? Are we treating a small sample as representative of everyone?

The white hat should not become an excuse to demand impossible certainty. The task is to establish what evidence is sufficient for the decision and what uncertainty will remain.

The red hat: acknowledge reactions

Red-hat thinking gives people a bounded opportunity to express feelings and intuition without having to construct an immediate argument.

Someone might say, "I am uneasy about the speed of this change," or, "I feel relieved by the idea of one simpler process." These reactions are relevant because decisions affect people, but they are not automatically evidence that a proposal is right or wrong.

Do not pressure people to disclose personal experiences. Allow a pass, written input or a brief private contribution to the facilitator. A team meeting is not a therapy session.

Capture the reaction without turning it into a claim about colleagues' motives. "I am worried about losing flexibility" is useful. "Anyone who supports this does not care about staff" shuts down discussion.

The black hat: examine risks constructively

Black-hat thinking asks where a proposal could fail, what assumptions are fragile and which constraints matter. It is disciplined caution, not an invitation to be hostile.

Make concerns specific. "This will never work" gives the team little to investigate. "The current rota leaves no cover for a two-hour session" identifies a practical barrier.

Distinguish a risk from a mandatory condition. A manageable delay may be a risk to mitigate. A breach of a legal obligation is not simply a downside to outweigh with benefits.

Ask what would prevent the failure, how likely it appears and what evidence supports the concern. Where consequences are serious, involve the appropriate specialist rather than treating a brainstorm as a formal risk assessment.

The yellow hat: look for credible value

Yellow-hat thinking explores benefits and the conditions under which an idea could succeed. It is not forced positivity.

For a new handover process, a potential benefit might be fewer repeated questions between shifts. The team should ask what would need to be true for that benefit to occur: information must be current, concise and easy for the next shift to access.

Encourage people who are sceptical to identify at least one plausible advantage. Similarly, ask enthusiastic participants to explain the mechanism rather than promising a vague improvement in morale or productivity.

Use conditional language where appropriate: "This could reduce duplicate entry if the systems connect." That is more useful than treating every hoped-for benefit as a guaranteed outcome.

The green hat: develop alternatives

Green-hat thinking opens the option set. Ask how the problem could be approached differently, what a smaller experiment would look like and whether an assumption can be challenged.

Separate generating ideas from selecting them. Capture several possibilities before evaluating. Allow quiet writing before discussion so that quick speakers do not define the whole shortlist.

If ideas stall, use SCAMPER. Could you substitute a step, combine two tasks, adapt an approach from another team or eliminate work that does not add value?

Creativity still has boundaries. A novel proposal is not permission to bypass safety, confidentiality or employment obligations. Capture the idea and examine those conditions before any pilot.

The blue hat: manage the conversation

Blue-hat thinking frames the task, names the current mode and closes with a decision or a clear next step. The facilitator is responsible for the process, not automatically entitled to decide the outcome.

At the start, state the question and who has decision authority. During the session, redirect contributions gently: "That is an important risk. I will record it for black-hat thinking; for now we are generating options."

At the end, distinguish agreement from unresolved disagreement. Summarise what the group knows, which options remain, what needs investigation and who will act.

If the group is not ready to decide, say so. A useful meeting can end with an evidence-gathering task rather than an artificial consensus.

A fictional workplace example: improving shift handovers

A customer-service manager wants to reduce problems at shift changes. They frame the question as: "What should we test to make handovers clearer without adding unnecessary administration?"

White-hat discussion identifies repeated queries and missing ownership on some tasks. It also reveals that the team has not measured the time spent on handovers. Under the red hat, colleagues express frustration about chasing updates and concern about another form to complete.

Green-hat thinking produces three options: a shorter shared checklist, a five-minute overlap between shifts and a single queue that clearly shows task ownership. Yellow-hat thinking identifies potential continuity benefits. Black-hat thinking reveals staffing constraints, access permissions and a risk that a checklist becomes a duplicate record.

The blue-hat conclusion is a two-week checklist pilot on one shift, with an owner and feedback from both outgoing and incoming colleagues. The group will review missing information and administration time before widening the test.

Nothing in this example establishes that the method caused an improvement. It shows how the hats can organise a discussion that leads to a testable next step.

A practical session agenda

For a non-urgent team decision, you could try this illustrative 35-minute agenda:

1. Blue: define the question, boundaries and decision owner, 3 minutes.
2. White: review information and gaps, 6 minutes.
3. Green: generate possible approaches, 7 minutes.
4. Yellow: explore potential value, 4 minutes.
5. Black: examine risks and conditions, 6 minutes.
6. Red: capture immediate reactions, 3 minutes.
7. Blue: summarise actions and review arrangements, 6 minutes.

These timings are a practical suggestion, not an official prescribed sequence. Change them to suit the problem and the group's needs. If evidence is disputed, return to white-hat thinking rather than rushing through the agenda.

Common facilitation mistakes

Assigning permanent hats to people reinforces stereotypes and prevents balanced participation. Using the black hat as a label for a difficult colleague is particularly unhelpful.

Another mistake is suppressing urgent concerns in the name of the sequence. If someone identifies an immediate safety issue, pause and address it. The method serves the work; the work does not serve the method.

Avoid claiming the hats remove bias. They may help you notice neglected perspectives, but assumptions, power differences and group pressure can still affect the conversation. Anonymous input and independent scoring may be needed alongside the method.

Finally, do not end with a colourful collection of notes and no ownership. A decision matrix can help compare the remaining options, but someone must still decide and explain the reasoning.

Reflection and further reading

Ask which mode your team normally overuses, which contribution changed your understanding and whether quieter colleagues were heard. Try one change in your next meeting and review the difference.

For related tools, read the ten problem-solving and decision-making techniques and the pros-and-cons guide.

• de Bono: official Six Thinking Hats summary
• de Bono: official website

Use the official resources for authorised training. This article summarises the method in original language and does not reproduce official course materials.