PM Feedback Guide
(2026 Edition)
The SBI model, 4 feedback scripts (critical, positive, upward, asking), and 6 rules for receiving feedback without defensiveness.
Build PM Feedback Muscle Daily — Free →The SBI Feedback Model
Situation
Anchor the feedback in a specific moment. 'In yesterday's sprint planning' — not 'you generally tend to.'
Behaviour
Describe what the person did — observable actions. 'You jumped in to answer before the designer finished.'
Impact
Explain the effect on others, the team, or outcomes. 'It felt like their perspective wasn't heard, which made them less forthcoming later.'
4 Feedback Scripts
Giving critical feedback to your engineer lead
❌ Don't say
“You need to be more responsive in reviews.”
✅ Say instead
“In yesterday's design review, when you pushed back on the wireframe without explaining why, the designer felt dismissed. Next time, can you share your reasoning? It'll help us converge faster.”
Giving positive feedback (make it specific)
❌ Don't say
“Good job on the launch!”
✅ Say instead
“In the launch retro, how you acknowledged the team's efforts specifically by name — that was well done. It built trust and motivated people to take ownership on the next project.”
Giving upward feedback to your manager
❌ Don't say
“I need more direction.”
✅ Say instead
“In our last 1:1, I left unclear on whether to prioritise A or B. In the future, could we end each 1:1 with the one thing I should most focus on? It would help me act faster with less back-and-forth.”
Asking for feedback
❌ Don't say
“Any feedback for me?”
✅ Say instead
“I've been working on being more decisive in meetings. From the sprint review yesterday, did that come through? What could I do differently next time?”
6 Rules for Receiving Feedback
Listen without interrupting. Even if the feedback is 'wrong,' hear the full version first.
Ask clarifying questions before defending: 'Can you give me a specific example?'
Assume good intent. Most feedback is given because the person wants you to grow, not to hurt you.
Separate the content from the delivery. Even poorly delivered feedback often contains real signal.
Say 'thank you' — even if you disagree. Feedback takes effort to give; acknowledge it.
Follow up. 2 weeks later: 'You mentioned X. I've tried Y. How's that landing for you?'
FAQ
How often should PMs give feedback to their team?
Small feedback weekly, structured feedback quarterly. Weekly small: 'that was a great catch in the review' or 'next time, can you push on X earlier?' Quarterly structured: sit-down conversations about growth, strengths, and areas to develop. PMs who only give feedback during annual reviews miss 48 opportunities to help their team grow — and their team notices the absence.
How do you give critical feedback without damaging the relationship?
Three rules: (1) Start with curiosity ('I want to understand what happened in that moment'), (2) Use SBI to stay specific and non-judgmental, (3) Show you're invested in their success. The feedback that damages relationships is usually vague, emotional, or delivered with hidden agendas. Feedback that's specific, timely, and clearly well-intentioned strengthens relationships more often than it hurts them.
What's the biggest feedback mistake PMs make?
Saving feedback for reviews. Feedback delivered 3 months after the event has lost most of its value — the person may not even remember the specific moment. Feedback is most useful within 48 hours of the behaviour. PMs who build a habit of quick, frequent, small feedback create teams that grow faster than teams running on periodic formal reviews alone.
Practice Hard PM Conversations
Daily scenarios on feedback, tough conversations, and stakeholder alignment.
Start Free Trial →