AceShowbiz - You've rehearsed the conversation in your head six times. Your coworker keeps missing deadlines, and it's starting to make your team look bad. But every time you think about saying something, you picture the awkward silence, the defensive eye roll, or worse — the Slack screenshot forwarded to three other people. So you say nothing.

Here's the problem with that strategy: research from Gallup found that only about one in four employees strongly agree they receive useful feedback. Meanwhile, the same body of research links regular, honest feedback to higher engagement and lower turnover. The gap between what we know is good for us and what we actually do is basically the entire story of workplace communication.

Giving feedback to peers is harder than giving it to direct reports, because you have no authority to fall back on. You can't pull rank. You can only build trust, choose your words carefully, and hope the other person hears you. The good news is that this is a learnable skill — and the people who master it tend to be the ones who get promoted, because they're the ones others trust with the truth.

Ask Permission Before You Drop the Bomb

The single biggest mistake people make with peer feedback is ambushing someone. You corner a coworker after a meeting and unload, and their brain immediately shifts into defense mode. They stop listening and start preparing their rebuttal. Nothing you say after that lands.

Instead, open with a small ask. Something like: "Hey, can I share something I noticed about the presentation? I think it could help next time." That one sentence does a surprising amount of work. It signals that feedback is coming, gives the person a chance to brace themselves, and — crucially — makes them a participant rather than a target. Psychologists call this "autonomy support," and it's the difference between someone hearing you and someone hardening up.

If they say "not right now," respect it. Offer to circle back later. A delayed conversation that goes well beats an immediate one that goes sideways. You're building a pattern of trust, not winning a single argument.

Practical tip: Before any feedback conversation, ask yourself: "Would I want this delivered to me in front of others, or privately?" The answer is almost always privately — and that's where you should start.

Be Specific, and Describe What You Saw, Not Who You Think They Are

"You're not being a team player" is not feedback. It's a character judgment dressed up as feedback, and it will make your coworker defensive in about half a second. The alternative is describing observable behavior: "In Tuesday's meeting, you said you'd send the draft by Thursday, and it came in Monday. Two other people were waiting on it."

Notice what's different. The second version is factual, verifiable, and impossible to argue with. It doesn't say your coworker is lazy or careless — it describes a specific event and its impact. That's the formula: situation, behavior, impact. It's the backbone of almost every credible feedback framework, from the Center for Creative Leadership's SBI model to whatever your company's HR team has been trying to teach you at onboarding.

The "impact" piece is the one people skip, and it's the one that matters most. Your coworker may not care that the draft was late in the abstract. But they probably do care that two teammates were blocked, or that a client saw a delay. Connecting the behavior to a real consequence makes the feedback land without you having to raise your voice or moralize.

Swap "Always" and "Never" for Actual Data

Words like "always" and "never" invite a fight. Your coworker will immediately think of the one time they didn't do the thing and use it to dismiss everything you said. Instead, bring a concrete example or two. "Three of the last four standups, you arrived about ten minutes late" is much harder to argue with than "you're always late."

Focus on the Work, Not the Person — and Keep the Ratio Human

There's a well-worn piece of advice floating around that you should sandwich criticism between two compliments. Most people who've received a sandwich know it feels manipulative — you can taste the criticism coming from a mile away, and the praise on either side feels like a bribe. Skip the sandwich. It doesn't fool anyone.

That said, the underlying instinct behind the sandwich is right: feedback shouldn't feel like an ambush of pure criticism. If the only time you talk to a coworker is to point out a problem, they'll start avoiding you. The fix isn't fake praise — it's a steady baseline of genuine, specific acknowledgment over time. When you tell someone "your summary of the client call last week was excellent, the way you framed the tradeoffs really helped" and you actually mean it, they'll trust you more when you have something harder to say.

This matters more than people think. Research on teams consistently shows that psychological safety — the shared belief that you can speak up without being punished — is the strongest predictor of team performance. You can't build that if feedback only flows in one direction, downhill and negative. It has to feel like part of the normal rhythm of work, not an event.

Practical tip: Aim for roughly five positive or neutral interactions for every one corrective conversation with a given peer. Not because you're keeping score, but because it keeps the relationship balanced enough that feedback doesn't feel like an attack.

Pick the Right Channel — and the Right Moment

Some feedback belongs in a Slack message. Some absolutely does not. A quick "hey, the doc link is broken, might want to fix before the client sees it" is fine in chat. A conversation about someone's communication style or reliability is not — it needs a face-to-face or at least a video call, where tone and body language can do their work.

Timing matters just as much. Feedback delivered in the heat of a tense meeting tends to escalate. Feedback delivered three weeks after the fact feels like a grudge. The sweet spot is usually within a day or two, privately, when neither of you is hungry, rushed, or still annoyed about something unrelated. If you're the one who's upset, wait until you've cooled off. Your goal is a useful conversation, not a satisfying one.

Also consider whether you're the right person to deliver it. If the issue is a pattern across the whole team, it might be a manager conversation, not a peer one. If it's a one-off, a quick note might be enough. And if you're not sure whether something is even a problem, ask a question instead of making a statement — "I noticed the timeline shifted — was that intentional?" often gets you further than an accusation.

Listen, Then Make It a Two-Way Street

Feedback isn't a monologue. After you've said your piece, stop talking. Ask: "How does that land?" or "What's your take on it?" Give the other person room to explain context you didn't have — maybe the deadline moved and nobody told you, or there's a personal situation you don't know about. You don't have to abandon your point, but you do have to be genuinely open to being wrong.

This is where a lot of well-intentioned feedback falls apart. People deliver their observation like a verdict and then wonder why the other person got defensive. The moment you invite their perspective, you shift from judge to collaborator. Even if you still disagree at the end, the relationship survives — and often improves, because the other person now knows you're someone who listens.

And be willing to receive feedback in return. If you're going to tell a coworker their meetings run long, you should be open to hearing that your emails are cryptic. The people who give feedback well are almost always the people who take it well. It's a two-way street, and the traffic has to actually flow.

Close the Loop Later

A week or two after the conversation, follow up. "Hey, I noticed the last two standups were right on time — thanks for that." This small act does two things: it confirms you weren't just nitpicking, and it shows you're paying attention to progress, not just problems. It's the difference between feedback that feels like a complaint and feedback that feels like support.

Know When to Escalate — and When to Let It Go

Not every issue is yours to solve. If you've had the conversation once or twice and nothing changes, and the behavior is genuinely affecting the work, it's time to loop in a manager — not as a tattletale, but as someone who can actually change the incentives. Frame it as a request for help: "I've talked with Jordan twice about the handoff delays and it's still happening. Can we figure out a better process?" That's a very different message than "Jordan is a problem."

On the flip side, some feedback isn't worth giving. If the issue is a personal preference — they write long emails, they like to talk through things out loud, they use a different formatting style — and it isn't actually hurting the work, let it go. Feedback is a limited resource. Spend it on things that matter, and you'll be taken seriously when it counts.

The bottom line: giving effective feedback to peers comes down to a few unglamorous habits. Ask first. Describe behavior, not character. Connect it to impact. Listen more than you talk. Follow up. None of it is dramatic, and none of it requires a personality transplant. It just requires the willingness to have a slightly uncomfortable conversation instead of letting resentment quietly build. The coworkers who do this well are the ones everyone wants on their team — and the ones who get trusted with the interesting work.