Practical scripts and systems that turn good intentions into everyday fairness
Shane Windmeyer is a Charlotte, North Carolina-based DEI strategist, speaker, and advisor who helps organizations build inclusive cultures grounded in trust, fairness, and measurable outcomes.
Managers avoid hard conversations for good reasons: they are awkward, they take time, and they can feel risky. The problem is not that the conversations are hard. The problem is that avoiding them makes fairness optional. Inclusion is not a slogan, and it is not a training module. Inclusion is what happens when managers consistently hold three kinds of conversations: performance clarity talks, conduct and boundary conversations, and identity-and-impact discussions. When these talks are regular, predictable, and documented, workplaces move from performative gestures to durable practice.
Below are practical explanations of each conversation, why it matters for inclusion, and short, copyable scripts and steps managers can use immediately.
1. Performance clarity: stop asking people to guess
Why managers dodge it
Giving specific feedback takes time and courage. It feels easier to say, “Do better” or “Be more strategic” than to name precise behaviors that need change.
Why it matters for inclusion
Vague feedback prizes insiders who already understand tacit norms. People who are new, from different backgrounds, or less connected get left behind. Making expectations explicit levels the playing field and turns promotion from a mystery into a process.
What to do now
Tie feedback to observable behaviors, not personality.
Offer one concrete example of what “better” looks like.
Set a measurable checkpoint and follow up.
Leave a two-line note in a coaching file after the conversation.
Quick script (copy/paste)
“Observation: In recent presentations, your slides focused on tactical fixes. Impact: That limited the team’s ability to evaluate longer term tradeoffs. Expectation: For the next deck, include one slide with system-level options and one with short-term steps. Let us check progress in two weeks.”
Why a tiny habit helps
Adding a brief entry to a shared coaching document takes a minute and preserves continuity. When reviewers see a trail of documented development, promotion conversations become about evidence, not impressions.
2. Boundaries and conduct: name behavior, describe impact, follow up
Why managers dodge it
Calling out disrespect or chronic interruption risks social friction. Some managers worry about losing a top performer or being drawn into messy interpersonal fights.
Why it matters for inclusion
When certain behaviors are tolerated because of results or status, fairness collapses. People who experience disrespect stop participating, document interactions obsessively, or leave. Predictable enforcement of basic standards is a powerful inclusion signal.
What to do now
Use a short behavior-impact-expectation frame.
Schedule a follow up to review progress.
Document the conversation succinctly.
Apply the same standard to every person.
Quick script (copy/paste)
“Behavior: I noticed you interrupted colleagues multiple times in yesterday’s meeting. Impact: Others stopped contributing and some good ideas did not get explored. Expectation: Please pause until the speaker finishes. I will call out interruptions in the moment. We will check back in two weeks.”
Why structure matters
A clear protocol reduces manager anxiety. It removes the need to find the “perfect” wording and replaces judgment with observable facts. That makes enforcement less personal and more consistent.
3. Identity, bias, and impact: center harm, then investigate
Why managers dodge it
This is the most sensitive talk. Managers fear saying the wrong thing or making matters worse.
Why it matters for inclusion
Small harms accumulate into systemic exclusion. Ignoring reports of bias signals tolerance for those harms and damages trust across the organization.
What to do now
Prioritize impact over intent in initial conversations.
Listen, validate, and collect concrete examples.
Look for patterns across incidents.
Use neutral reviewers or panels when conflict of interest is likely.
Articulate repair options and timelines.
Quick script (copy/paste)
“Thank you for telling me. I hear that the comment made you feel excluded. Can you share the examples so we can understand the pattern? I will review this with HR and a neutral reviewer and propose next steps within five business days.”
Why patterns matter
Single incidents must be taken seriously. Recurrent patterns are what reveal structural risk. Designing responses that surface recurrence helps organizations fix root causes rather than only treating symptoms.
Make the conversations predictable - not optional
Across all three conversations, a few design rules make them easier and more reliable:
Provide short scripts and norms so managers do not improvise under pressure.
Require brief documentation so future reviewers have context.
Separate coaching from corrective action. Give a chance to improve, and escalate when patterns persist.
Train managers with role play to lower emotional friction.
Measure outcomes. Track promotions, allocation of visible work, and complaint recurrence to confirm change.
Small, repeatable habits scale. Ask every manager to log a two-line coaching note after 1:1s, to use the behavior-impact-expectation frame in conduct conversations, and to document impact-first responses for bias reports. Those tiny moves create an institutional memory that protects fairness.
The payoff
Teams that routinely conduct these three conversations become places where people take healthy risks, collaborate across difference, and trust that the system will treat them equitably. Avoidance creates a slow leak in trust that is far more costly than the discomfort of direct dialogue. When the organization makes these conversations ordinary, inclusion shifts from aspiration to daily practice.
Shane Windmeyer is a Charlotte, North Carolina-based DEI strategist, speaker, and advisor who helps organizations build inclusive cultures grounded in trust, fairness, and measurable outcomes. Learn more at Shane Windmeyer’s website.
Top comments (0)