Feedback is how teams learn faster than production incidents teach them. Avoided feedback becomes surprise performance reviews. Vague feedback becomes demotivation. Specific, timely, behavior-based feedback builds trust even when the message is hard.
Your job is not to collect evidence for a verdict. Your job is to help someone see a pattern early enough to change it, and to name strengths so they scale on purpose.
A simple feedback frame
Example: “In yesterday’s design review, you jumped to implementation details before the problem statement was clear. Two engineers stopped contributing. Next time, can we hold solutions until we confirm the user problem?”
- Situation: when and where it happened (concrete, recent).
- Behavior: what the person did or said (observable, not character).
- Impact: effect on users, teammates, delivery, or trust.
- Request: what good looks like next time, or a joint experiment.
Positive feedback is not fluff
People repeat what gets recognized. Praise the behavior you want more of: careful incident write-ups, mentoring juniors, shipping boring reliability work. Public recognition for collaborative wins; private recognition for sensitive growth moments.
- Be as specific with praise as with critique.
- Connect the behavior to team outcomes so it does not feel random.
- Do not sandwich hard feedback between fake compliments.
- Keep a private log of strengths so reviews are not only problem memory.
Growth conversations that stick
1:1s are where growth compounds. Rotate through career goals, current blockers, feedback both ways, and wellbeing. One coaching focus per person beats five half-started improvement plans.
- Agree one growth focus for the next 4-6 weeks.
- Define what better looks like with a concrete example.
- Schedule practice reps (reviews, designs, demos, facilitation).
- Review evidence together; adjust the plan, not just the pep talk.
If you wait for the review cycle to share something important, you failed the coaching job. Small, frequent, documented feedback prevents both surprises and mythology.
When performance is off track
Early honesty is kinder than late drama. Separate skill gaps from will gaps, and unclear expectations from true underperformance. Put expectations in writing. Offer support. Set a check-in date. Escalate to a formal plan only when informal coaching has failed with clear evidence.
- Restate role expectations and the gap with examples.
- Ask what support or clarity they need from you.
- Agree measurable checkpoints and a timeline.
- Document the conversation for shared memory, not as a trap.
- Involve your manager or HR early when risk is high, not after trust collapses.
Receiving feedback as a lead
Your team watches how you take feedback more than how you give it. Thank people, clarify without defending, and report back what you changed. If you only solicit praise, people will stop telling you the truth.
- Ask regularly: “What should I start, stop, or continue?”
- Use anonymous or third-party channels when power distance is high.
- Pick one thing to improve visibly within two weeks.
- Close the loop: “You said X; here is what I tried.”
Feedback is a gift only if the wrapper is respect and the content is usable.