'Not a Team Player' and Other Coded Firing Reasons

You raised a concern about safety, pay equity, or harassment at work.

A few weeks later, HR called you in and said you were being let go because you were "not a team player" or "not a culture fit."

The reason felt hollow—vague enough to mean anything, or nothing at all.

Here's what you'll learn in this article: how courts evaluate vague, coded, or shifting termination reasons, when those explanations become evidence of unlawful pretext, and what the McDonnell Douglas framework requires an employer to prove.

• The three-step burden-shifting test and why the employer's stated reason matters
• How vague language like "not a team player" is scrutinized in court
• When shifting or contradictory explanations suggest pretext

The McDonnell Douglas Framework: Why the Employer Must Give a Real Reason

Most retaliation claims are built on circumstantial evidence.

You won't find an email saying "I'm firing you because you complained." Instead, you'll find a reason that sounds plausible on its face—poor performance, culture fit, budget cuts—but doesn't line up with the facts.

That's where the McDonnell Douglas test comes in.

In McDonnell Douglas Corp. v. Green, 411 U.S. 792 (1973), the Supreme Court created a three-step process for evaluating discrimination and retaliation claims when there's no smoking-gun evidence.

Step one: You establish a prima facie case—protected activity, adverse action, and a causal link.

Step two: The employer must articulate a legitimate, non-retaliatory reason for the adverse action.

Step three: You get the chance to prove that the stated reason is pretextual—a cover story for the real, unlawful motive.

The framework doesn't decide the case. It just organizes who has to prove what, and in what order.

What Courts Mean by a "Legitimate, Non-Retaliatory Reason"

Under McDonnell Douglas, the employer's burden at step two is light.

They don't have to prove the reason was true. They just have to articulate it clearly enough to allow you to respond.

But the reason still has to be concrete.

Courts have said the explanation must be "clear and reasonably specific"—detailed enough that a fact-finder can evaluate whether it's believable and whether your evidence undermines it.

That's where coded language like "not a team player" starts to break down.

If the employer can't explain what made you not a team player, or point to specific incidents, the explanation may not meet the step-two standard.

Here's the thing:

A reason that's too vague invites the inference that the employer is hiding the real motive.

Examples of Vague and Coded Termination Reasons

These are phrases courts have scrutinized as potentially pretextual when an employer can't back them up with facts:

• "Not a culture fit"
• "Attitude problems"
• "Failure to mesh with the team"
• "Lack of commitment"
• "Not meeting expectations" (without stating what the expectations were)
• "Performance concerns" (with no prior documentation or warning)

None of these is automatically pretext. But each becomes suspect when paired with timing close to protected activity, a history of positive reviews, or the absence of contemporaneous documentation.

When Shifting Explanations Become Evidence of Pretext

Sometimes the reason changes.

In the termination meeting, the manager says "budget cuts." In the unemployment hearing, HR says "poor performance." In the EEOC response, the company says "insubordination."

Courts treat shifting explanations as red flags.

If the employer can't keep its story straight, a fact-finder can infer the employer is dissembling—making it up as it goes to justify a decision that was really retaliatory.

In Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133 (2000), the Supreme Court held that a fact-finder can reasonably infer intentional discrimination from the falsity of the employer's explanation, combined with the prima facie case.

Reeves rejected the idea that you must always introduce additional evidence beyond disproving the employer's reason.

If the jury doesn't believe the employer's story, and your prima facie case shows protected activity followed by termination, the jury can connect the dots.

Now, here's where it gets interesting:

A changing explanation is often more powerful evidence than a bad explanation that stays consistent. It suggests the employer knew the real reason couldn't be stated and scrambled to find something defensible.

Subjective vs. Objective Performance Reasons

Courts distinguish between objective, measurable criteria and subjective judgments.

Objective reasons include:

• Sales quotas you missed
• Attendance records showing tardiness
• Budget targets not met
• Written warnings for specific policy violations

Subjective reasons include:

• "Not a team player"
• "Bad attitude"
• "Doesn't fit our culture"
• "Lacks leadership presence"

Subjective reasons aren't illegal. Employers can fire based on subjective judgment.

But subjective reasons are easier to challenge as pretext, especially when the decision-maker can't articulate what the phrase actually means or cite examples.

If your employer says you were fired for "poor performance," but you were meeting all measurable targets and had no write-ups, the mismatch is evidence the stated reason is false.

Under Reeves, that falsity can support an inference that the real reason was your protected activity.

When Documentation (or the Lack of It) Matters

Employers often document performance problems before termination.

When they don't—and then cite performance as the reason in court—the gap is telling.

If you complained about discrimination on January 15 and were fired on February 1 for "performance issues" that were never mentioned in your last three reviews, that timeline speaks for itself.

Courts don't require documentation. But when an employer has a policy of documenting poor performance and doesn't follow it in your case, a jury can infer the employer knew the real reason was unlawful and skipped documentation to avoid creating a paper trail.

How Timing and Proximity Strengthen a Pretext Argument

A coded or shifting reason becomes even more suspect when the termination happens soon after protected activity.

