How to Talk to an Employee About Their Negative Attitude

You’re in a team meeting, walking through the quarterly projections. You get to the slide on the new initiative, and from the far side of the table, you hear it: a heavy, theatrical sigh. A moment later, a colleague is mid-sentence when the same employee cuts in with, “We tried that three years ago and it was a disaster.” The energy in the room instantly curdles. Everyone looks down. You feel your jaw tighten and think, “I have to do something about this.” Later, at your desk, you find yourself typing some version of "how to give feedback on a bad attitude without a fight" into a search bar.

The situation feels impossible because you’re caught in a communication trap. You want to address the problem, but the problem you’ve named in your head, a “negative attitude”, is an unprovable judgment about their inner state. The moment you make the conversation about their personality, you’ve lost. They will defend their character, you will insist on your interpretation, and you will both walk away frustrated and entrenched. The conversation isn’t about their behaviour anymore; it’s about who is right. And that’s a stalemate.

What’s Actually Going On Here

The core issue is that you are reacting to a label (“negative attitude”) instead of specific, observable behaviours. An “attitude” is just a shorthand we use for a pattern of actions: sighing in meetings, consistently pointing out obstacles without offering solutions, speaking in a sarcastic tone, or dismissing colleagues’ ideas before they’re fully explained. Because you’ve bundled all these different behaviours into one vague label, you’re preparing for a fight about their identity, not a conversation about their actions.

This creates a self-sustaining loop that keeps you and the employee stuck. It works like this:

1. You observe the behaviour (e.g., they roll their eyes when you mention a new project).
2. You interpret it through the “negative attitude” label. You think, “There Mark goes again, being negative.”
3. You brace for conflict. The next time you talk to Mark, your tone is a little more guarded, your questions more pointed. You’re already expecting a problem.
4. Mark feels your tension. He senses he’s being managed with suspicion, not trust. In response, he becomes more defensive and withdrawn, which looks to you… exactly like more negativity.

The system is now perfectly calibrated to produce the very outcome you’re trying to prevent. You both feel justified in your approach because you are both just reacting to what the other person is doing. You feel you’re managing a difficult employee; he feels he’s working for a manager who has it in for him.

What People Usually Try (and Why It Backfires)

When caught in this loop, managers tend to reach for a few standard tools. They seem logical, but they almost always reinforce the problem.

• The Direct Accusation. You say: “Frankly, your attitude is becoming a problem for the team.” This goes wrong because it’s a direct assault on their character. It forces them to defend who they are, not what they did. The conversation immediately derails into a debate over whether they are, in fact, a “negative person.”

• The Vague Prescription. You say: “I need you to be more of a team player,” or “We need more positivity from you.” This backfires because it’s unactionable. It gives the employee no clear idea of what to do differently. What does “more positive” look like on a Tuesday morning in a budget meeting? Without specifics, it just sounds like you’re telling them to have different feelings.

• The Feedback Sandwich. You say: “You’re a brilliant analyst, but your negativity is dragging people down. Still, your reports are always excellent.” This fails because the praise feels like a disingenuous prelude to the attack. The employee dismisses the good parts and focuses solely on the criticism, feeling manipulated in the process.

• The Appeal to Emotion. You say: “Your comments are really hurting team morale.” While the impact on the team is real, framing it this way centers the conversation on other people’s feelings, which the employee can easily dismiss. They might reply, “I’m just being realistic. It’s not my fault if people are too sensitive.”

A Different Position to Take

To break the cycle, you have to adopt a different position. Stop being a mind-reader trying to diagnose their “attitude” and start being an observer describing the impact of their behaviour on the work. Your job is not to make them a happier or more optimistic person. Your job is to ensure their actions don’t derail projects, shut down collaboration, or make it impossible for the team to function.

This is a profound shift in intent. You are no longer trying to fix their personality. You are letting go of that entirely.

Your new position is this: You are the manager of a process. You are responsible for the team’s ability to talk, think, and work together effectively. Your intervention is not about the employee’s internal state; it’s about protecting the operational integrity of the team. You will hold them accountable for their observable behaviour, what they say and what they do, and its concrete effect on shared work. This frees you from the unwinnable argument about their attitude and grounds the conversation in your actual responsibilities.

Moves That Fit This Position

When you operate from this position, your language changes. The following are not a script, but illustrations of how you might sound when you’re focused on behaviour and impact, not personality.

• Describe, Don’t Characterize. Instead of “You were really negative in that meeting,” try: “In the planning meeting this morning, when Susan outlined the launch plan, you said, ‘That timeline is a fantasy.’ After you said that, two other people who were about to speak went quiet. I need to understand what risk you were flagging, because the effect was that it shut down the conversation.” This is data, not judgment. It separates their intent from the actual impact.

• State the Standard and the Gap. “One of our working agreements as a team is that we challenge the idea, not the person. Another is that when we identify a problem, we try to propose a solution. In the last few meetings, I’ve noticed you pointing out flaws without offering an alternative. That puts the entire burden of solving the problem back on the team.” This connects their behaviour to a shared, neutral standard of conduct, not your personal preference.

• Re-channel Their Energy. Often, the employee sees their “negativity” as “realism.” Use that. Instead of asking, “Why do you have to be so critical?” ask, “What data do you have that the rest of us are missing?” or “You seem to have spotted a significant risk here. Can you walk me through your thinking on that?” This move reframes their contribution from a complaint to a piece of critical analysis, and it invites them to participate constructively.

• Name the Pattern, Define the Need. “I’ve noticed a pattern that when we’re in the early stages of brainstorming, you tend to immediately point out why an idea won’t work. We absolutely need your eye for risk, but we need it at the right time. How can we make sure we get the benefit of your critical thinking without stopping new ideas from getting a fair hearing?” This acknowledges a potential strength while clearly defining the problematic behaviour and stating what you need instead.