🎙 A LIVE CALL-IN SHOW IS COMING — JOIN THE WAITLIST →
THE HUMAN FREQUENCY
Find Common Ground
Live Tune in →
HUMAN OS WIKI · 03 · UNDERSTANDING EACH OTHER

WORKPLACE MICROAGGRESSIONS

A subtle slight lands and you're stuck between two bad options: let it pass and it festers, or name it and watch the person shut down defensively. There's a third path — address the impact without indicting the character — and three scripts that make it sayable.

7 min read Last updated June 2026 Source: Difficult Conversations, Ch. 11
Directly labeling the aggressor as prejudiced will immediately trigger a severe amygdala hijack. The objective is to separate intent from impact — "calling in" for education rather than "calling out" for public shaming. — Difficult Conversations, Ch. 11
SHORT ANSWER

Microaggressions are brief, everyday slights that communicate hostility or dismissal toward marginalized groups, threatening the SCARF domains of Status, Relatedness, and Fairness. Directly labeling the person as prejudiced triggers a severe amygdala hijack and shuts down any chance of change — so the goal is to separate intent from impact, "calling in" for education rather than "calling out" for shame. Three scripts do this: asking for clarification ("Could you elaborate on what you meant?"), paraphrasing and reflecting ("It sounded like you were implying X — is that accurate?"), and addressing impact ("I know you likely didn't intend it this way, but when you said that, it felt dismissive of my experience"). Organizations counter the accumulation with micro-affirmations — small, deliberate acts of inclusion.

GET THE FREE PRINTABLE ↓ One page, wallet-card layout. Free. One email below, no spam, unsubscribe in a click.

The problem

Someone says the thing — the backhanded comment, the assumption about who you are, the joke that isn't — and the room moves on while you sit with it. You replay the two options you always have. Stay quiet, and it festers, and the next one lands easier. Or name it, and watch them get defensive, deny it, and somehow become the wronged party.

Both options feel bad because both are real traps. Silence lets the pattern compound; confrontation that indicts their character trips the threat response, and a threatened brain can't learn — it can only defend. You're not imagining the bind. It's built into how the situation is usually framed.

There's a third path: address what happened without putting the person's character on trial. It's harder to do in the moment, which is exactly why you script it in advance.

The mechanism

Microaggressions are brief, everyday indignities — often unintended — that communicate a slight toward someone in a marginalized group. Individually small, they accumulate into a real burden, and they hit three of the five SCARF social-threat domains hardest: Status (being diminished), Relatedness (being made an outsider), and Fairness (being treated by a different standard). The brain processes these as genuine threats.

Here's the trap, mechanically: if you respond by labeling the person as prejudiced, you trigger a severe amygdala hijack in them. Their thinking brain goes offline, and a hijacked brain cannot reflect, learn, or change — it can only defend. So the very response that feels most justified is the one most guaranteed to fail.

The way through is to separate intent from impact — to address what the comment did without claiming to know the person's heart — and to "call in" (educate) rather than "call out" (shame). Three scripts do this without tripping the alarm: asking for clarification ("Could you elaborate on what you meant by that?"), which forces the person to consciously unpack their own assumption; paraphrasing and reflecting ("It sounded like you were implying X — is that accurate?"); and addressing impact ("I know you likely didn't intend it this way, but when you used that phrase, it felt dismissive of my experience, and here's why"). And at the organizational level, micro-affirmations — small deliberate acts of inclusion — counteract the accumulation.

The operating system

Five steps to respond in a way that can actually land.

STEP 01

Name it to yourself first

Before responding, register what happened and which SCARF domain it hit — status, relatedness, or fairness. Naming it internally steadies you and clarifies what you actually want to address, so you respond to the specific impact rather than to a wave of vague anger.

The internal naming also confirms you're not "overreacting" — the threat response is real and proportionate to a real slight.
STEP 02

Separate intent from impact

Decide, deliberately, to address what the comment did rather than to prosecute the person's heart. You don't have to concede they meant well — you just don't lead with "you're prejudiced," because that claim about their character is what triggers the hijack and ends the learning.

Impact is observable and arguable; intent is unknowable and defended to the death. Stay on the impact.
STEP 03

Use the clarification or paraphrase script