If you filed an EEOC charge on Monday and were fired on Friday for being "not a culture fit," the temporal proximity is powerful circumstantial evidence.

Courts have repeatedly said that timing alone doesn't prove retaliation. But timing combined with a weak or contradictory explanation can be enough for a jury to find pretext under Reeves.

The closer the termination to the protected activity, the harder it is for the employer to argue coincidence.

Here's the thing:

An employer who had legitimate performance concerns months before your complaint but didn't act on them—then suddenly fires you two weeks after you report harassment—invites skepticism.

Why now? If the problem was real, why wait?

What Pretext Looks Like in Practice

Pretext is not a separate claim. It's the mechanism for proving the employer's stated reason was a lie covering an unlawful motive.

Here's how it plays out:

Scenario one: You complain to HR about unpaid overtime. Three weeks later, your manager fires you for "not being a team player." You ask what that means; the manager says "you know what you did." No prior warnings. No documentation. No examples.

That's a textbook pretext case. The reason is too vague to defend, and the timing is close.

Scenario two: You report sexual harassment. Two months later, you're terminated for "poor performance." Your last performance review was "meets expectations." Your metrics are on target. The company's progressive-discipline policy was ignored.

The employer's reason doesn't match the record. Under Reeves, the jury can disbelieve the explanation and infer retaliation.

Scenario three: You're fired for "attendance issues." The termination letter lists three tardies. At deposition, the HR director says the real reason was "failure to meet deadlines." At trial, the manager testifies it was "attitude."

Shifting explanations. Each one contradicts the last. A jury can infer none of them is true and the real reason was your protected activity.

Can an Employer Defend a Vague Reason?

Yes—but they have to add specifics later.

If the termination letter says "not a culture fit," but at deposition the employer provides detailed examples of conflicts with coworkers, missed deadlines, and emails showing unprofessional conduct, the reason becomes concrete enough to test.

You can still argue pretext by showing those incidents were minor, not policy violations, or tolerated in others.

But the vague label alone won't carry the day if the employer fleshes it out with facts.

The problem arises when the employer can't add detail—when the decision-maker is asked "What did 'not a team player' mean?" and responds "It was just a feeling" or "I don't recall specific incidents."

That's when Reeves comes into play: the jury can disbelieve the explanation and find retaliation.

For a deeper look at how courts evaluate whether an employer's explanation is credible, see Proving Pretext: When Employer Explanations Don't Hold Up.

The Role of Comparator Evidence

One way to prove a stated reason is pretext is to show the employer treated similarly situated employees differently.

If you were fired for being "not a culture fit," but a coworker who didn't engage in protected activity and had the same behavioral issues was not fired, that disparity is evidence of pretext.

Comparator evidence isn't required. But it's one of the most persuasive tools for showing the stated reason is a cover story.

But it gets better:

You don't need a perfect comparator. Courts recognize that no two employees are identical. What matters is whether the other employee was similar in all relevant respects—same role, same supervisor, same policy violations—and treated more favorably.

When Is a Coded Reason Not Pretext?

Not every vague termination reason is pretext.

If the employer provides contemporaneous documentation, witness testimony, and specific examples that align with the coded phrase, the reason may hold up even if the initial wording was imprecise.

Example: You're fired for "not meeting expectations." The employer produces emails showing you missed three project deadlines, a performance-improvement plan you signed, and testimony from two coworkers about work you didn't complete.

The phrase "not meeting expectations" was vague, but the underlying facts are concrete. That's not pretext—that's a poorly worded legitimate reason backed by evidence.

The difference is substance. A reason is pretext when the facts don't support it, when it shifts, or when the employer can't articulate what it actually means.

Why the McDonnell Douglas Framework Matters Here

McDonnell Douglas forces the employer to go on record with a reason before trial.

That reason gets locked in—usually in the EEOC position statement, the answer to the complaint, or early discovery.

If the employer changes the reason later, you can point to the earlier statements and argue fabrication.

For a step-by-step explanation of how the burden-shifting test works, see McDonnell Douglas Burden-Shifting: A Plain-English Walkthrough.

The framework also clarifies that once the employer states a reason, your job is no longer to prove retaliation directly. Your job is to prove the stated reason is false.

Under Reeves, proving falsity can be enough—if combined with your prima facie case—for a jury to infer the true motive was retaliation.

What Happens at Summary Judgment

Many retaliation cases are decided on summary judgment—before trial—when the employer asks the court to rule that no reasonable jury could find retaliation.

To survive summary judgment, you must show a genuine dispute of material fact about whether the employer's reason is pretext.

A vague, shifting, or contradictory reason often creates that dispute.

If you've pointed to:

• Temporal proximity between protected activity and termination
• Inconsistent explanations across documents or testimony
• Lack of documentation for a stated performance reason
• Comparator evidence showing others treated more favorably

...the court will typically deny summary judgment and let a jury decide whether to believe the employer.

Courts don't weigh credibility at summary judgment. If the employer's explanation is disputed, the case goes forward.

Frequently Asked Questions