Inclusivity isn't a buzzword, it's what makes teams stronger

I had an engineer on one of my teams who rarely spoke in group meetings. His pull requests were excellent: careful, well-reasoned, with clear commit messages. But in sprint planning and architecture reviews, he was almost invisible.

It took me a few months to notice the pattern: he wasn’t absent. He was present and listening closely, but the meeting format didn’t give him room. By the time he’d finished processing a discussion point, the conversation had moved on. Other engineers filled the space faster, not because their ideas were better, but because they were more comfortable with the cadence of live debate.

I started sending him the agenda beforehand, asking for written input on key questions before the meeting, and leaving a deliberate pause for him after others had spoken. What came back was consistently some of the most considered analysis in the room.

We’d been holding the meeting wrong for months.

What “inclusive” actually means in practice

Inclusivity gets used as a hiring metric and a culture statement, and in both cases it tends to stay abstract. What matters in daily team life is much more concrete: does every person on the team have a realistic path to contributing, being heard, and growing? Not in theory, but in the actual structure of how work gets done.

For the engineer above, the gap wasn’t attitude or intent. It was meeting format. For a developer who’s neurodivergent, the gap might be in how feedback is delivered. For someone from a different cultural background, it might be in how directness is interpreted. For a junior engineer on a team of seniors, it might be in whose opinions get deferred to by default.

These gaps don’t close on their own. They require someone to notice them and do something specific.

The gender imbalance isn’t a pipeline excuse

I’ve pushed for gender balance in my teams throughout my career, and I’ve heard the same response more than once: “there just aren’t enough women in tech programs.” That may be true at the university intake level. It doesn’t explain why teams end up 90% male when the candidate pool isn’t that skewed, and it certainly doesn’t explain pay gaps within teams that already exist.

When I’ve had the opportunity to influence hiring, I’ve required diverse shortlists and scrutinized the reasons behind rejections. When I’ve had budget decisions, I’ve checked compensation data by gender before finalizing offers. It’s not complicated work, it just requires actually doing it rather than citing the pipeline problem as a terminal excuse.

What managers can actually do

Rotate meeting facilitation. Early in my career, the same three engineers facilitated every discussion, and the same pattern of who spoke and who didn’t reinforced itself sprint after sprint. Rotating facilitation, even if uncomfortable at first for quieter engineers, changed the dynamic. People facilitate differently, which changes who contributes and how.

Audit who gets promoted and why. “Merit” in practice often means “performed well in the ways we think about performance,” which can encode bias without anyone intending it. Regularly checking whether promotions and salary adjustments track consistently across gender, background, and working style is basic diligence.

Push back when speed trumps diversity in hiring. An executive once pushed my team to hire fast to fill headcount, and the practical effect would have been a less diverse team because rapid hiring defaults to the most available pipeline. I made the case that we were building for the next three years, not the next quarter. The short-term cost of taking more time to build a more balanced team is almost always worth it.

Notice the things that make belonging harder without anyone planning them: the meeting time that works for North America and makes collaboration painful for someone in another timezone, the team chat that’s full of cultural references some people don’t share, the recognition that goes to the engineers who are most vocal about their own work. None of those are deliberate exclusions. They’re defaults that nobody challenged.

Inclusivity isn’t a value statement. It’s a set of decisions made in specific moments. The manager is usually in the best position to make the right ones.