Use when a manager wants to create a team environment where people from different backgrounds have equitable access to voice, visibility, advancement opportunities, and meaningful work — beyond just having diverse representation on the team.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill build-inclusion-practices --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Build Inclusion Practices?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-build-inclusion-practices)More formats (shields.io, HTML) on the badges page.
---
name: build-inclusion-practices
description: Use when a manager wants to create a team environment where people from different backgrounds have equitable access to voice, visibility, advancement opportunities, and meaningful work — beyond just having diverse representation on the team.
source: "Catalyst \"Inclusive Leadership: The View From Six Countries\" (2012, 1,500 employees); McKinsey \"Diversity Wins\" (2020); Project Include \"Starting from Within\" framework; Kecia Thomas \"Inclusion Paradox\" research"
tags: [inclusion, diversity, equity, belonging, manager, bias, equitable-practices, underrepresented]
---
# Build Inclusion Practices
Create team conditions where employees from all backgrounds have equal access to voice in decisions, visibility with senior leaders, sponsorship for growth opportunities, and feedback that helps them advance — not just representation on the roster.
## Why This Is Best Practice
**Why best:** Inclusion practices convert diverse representation into equitable access to voice, opportunity, and advancement — without them, diversity produces presence without participation.
**Adopted by:** Catalyst's research (1,500 employees across six countries, 2012) identifies inclusive leadership behaviors as the primary driver of innovation and engagement in diverse teams; McKinsey's "Diversity Wins" report (2020, 1,000+ companies, 15 countries) is the most rigorous large-scale study of diversity's business impact; Project Include — founded by Ellen Pao and 7 other technology executives — provides the most operationally specific inclusion guidance for technology organizations; the Human Rights Campaign's Equality Index evaluates inclusion practices at 1,100+ companies annually
**Impact:** McKinsey "Diversity Wins" (2020) found companies in the top quartile for ethnic diversity were 36% more likely to achieve above-average profitability than companies in the bottom quartile, and those in the top quartile for gender diversity were 25% more likely to achieve above-average profitability; Catalyst research (2013, 1,500 employees) found that employees with inclusive managers report 70% higher team innovation and are 45% more likely to report high team morale; Deloitte's Global Human Capital Trends survey (2017, 10,000+ respondents) found that 69% of employees felt their organization's diversity efforts were not creating equal opportunities at the team level — indicating that diversity programs without manager-level inclusion behavior produce minimal impact
Sources: Catalyst "Inclusive Leadership: The View From Six Countries" (2012); McKinsey "Diversity Wins: How Inclusion Matters" (2020); Project Include "Starting from Within" (projectinclude.org); Deloitte "2017 Global Human Capital Trends"
## Steps
### 1. Distinguish inclusion from diversity
**Diversity**: who is in the room — representation across gender, race/ethnicity, age, neurodivergence, background, experience
**Inclusion**: whether everyone in the room has equal access to voice, resources, and advancement
A diverse team without inclusion practices is a team where underrepresented members are present but not heard. Inclusion is what makes diversity functional. Managers primarily control inclusion; HR and executives primarily control diversity hiring. This skill is about the manager's sphere.
### 2. Audit voice equity in team interactions
Track who speaks, who is heard, and who gets credit in team meetings and decisions. This does not require surveillance — it requires attention. Patterns become visible over time:
- Who consistently speaks first in brainstorm sessions? (First-speaker anchoring means their ideas receive more weight)
- Whose ideas are acknowledged when stated, and whose are re-stated by someone else and credited differently?
- Who is routinely interrupted?
- Whose names appear in project documentation as contributors vs. coordinators?
What to do about it:
```
Amplification: when an underrepresented team member makes a point that isn't
acknowledged, the manager amplifies it:
"[Name] raised something important — [repeat the point and credit them by name]."
```
This technique was used explicitly by Obama White House female staffers and documented in a 2016 Washington Post article — and significantly increased the frequency with which women's ideas were credited.
**Structured turn-taking**: in brainstorm or decision meetings, rotate who presents first. "Let's hear from everyone before we discuss — [Name A], start us off." This prevents the first-speaker from anchoring the discussion.
### 3. Equalize access to stretch opportunities
High-visibility projects, presentations to senior leadership, cross-functional collaborations, and conference speaking opportunities are career-accelerating. They are typically distributed informally — given to people the manager knows well, trusts, or finds easy to work with.
This informal distribution systematically favors whoever has the strongest relationship with the manager. Because relationship quality correlates with demographic similarity (affinity bias), informal distribution produces systematic inequality in opportunity access.
**Structured approach:**
- Maintain a list of each direct report's visible opportunities in the last 6 months
- Before assigning a stretch project, ask: "Who has had fewer high-visibility opportunities lately? Who would benefit most from this exposure?"
- Do not default to the highest performer for every stretch — that compounds their visibility advantage; the goal is for everyone to develop, not just for the best person to do the best work
Document opportunity distribution. If the distribution shows systematic skew — one demographic group consistently receiving more stretch opportunities — address it explicitly.
### 4. Give consistent, specific feedback to all direct reports
Research by Shelley Correll and Caroline Simard (Harvard Business Review, 2016) found that performance feedback given to women is more likely to be vague ("you should improve your leadership skills"), while feedback given to men is more likely to be specific and actionable ("you should speak up more in client meetings"). Vague feedback cannot be acted on; it disadvantages those who receive it.
Audit your feedback pattern:
- Is the feedback you give to underrepresented team members as specific as the feedback you give to others?
- Do you give developmental feedback to all direct reports, or primarily to those you feel most comfortable with?
- Are you avoiding giving critical feedback to underrepresented members to avoid discomfort — and thereby disadvantaging them by preventing their development?
Candid, specific feedback is one of the most equitable things a manager can do. Withholding honest developmental feedback to protect someone from discomfort protects the manager from discomfort and deprives the employee of growth.
### 5. Provide sponsorship, not just mentorship
**Mentorship**: giving advice and counsel — "here's what worked for me"
**Sponsorship**: using your influence to advocate for someone's advancement — "you should give [Name] this opportunity; here's why"
Mentorship is low-risk for the manager. Sponsorship stakes the manager's credibility on the person they advocate for. Research by Sylvia Ann Hewlett (Center for Talent Innovation) found that:
- Employees with sponsors are 23% more likely to advance in their careers
- Underrepresented employees are significantly less likely to have sponsors (vs. mentors) because sponsorship requires the sponsor to risk their credibility — which requires trust — which is built through interaction — which requires access
Manager-level sponsorship practices:
- Proactively name your direct reports in conversations with senior leaders: "This analysis was done by [Name] — they're one of the strongest on the team."
- Advocate explicitly in talent discussions: "I want to make the case for [Name] for this opportunity. Here's the evidence."
- Invite direct reports to present their own work in leadership settings — don't present it for them.
### 6. Examine your own bias in performance and promotion decisions
Affinity bias — rating more favorably those who are demographically similar or who interact in culturally familiar ways — is the most common bias in performance evaluation. It is not eliminated by good intentions.
**Structural mitigations:**
- Before writing a performance review, list the specific evidence for each rating. Ask: "Is this evidence, or is this impression?" Impressions are bias-vulnerable; evidence is more resistant.
- Use the same questions for all employees in performance calibration: "What did this person specifically accomplish? What specific evidence do we have for this rating?"
- If asked to name high-potential employees, require yourself to name the specific evidence for each person's potential — not a global sense of their capability.
- In promotion discussions: "Would we say the same things about this person if they were [different demographic]?" This is an uncomfortable question. It surfaces bias when it is not asked.
## Rules
- Distinguish inclusion from diversity — having a diverse team without inclusion practices produces presence without voice; the manager's job is inclusion
- Audit voice distribution actively — patterns only become visible through attention; track who speaks, whose ideas are credited, who receives stretch opportunities
- Give equally specific feedback to all direct reports — withholding honest critical feedback to protect someone from discomfort is not kindness; it deprives them of development
- Sponsor, don't just mentor — using your influence to advocate for someone's advancement is the highest-impact inclusion action a manager can take
- Examine your own bias structurally — good intentions do not prevent affinity bias; structural practices (evidence requirement, calibration questions) mitigate it
## Common Mistakes
- **Treating inclusion as an HR initiative**: HR creates programs; managers create culture; the daily decisions a manager makes about who speaks, who gets opportunities, and who receives feedback determine inclusion on the team.
- **Confusing comfort with inclusion**: managers often feel more comfortable with team members who share their background, communication style, or social norms; that comfort is affinity bias; acting on it produces exclusion.
- **Giving the same stretch opportunities to the same high performers**: this compounds performance advantage rather than developing the team; diversify who receives high-visibility opportunities.
- **Avoiding difficult feedback to underrepresented team members**: out of discomfort or fear of misinterpretation, managers give less honest feedback to some team members; this is well-intentioned harm — they cannot develop without honest input.
- **Treating a diversity event as inclusion work**: a one-time cultural celebration or inclusion workshop is a gesture; inclusion is built through daily manager behavior over months and years.
## When NOT to Use
- As a substitute for addressing active discrimination or harassment — systemic inclusion practices are long-term culture work; active discrimination requires immediate HR and legal intervention, not an inclusion program.
- As a template applied uniformly without understanding the team's specific gaps — some teams have voice equity issues; others have sponsorship gaps; others have feedback consistency problems; diagnose before prescribing.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!