Ask a design team how their critique sessions feel and the honest answers cluster at two extremes. Some sessions drift into open debate where the loudest opinion wins and the work barely improves. Others stay so carefully polite that nothing of substance gets said. Both patterns waste the one resource a small studio cannot spare: focused time together in front of the work. The work needs criticism to improve, but unmanaged criticism costs more than it returns.
The six thinking hats method fixes this by structuring the design critique itself. Developed by Edward de Bono, it assigns six modes of thinking, each represented by a coloured hat, and has the whole group adopt the same mode at the same time. This parallel thinking keeps feedback balanced and focused, separating facts from feelings and risks from ideas, in sessions of 60 to 90 minutes.
What Is the Six Thinking Hats Method?
Edward de Bono introduced the six thinking hats technique in his 1985 book of the same name, as an antidote to adversarial discussion. Instead of arguing positions, a group thinks in parallel: everyone examines the work from one perspective at a time, signalled by a metaphorical coloured hat.
- The White Hat deals in facts and objective data.
- The Yellow Hat looks for benefits and reasons for optimism.
- The Black Hat surfaces risks, gaps and potential failures.
- The Red Hat gives emotion and gut feeling a legitimate voice.
- The Green Hat pushes for alternatives and creative directions.
- The Blue Hat manages the process itself, opening and closing the session.
Applied to a design critique, the hats do quietly radical work: they separate the reviewer from the review. Feedback stops being about who said what and becomes about which mode of thinking produced it, which is exactly what makes criticism easier to give and easier to receive. Where the laws of UX describe how people perceive and decide inside an interface, this method governs how the team behind the interface talks.
How to Run a Six Thinking Hats Design Critique
A session needs a timebox of 60 to 90 minutes, a facilitator, the designs under review, and somewhere to capture feedback: sticky notes in a room, or a shared FigJam board for remote teams. The structure matters more than the setting. From there, four steps.
1. Share the Work Before the Session
Circulate the designs at least a day ahead, with a short note on what stage the work is at and what kind of feedback is useful. Reviewers arrive with considered observations instead of first reactions, and the session starts at depth rather than working slowly towards it. Nielsen Norman Group's research on critique culture reaches the same conclusion: critiques succeed or fail on preparation and facilitation.
2. Assign the Hats and Agree the Sequence
The whole group can wear the same hat simultaneously, which preserves parallel thinking, or each person can hold one hat for the session. For critique, the shared sequence works best: open with the Blue Hat to set scope, then White, Yellow, Black, Red and Green, before the Blue Hat closes. Agreeing the order up front removes the negotiation that usually eats the first twenty minutes.
3. Move Through the Hats Together
Timebox each hat, keep feedback to one observation per note, and group the notes by hat colour so the session produces a visual record of the discussion. The facilitator's job is keeping modes clean: a risk raised during the Yellow Hat gets parked until the Black Hat's turn. The studio's free FigJam Six Thinking Hats template, covered in more detail below, lays this structure out ready to run.
4. Close With the Blue Hat and Capture Actions
The Blue Hat ends the session by turning notes into decisions: what changes, who owns it, what gets tested. Feedback that never becomes an action decays into opinion. Deciding which feedback deserves action is its own discipline; opportunity mapping gives teams a way to choose outcomes over outputs when the list is long.
Free Six Thinking Hats Design Critique Template
The free design critique template on Figma Community gives the method a ready-made home: one FigJam section per hat in the agreed sequence, a Blue Hat frame to open and close the session, and space to group notes by colour as the discussion moves. It doubles as a six thinking hats worksheet for teams who prefer to print and pin, and needs nothing beyond duplicating the file and dropping in the designs under review.
What Changes When Critique Has Structure
The first change is balance. Every design gets examined for facts, upside, risk, feeling and alternatives, in that order, every time, so no single register dominates. The second is psychological safety: the Black Hat criticises, not the person wearing it, and reviewers who would otherwise stay quiet contribute because the structure asks them to. The third is speed, since disagreement that is organised resolves faster than disagreement that is suppressed, for the same reason structured communication persuades where scattered argument cannot.
I first used the method to rescue the feedback culture of a product team I worked with earlier in my career, where sessions had drifted into unstructured video calls, tired faces and too many wireframes at once. Reviewing designs in advance and walking through the hats together turned the most dreaded meeting of the week into the most productive one.
Where Six Thinking Hats Critiques Go Wrong
Three failure patterns show up repeatedly. The first is skipping preparation: a group seeing the work for the first time produces surface reactions dressed up as structured feedback, whatever hats they wear.
The second is treating the hats as personalities rather than a sequence. Nobody should be the resident Black Hat; the entire point is that everyone criticises during the Black Hat's turn and everyone imagines alternatives during the Green Hat's. Fixed roles quietly rebuild the adversarial dynamic the method exists to dissolve.
The third is running the session without a working Blue Hat. Without facilitation the modes blur and the critique reverts to open debate; without a closing pass, nothing gets captured and the session evaporates. If only one hat gets your full attention, make it this one.
Which Hat Should Your Team Try First?
The Blue Hat, because structure is the whole argument of the six thinking hats method and the Blue Hat carries it. Start with a single critique session: circulate the work a day early, agree the sequence, timebox each hat, close with actions. One well-run session is usually enough to convince a sceptical team, because the difference is felt immediately: the same people and the same work, producing a different quality of conversation. From there the method earns a permanent place in a product design process rather than being imposed on one.
At Krueger Design, Manuel Krueger holds a certified UX Design qualification (2022) and a HubSpot Academy SEO certification, applied in hands-on work for teams whose products depend on honest critique: UX research for the Phāea resort group, client work for Noble Co. and Testlio, and an ongoing research partnership with Userlytics. The process stays consistent: a method earns its place by changing how a team works, not by decorating a workshop agenda.
Curious what structured critique could do for your product? Try the free FigJam Six Thinking Hats template, or book a free 30-minute discovery call.
