Six Thinking Hats

Based on Edward de Bono's method, this format has the team look at the sprint through six distinct mindsets. Each hat directs attention to one angle — facts, feelings, caution, optimism, creativity and process — so the discussion stays balanced and no perspective is missed. It's a powerful way to break out of habitual thinking and explore an issue from every side.
Green Hat

Creativity: alternatives and ideas, no judgement yet

Roman

Roman

What if support triaged bugs before they reach the board?
Maria

Maria

We could ship the export as a scheduled email instead
Blue Hat

Process: what this discussion is for and what stays out of it

Anna

Anna

Fifteen minutes per hat, facts before opinions
Daria

Daria

Park the roadmap debate — today is about the last sprint
White Hat

Facts: numbers and observations, no interpretation

Maria

Maria

Review took 2.1 days on average, up from 0.9
Kirill

Kirill

Four of seven tickets rolled over
Red Hat

Feelings: gut reactions, no justification required

Daria

Daria

The scope change on Friday felt disrespectful
Roman

Roman

Relief that the outage was handled without blame
Black Hat

Caution: risks and what could go wrong

Kirill

Kirill

One person owns billing — if they are out, we stop
Anna

Anna

The peak season plan assumes headcount we do not have
Yellow Hat

Benefits: value and what already works

Roman

Roman

Even with rollovers, the migration risk is behind us
Maria

Maria

The new pipeline already saves an hour a day

What is the Six Thinking Hats retrospective?

The Six Thinking Hats retrospective adapts Edward de Bono's classic thinking framework into a structured team reflection. Instead of arguing from fixed positions, everyone "wears" the same hat at the same time, exploring a topic from one angle before moving to the next. This parallel thinking reduces conflict, ensures every dimension gets attention, and is especially powerful for complex decisions, post-incident reviews, or sprints that triggered strong opinions. The format uses six columns, one per hat:

  • White Hat — facts and data.
  • Red Hat — emotions and gut feelings.
  • Black Hat — risks and caution.
  • Yellow Hat — benefits and optimism.
  • Green Hat — creativity and new ideas.
  • Blue Hat — process and next steps.

White Hat

The White Hat is about objective information: what actually happened, the metrics, and the facts everyone agrees on. Keep opinions out — record only data, so the discussion starts from shared reality.

Red Hat

The Red Hat invites honest emotions and intuition without justification. How did the sprint feel? What gut reactions came up? Naming feelings openly prevents them from leaking into the rest of the conversation.

Black Hat

The Black Hat is the voice of caution: risks, weaknesses, and reasons something might fail. Used deliberately, it is critical thinking, not negativity — it helps the team spot problems before they bite.

Yellow Hat

The Yellow Hat focuses on the positives: benefits, opportunities, and reasons for optimism. It balances the Black Hat and reminds the team of the value in what they are doing.

Green Hat

The Green Hat is for creativity: new ideas, alternatives, and experiments. There are no bad suggestions here — quantity and imagination matter more than feasibility.

Blue Hat

The Blue Hat manages the process itself: summaries, decisions, and next steps. It is usually worn by the facilitator at the start to set the agenda and at the end to capture outcomes.

Benefits of the Six Thinking Hats retrospective

  • Examines a topic from six complementary angles.
  • Reduces conflict by aligning everyone's thinking mode.
  • Gives equal space to facts, feelings, and creativity.
  • Surfaces both risks and opportunities deliberately.
  • Works well for complex or emotionally charged topics.
  • Produces well-rounded, defensible decisions.

How to run a Six Thinking Hats retrospective

  1. Create a board in QRetro from the Six Thinking Hats template and invite your team.
  2. Put on the Blue Hat to frame the topic and explain how each hat works.
  3. Move through the hats together, spending a few minutes adding cards to one column at a time.
  4. Read each hat's column aloud before switching to the next perspective.
  5. Return to the Blue Hat to summarize insights and agree on next steps.
  6. Assign owners to the actions and save the board for reference.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
Post Mortem Retro
A reflective format for looking back on a finished project or major milestone. The team gathers what it liked, what it missed, what individuals learned and what to do differently next time, closing with appreciations. The wider lens makes it ideal for drawing lasting lessons rather than tweaking the last sprint.
Rose Bud Thorn
A gentle, well-balanced format that gives equal weight to the good, the painful and the promising. The rose marks what went well, the thorn what hurt or got in the way, and the bud what shows potential and is worth nurturing. Including the bud keeps the conversation forward-looking instead of dwelling only on the past.
Hopes and Fears
A forward-looking format best used at the start of a project, quarter or initiative. The team shares its hopes for what could go right alongside its fears about what might go wrong. Naming both early builds shared understanding and surfaces risks while there's still time to act on them.
Good Bad Better Best
A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.
Likes / Wishes / Wonders
A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.
OKR Template
A goal-focused format that ties reflection to objectives and key results. The team reviews its objectives, examines the key results that measure progress and aligns on the initiatives that will drive them forward. It's a strong choice for connecting day-to-day retrospectives with the bigger goals the team is accountable for.
Try Template