Workplace Harassment — National Origin & Cultural Respect

A Senior Employee Gives Everyone Nicknames — but the One for Our Immigrant Colleague Mocks Their Actual Name. They Say It’s Affectionate. The Colleague Goes Quiet When It’s Used. Is That Harassment?

A real workplace compliance scenario — with three decision options and the right answer.

The Situation

A senior employee — well-liked, influential, long-tenured — has a habit of giving everyone on the team informal nicknames. Most are playful abbreviations or inside jokes and are genuinely well-received. But the nickname they use for Arjun, a newer colleague who recently immigrated, is a phonetic parody of Arjun’s actual name. The senior employee says it’s affectionate: “He doesn’t mind — it’s just how I am with people I like.” Other team members have adopted the nickname.

You’ve noticed that Arjun goes quiet and slightly tense whenever the nickname is used in team settings. He hasn’t raised a complaint and when you asked him privately how things were going, he said “fine” and changed the subject. The senior employee has not been approached about it.

Choice ASay nothing. Arjun hasn’t complained, the senior employee says it’s affectionate, and getting involved in someone else’s workplace dynamic — especially involving a well-liked senior colleague — is not your place.

Choice BReport the situation to HR based on what you have observed — the nickname, the pattern of adoption by other team members, and Arjun’s visible discomfort. A nickname that phonetically mocks a colleague’s actual name based on national origin is a harassment concern regardless of the intent behind it.

Choice CSpeak privately to the senior employee and ask them to stop using the nickname — handle it informally before involving HR. If they continue after being asked, then escalate.

The Right Call

Choice B — Report to HR. Choice C may be a reasonable first step in some organizations, but it is insufficient on its own given the seniority dynamic.

The core issue with Choice C is the power dynamic. Approaching a senior, well-liked, long-tenured employee privately and asking them to stop a behavior they believe is affectionate requires that employee to receive the feedback gracefully and act on it immediately. The nickname has also already spread to other team members — a private conversation with the originator doesn’t stop the adoption. HR has the authority to address both the source and the spread in ways a peer conversation cannot. Choice A is a failure to act on an observed harassment concern — and the rationale (Arjun hasn’t complained; the senior employee says it’s fine) is a common rationalization for inaction that doesn’t change the compliance obligation.

Intent and impact are different standards — and both matter.

The senior employee genuinely believes the nickname is affectionate. That belief is not in dispute. But harassment law and most workplace harassment policies apply an impact standard alongside an intent standard — the question is not only what the senior employee meant, but how a reasonable person in Arjun’s position would experience being referred to by a phonetic mockery of their name in a professional setting. Intent shapes culpability and remediation; it does not determine whether conduct violated the policy.

Arjun going quiet is a signal — not evidence of comfort.

“He doesn’t mind” is the observer’s interpretation of Arjun’s quietness. Going quiet when a name-mockery nickname is used in a team setting is a withdrawal behavior — a signal that the person has decided absorbing the discomfort is safer than raising an objection. The power differential between a well-liked senior employee and a newer immigrant colleague is exactly the dynamic that makes the absence of complaint unreliable as evidence that the conduct is acceptable.

The nickname spreading to other team members escalates the harm.

What started with one person has become a team-wide pattern. Every person who adopts the nickname becomes part of the conduct pattern — even if they don’t know that Arjun finds it uncomfortable. The normalization of the nickname in the team environment is itself a harm that extends beyond any individual incident, and it requires an organizational response rather than a peer-to-peer conversation.

Is national origin harassment covered by federal law?

Yes. Title VII of the Civil Rights Act prohibits harassment based on national origin — including mockery of accents, names, cultural practices, and ethnic backgrounds. The EEOC has issued specific guidance on national origin harassment covering linguistic characteristics, accent, and name mockery as forms of harassment. The conduct does not need to be physically threatening or severe to be illegal — pervasiveness or a hostile environment is sufficient.

Does it matter that the targeted employee hasn’t complained?

For purposes of organizational policy and the bystander’s reporting obligation, no. An organization’s harassment policy creates obligations for observers and the organization — not only for the target. The target’s failure to complain is often a result of power dynamics, concern about retaliation, or uncertainty about whether the behavior qualifies — not a signal that the behavior is acceptable. The bystander’s independent reporting obligation exists regardless of the target’s choices.

What’s the difference between a nickname that’s just playful and one that constitutes harassment?

Context and content. A nickname that is accepted by the recipient, not based on a protected characteristic, and not experienced as demeaning is unlikely to constitute harassment. A nickname that mocks a colleague’s actual name in a way that highlights their national origin or ethnicity — particularly when applied to a newer employee by someone more senior — carries the elements that courts and HR investigations look for: connection to a protected characteristic, power differential, and an impact the recipient has not consented to.

How to Use This Scenario in Training

Recommended for all employees — particularly effective for teams with diverse workforces and for managers who need to understand that seniority doesn’t reduce the compliance obligation. The key recognition skill is distinguishing between impact and intent—and understanding that an employee’s silence does not indicate comfort when power dynamics are present.

This scenario is built on the Decision Readiness Engine™ — the Xcelus methodology that trains employees to recognize a compliance moment, pause under pressure, and take the right action before the rationalization wins. Learn how it works →

More Workplace Conduct Scenarios

Use these scenarios in your monthly compliance program.

The Compliance Reinforcement Kit™ delivers scenario-based training like this one every month — with weekly employee emails and a  Manager Discussion Guide. Starting at $3,500/year. No LMS required. See how it works →

Want These Scenarios in Your Program?

Xcelus builds scenario-based harassment training covering national origin, cultural respect, and bystander obligations — for all employees and managers.

View Compliance Programs →
Contact Xcelus