Frameworks for Feedback
summary
Asserts that code reviews are by far the best way to detect error, recommends concrete frameworks — situation behavior impact and mirror empathy validation — and gives repeatable rituals: scheduled one‑on‑ones, monthly anonymous satisfaction forms reviewed in a meeting, retros and start stop continue prompts. Uses the forced‑push‑to‑prod example to show actionable feedback (check with team before breaking deploy process), urges follow‑up on action items so feedback actually changes behavior.
AI-written summary · about
chapters (20)
- 0:00Platinum
- 0:14Silver
- 1:13Feedback: type of communication
- 1:37Feedback works!
- 2:43Let's talk about feedback
- 4:37Feedback Structures
- 8:13Give Feedback
- 9:11Situation, Behavior, Impact
- 10:17Don't forget positive feedback
- 11:27Receive feedback
- 13:56MEV: Mirror
- 14:45MEV: Empathy
- 16:19Empathy is a skill
- 17:20Request Feedback
- 19:00Good Feedback
- 21:00Accountability
- 22:34Power dynamics
- 23:52Microaggressions
- 27:05How to respond to being called out
- 28:27Non-violent communication
related talks
32mBetter: Fearless Feedback for Software Teams
22mFeedback matters
52mFacilitating Safe and Inclusive Feedback
47mThe Power of Performance Feedback
42mFacilitating Safe and Inclusive Feedback
46mBetter: Fearless Feedback for Software Teams
01h 01mBetter Code Reviews FTW!
15mCorrections and Constructive Criticism