Inclusive Workplace Practices

For two decades, I’ve led engineering teams through rapid growth, challenging projects, and the ever-present pressure to just ship. But over time, I’ve realized that technical excellence alone isn’t enough. Building high-performing teams means building inclusive teams – and it goes far beyond simply ticking DEI boxes. It's about creating an environment where everyone feels empowered, valued, and able to bring their whole selves to work.

This isn't just “the right thing to do” (though it absolutely is). Diverse teams are demonstrably more innovative, resilient, and better at solving complex problems. But achieving true inclusivity requires a deliberate, ongoing effort – and a shift in how we think about management.

The Problem with Performative Inclusion

I recently worked with a company that launched a highly publicized DEI initiative, complete with new training programs and revised hiring practices. Six months later, little had changed. The same senior engineers dominated design discussions, and underrepresented voices remained unheard. This is a common scenario. Companies often focus on compliance – checking boxes – rather than fostering a culture of genuine inclusion. This “performative inclusion” creates cynicism and ultimately undermines trust. It sends the message that diversity is valued in theory, but not in practice.

Why does this happen? Because inclusion isn’t a program; it’s a practice. It’s not about telling people to be inclusive; it's about creating systems and norms that enable inclusion.

Moving Beyond Compliance: Practical Strategies for Engineering Managers

Here’s what I’ve learned, leading teams both at startups and large organizations. These aren’t quick fixes, but consistent application of these principles can have a profound impact:

• Radical Candor with Empathy: Kim Scott’s framework is powerful, but the ‘empathy’ piece is often overlooked. It's not enough to be direct; you must genuinely care about the individual and their growth. Empathy in this context means understanding their perspective, acknowledging their challenges, and supporting their development. Ask why someone might be struggling, and listen actively. This creates psychological safety – the foundation of inclusive teams.
• Decentralize Decision-Making: Too often, engineering managers fall into the trap of being the “chief problem solver.” Instead, empower your team to make decisions – even (and especially) when you disagree. This builds trust, develops skills, and ensures a wider range of perspectives are considered. I’ve found that stating “I’m interested to hear your approach to this” does wonders. Empowering the team also means allowing for experimentation and accepting that mistakes will happen – and that’s okay.
• Challenge Assumptions & Encourage Diverse Voices in Design: Technical design reviews are critical, but are they truly inclusive? Ensure everyone has a chance to speak, not just the most senior or outspoken members of the team. Specifically ask for input from those who haven’t yet contributed. Actively challenge assumptions and biases in the design process. "What perspectives haven't we considered?" is a simple, yet powerful question. For example, during a recent design review, I specifically asked a junior engineer for their thoughts, and they identified a potential edge case that the rest of us had overlooked.
• Normalize Vulnerability & Feedback: Create a culture where it's safe to admit mistakes, ask for help, and give constructive feedback. I’ve implemented “Dedicated Failure Analysis Sessions” where the team openly discusses what they learned from failures – no blame, just learning. This reduces fear, encourages experimentation, and fosters a growth mindset.
• Beyond the Resume: Recognizing Value Beyond Technical Skills: Technical competence is essential, of course, but don’t underestimate the value of “soft skills” like communication, empathy, and collaboration. When evaluating candidates (or promoting team members), look for evidence of these qualities. A brilliant coder who can’t collaborate effectively can be more detrimental than a competent coder who is a strong team player.
• Address Microaggressions Directly (and Educate): Microaggressions – subtle, often unintentional, expressions of bias – can erode trust and create a hostile environment. As a leader, you have a responsibility to address them directly, even if it's uncomfortable. Don't dismiss them as "just a joke." Use it as a teaching moment.

The “Benefit of Others” – A Shifting Mindset

One common thread I’ve observed is the need for a shift in mindset. It’s about moving from a transactional approach ("What can I get out of this?") to a relational one ("How can we succeed together?"). This requires intentionality – modeling inclusive behavior, actively listening, and genuinely caring about the well-being of your team. It’s also important to acknowledge that shifting to this mindset can be difficult. Some team members may initially resist the idea of prioritizing collective success over individual achievement. Openly discussing these challenges and emphasizing the long-term benefits of collaboration can help overcome this resistance.

Retrospectives: Sustaining Inclusion and Continuous Improvement

Retrospectives are crucial for not only improving processes but also for sustaining inclusivity. Conduct retrospectives at both the team and organizational level.

• Team-Level Retros: Focus on immediate challenges and solutions. How can we improve our communication? How can we better support each other?
• Organization-Level Retros: Identify systemic issues that hinder inclusion. What processes are biased? What policies need to be changed?

Crucially, ensure that action items from retrospectives are actually implemented. Too often, they gather dust on a shared document. Assign ownership and track progress. This demonstrates a genuine commitment to creating a more inclusive environment.

Creating Meaningful Work & Engagement

Disengagement can exacerbate feelings of exclusion. As leaders, we need to create opportunities for growth, challenge, and purpose. This isn't about offering perks; it's about understanding what motivates each individual and providing opportunities for them to contribute meaningfully. This can be integrated into decentralizing decision-making by giving team members ownership over challenging projects and allowing them to propose innovative solutions.

Final Thoughts

Building truly inclusive engineering teams isn’t easy. It requires ongoing effort, self-reflection, and a willingness to challenge the status quo. But the benefits – increased innovation, improved performance, and a more engaged workforce – are well worth the investment. Start by challenging assumptions in your next design review or actively soliciting feedback from quieter team members. It’s about creating a workplace where everyone feels valued, respected, and empowered to bring their whole selves to work. Creating this environment isn’t just the right thing to do; it’s also the smart thing to do.