Closing the Code Gap: A Practical Allyship Playbook for Men in IT/STEM
Created:
Introduction: The Role of Men as Allies in IT/STEM
Allyship is about taking responsibility for creating an inclusive environment. It’s about recognizing privilege and using it to support those who are underrepresented.
Allyship isn’t theoretical—it’s a set of daily, actionable steps that create real change. Below is a practical playbook for men in IT/STEM who want to support their female colleagues. Each action is specific, measurable, and tied to real-world impact.
A Practical Allyship Playbook
Principles that can be applied in various contexts, from meetings to code reviews, hiring, promotions, and social settings. Each section includes specific actions that can be taken in 30 seconds to 1 hour, making it easy to integrate into your daily routine.
This Playbook has been designed to be practical, actionable, and measurable. It’s not about grand gestures; it’s about consistent, small actions that accumulate into significant change.
#1 In Meetings: The 30-Second Rule
Problem: Women’s ideas are interrupted 2–3x more often than men’s in male-dominated settings, and their contributions are ~40–50% more likely to be credited to a man in group discussions1.
Your 30-Second Actions:
-
If a woman is interrupted:
"Let [Name] finish—she had a great point about [topic]." > (Takes 5 seconds, prevents derailing.)
-
If a woman’s idea is ignored:
"I want to circle back to [Name]’s suggestion about [idea]. It aligns with [goal/project]. Let’s explore it." > (Takes 10 seconds, ensures credit.)
-
If a woman is the only one taking notes:
"I’ll take notes today—[Name], you focus on the discussion." > (Takes 2 seconds, redistributes invisible labor.)
Impact: Teams with active amplification see a 30% increase in women’s speaking time in meetings2.
#2 In Code Reviews: The "Credit Check"
Problem: Women’s code is scrutinized more harshly (e.g., 1.5x more comments per PR) and ~20–30% less likely to be approved on the first pass in open-source projects3.
Your 30-Second Actions:
-
Before submitting feedback:
- Ask: "Would I phrase this differently if the author were a man?"
- Replace: "This is confusing" → "Can we clarify [specific part] for better readability?"
- Replace: "This doesn’t work" → "I noticed [specific issue]. Here’s a suggestion: [solution]."
-
If you see bias in others’ reviews:
"I think [Name]’s approach here is solid. Maybe we can test it before suggesting changes?"
-
Publicly praise good work:
- In Slack/Teams: "Great solution on [PR #123], [Name]! The way you handled [specific part] was clever."
- In team meetings: "[Name]’s refactoring of [module] saved us 10 hours of debugging."
Impact: Women whose code is publicly praised are 1.8–2.2x more likely to contribute again in the following 6 months3.
#3 In Hiring: The "Rooney Rule" for Tech
Problem: Women are 25–35% less likely to be hired for tech roles when applying with identical qualifications, with the gap widening for senior positions4.
Your 30-Minute Actions:
-
For every hiring panel:
- Insist on at least one woman on the interview panel. If not, ask: "Why not?"
- Push for blind recruitment: Remove names, photos, and genders from CVs (use tools like Gender Decoder)4.
- Challenge biased language in job descriptions:
- Bad: "We’re looking for a rockstar ninja coder."
- Good: "We’re looking for a collaborative problem-solver with expertise in [X]."
-
During interviews:
- If a woman is asked "Are you comfortable with the team’s fast pace?" (a question men rarely hear), redirect:
"We ask all candidates about their ability to meet deadlines. [Name], can you share an example of how you’ve handled tight timelines?"
- If a woman is asked "Are you comfortable with the team’s fast pace?" (a question men rarely hear), redirect:
-
After interviews:
- If a woman is rejected, ask: "What specific skills was she missing? Would we reject a man for the same?"
Note: The Rooney Rule (requiring at least one woman/minority candidate per interview slate) has mixed effectiveness. While it increases diversity in candidate pools, its impact on final hires depends on enforcement, bias training, and leadership buy-in5.
Impact: Companies using blind recruitment + diverse panels see a 30–50% increase in female hires, with the highest gains in early-career roles5.
#4 In Promotions: The "Sponsorship Pledge"
Problem: Women are 50–60% less likely to have a sponsor in male-dominated industries like tech, with the gap even larger for women of color3.
Your 1-Hour Actions:
-
Identify 1–2 high-potential women in your team/organization.
-
Advocate for them in 3 ways:
- Nominate them for high-visibility projects:
"[Name] would be perfect for leading [Project X]. She’s already done [Y] and [Z]."
- Push for their inclusion in leadership discussions:
"We should include [Name] in the [Strategy Meeting]. Her insights on [topic] are valuable."
- Give them stretch assignments:
"[Name], I’d like you to present our team’s work at the next all-hands. You’ve got great ideas—this will help you get visibility."
- Nominate them for high-visibility projects:
-
If they’re overlooked for a promotion:
- Ask your manager: "Why wasn’t [Name] considered? Her work on [X] was outstanding."
- Document their achievements and share them with decision-makers.
Impact: Women with sponsors are 25–30% more likely to ask for a raise and 10–15% more likely to be promoted within 2 years3.
#5 In Social Settings: The "No Bro Talk" Rule
Problem: 60–70% of women in German tech report experiencing sexist jokes, exclusionary language, or "locker room talk" in the past year, with higher rates in startups6.
Your 5-Second Actions:
-
If someone makes a sexist joke or comment:
- Shut it down immediately:
"That’s not funny. Let’s keep it professional." > "I don’t get it—can you explain?" (Forces them to confront the inappropriateness.)
- Redirect the conversation:
"Speaking of [topic], did you see [Name]’s work on [project]? It’s impressive."
- Shut it down immediately:
-
If you hear "She’s too emotional" or "She’s not technical enough":
"I’ve worked with [Name]—she’s one of the most logical/technical people here. Can you give me an example of what you mean?"
-
If women are excluded from after-work events (e.g., "guys’ night out"):
"We should invite the whole team. [Name] and [Name] would add a lot to the discussion."
Impact: Workplaces with clear anti-harassment norms + ally training see a 40–60% drop in gender-based microaggressions over 12 months6.
#6 In Mentorship: The "1-Hour-a-Month" Commitment
Problem: 65–75% of women in tech report never having a formal mentor, with the rate higher for mid-career professionals3.
Your 1-Hour Actions:
- Reach out to 1–2 junior women in your company/network:
"I’d love to help you grow in your career. Can we grab coffee for 30 minutes this month?"
- Offer specific guidance:
- "I noticed you’re working on [X]. Here’s how I approached a similar problem: [Y]."
- "Have you considered applying for [opportunity]? I can introduce you to [Person]."
- Introduce them to your network:
- Forward their work to others with a note: "[Name] did a great job on [X]. You should connect with her."
- Share opportunities:
- "There’s a conference coming up on [topic]. I think you’d be a great fit for a talk—want me to help you draft a proposal?"
Impact: Women with mentors are 60–70% more likely to stay in tech, with mentorship reducing attrition by ~40% in high-turnover companies3.
#7 In Parenting: The "50/50 Pledge"
Problem: Women in tech are 2.5–3.5x more likely to leave after having children, with lack of flexible work options and unequal parental leave uptake as key drivers7
Your Daily Actions:
-
If you’re a father:
- Take your full paternity leave (Germany offers 14 months—men take ~25% of Elterngeld days, though uptake is rising due to policy changes like ElterngeldPlus)8.
- Split childcare duties equally: If your partner handles bedtime, you handle mornings. If she cooks, you clean.
- Normalize flexible work: If you leave early for a kid’s event, say it proudly:
"I’m heading out for my daughter’s recital. I’ll be back online at 8 PM."
-
If you’re a manager:
- Encourage fathers to take leave:
"Take the full 14 months—it’s good for you, your family, and the team."
- Offer flexible work options to all parents, not just mothers.
- Encourage fathers to take leave:
Note: Countries with mandated, non-transferable paternity leave (e.g., Sweden’s 90 days for fathers) see 80%+ of women return to work post-childbirth, compared to ~60% in countries with low uptake7.
Impact: In Sweden, where 90% of fathers take paternity leave, 80% of women return to work after childbirth7.
#8 In Advocacy: The "1% Rule"
Problem: ~12–15% of tech startups in Germany have female founders, with the rate stagnant since 2020 despite increased VC funding for diverse teams9.
Your 1-Hour Actions:
-
Spend 1% of your time (~5 minutes/day) advocating for systemic change:
- Sign petitions for pay transparency, diversity quotas, or childcare subsidies.
- Attend or organize a diversity workshop in your company.
- Donate to organizations like Girls Who Code, or FrauenLoop.
- Push for policy changes in your workplace (e.g., pay audits, blind recruitment).
-
Use your platform:
- If you have a blog, social media, or speaking opportunities, highlight women’s work:
"Check out [Name]’s talk on [topic]—it changed how I think about [X]."
- If you have a blog, social media, or speaking opportunities, highlight women’s work:
Impact: Companies with male allies advocating for policy changes see faster progress in gender diversity2.
Your Weekly Allyship Checklist
Use this to track your progress. Aim for at least one action per week.
| Week | Action | Done | Notes |
|---|---|---|---|
| 1 | Amplify a woman’s voice in a meeting. | [ ] | |
| 1 | Give public praise for a woman’s code/contribution. | [ ] | |
| 2 | Call out a microaggression or sexist comment. | [ ] | |
| 2 | Mentor a junior woman (1:1 coffee chat). | [ ] | |
| 3 | Advocate for a woman in a promotion/hiring discussion. | [ ] | |
| 3 | Challenge biased language in a job description. | [ ] | |
| 4 | Take on a "non-promotable" task (e.g., notes, organizing) to free up a woman. | [ ] | |
| 4 | Share a woman’s work on social media or in a team email. | [ ] |
Common Excuses And How to Overcome Them
| Excuse | Reality | Action |
|---|---|---|
| "I don’t know what to say." | You don’t need a perfect script—just speak up. | Start with: "I noticed [X]. Let’s change that." |
| "I’ll be seen as ‘woke’ or ‘not a real techie’." | True allies are respected. Most people (including women) appreciate the effort. | Focus on actions, not labels. |
| "It’s not my place to speak up." | Silence = Complicity. If you see bias, you have a responsibility to act. | Ask: "What would I want someone to do if this happened to my sister/daughter?" |
| "I don’t see any bias here." | Bias is often invisible to those who benefit from it. | Take the Implicit Association Test10. |
| "I’m too busy." | Allyship takes minutes, not hours. | Start with one 30-second action per day. |
The Ripple Effect: How Small Actions Lead to Big Change
Your individual actions create a ripple effect:
- 1 man amplifying a woman’s voice → She gains confidence → She speaks up more → More women enter leadership.
- 1 man mentoring a junior woman → She stays in tech → She mentors others → The pipeline grows.
- 1 man calling out a sexist joke → Others think twice → Culture shifts.
Example: At Salesforce, after CEO Marc Benioff publicly committed to pay equity, 16,000 employees (including many men) pushed for change. The result? $16M spent to close the gender pay gap—and a 30% increase in women in leadership2.
Your First Step in Allyship: Pick One Action
Pick one action from this guide and do it today.
- Easiest: Amplify a woman’s idea in your next meeting.
- Most impactful: Sponsor a woman for a promotion or high-visibility project.
- Most scalable: Mentor a junior woman in your network.
Then, share your commitment publicly (e.g., on LinkedIn, in a team chat):
"I’m committing to being a better ally in tech. My first action: [X]. Who’s with me?"
Remember: You don’t have to be perfect. Progress > Perfection. The tech industry—and the women in it—need you to start now.
Deep Dive into the Data and Research
Do a deep dive into the data and research behind these actions and their impact. Understanding the why will make your allyship more effective.
Visit Closing the Code Gap: Why Germany Lags in Female Tech Participation—and How to Fix It for a comprehensive look at the statistics, studies, and research that inform this playbook.
Resources
Footnotes
Feedback
Have thoughts or experiences you'd like to share? I'd love to hear from you! Whether you agree, disagree, or have a different perspective, your feedback is always welcome. Drop me an email and let's start a conversation.