Six Thinking Hats: a structured approach to decisions and creative thinking

What is the Six Thinking Hats method?

The Six Thinking Hats is a group thinking method created by Edward de Bono that asks everyone in a meeting to look at a topic from the same angle at the same time. He called this "parallel thinking" instead of arguing from different points of view, the whole group thinks in one mode, then switches together to the next.

Each hat stands for a different mode of thinking:

• White: Facts and information

• Red: emotions and gut feelings

• Black: caution and risks

• Yellow: optimism and benefits

• Green: creativity and new ideas

• Blue: managing the thinking process

It helps to know what the Six Thinking Hats method is not. It is not a personality test. It is not a permanent role. No one is "the critical person" or "the creative person" — everyone wears every hat during a session.

De Bono introduced the method in his 1985 book of the same name, and teams in business, schools and government have used it ever since. The core idea is simple: when you separate thinking types into clear phases, you eliminate the conflict that arises when people argue from different mental modes simultaneously.

When should you use Six Hat Thinking in decision-making?

The 6 hat thinking method works best when a group has to look at a problem from many angles before committing to an answer. It is less useful for quick, solo, or routine choices.

You will get the most value from the method in situations like these:

• Strategic planning sessions: When your team has to weigh long-term direction

• Complex problem-solving: when there is no obvious answer and you need creative options.

• High-stakes decisions: when the cost of getting it wrong is high.

• Conflict resolution: when team members hold opposing views and need neutral ground.

• Innovation and brainstorming: when you want creative ideas followed by honest evaluation.

• Post-mortems and retrospectives: when you want to analyze what went wrong without blame.

Skip the method for routine decisions, time-sensitive emergencies, or work you can finish on your own. Running a full session takes time, so save it for choices that are worth that effort.

The six hats of thinking and what each one does

Each of the six hats represents a mode of thinking, and the method's power comes from everyone wearing the same hat at the same time. The hats of thinking — sometimes called the de Bono hats — represent the main ways people approach problems.

Here is what each of the six hats does, with a short example you can picture.

White hat thinking

White hat thinking is the facts and information mode. When you wear the white hat, you focus on what is known, what data is missing, and what you still need to find out.

White hat thinking asks:

• What facts do we have?

• What data is missing?

• What do we need to find out?

The output is a list of verifiable facts, figures, and gaps — not opinions. In a product launch decision, white hat thinking gathers customer research, sales data, and competitor pricing.

Red hat thinking

Red Hat thinking is the emotions and intuition mode. The red thinking hat gives people permission to share feelings and gut reactions without having to explain them.

The red hat asks:

• How do I feel about this right now?

• What is my gut reaction?

• What emotions does this trigger?

Red hat time is short — usually one or two minutes — and no justification is required. A teammate might say they feel nervous about a tight deadline or excited about a new feature, and that is enough.

Black hat thinking

Black hat thinking is the cautious, risk-averse mode. A black hat thinker looks for problems, risks, and weaknesses before they become real.

The black hat asks:

• What could go wrong?

• What are the risks?

• Why might this not work?

It is protective, and it helps your team avoid costly mistakes. For a product launch, black hat thinking surfaces supply chain risks, customer objections and any regulatory hurdles.

Yellow hat thinking

Yellow hat thinking is the optimistic, benefits-focused mode. When you wear the yellow hat, you look at value, advantages, and positive outcomes — but you have to keep it realistic.

The yellow hat asks:

• What are the benefits?

• Why would this work?

• What value does this create?

For the same product launch, yellow hat thinking would point out how the launch could win market share, strengthen the brand and open new revenue streams.

Green hat thinking

Green hat thinking is the creative mode. The green hat in the six thinking hats is when the group generates new ideas and alternatives without judging them yet.

The green hat asks:

• What other approaches could we try?

• What new ideas can we generate?

• How else could we solve this?

During green hat time, criticism is paused so ideas can flow. For a product launch, green hat thinking might surface unusual marketing channels, partnership ideas or new pricing models.

Blue hat thinking

Blue hat thinking is the process control mode. The blue thinking hat manages the session itself — setting the agenda, summarizing, and choosing which hat comes next.

Thinking hats blue asks:

• What is our goal for this session?

• Which hat should we use next?

• What have we learned so far?

The facilitator usually wears the blue hat, but anyone in the group can call for it if the discussion drifts. Blue hat thinking opens a session by defining the question and closes it by summarizing the decisions.

Here is a quick reference table:

Step-by-step guide to running a de Bono six thinking hats session

A good Edward de Bono Six Thinking Hats session takes a bit of prep. De Bono's Six Thinking Hats approach works when the facilitator plans the question, the order, and the method of capture before anyone walks in.

1. Define the question

Start with a clear question. Write it in specific, action-oriented terms — not "Should we grow?" but "Should we launch Product X in Q2?" Share the question with participants in advance so they arrive ready to think. Put it at the center of your mind map so it stays visible throughout the session.

2. Set the hat sequence and timing

Next, decide which hats to use and in what order. The most common sequence is Blue (opening) → White → Green → Yellow → Black → Red → Blue (closing), but you can adjust to fit the decision.

Not every session needs all six hats. For a risk review, you might use only white and black. Set time limits for each hat — usually five to 15 minutes, except red hat, which stays at one or two minutes. Shorter times suit small groups; longer times suit complex topics.

