Why Diversity in Tech Is Personal to Me

Tech loves to describe itself as innovative, inclusive, and built on merit. Sometimes it is. Often it isn’t. Diversity in tech isn’t an abstract idea to me. It’s something I’ve felt in meetings, in client work, and in the quiet calculations about when it’s safe or useful to speak up.

When we talk about diversity, I’m thinking about women, trans and nonbinary people, LGBTQ+ folks, and neurodivergent people. Not as a checklist, but as real humans whose lived experience changes what we notice, what we question, and what we build.

Tech Is Built by People, and People Aren’t Neutral

Every product carries assumptions. About who the “default user” is, what bodies can do, what family structures look like, what names are “normal,” and what kinds of brains are expected to succeed. When teams are built from a narrow slice of humanity, blind spots become features.

This is why inclusion matters at the product level, not just the hiring level. If we want technology that works for real people, we need real people in the room when decisions get made. Professional standards in computing explicitly call for fairness and non-discrimination because the impact of our work extends far beyond our teams.

Women, Trans People, and LGBTQ+ People Improve Products Because We Notice Different Risks

Being a woman in tech trains you to read systems and power dynamics quickly. You notice who gets interrupted, who gets credited, and who has to prove their competence over and over. That awareness translates directly into design. It makes you more sensitive to friction, unequal outcomes, and invisible barriers.

For trans and LGBTQ+ people, “small” design choices can carry real consequences. A form that forces binary gender options, a platform that doesn’t respect chosen names, or a system that exposes sensitive information can be more than annoying. It can be unsafe. Inclusive design pushes us to ask better questions early, before exclusion becomes baked into the product.

Neurodiversity Changed How I Think About Design

I also think a lot about neurodiversity and cognitive accessibility. Many digital systems assume one “right” way to process information, prioritize tasks, and move through steps. But people’s brains are different, and good design respects that.

Accessibility standards recognize cognitive and neurological needs as part of the accessibility landscape. That matters because clarity, predictable interactions, and reduced cognitive load help everyone, not just a subset of users.

Inclusive Design Is a Practical Skill, Not a Vibe

Inclusive design is not about being perfect or saying the right things. It’s a practice. It’s noticing who gets excluded, learning from diverse experiences, and building with that knowledge. One approach I return to often is the idea of “solve for one, extend to many,” which helps teams design with real people in mind while improving outcomes broadly.

This is also why I care about accessibility and structure so much. When we design with clarity, flexibility, and respect, we reduce friction for everyone. Not because we’re adding extra features, but because we’re removing unnecessary barriers.

Diversity Is Not a Trend. It’s How We Build Better Systems.

I don’t think diversity is valuable only because it can improve metrics. I think it matters because tech shapes people’s lives, and people deserve tools that don’t erase them, exclude them, or make everything harder than it needs to be.

If we want technology that actually serves the world, then the people building it need to reflect the world. Not as tokens. Not as exceptions. As real voices with real influence.

Why Diversity in Tech Is Personal to Me