Facilitating Better Code Reviews for Quality and Team Growth
Designed for Engineering managers, tech leads, and software engineers improving code review quality and team learning to spark real collaboration and high-energy learning.
A practical workshop for engineering teams that want code reviews to improve software, spread knowledge, and grow engineer confidence instead of becoming transactional bug hunts.
The Perfect Review That Failed
Participants read a code review containing technically correct, respectful, and detailed comments. They predict how the author will respond, then learn that the author became reluctant to submit future pull requests because the review felt like a list of corrections rather than a conversation. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
The prediction error shows that technically accurate feedback can still discourage collaboration when it ignores the author's experience.
Same Pull Request, Different Priorities
Every group reviews the same pull request, but each receives a different review objective. One group optimizes for performance, another for readability, security, maintainability, or onboarding junior developers. When groups compare their feedback, they see how shared priorities shape useful review comments. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
The hidden review objectives demonstrate that many disagreements are priority disagreements rather than simple technical mistakes.
The Context Nobody Had
Participants role-play a code review between an author and reviewer. The reviewer sees only the code, while the author secretly knows important constraints such as a tight deadline, a legacy dependency, or a customer commitment. After the review, participants reveal the missing context and identify questions that would have made the discussion more productive. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
The hidden context makes it clear why judging a code decision without understanding the circumstances can create unnecessary conflict.
Which Comment Adds Value
Teams receive twelve realistic code review comments covering style, architecture, performance, documentation, testing, and security. They rank which comments create the greatest long-term value for the team, focusing attention on impact rather than the volume of feedback. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
Forced ranking helps reviewers distinguish high-leverage feedback from personal preference and low-value polish.
Two Reviews, Two Cultures
Participants compare two code review conversations. One is dominated by nitpicking, isolated corrections, and one-way feedback. The other combines technical discussion with thoughtful questions, recognition of good decisions, and shared problem-solving. Participants identify the behaviors that create healthier engineering cultures. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
The comparison makes culture visible in everyday review language and gives teams a concrete vocabulary for changing it.
Review Your Pull Request
Participants switch perspectives and become the author receiving feedback. They experience several review styles, from overly critical to highly collaborative, and rate which comments motivate improvement versus simple compliance. They then rewrite one review comment to be clearer, more actionable, and more respectful. Facilitating Better Code Reviews for Quality and Team Growth
Tap to view the full activity.
Why this works
Role reversal helps reviewers think about how feedback will be received, not only how technically correct it sounds when written.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.