🟢 READ | ⏱ 8 min | 📡 9/10 | 🎯 Tech leads, engineering managers, senior engineers

TL;DR

A practical guide for tech leads managing overwhelm without sacrificing team health. Covers systems for triaging requests (log, prioritize, delegate), communicating capacity clearly to stakeholders, protecting code time via calendar blocking, and negotiating tradeoffs instead of saying flat "no." The author emphasizes that the role requires balancing technical depth, mentorship, and strategic thinking—all of which suffer when you're context-switching constantly.

Signal

• Triage system: Log every request, ask (1) Is this important? (2) Can I delegate? (3) Does it align with priorities? Dramatically cuts through noise and reveals what actually requires your attention
• Tradeoff negotiation: Instead of "no," say "Sure, we can do that, but it means we won't ship the checkout flow until next month. Are you happy with that?" Makes consequences visible and often causes requesters to reprioritize themselves
• Code time protection: Block calendar time for hands-on work, group meetings strategically, and resist becoming a pure manager. Tech leads who lose touch with the codebase can't empathize with their team or spot architectural problems

What They're NOT Telling You

The guide assumes you have enough organizational support to actually say no and have it respected. In dysfunctional orgs with weak leadership, this framework will backfire—you'll be seen as uncooperative rather than protecting capacity. Also doesn't address the root problem: if you're getting this volume of interrupts, the organizational structure itself may be broken.

Trust Check

Factuality ✅ | Author Authority ✅ | Actionability ✅