3. Capture inputs visually

As the group talks, capture each hat's ideas in a separate branch of a mind map. One person — the facilitator or a note-taker — adds points as people share them. Visual capture keeps thinking visible and prevents the same idea from being repeated.

4. Review and decide

Once you have worked through the hats, switch back to blue hat thinking. Summarize what came up under each hat, then look for patterns, conflicts or gaps. Use that full picture to guide the group to a decision or a next step, and share the final map so everyone can refer back to it.

Mind mapping each hat in MindMeister using the Six Thinking Hats method

A mind map fits this method naturally. Each hat gets its own branch, so ideas stay grouped by perspective instead of mixed together in a long list.

Structure the map around three layers:

• Central topic: the decision or problem you are exploring

• Six main branches: one for each hat

• Sub-branches: the questions and inputs captured under each hat

Working this way gives your team a few practical advantages:

• Visual separation: each hat's thinking stays distinct and easy to scan

• Real-time collaboration: teammates can add ideas at the same time, even when remote

• Permanent record: the map can be revisited weeks later

• Easy sharing: send the map link to stakeholders who were not in the session

To put the Six Thinking Hats method to work:

1. Open a blank mind map and place your specific question or decision at the center.

2. Add six main branches, one for each hat.

3. As you move through each hat, add sub-branches under that section.

4. Use notes, links or attachments to add context to specific ideas.

Create one map per session rather than reusing the same map for several decisions. A fresh map per decision keeps the thinking focused and makes results easier to share.

Worked example: solving a product launch with the six hats model

To see the Six Thinking Hats model in action, consider a real question: "Should we launch our new project management feature in March or wait until June?" Here is how a team might work through the six hats model in 60 minutes.

Blue hat (opening): The facilitator defines the question and sets the agenda. The team agrees to use the sequence White → Green → Yellow → Black → Red → Blue (closing).

White hat (facts):

• The feature is 80% complete

• Beta testing scheduled for February

• Competitor launched a similar feature in January

• More than 200 customer requests in the past six months

• Marketing budget available: $50,000

• Engineering capacity: three engineers through March, two in April

Green hat (alternatives):

• Launch core features in March, add advanced features in June

• Launch in beta to select customers in March, full launch in June

• Wait until June and run a pre-launch campaign starting in March

• Partner with a complementary tool to speed up development

Yellow hat (benefits of a March launch):

• First-mover advantage over the competitor

• Revenue starts three months sooner

• Customer satisfaction improves earlier

• Morale boost from shipping

Black hat (risks of a March launch):

• Incomplete testing could lead to bugs

• Marketing may not have enough time to prepare

• The support team needs four weeks of training

• A rushed launch could hurt the brand

Red hat (gut reactions):

• Excitement about beating the competitor

• Anxiety about quality

• Confidence in the core feature set

• Concern about support readiness

Blue hat (closing): The facilitator summarizes the discussion. The team decides to launch core features to beta customers in March, with a full launch in June. Next steps: finalize the beta customer list, begin support training now and set aside extra budget for post-launch fixes.

In the map, the question sits at the center and six branches radiate out, one per hat, each filled with the points above as sub-branches. The map becomes the record of the decision and the thinking behind it.

Tips to help you get more done in Thinking Hats meetings

Facilitation makes or breaks a session. The method is simple, but it relies on the facilitator to keep the group disciplined and the thinking visible.

A few tips that help:

• Enforce the hat discipline: Do not let people jump between hats or argue from different modes at once.

• Keep time limits visible: use a timer and announce when hat time is ending.

• Capture everything without filtering: even obvious ideas belong on the map.

• Do not skip red hat: feelings are data, and suppressing them creates resentment.

• Use blue hat to reset: if the group drifts, pause and refocus with blue hat thinking.

• Rotate facilitation: different facilitators bring different strengths, so swap the blue hat role across sessions.

Common pitfalls and how to avoid them

Even with a clear process, teams run into the same mistakes. Watch out for these:

• Skipping hats: Some teams skip the black hat to "stay positive" or skip the red hat to "be rational." Every hat serves a purpose.

• Letting one person dominate: make sure everyone contributes under each hat, not just the loudest voices.

• Treating hats as personality types: everyone wears every hat. No one is "the black hat person."

• Rushing through hats: give white and black hats especially enough time for real exploration.

• Failing to capture thinking: if ideas are not written on a shared map, they will be forgotten or misremembered.

• Using the method for every decision: save it for decisions that are worth the time.

Beyond six thinking hats: comparing other decision tools

Six Thinking Hats is one of several decision-making methods, and it suits some situations better than others. The table below compares it with other common frameworks.

These methods are not mutually exclusive. Six hats decision-making often pairs well with the others — you might run a SWOT analysis to gather white hat facts, then use Six Thinking Hats to work out what the data means and what to do about it.

Start your own Six Thinking Hats session

Six Thinking Hats gives your team a clear way to think together, reduces conflict, and leads to better decisions. The hardest part is usually getting started, which is where a mind map helps.

Open MindMeister and create your own mindmap, with a branch for each hat. From there, you can:

1. Add a central topic for your decision or question.

2. Create six branches, one for each hat.

3. Share the map with your team for real-time collaboration.