Giving Feedback
Prerequisites: Career Development and Performance Reviews Leads to: After this, you'll be ready for Coaching.
Why This Matters
A QA Lead who saves feedback for the formal review. A QA Lead notices, in March, that a team member's bug reports consistently lack enough detail for developers to reproduce issues efficiently. Rather than saying anything in the moment, the Lead saves the observation for the performance review in September — six months later, after the pattern has repeated dozens of times, each one a small, avoidable cost to the team, and long after the specific examples that would have made the feedback concrete and useful have faded from memory.
A QA Lead who gives feedback close to the moment. A peer noticing the same pattern instead raises it within a day or two of a specific instance — "this bug report was hard for the developer to reproduce; here's specifically what was missing, and here's what would have made it faster to act on." The team member can immediately connect the feedback to a fresh, specific example, and the pattern measurably improves within a few reports, rather than persisting unaddressed for months.
Both leads noticed the same issue. Only one addressed it while it was still specific, fresh, and actionable — because feedback delayed until a formal review loses most of its power to actually change behavior, and costs the team the intervening months of the same avoidable pattern.
What Makes Feedback Actually Actionable
Specific, not general. "Your bug reports could be clearer" gives the recipient little to act on; "this report didn't specify the exact steps to reproduce, which is what made it hard for the developer to act on quickly" gives them something concrete to change next time.
Close to the moment, not delayed. Feedback given within days of the relevant instance, while the specific example is still fresh for both people, is far more useful than feedback reconstructed months later from vague memory — the same principle behind the running-record practice from Career Development and Performance Reviews.
Behavior-focused, not character-focused. "This report was missing reproduction steps" addresses a specific, changeable action; "you're not detail-oriented" attacks a trait, invites defensiveness, and gives no clear path to improvement.
Balanced with genuine positive feedback, given with the same specificity. Positive feedback deserves the same concrete, specific treatment as constructive feedback — "that root-cause investigation was excellent, specifically because you narrowed the search systematically before proposing a fix" reinforces the exact behavior worth repeating, the same way specific constructive feedback clarifies what to change.
Common Mistakes
Mistake 1: Saving feedback for the formal review instead of giving it close to the relevant moment. This module's opening scenario — delayed feedback loses specificity, loses its connection to a fresh example, and costs the team months of an unaddressed, avoidable pattern.
Mistake 2: Giving vague, general feedback with no specific example attached. "Be more thorough" or "communicate better" gives the recipient nothing concrete to actually change — specificity is what makes feedback genuinely actionable.
Mistake 3: Framing feedback around character or personality rather than specific, changeable behavior. Character-focused feedback ("you're careless") invites defensiveness and offers no clear path forward; behavior-focused feedback ("this specific step was missed") does.
Mistake 4: Giving only constructive feedback, never specific positive feedback. Without specific positive feedback, people don't reliably know which of their own behaviors are actually working well and worth repeating — positive feedback deserves the same specificity as constructive feedback.
Best Practices
Practice 1: Give feedback within days of the relevant instance, not weeks or months later. Proximity to the specific example is what keeps feedback concrete, credible, and genuinely actionable — the longer the delay, the vaguer and less useful it becomes.
Practice 2: Always attach a specific example, for both constructive and positive feedback. A specific instance makes feedback something the recipient can genuinely learn from, rather than a general impression they can't easily connect to a concrete action.
Practice 3: Frame feedback around a specific, changeable action, not a character trait. Describing what happened and what would work better keeps the conversation focused on something the person can actually act on next time.
Practice 4: Balance constructive feedback with genuine, equally specific positive feedback over time. A pattern of only ever hearing what's wrong, with no acknowledgment of what's working, erodes trust and doesn't actually help someone understand their own strengths.
A QA Lead at AtlasBank noticed a pattern across several sprints: a specific team member's defect reports frequently omitted environment details that developers needed to reproduce issues efficiently, adding real delay to defect resolution each time. Rather than waiting for the next formal review, the Lead began giving specific, immediate feedback after each instance — pointing to the exact missing detail in that specific report, and what including it would have looked like. Within three sprints, the pattern had essentially disappeared, and the same engineer's defect reports became a model the Lead began pointing other team members toward — an outcome unlikely to have happened with feedback held back for a review six months away, by which point the specific, fixable pattern would have repeated dozens more times.
Mini Challenge
Scenario: You notice a team member has, twice this week, submitted test cases that don't specify expected results clearly enough for someone else to execute independently.
Your task: Write the specific, behavior-focused feedback you'd give, including a concrete example from this week and what you'd suggest instead.
Key Takeaways
- Feedback given close to the relevant moment is far more actionable than feedback saved for a formal review months later.
- Specific, example-backed feedback gives the recipient something concrete to change; vague feedback doesn't.
- Framing feedback around specific, changeable behavior, rather than character, keeps the conversation constructive and actionable.
- Specific positive feedback deserves the same attention as constructive feedback, so people know what's working and worth repeating.
What You Just Learned
- Why feedback delayed until a formal review loses most of its power to actually change behavior
- The specific qualities — specificity, timeliness, behavior focus — that make feedback genuinely actionable
- Why positive feedback needs the same specificity as constructive feedback
- The AtlasBank example of immediate, specific feedback resolving a recurring pattern within three sprints
Related Topics
- Career Development and Performance Reviews — How ongoing, specific feedback feeds directly into a genuinely useful formal review
- Mentoring Engineers — The related but distinct skill of building judgment through guided questions, rather than delivering direct feedback
- Coaching — Extending specific, timely feedback into an ongoing growth-focused relationship
Interview Questions
Q1: How do you give constructive feedback in a way that actually changes behavior?
What to look for: A description emphasizing specificity, timeliness, and behavior focus — not just "I'm direct but kind," which describes tone without describing the actual mechanism that makes feedback effective.
Q2: Tell me about a time you gave feedback that was difficult to deliver. How did you approach it?
What to look for: A real example showing specific, behavior-focused framing and reasonably prompt delivery — not a story that dwells only on the difficulty of the conversation without describing how it was actually structured.
Many candidates describe feedback delivery purely in terms of tone — being kind, being direct, using a particular framing technique. A strong answer also addresses timing and specificity, recognizing that delayed or vague feedback fails regardless of how gently or directly it's delivered.
Q3: How do you make sure your team knows what they're doing well, not just what needs improvement?
What to look for: A description of specific, deliberate positive feedback, not just an assumption that no news is good news — showing the candidate treats positive feedback as equally important and equally requiring specificity.
Glossary
Behavior-Focused Feedback: Feedback framed around a specific, changeable action rather than a character trait, keeping the conversation constructive and actionable.
Feedback Proximity: How close in time feedback is given relative to the relevant instance — closer proximity generally produces more specific, credible, and actionable feedback.
Quick Revision
Remember these five points:
✓ Feedback given close to the relevant moment is far more actionable than feedback saved for a formal review months later.
✓ Specific, example-backed feedback gives the recipient something concrete to change; vague feedback doesn't.
✓ Framing feedback around specific, changeable behavior, not character, keeps the conversation constructive.
✓ Specific positive feedback deserves the same attention as constructive feedback.
✓ Delayed feedback costs the team the intervening time during which an avoidable pattern continues unaddressed.