Giving constructive feedback
How do I give honest feedback at work without hurting feelings or creating tension?
Projekt-Plan
Why: Effective feedback requires a balance between personal care and direct challenge to avoid being perceived as either aggressive or insincere.
How:
- Study Kim Scott’s 'Radical Candor' framework: aim for the top-right quadrant (Care Personally + Challenge Directly).
- Avoid 'Ruinous Empathy' (being too nice to be helpful) and 'Obnoxious Aggression' (being direct without caring).
- Internalize that feedback is a gift for the recipient's growth, not a personal attack.
Done when: You can explain the four quadrants of Radical Candor and identify your natural tendency.
Why: Using a structured model removes emotional bias and focuses the conversation on objective, observable facts.
How:
- Situation: Define the exact time and place (e.g., 'During Tuesday's client pitch').
- Behavior: Describe the observable action without judgment (e.g., 'You interrupted the client twice').
- Impact: Explain the result (e.g., 'The client stopped sharing their requirements, and we missed key data').
Done when: You have written down one practice SBI statement for a past situation.
Why: Modern research shows that sandwiching criticism between praise creates distrust and dilutes the actual message.
How:
- Recognize that recipients often ignore the praise while waiting for the 'but'.
- Commit to being direct and clear with your corrective feedback.
- Keep positive reinforcement separate from corrective sessions to ensure both are taken seriously.
Done when: You have committed to a direct-entry approach for your next feedback session.
Why: Vague feedback like 'you need to be more proactive' is unactionable and frustrating for the recipient.
How:
- Review your notes or project logs from the last 48 hours.
- Identify 1-2 specific instances where behavior did not meet expectations.
- Ensure the behavior is something the person can actually control.
Done when: You have a list of 2 concrete examples ready for the SBI model.
Why: Scripting prevents you from using 'always/never' exaggerations and helps you stay calm during the meeting.
How:
- Write out the Situation, Behavior, and Impact for each example.
- Use 'I' statements (e.g., 'I noticed...' or 'I felt...') to reduce defensiveness.
- Prepare a 'Feedforward' suggestion: what should they do differently next time?
Done when: A written script of max 150 words is ready.
Why: Feedback delivered in public causes shame and immediate shutdown; privacy is essential for psychological safety.
How:
- Book a quiet room or a private video call.
- Set the duration to 15-20 minutes (short and focused).
- Title the invite neutrally (e.g., 'Quick sync: [Project Name] feedback') to avoid pre-meeting anxiety.
Done when: A calendar invite is sent and accepted.
Why: Opening with your 'why' reduces the recipient's threat response.
How:
- Start with: 'I’m sharing this because I want you to succeed in this project...'
- Or: 'I value our working relationship and want to ensure we're aligned...'
- Keep this opening under 30 seconds.
Done when: The conversation has started with a clear, supportive purpose.
Why: Directness shows respect for the other person's time and intelligence.
How:
- Read or paraphrase your drafted SBI script.
- Pause immediately after stating the Impact to let the information sink in.
- Maintain neutral body language and a calm tone.
Done when: The core feedback has been delivered without 'softening' or 'sandwiching'.
Why: Feedback should be a dialogue; there may be context or obstacles you are unaware of.
How:
- Ask: 'What is your perspective on this?' or 'What was happening for you in that moment?'
- Listen without interrupting for at least 2 minutes.
- Summarize their point to show you understood (e.g., 'So, you're saying the data was late from the other team?').
Done when: The recipient has shared their side of the story.
Why: People are more likely to change behavior if they are involved in the solution.
How:
- Ask: 'How can we prevent this next time?'
- Define one SMART goal (Specific, Measurable, Achievable, Relevant, Time-bound).
- Offer your support (e.g., 'I can review your draft 2 hours before the next meeting').
Done when: One concrete next step is agreed upon by both parties.
Why: Documentation prevents 'memory creep' and ensures both parties are working toward the same goal.
How:
- Keep it brief: 'Thanks for the chat. Just confirming our plan: [Action Step] by [Date].'
- Reiterate your support and belief in their ability to improve.
Done when: A follow-up email is in the recipient's inbox.
Why: Feedback without follow-up is often forgotten; a check-in reinforces the importance of the change.
How:
- Set a 10-minute calendar appointment for exactly 7 days later.
- Use the time to recognize progress or troubleshoot remaining hurdles.
Done when: A follow-up meeting is on the calendar.
Why: Asking for feedback builds trust and shows that you are also committed to growth.
How:
- Ask: 'How did this conversation feel for you? Was the feedback clear and helpful?'
- Listen to their response without defending your approach.
Done when: You have received at least one piece of input on your feedback style.
Why: Learning from others' difficult conversations accelerates your mastery of the skill.
How:
- Identify a colleague known for their strong leadership or communication skills.
- Schedule a 30-minute 'Coffee & Feedback' session.
- Ask: 'How do you handle delivering tough news to high-performers?'
Done when: You have completed one networking meeting focused on communication skills.