Constructive feedback
Say the hard thing clearly and kindly, and hear it back without flinching.
Case study: Ramesh and the hint that never landed
Ramesh, a tech lead in Hyderabad, noticed that Karthik kept joining the 9:30 standup ten minutes late. For a month he dropped hints: "Some people are taking standup very lightly." Karthik assumed it was about someone else. Then the US client complained in a steering call, and Ramesh snapped at Karthik on the team Slack channel. Karthik felt humiliated and stopped speaking in meetings. When Ramesh finally talked to him privately, it took four minutes. Karthik explained that his cab reached the office at 9:35, and they moved his updates to the end of the call.
Takeaway: Feedback works when it is specific, private and early. Hints and public scolding both fail.
Many of us soften feedback until it disappears, or save it up until we explode. Global teams expect direct, private, specific feedback about behavior, delivered soon after it happens.
Giving feedback
Goal: Name one specific behavior and its impact, and agree on a change together.
Step by step
- Go private. Ask for five minutes one to one, soon after it happens.
- Situation. Say when and where: 'In Tuesday's client demo...'
- Behavior. Describe what you saw, not what you think of them.
- Impact. Explain the effect on the team, the client or the work.
- Ask and agree. Get their view, then agree on one next step.
Say this, not that
| Do you have five minutes? I'd like to share some feedback. | We need to talk. | Ominous openings make people defensive before you start. |
| In the last three standups, you joined about ten minutes after we started. | You are always late and careless. | Specific facts are hard to argue with. Labels start a fight. |
| The impact is that the client sees gaps in our updates, and the team has to repeat things for you. | Impact explains why it matters, so it doesn't feel personal. | |
| Is there something going on that I'm not aware of? | Why can't you just come on time? | Curiosity often reveals a fixable cause. |
| What would help you make it on time? Let's agree on something that works. |
Model conversation
- You
- Hey Karthik, do you have five minutes? I'd like to share some feedback, just between us.
- Karthik
- Sure. Is something wrong?
- You
- In the last three standups, you joined about ten minutes after we started. Yesterday the client asked twice where your update was.
- Karthik
- Oh. I didn't realize it was that noticeable.
- You
- It is, and I don't think it's a reflection of your work. Is something making the mornings hard?
- Karthik
- Honestly, my cab gets in at nine thirty five. I log in as soon as I reach my desk.
- You
- That makes sense. What if we put your update at the end of the call, and you join from your phone in the cab?
- Karthik
- That works. Thanks for telling me directly instead of letting it build up.
Receiving feedback
Goal: Hear the feedback fully, understand it, and leave with one clear commitment.
Step by step
- Thank them. Giving feedback is uncomfortable. Make it easy for them.
- Listen fully. No interrupting, no explaining yet.
- Clarify. Ask for an example so you know exactly what to change.
- Commit. Say what you will do, and when you'll check back.
Say this, not that
| Thanks for telling me. I'd rather hear it than not. | But that wasn't my fault. | Defending first tells people not to bother next time. |
| Could you give me a specific example, so I know exactly what to change? | Who told you this? | Clarifying is not arguing. It makes the feedback usable. |
| That's fair. I can see how that came across. | Actually, sorry, sorry, very sorry. | One calm acknowledgment is stronger than repeated apologies. |
| Going forward, I'll share a status update before every client call. | ||
| Can we check in on this in two weeks, so you can tell me if it's better? | Asking for a follow-up shows you're serious. |
Model conversation
- Megan
- I wanted to share some feedback on yesterday's client call. Is now okay?
- You
- Of course. Thanks for telling me.
- Megan
- When the client asked about the delay, you went into a lot of technical detail. They looked lost, and we ran out of time for the roadmap.
- You
- Thanks. Could you tell me what you'd have liked to hear instead?
- Megan
- A one-line summary first: what's late, why, and the new date. Then detail only if they ask.
- You
- That's fair. I think I was nervous, so I over-explained.
- Megan
- Totally normal. You clearly know the system inside out.
- You
- Next call, I'll lead with a short summary. Could we check in afterward on how it went?
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.