The pull request has been sitting there for 72 hours. Untouched. Ignored. Your sprint deadline is tomorrow.
You refresh GitHub again and feel the frustration rising. Still no reviews. Not even a single comment.
This is the third time this week. And you're about to lose it.
Your team has completely checked out of code reviews.
What started as occasional delays has become a full-blown crisis. Engineers are skipping reviews, or just commenting with "LGTM" without even looking at the code.
The code quality is suffering. Technical debt is now actively growing. And the tension is rising.
What would YOU do?
Outline
🔒 3 potential options (and their consequences)
🔒 Why some teams hate code reviews
🔒 What most leaders get wrong
🔒 My preferred approach (a complete reframe)
🔒 The unexpected outcome
🔒 Key takeaways
🔒 Some useful links from me
If you enjoy posts like this, consider supporting my work and subscribing to this newsletter.
As a free subscriber, you get:
✉️ 1 post per week
As a paid subscriber, you get:
🔒 50 Engineering Manager templates and playbooks (worth $79)
🔒 The Engineering Manager’s Field Guide (worth $29)
🔒 A weekly "What would you do?" scenario & breakdown like this one from real challenges EMs face
🔒 The complete archive