Feedback Template for Engineers (Manager to Direct Report)

Give constructive, actionable feedback to software engineers using this proven template. Balance positive feedback with growth areas effectively.

Effective feedback is specific, actionable, and timely. Use this template to structure feedback conversations that help engineers grow without damaging trust.

Template (Copy & Paste)

# Feedback Template: [Engineer Name] - [Date]

## Context
**Topic:** [What this feedback is about]
**When:** [When the situation occurred]
**Why Now:** [Why you're giving this feedback now]

## The Situation (Observation)
**What I Observed:**
[Describe the specific behavior or situation objectively, without judgment]

**Example:**
"In yesterday's architecture review, when Sarah questioned the database choice, I noticed you responded with 'that's a bad idea' and moved on without explaining your reasoning."

## The Impact (Effect)
**Impact on Team:**
[How this affected the team, project, or others]

**Impact on Work:**
[How this affected the quality, timeline, or outcome]

**Impact on Career:**
[How this might affect their growth or perception]

**Example:**
"This had a few effects:
- Sarah seemed shut down and didn't contribute further
- We missed her valid concern about query performance
- The team might hesitate to give you feedback in the future
- As you move toward Senior level, communication style matters more"

## The Request (Change)
**What I'd Like to See:**
[Specific behavior change you're requesting]

**Example:**
"In future design discussions, when someone questions your approach:
1. Pause and thank them for the question
2. Explain your reasoning out loud
3. Ask for their concerns explicitly
4. Discuss tradeoffs together
This shows technical leadership, not just technical skill."

## Support Offered
**How I Can Help:**
- [Support item 1]
- [Support item 2]

**Example:**
- I can review your design doc drafts before sharing
- I can sit in on architecture discussions and give you feedback
- I can share resources on technical communication

## Follow-Up
**What Success Looks Like:**
[Concrete examples of improved behavior]

**Check-In:**
[When you'll revisit this - typically 2-4 weeks]

**Example:**
"Success is:
- Team members continue sharing concerns freely
- You explain your technical decisions clearly
- You demonstrate openness to alternative approaches

Let's check in during our 1:1 in 2 weeks to see how it's going."

## Discussion Notes
[Space for their response, questions, and agreement on next steps]

---

## Feedback Delivery Script

**1. Set the Stage:**
"Hey [Name], I want to share some feedback about [topic]. Do you have 15 minutes to discuss now, or should we schedule time?"

**2. Share Observation:**
"I noticed [specific behavior]. Can you help me understand what was going on from your perspective?"

**3. Listen First:**
[Give them space to explain their reasoning or context you might have missed]

**4. Share Impact:**
"Here's why this matters..."

**5. Make Request:**
"Going forward, here's what would be helpful..."

**6. Offer Support:**
"How can I help you with this?"

**7. Close with Appreciation:**
"I'm sharing this because I believe in your potential and want to see you grow. Questions?"

How to Use This Template

  1. 1Give feedback as soon as possible after the event (within 48 hours)
  2. 2Choose private setting - never give corrective feedback publicly
  3. 3Use "I observed" language, not "you are" judgments
  4. 4Be specific - vague feedback like "be more proactive" isn't actionable
  5. 5Listen to their perspective - you might be missing context
  6. 6Focus on behavior, not personality
  7. 7Balance: give 3-5x more positive than negative feedback overall
  8. 8Make it a conversation, not a lecture
  9. 9End with clear next steps and timeline for follow-up
  10. 10Document the conversation in your 1:1 notes

Common Mistakes to Avoid

  • Feedback sandwich (praise-criticism-praise) feels manipulative - be direct
  • Vague language: "sometimes" "maybe" "sort of" - be specific
  • Waiting too long - feedback loses impact after 2+ weeks
  • Giving feedback when angry - wait until you're calm
  • Only giving feedback during performance reviews - too infrequent
  • Not asking for their perspective first
  • Making it about you ("I feel") instead of impact on team/work
  • No follow-up - feedback without accountability is just complaining
  • Death by a thousand cuts - address patterns, not every incident
  • Not balancing with positive feedback - builds resentment

Related Resources

Ready to Level Up Your Engineering Leadership?

Ledger helps engineering managers and ICs track 1:1s, performance reviews, career goals, and impact logs — all in one place. Stop using spreadsheets and scattered docs.

No credit card required • Cancel anytime