I used to dread the end-of-year feedback season. Not because I hated hearing about my own performance—I could handle that. It was the moment I had to figure out how to give feedback at work properly to colleagues I genuinely liked, without accidentally burning bridges.
Last December, my inbox flooded. As a project manager, I had worked with a dozen people across different teams, and suddenly everyone needed “a few honest observations.” One message I’ll never forget: “I’d love 2-3 things I’ve done well and one thing I could improve. No pressure.” No pressure, right? My stomach knotted up anyway.
That’s when I started experimenting. I made mistakes. I gave feedback so cushioned with praise that the real message got lost. Once, I told a developer he should “be more strategic,” and the blank stare he gave me told me he had no clue what I meant—and honestly, neither did I. I’ve also watched colleagues deliver feedback that felt like a checklist audit, and the room went ice cold.
What I landed on, after a lot of trial and error, is a way of speaking that feels human: honest, specific, and surprisingly safe for both sides. If you’re staring at that blank feedback form right now, here’s what I’ve learned.
Quick note on me: I’m not an HR professional. I’m a project manager who’s given and received hundreds of feedback conversations—some badly, some well. These are the patterns that survived.
Quick Ways to Give Feedback at Work Properly Today
If you’re about to give feedback and don’t know where to start, try these:
- Acknowledge the awkwardness right away. It disarms the other person.
- Lead with something you genuinely admire about their work style—with a specific example.
- Frame your growth suggestion as if you were in their shoes, not as a verdict.
- If you only have an hour of shared work, say so. Don’t invent feedback.
- Ask what they’re hoping to get from the feedback before you dive in.
Why Is It So Hard to Give Honest Feedback at Work?
The root problem is simple: when you give feedback to a peer, you’re not their boss. You have no authority to “coach” them. You’re risking a relationship you rely on every day. You might need their help next week, and here you are telling them they fall short in meetings. That social tension is real. I’ve sat across from a colleague I considered a friend, tried to mention that his emails come off as brusque, and watched his face shift into a careful, polite smile. I lost sleep that night.
The other piece is that many workplaces treat peer feedback like a performance evaluation task, not a conversation. People are “encouraged to seek out feedback,” as the corporate language goes, but they really want validation or ammunition for a promotion. If you deliver something too honest, it can end up in a file you didn’t intend. I learned to treat every request with care, because written feedback has sharp edges.
One Reddit user put it bluntly: “Feedback that is 100% positive is not feedback, it is stroking. But when they are your peers, there is a tendency for this to go bad.” I agree. The challenge is how to give feedback at work properly without it turning into either fluff or a confrontation.
How to Give Feedback at Work Properly Without Offending Anyone
After some messy attempts, I settled on a rhythm that feels less like evaluating and more like thinking out loud together.
First, set the container. I always ask what they’re hoping to get from the feedback. Do they want specific examples or just a general sense? That sets expectations.
Then share one thing you consistently appreciate. Not a vague “you’re great,” but a concrete moment. “Remember that client call where you re-explained the timeline without sounding defensive? That was masterful.” That gives them a real anchor.
For the improvement part, I never say “you should.” I pivot to “If I were in your situation…” This tiny shift takes me out of the judge’s seat and into a thinking partner role. For example, instead of telling a colleague she interrupts too much, I’ll say, “If I were leading that weekly sync, I think I’d try leaving a two-second pause after each person speaks, just to make sure everyone’s thought lands. That’s something I’ve had to watch in myself.” It lands differently. The feedback feels like shared learning, not a criticism.
Keep it to one growth area. Giving three strengths and one improvement is a decent ratio, but if you list three separate things to fix, it feels like an attack.
Add a caveat. I try to mention that I’m sharing my own subjective view, not absolute truth. “This is just my take—you might see it completely differently.” That little caveat makes the whole exchange safer.
End with an offer. I always ask if they’d like to discuss it further or just have it written. Giving them control over what happens next honors the relationship.
The “If I Were You” Feedback Method
This is the framework I wish I’d discovered years ago. I borrowed it from a Reddit comment that reframed everything. The core idea: never present your feedback as a diagnosis. Present it as what you would do if you were in their exact position, facing the same constraints.
The script works like this: “If I were in [situation], I think I would [specific action] because [reason]. This might help me avoid [potential downside].”
Here’s a real example I used with a junior PM who was drowning in meeting notes. I said, “If I were managing this project’s weekly update, I think I’d record a two-minute voice memo after each meeting instead of typing notes, because my brain processes faster when I talk. That might save me from those late-night document cleanups.” She tried it, and it worked. No one felt defensive.
Why this works: It removes the power dynamic. You’re not saying they’re wrong. You’re saying, “Here’s what I’d try if I were you.” It invites them to consider an idea without needing to defend their current approach. It also keeps the conversation hypothetical and low-stakes. I’ve used this in meetings, in one-on-ones, and even in a quick Slack message. It fits anywhere the risk of offending is high, which is pretty much all peer feedback.
When You Barely Worked Together: Giving Feedback to Peers You Don’t Know Well
Sometimes a colleague requests feedback, but you’ve only crossed paths on a single project or a handful of emails. In those cases, inventing growth areas is worse than saying no. I used to try the vague “you could be more strategic” line, and it never helped.
Now, I’ll say something like, “I value our working relationship, but I honestly haven’t observed enough of your day-to-day to give meaningful feedback. I’d rather not make something up that won’t help you. Maybe ask Janet, who collaborated with you on the big launch?” Turning away a request gracefully is a form of respect.
If I do have one specific positive observation, I share it and leave it at that. “One thing that stood out during our sprint was how you kept the team focused when the requirements changed. That was impressive.” No need to force a “could improve” if there isn’t one. People can smell B.S. from a mile away.
Written vs. Verbal Feedback: Choose Your Medium Wisely
I have a personal rule now: serious constructive feedback is never written down unless I’m ready for it to be screenshot and forwarded to a manager’s manager. That thought might sound paranoid, but it’s happened. A well-meaning note about someone needing to “communicate deadlines better” can turn into a permanent stain in a performance file.
So I deliver the nuance in a quick call or over coffee. I might follow up with a brief, positive summary in writing, but the messy, real conversation stays verbal.
For written feedback requests, I keep it light and future-oriented. “You’re great at rallying the team around a deadline. One thing I might try if I were you is sending a one-sentence status update mid-week, just to keep cross-functional partners in the loop.” Short, actionable, and not overly critical. That way, if it’s ever quoted, it reads like a friendly suggestion, not a flaw.
FAQ: How to Give Feedback at Work Properly
Q: How do I give feedback to someone more senior than me?
A: Use the “If I Were You” method. Frame it as a suggestion, not a critique. Say something like, “I noticed this approach worked well on a past project. I wonder if it might be useful here?” Keep it humble and specific.
Q: What if the person gets defensive?
A: That’s normal. Pause and acknowledge it. “I can see this is landing in a way I didn’t intend. I’m sharing this because I want to help, not criticize. Do you want me to explain more, or should we pause?” Giving them an out often lowers the temperature.
Q: How much positive feedback do I need before giving criticism?
A: A 3:1 ratio is a decent guideline—three specific positives to one area for growth. But the positives must be genuine, not filler. People notice when you’re just padding.
Q: Is it better to give feedback in person or in writing?
A: For anything constructive, in person (or on a call). Written feedback lacks tone and context. Save writing for positive notes or simple, factual observations.
Q: What if I don’t have any constructive feedback to give?
A: Then don’t invent it. It’s better to say, “I really appreciated working with you on X. I don’t have any suggestions for improvement—it was a smooth collaboration.” Honesty beats forced criticism every time.
One Last Thing
That knot in your stomach when the feedback request lands? It’s a sign you care. Honestly, that’s the most important part. The best feedback comes from wanting someone to succeed—not from a checklist.
The next time you’re staring at that blank form, remember: you’re not a performance evaluator. You’re a coworker who sees a few things worth mentioning. Say them kindly. Then go grab coffee together.
References
- Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin’s Press.
- Stone, D., & Heen, S. (2014). Thanks for the Feedback: The Science and Art of Receiving Feedback Well. Viking.
- Grant, A. (2019). The Right Way to Give Negative Feedback. Harvard Business Review.
