Most team meetings follow the same basic pattern no matter who’s in the room. A couple of strong voices steer the conversation to where they want it to go, and someone raises an objection at just the wrong time. By the end, the meeting closes without a choice. Do that for enough weeks in a row, and it stops being a meeting – it just turns into a recurring appointment that everybody dreads.
Edward de Bono was onto this idea long before most organizations even had a name for it. His 1985 book laid out a strategy that splits the thinking into separate roles – each one represented by a different colored hat. The reasoning behind it still holds up – when a group needs to process facts, weigh problems, come up with new ideas and make room for gut feelings all at the same time, the thinking gets tangled fast, and the loudest voice tends to win.
A sharper group doesn’t automatically run better meetings – a more structured one does. The Six Thinking Hats framework was designed to fill just that gap – from how to open a session well and how to sequence the hats in an order that actually makes sense, to how to keep honest thinking alive in the room so the conversation doesn’t grind to a halt.
No framework is a perfect fit for every situation – and a big part of what makes this framework work well is the ability to see when a different tool would be more helpful. A sense of where any framework runs into its limits is as helpful as the ability to run one well. When teams get that balance right, their meetings start to feel noticeably different.
Let’s get started with how the Six Thinking Hats can shake up your team meetings!
What Each of the Six Hats Does
The Six Thinking Hats framework gives each hat its own job. The whole system gets much easier to follow once you know what each hat is responsible for.
The White Hat is purely about the facts and data. In a product launch meeting, your team lays everything out – sales forecasts, market research, and what the numbers are telling you. The Red Hat works a bit differently – it gives everyone permission to voice how they feel about something without needing to back it up with logic or evidence. A bad gut feeling about the timing counts as a valid contribution to the conversation.
The Black Hat is the one that tends to give teams the most trouble. It’s not about being negative for the sake of it – the whole point is to catch what could go wrong before it does. In a product launch conversation, the Black Hat pushes your team to ask where the plan has gaps and what the dangers are. The Yellow Hat is the counterpart to that, and it zeroes in on what could go right and why the idea might actually work.
The Green Hat is next, and the goal is new ideas and creative thinking. When a launch plan starts to feel a little too locked in, the Green Hat gives the team permission to step back and look at the plan from a different angle. Last up is the Blue Hat, and it works differently from the rest – the Blue Hat manages the whole conversation instead of adding to the ideas. Whoever has it decides which hat the group should use next. It also keeps the discussion on track.
De Bono built these six perspectives to work as one full set, and every one of them contributes something that the others just can’t do.
The Same Hat Cuts Out the Ego
The whole energy in that space changes when an entire room adopts the same mindset at the same time. Criticism lands very differently when no one singles anyone out – it’s just the group doing its job all at once as a single unit.
Amy Edmondson is a professor at Harvard Business School, and she’s spent years studying what she calls “psychological safety” (the idea that everyone feels safe enough to speak up at work without fear of judgment or punishment). Her work has shown again and again that teams with that sort of environment just do better work.
In most meetings, the person who proposed an idea goes into defense mode the second someone pushes back on it. At that point, it’s no longer about the idea – it can become about ego. Parallel thinking sidesteps that – everyone examines the same angle at the same time, and that keeps the conversation on the work instead of on the coworkers in the room.
One point to keep in mind, though – these hats only work the way they’re supposed to when everyone in the room uses them the same way. The whole process starts to fall apart the second someone says something like “you always put the Black Hat on everything.” That sort of comment takes what’s meant to be a tool and turns it into something personal, and those personal digs can close a conversation down instead of helping it move forward. The entire point of it is to take that personal side of the discussion out of the room.
A quick conversation first about how to actually refer to the hats (before the session starts) matters in how well this lands. The framework will only take you as far as the group is willing to get behind it.
Get Your Team Ready for the First Session
A little prep work before your first Six Hats meeting will pay off. The biggest step is picking a real problem to work through – not a hypothetical or a made-up scenario. A real problem gives the group somewhere to go, and the conversation gets a whole lot more honest when there’s actually something on the line.
It also helps to have a facilitator ready before the meeting even gets underway. This person doesn’t need to be the most senior person in the room – just someone who can guide the group from one hat to the next and reel the conversation back in when it starts to drift. It’s more of a light traffic-control role than a leadership one. A one-page cheat sheet is worth every bit of the 5 minutes it takes to put together. Give each hat a color, a name and a quick line about what it wants from the group. Pass it out before the meeting starts so no one wastes the first 10 minutes trying to work out what the black hat even means.
Time limits are one area that groups usually underestimate. Without them, the conversation just drifts toward the easier hats and races right past the harder ones. Give each hat a rough time cap and hold to it as best you can – even when a particular conversation still has a bit more left to it.
A low-stakes trial run is usually the right first move for a team that’s new to this. Grab something small and unimportant to test the format on – it gives everyone a chance to get comfortable with how the whole process works before anything that matters is on the line.
One more point is worth flagging – especially if part of your group is joining remotely. Remote attendees need to hear the explanation just as much as the participants in the room do. A confused person on the other end of the screen can slowly derail the whole session, and it’s far too tempting to just think that everyone already got the memo when they didn’t.
End the Meeting with the Blue Hat
The Blue Hat belongs to the facilitator, and it comes with two very particular jobs attached to it – it’s what opens the meeting at the start, and it’s also what brings everything to an official close at the end. The facilitator starts with the Blue Hat, and the whole point of this opening move is to get the agenda on the table. A plain-language statement of the goal and a quick overview of how the session will run – that’s all it takes, maybe 2 minutes. It’s a small step. But it gets everyone pointed in the same direction before any of the actual thinking begins.
At the end of the session, the Blue Hat comes back on – that’s the part where the facilitator rounds up everything the group actually landed on (who owns what and what the next steps are, with real names and deadlines attached to them). Plenty of meetings end strong with everyone nodding and great energy in the room. Yet almost no one leaves with a sense of what they need to do next. The Blue Hat closing is what addresses that – it takes a productive conversation and turns it into a concrete action plan.
The facilitator can step in and put the Blue Hat on right when a conversation starts to drift, or the group loses its focus – there’s no need to wait until the end of the session. It’s a quick way to pause and get everyone back on the same page and then move forward without losing any of the progress the group has already made.
The Blue Hat is one of the more helpful hats in the set, and a big part of its value is that it gives the facilitator a well-recognized role. Everyone in the room already understands that the Blue Hat is there to manage the process – not to push for any particular point of view. That separation alone makes it much easier to keep the group on track without stepping all over each other’s ideas.
The Right Order for the Other Five Hats
The order in which you run the hats can make or break the whole session – and most teams don’t give it nearly enough thought. A brainstorming session takes a very different sequence than a quick group call does, so it’s worth figuring this out before the meeting even starts.
One of the more popular brainstorming sequences is to open with the White Hat to get the facts out on the table, then switch to the Green Hat to let the ideas actually flow, move on to the Yellow Hat to pull out what’s strongest in those ideas, and close with the Red Hat to get an honest gut read from everyone in the room. The reason this order works is that it gives the whole group a shared picture of reality before the creative part even starts – and no one has to settle on a feeling about any of it until after they’ve had a chance to think. The sequence can be shortened when speed is a priority.
With that said, flexibility does matter. A rigid sequence can start to feel a bit mechanical – especially in shorter meetings where the conversation is already heading somewhere on its own. It’s best to treat the whole sequence as a guide instead of a strict script that you have to follow to the letter.
Time limits matter, and the Red Hat in particular does need them. It’s designed to be a quick temperature check on the room and not a full-on open forum – 30 seconds or so per person is usually all it takes to get an honest read on how everyone is feeling. Push past that and the discussion starts to drift. Emotions take over the whole session, and the other hats lose their weight as a result.
A Black Hat Session That Fights Groupthink
Groupthink is one of the quietest threats in any team setting. When the energy is high and an idea starts to gain traction, team members tend to hold back their doubts and just go along with where the group is headed. Irving Janis spent decades researching how groups make decisions, and what he found was that this pattern played a part in some of history’s most damaging mistakes – the Bay of Pigs invasion is probably the most famous example of this.
The idea gains momentum and a plan starts to take shape around it. Those original doubts just get left behind, and by the time they resurface, they’re far more tangled and far more expensive to sort out.
Gary Klein developed a technique called the pre-mortem – where the team imagines the plan has already failed and then works backward to piece together why. It’s a structured way to get everyone to actually say what they’re already sensing but have been holding back. A scheduled Black Hat session works in the same way – and it also helps protect the strong ideas because a plan that’s been pressure-tested is one that your whole team can get behind.
That said, it’s worth watching the time. When Black Hat time drags on too long, the energy in the room starts to fade – and even the strongest ideas can start to seem weaker than they are. The goal was never to be critical for its own sake – it’s just to stress-test what’s already there. A tight window with a defined endpoint will usually get you better feedback than an open session with no end.
Where SCAMPER Has the Edge
The Six Hats framework holds its own, and it delivers for most situations. That said, it’s not a perfect fit for every scenario. A more direct and creative way of thinking will probably pay off a bit more if your team’s goal is to take something that already exists (a product, a process, or a system) and make it better.
SCAMPER is where that comes together. Bob Eberle developed it in 1971 and built on the earlier work of Alex Osborn. At its core, it gives teams a structured set of questions that push their thinking in new directions. Each letter in the acronym stands for a different type of question: substitute, combine, adapt, modify, put to another use, eliminate, and reverse. Instead of asking “what do we make of this idea,” it flips the question to “what can we do to change it.” For a team trying to get unstuck, that’s a real change in how they look at a problem.
The Six Hats framework holds up well when your group needs to separate emotion from logic or when it needs to make sure no single voice ends up driving the whole conversation. The place where it starts to lose its value is when your goal is to reinvent or rework something that already exists. The one-hat-at-a-time strategy tends to work against you more than it helps in that scenario.
The great news is that you don’t have to choose one or the other – these two tools actually work well together. Plenty of facilitators fold SCAMPER right into the Green Hat phase because that’s already the space set aside for creative thinking. Open the floor with the Green Hat and then work through the SCAMPER questions to give your team something concrete to respond to. That combination tends to pull out far more grounded and original ideas than open brainstorming ever does on its own.
In my experience, it’s one of the more underrated pairings in facilitation. Each one fills in the gaps that the other leaves behind, and that’s what you want when you’re trying to get the most out of your session.
Put the Six Hats to Work
The three factors most likely to make or break a Six Hats session are also the easiest to miss – a Blue Hat opening that gives everyone a direction, enough time on the clock for every color hat to get used, and a dedicated slot on the agenda for the Black Hat instead of a rushed mention squeezed in at the very end. The whole session changes with all three in place – it stops feeling like a debate and starts feeling like a group that’s actually working through something together.
The best place to start for teams that haven’t done this before is also the easiest one – pick a single agenda item from next week’s meeting and run it through the hats. Stick to just one item and nothing more. The first session will probably feel a little off, and that’s fine. Any new framework takes a few rounds before it starts to click.
Ask yourself what your meetings would look like if every voice in the room had a chance to contribute, if criticism had a designated place on the agenda instead of always coming up at the worst possible time, and if everyone left with a decision. A meeting process like this makes that possible – it’s what it’s built for.
HRDQ‘s Neurolinguistic Communication Profile helps team members get a better read on their own communication style, and it gives them some tools for working with teammates who think a bit differently. It pairs well with this as an add-on to any group decision process.
Leave a Reply