Saying no is one of the most important skills for a tech lead. To PMs, to stakeholders, sometimes to your own team. Here’s how to do it well.

Josh Hornby

Saying no is a critical skill for tech leads to protect team capacity and delivery quality. The article explains when to push back (when value doesn't justify cost, quality will suffer, team is overloaded, better solutions exist, or conflicts with priorities), how to do it effectively through problem-solving language rather than rejection, and how to adapt the approach for different stakeholders. Building credibility through consistent reasoning, reliable execution, and strategic yes's makes your no's more effective. While you'll sometimes be wrong, saying yes to everything guarantees worse outcomes through burnout and declining quality.

When to Say No