Running inclusive meetings

Why meetings are where inclusion is won or lost

You can have the best inclusion policy in the world, but if your meetings routinely amplify the same three voices and sideline everyone else, that's the culture people actually experience. Meetings are one of the most visible expressions of how power and voice are distributed in a team. As I've put it on the Inclusion Bites podcast: "You can be included but not feel belonging." Being invited to the meeting is not the same as being able to genuinely contribute to it.

There's also a psychological safety dimension that most leaders underestimate. When someone raised a concern in a previous meeting and the response was defensive, dismissive, or resulted in them being labelled "not a team player" — that memory trains the whole room to self-censor. People stop speaking up not because they don't care, but because speaking up has become more dangerous than staying quiet. Meetings end, flawed plans move forward, and the disengagement sets in silently.

Before the meeting: set the conditions

Inclusive meetings are mostly won or lost before anyone joins the call or walks into the room. Getting the conditions right in advance removes a huge amount of cognitive load and lets people actually think, rather than spend the first twenty minutes working out what they're supposed to be doing.

• Share a clear agenda and purpose. People need to know why they're there, what decision needs to be made, and how their input will shape the outcome. When that's missing, participants spend their energy scanning the room reading emotional temperatures instead of focusing on the work — and they leave exhausted having accomplished nothing.
• Send pre-reads in time to actually read them. This is especially important for introverts, neurodivergent colleagues, and anyone for whom English is a second language — groups who often need processing time that in-the-moment verbal discussion doesn't allow.
• Only invite people whose input genuinely matters. Every unnecessary attendee signals that you haven't thought about what the meeting is actually for.
• Offer alternative contribution routes. A shared document, a pre-meeting survey, or a chat thread lets people contribute on their own terms, not just those who think fastest out loud.

During the meeting: managing voice and power

The most important thing an inclusive chair does is actively manage who gets heard — especially when hierarchy or personality is pulling the room in one direction.

• Ask for input before stating your view. Once a senior voice has landed, others anchor to it rather than think independently. Invite contributions first, then share your perspective. This one habit shifts the power dynamic in the room more than almost anything else.
• Explicitly invite quieter voices. "We haven't heard from everyone yet — [name], what's your read on this?" isn't putting someone on the spot; it's signalling that their contribution is wanted.
• Credit ideas back to the person who raised them. "Going back to what [name] said earlier…" prevents the common pattern where a quieter person's idea gets picked up and amplified by a louder voice — and the credit quietly transfers.
• Intervene when someone is interrupted. "Let's let [name] finish" is a simple signal that all voices are protected in this space.
• Use structured techniques for high-stakes discussions. Silent brainstorming, writing ideas before discussion, or going round the table in order all reduce the dominance of fast, loud, extroverted contributions.

Hybrid and remote inclusion

Hybrid meetings carry a structural disadvantage for remote participants that doesn't fix itself. If you're in the room, you can read body language, catch the moment the conversation opens, and be noticed. On a call, you can't. Inclusive hybrid meeting design requires actively compensating for that gap.

• Acknowledge the disadvantage and design for it. Treat remote participants as your primary audience, not an add-on.
• Check in with remote participants explicitly. Don't wait for people to jump in on mute — go to them directly.
• Avoid side conversations in the room. Anything said away from the microphone excludes everyone on the call.
• Use captions and provide transcripts. This helps participants with hearing differences, those in noisy environments, and anyone who needs processing time to keep up with fast verbal exchanges.
• Use chat and shared documents as parallel contribution channels. Contribution shouldn't depend solely on being quick on the unmute button.

The psychological safety piece

None of the structural techniques above will sustain themselves without psychological safety — the belief that speaking up won't cost you. As I've observed from conversations with belonging researchers: when the last time somebody raised a concern, a leader got defensive or a manager got defensive, or someone was labelled not a team player — it trains people to stay quiet. That pattern doesn't announce itself; it just quietly produces meetings full of nodding and silence, followed by disengagement outside the room.

Building psychological safety in meetings means responding to challenge with curiosity rather than defensiveness. It means closing the loop — "Last week you raised X; here's what we've done since." It means making it visibly safe to be wrong, to not know, and to disagree. These behaviours are at the core of inclusive leadership more broadly — the meeting is just where they're most visibly tested.

Connecting meetings to the bigger picture

Running inclusive meetings isn't a standalone skill — it's one expression of inclusive leadership in action. The habits that make a meeting inclusive — asking before telling, creating space for different voices, crediting contribution, responding to challenge with curiosity — are the same habits that make a team, a culture and an organisation inclusive. The meeting is just where it's easiest to see whether those habits are present or not.

Explore the keynote The Inclusive Leader's Journey to see how these behaviours connect to the full arc of inclusive leadership development.