For a lighter touch that makes the person hear themselves, ask them to elaborate ("Could you say more about what you meant by that?") or reflect it back ("It sounded like you were implying X — is that right?"). Both force conscious deconstruction of the assumption, often doing the work without you having to make the accusation at all.

Asking someone to explain a microaggression out loud frequently makes them hear it for the first time — and retract it themselves.
STEP 04

Use the impact script when you need to be direct

When it needs naming plainly, use the impact format: "I know you likely didn't intend it this way, but when you used that phrase, it felt dismissive of my professional experience, and here's why…" The opening clause keeps their prefrontal cortex online; the rest tells them precisely what landed and why it mattered.

"I know you likely didn't intend it this way" isn't letting them off the hook — it's the oxytocin cue that keeps them able to hear the rest of the sentence.
STEP 05

Build micro-affirmations into the climate

Individual responses address incidents; micro-affirmations address the pattern. Practice small, concrete acts of inclusion — visibly crediting a colleague's idea, actively drawing in a quieter or marginalized voice, naming a specific contribution in public. Calendar three this week. The everyday climate is built one of these at a time.

Make them specific and scheduled, not aspirational. "Credit Maria's idea in Thursday's review" beats "be more inclusive."

The printable: the response scripts

Print it. Have the words ready before you need them.

MICROAGGRESSION RESPONSE SCRIPTS
Address the impact. Don't indict the character.

CLARIFY
"Could you elaborate on what you meant by that?"
Forces them to unpack the assumption.
PARAPHRASE
"It sounded like you were implying [X]. Is that accurate?"
They often hear it for the first time.
ADDRESS IMPACT
"I know you likely didn't intend it this way, but when you said that, it felt dismissive, and here's why…"
The opening clause keeps their PFC online.
MICRO-AFFIRMATIONS
Credit ideas · draw in quiet voices · name contributions publicly.
Calendar three this week. Specific, not aspirational.

THE HUMAN FREQUENCY · FIND COMMON GROUND

Go deeper

This page is the surface. Each layer below goes further.

Common questions

What is a microaggression?
A microaggression is a brief, everyday verbal or behavioral indignity that communicates a hostile or derogatory slight toward a marginalized group — often unintentional. Individually small, they accumulate, and they threaten the SCARF domains of Status, Relatedness, and Fairness, which the brain registers as genuine social threat.
How do I respond to a microaggression without making it worse?
Separate intent from impact, and 'call in' rather than 'call out.' Directly labeling someone as prejudiced triggers an amygdala hijack and ends the conversation. Instead use one of three scripts: ask for clarification, paraphrase and reflect what you heard, or address the impact on you while acknowledging their likely intent. The goal is education, not public shaming.
What's the difference between calling in and calling out?
Calling out is public confrontation aimed at exposure or shame; it usually triggers defensiveness and shutdown. Calling in is a more private, educational approach that invites the person to reconsider without indicting their whole character. Calling in keeps the prefrontal cortex online, which is the only state in which someone can actually learn from the feedback.
What are micro-affirmations?
Micro-affirmations are small, subtle, deliberate acts of inclusion that counteract the accumulation of microaggressions — visibly validating a colleague's idea, actively asking for input from marginalized members, or publicly acknowledging specific contributions. Institutionalizing them shifts the everyday climate, not just individual incidents.

Continue the wiki

More operating systems most readers of this page also need.

SOURCES & CITATIONS

All claims on this page are cited in the difficult-conversations work, Chapter 11: Navigating Workplace Microaggressions. Underlying concepts:

  • Sue, D. W. and colleagues — the concept and taxonomy of microaggressions.
  • Rock, D. — the SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness) as social-threat domains.
  • Rowe, M. — micro-affirmations and micro-inequities in organizational climate.

For the full framework set, see The Human Frequency store.

Where we get our research: We cite peer-reviewed work from PubMed (pubmed.ncbi.nlm.nih.gov), ScienceDirect (sciencedirect.com), and indexed journals via their publishers (Cell Press, Lancet, JAMA Network, JBI). For framework owners we link directly to their published work — the Gottman Institute, polyvagal theory (Porges), and Harvard's Program on Negotiation are the most common. See our editorial policy for the full sourcing standard.