Communication

How to give feedback to a coworker when you're new

Learn how to give feedback to a coworker without sounding bossy or awkward. Use clear scripts and simple rules to keep work relationships strong.


Cartoon of young new hire in their early twenties, short curly hair and a burnt-orange cardigan over a plain tee, sits at a d

You spot the error in a shared doc. It’s small. It’ll take you seconds to fix. And you spend the next stretch of your afternoon rehearsing a message in your head, because every version sounds like you’re picking a fight with someone who has been here longer than you.

Learning how to give feedback to a coworker when you’re new is mostly about dropping the drama. You don’t need authority. You need one clear observation, one sentence about why it matters, and a way forward. The person-versus-problem framing gets repeated so often that it stops meaning anything. Here’s the version that actually works.

How to give feedback to a coworker: decide whether this gets a message at all

Before you type, run the case.

One-time slip or a pattern? A reliable peer misses a deadline once, let it go. The same task slips twice, say something.

Can you fix it yourself in under five minutes? Fix it. Correct the broken formula, mention it in passing, move on with your day.

Does it affect the team’s work or the client’s trust? Then speak up. If it’s a font you’d have chosen differently, that’s a preference, and your preferences can wait.

New hires get this wrong in one of two ways. Some swallow everything and turn quietly resentful, then one day send a message that reads like a legal complaint. Others flag everything and become the person nobody wants on their project. The three questions keep you in the middle. If you’re still calibrating where your judgment ends and someone else’s begins, saying no without saying it out loud uses the same muscle.

The three failure patterns that make feedback weird

Over-apologizing. Drop the sorry and state the fact.

Passive-aggression. No rush, whenever you get to it, when you needed it yesterday. Name the deadline. A vague nudge trains your coworker to ignore you, which is a strange thing to teach someone.

Dumping. Three errors, formatting, and stale data in one message. Too much lands as an attack, and the person stops reading halfway through. Pick the one thing that matters most and lead with it. The rest can wait a week.

There’s a quieter one too. You hedge so hard the ask disappears entirely, and your coworker reads a fog of if you get a chance, no pressure and moves it to the bottom of the pile. If you catch yourself softening every sentence, ask for help politely instead of hinting at it. Same words, less fog.

What a Slack message looks like

Async messages are where most peer feedback happens, and where most of it goes wrong. Start with the shared goal, not the mistake. Name the gap. Offer a way forward.

The last question is doing real work. It turns a correction into a collaboration. If you’re the one sending a lot of these, updates like a pro keep the same tone without the awkwardness.

How do I give feedback to a coworker without sounding like I’m bossing them around? Lead with the shared goal, name the gap, and offer to help fix it. You’re flagging a problem in the work, not grading the person.

Say it live when the stakes are higher

A phone call or a quick video chat beats text when the person is likely to take it badly, or when the stakes are higher than a shared sheet. Open with a neutral observation. State the impact, not the blame. Ask for their perspective. Agree on a fix.

What happened there is the line that saves the conversation. It keeps you curious instead of prosecutorial, and half the time the answer is something you didn’t know. If you’re on the receiving end, this is where ask for help beats defending the draft.

The word itself trips people up

Treat feedback as a neutral label for information that improves the work, not a verdict on the person. In practice:

  • I have some feedback on the agenda for tomorrow’s meeting.
  • Can I give you some feedback on the Slack message you sent the client?

Notice neither is an apology. Each one announces what’s coming, so the other person isn’t ambushed by a wall of text late on a Friday. That small heads-up does most of the work. As I wrote in Cubicle To Corner Office, in the chapter on interacting with managers, feedback is not a criticism of you as a person but an assessment of the task at hand. Same holds sideways, peer to peer.

A note for the manager reading this

If you want your team to trade feedback without drama, model it. In your next 1:1, mention it out loud: I gave Sarah some feedback on her report yesterday, and she handled it well. That one sentence tells everyone this is normal here. Set the norm directly too: on this team, we flag things early so nobody gets surprised at review time. And if your team is remote and quiet, reader asks about camera norms is worth a skim before you assume silence means agreement.

There’s more on the giving and receiving side in the paperback of Cubicle To Corner Office.

What if my coworker gets defensive? Ask what happened before you push a fix. Half the time there’s a reason you didn’t know, and asking keeps the conversation from turning into a fight.

Put the small, low-stakes fixes in a Slack message. Send it. Then go back to your actual work.

Filed under: Communication , Collaboration

Cubicle To Corner Office by Mike Halpert, book cover
From the book

Cubicle To Corner Office

The 317-page playbook for the transition from student to professional.

Comments
—comments

Join the conversation

Real readers (and Mike) reply in here. The number next to each comment is its upvote score — sign in with just a display name to add your vote or post a reply. No email or password required.

← Back to all writing