The Mistake of Using ''We'' When You Really Mean ''You

The meeting room is cold. You’re sitting opposite your direct report, a decent performer who has been dropping the ball. The cursor on your screen blinks, waiting for the notes you’re supposed to be taking. You’ve rehearsed this. Be supportive, be collaborative. You open your mouth and the practised words come out: “I think we need to be more careful about the details on these client reports.” The person nods, a little too quickly. They agree. And in that moment, you both know nothing will change. You leave the room and head back to your desk, typing into your search bar: “my direct report isn’t taking ownership.”

This isn’t a failure of courage. It’s a communication trap, a specific kind of mixed message that feels like the right thing to do but is guaranteed to fail. You’re trying to soften a direct criticism by wrapping it in the language of shared responsibility. But instead of softening the blow, you’ve made the message impossible to act on. You’ve created a conversational double bind: you’re telling them there’s a problem to fix, but you’re also telling them it’s not entirely their problem to fix. So they do nothing, and you get more frustrated.

What’s Actually Going On Here

When you use “we” to refer to a problem that belongs to one person, you are diffusing responsibility. It’s a logical move, driven by a desire to avoid a direct confrontation and preserve the idea of being a supportive “team player.” Your brain is trying to protect you from the social discomfort of accusation. The problem is, you’re not just protecting yourself; you’re protecting the other person from the clarity they need to actually improve.

This vagueness creates a state of plausible deniability for everyone involved. The direct report hears “we need to be more careful” and thinks, “Right, the team has been a bit sloppy. I’ll keep an eye out.” They don’t hear, “Your last three reports contained significant errors that I had to fix.” You, the manager, can tell yourself you’ve addressed the issue. You had the conversation. But you haven’t delivered the one thing that allows for change: a clear, unambiguous statement of observation, impact, and expectation.

This pattern is often reinforced by the organisation itself. Cultures that prize harmony over clarity, or that penalise managers for “demotivating” their staff, create powerful incentives to speak in these vague, collective terms. People get promoted for being seen as collaborative leaders, not for having the difficult, specific conversation in a one-on-one. So the system quietly rewards the very behaviour that ensures problems never get solved, leaving competent people like you feeling like you’re taking crazy pills.

What People Usually Try (and Why It Backfires)

You know the vague “we” isn’t working, so you try a different approach. The problem is, most of the standard moves are just different flavours of the same avoidance.

• The Appeal to Abstract Values. You say something like, “We’re a team that values excellence, and we all need to be demonstrating that.” This feels like you’re raising the standard, but it’s a platitude. It lets the person with the specific issue hide in the group and avoid personal accountability.

• Making It About the Process. You say, “Let’s review our QA process. Maybe we can build in another checkpoint.” This is a great move if the process is actually broken. But if the process is fine and one person is skipping a step, you’re now adding bureaucratic overhead for the entire team to manage one person’s performance issue.

• The Upbeat Group Resolution. In a team meeting, you say, “Okay team, moving forward, let’s all double-check our work for these kinds of errors!” You sound like you’re taking charge of the problem. But you’ve just given the under-performer a perfect excuse to not change, because the problem has been publicly framed as a collective failure, not a personal one. The rest of the team knows exactly who you’re talking about, and now they resent you for not handling it directly.

The Move That Actually Works

The counter-intuitive move is to stop trying to make the message more palatable and start making it more clear. This isn’t about being harsh or aggressive. It’s about being precise. The real kindness isn’t softening the feedback; it’s delivering it in a way that the other person can actually hear, understand, and use.

The shift is to take full responsibility for your own perspective by using “I,” and to assign clear ownership for the action or behaviour to the other person by using “you.” This stops the conversation from being about a vague, shared problem in the ether and grounds it in a specific, observable reality between two people.

This feels more confrontational in the moment, but it is profoundly less so in the long run. By using “I” and “you,” you are defining the boundaries of the problem. “I observed this.” “This was the impact on me/the project.” “I need you to do this.” You are not judging their character or intent. You are stating a fact about your own experience and making a direct, respectful request. This clarity removes the confusing double bind and gives the other person a straightforward choice: they can either meet the expectation or not, but they can no longer pretend they don’t know what the expectation is.

What This Sounds Like

These are not scripts to be memorised, but illustrations of how to use “I” and “you” to create clarity instead of confusion.

• Instead of: “We need to make sure we’re hitting our deadlines.” Try: “I need to talk about the deadline for the quarterly report. You missed it by two days, which meant I had to present preliminary numbers to the board.”

  • Why this works: It connects a specific action (“you missed it”) to a concrete impact (“I had to present…”). It’s not an attack; it’s a statement of cause and effect.

• Instead of: “We should probably get ahead of communicating roadblocks.” Try: “When you realised the data wasn’t going to be ready, I needed you to tell me immediately.”

  • Why this works: It shifts from a vague, forward-looking wish (“we should be”) to a clear, past-tense need (“I needed you to”). It establishes a clear behavioural expectation for the future without being preachy.

• Instead of: “We have to do a better job of catching these errors.” Try: “I found three major typos in the final version you sent to the client. I need you to be the one who does the final proofread before anything goes out.”

  • Why this works: It clearly separates the observation (“I found”) from the required action (“I need you to”). The responsibility is no longer floating in the “we” space; it has been explicitly and calmly assigned.