Diversity & Inclusion Prompt Templates

Team,

Starting next month, we're implementing blind resume screening for all open roles. Here's what that means and why we're doing it.

The change:
When recruiters do initial resume reviews, they'll see skills, experience, and accomplishments, but not names, schools, or graduation years. We'll restore this information before interviews.

Why we're doing this:
We looked at our hiring data and found that our interview pipeline is less diverse than our applicant pool. Something is happening in the screening stage. Research consistently shows that names and school names trigger unconscious bias, even among people trying to be fair. Blind screening removes that variable.

What this won't fix:
This addresses one stage of hiring. It's not a silver bullet. We're also reviewing our interview process and where we source candidates.

How we'll know if it's working:
We're tracking demographic data at each hiring stage. If this helps, we should see more diversity making it to interviews. We'll share progress in quarterly updates.

Questions or concerns? Reach out to [HR contact] or me directly.

[Your name]

This posting has several issues that could discourage diverse candidates:

Problematic language:
- 'Rockstar,' 'ninja,' 'crush,' 'dominate': These terms are often associated with aggressive, masculine tech culture. They can signal an environment that's unwelcoming to people who don't fit that mold.
- 'Work hard, play hard': Often code for long hours and drinking culture. Discourages people with caregiving responsibilities or those who don't drink.
- 'Top university': Creates unnecessary barriers. Great engineers come from all kinds of educational backgrounds.
- '10+ years of experience': Unless truly necessary, this excludes people who learned later or took non-traditional paths.

Missing information:
- No mention of remote/hybrid flexibility
- No salary range (many diverse candidates won't apply without it)
- No information about benefits or accessibility

Suggested rewrite:
'We're looking for a senior developer to join our team. You'll build features that matter, write clean code, and help us solve interesting problems.

What you'll need:
- Strong experience building and shipping software
- Proficiency in [specific technologies]
- Ability to collaborate with designers, PMs, and other engineers

Nice to have:
- [Specific domain knowledge]

What we offer:
- Salary range: $X-Y
- Flexible schedule, remote-friendly
- [Key benefits]

We encourage applications from people of all backgrounds. If you're not sure you meet every qualification, apply anyway.'

2024 DEI Progress Update

A year ago, we set specific goals for diversity and inclusion. Here's an honest look at where we landed.

What we committed to and where we are:

1. Increase underrepresented groups in engineering from 15% to 25%
Result: 19%
We made progress but didn't hit the target. Our hiring pipeline improved, but we also had retention issues that offset some gains. This tells us hiring isn't enough. We need to focus on why people stay.

2. Launch Employee Resource Groups
Result: Done
We launched three ERGs: Women in Tech, BIPOC Alliance, and Pride Network. Combined membership is 120 employees. Feedback has been positive, though some groups want more budget for programming.

3. Inclusive leadership training for all managers
Result: 80% complete
Most managers completed the training. Feedback was mixed. Some found it valuable, others said it felt generic. We're revising the program based on this feedback.

What we're doing in 2025:
- Revising our sourcing strategy to reach more diverse candidates earlier in the pipeline
- Exit interview analysis to understand retention gaps
- Allocating dedicated budgets for each ERG
- Redesigning manager training with more practical, scenario-based content

I'm sharing this because transparency matters. If we only report wins, you can't trust the information. We made real progress this year. We also have more work to do.

[Your name]

Inclusive Meeting Guidelines: Global Teams

These guidelines address specific problems we've noticed: the same voices dominating, remote participants getting excluded, and decisions happening outside meetings.

Before the meeting:
- Share agenda and materials 24 hours ahead. This gives non-native English speakers and introverts time to prepare.
- Rotate meeting times if they regularly fall outside some time zones' working hours. 8am for San Francisco shouldn't always mean 11pm for Singapore.
- State clearly whether the meeting is for discussion, decision, or information. People engage differently when they know the goal.

During the meeting:
- Facilitator role: One person runs the meeting, watches for raised hands, and actively invites quieter participants to speak. This shouldn't always be the most senior person.
- 'Chat then speak' rule: For brainstorms, have everyone type ideas in chat first, then discuss. This surfaces ideas from people who don't jump in verbally.
- Remote-first mindset: If anyone is remote, everyone uses their own camera and mic. No conference rooms where remote folks can't see who's talking.
- Wait time: After asking a question, wait 5-10 seconds before moving on. Some people need time to formulate responses, especially in a second language.
- Check the chat: Remote participants often share thoughts in chat. The facilitator should surface these verbally.

For decisions:
- State decisions explicitly at the end of the meeting. 'We decided X, and the next step is Y.'
- Don't finalize decisions in hallway conversations after the meeting. If something changes, bring it back to the group.

After the meeting:
- Share notes within 24 hours, including decisions and action items.
- For important discussions, offer async follow-up for people who couldn't attend or didn't have time to contribute.

For specific meeting types:

Standups:
- Keep them short (15 min max) and focused on blockers, not status reports.
- Consider async standups for teams spanning more than 6 hours of time zones.

Brainstorms:
- Use silent brainstorming techniques (sticky notes, digital boards) before group discussion.
- Explicitly invite ideas from people who haven't spoken.

Planning meetings:
- Share the problem statement and constraints in advance.
- Use structured techniques (dot voting, trade-off matrices) so the loudest voice doesn't automatically win.