Saying no is the deliberate refusal or renegotiation of a request that cannot be accepted appropriately or sustainably. For engineering managers, it protects team capacity, clarifies priorities, and keeps effort aligned with meaningful responsibilities. A good refusal is not dismissive: acknowledge the opportunity, reflect before responding, explain the constraints or misalignment, and work with the requester on a constructive alternative. section 11.2.2
Use this sequence when a new request threatens existing commitments:
- Acknowledge the request and express gratitude for being considered. section 11.2.2
- Assess the request against current priorities, broader objectives, personal goals, available time, and team capacity. section 11.2.2 section 14.2.4
- Explain the likely trade-offs objectively, including delayed commitments, reduced quality, or strain on the team. section 14.2.4
- Offer alternatives: reprioritize existing work, adjust timelines, involve another team, or identify a better-suited resource. section 11.2.2 section 14.2.4
- Set expectations clearly with stakeholders and revisit the decision when priorities or resources change. section 14.2.4
A stretched team and an urgent request
An engineering manager is leading a crucial project when a manager requests immediate help with another urgent task. The manager explains that the team is already committed and that accepting the work would jeopardize current deliverables. Rather than refusing without a path forward, they propose comparing priorities, finding resources from another team, and communicating any timeline changes to stakeholders. The response protects the team while addressing the underlying need. section 14.2.4
