Tell me about saying no to a senior stakeholder
Model answer
Use the STAR structure.
Situation. A VP asked us to add a custom reporting module for one large customer, in the middle of a quarter focused on improving onboarding.
Task. Decline or reshape the request without damaging the relationship, and keep the team focused on the agreed goal.
Action. I first listened to understand the real need: the customer wanted weekly data in a spreadsheet. I then showed the VP what the module would cost in engineering time and which onboarding work would be delayed, and how that affected our quarterly target. I proposed a lighter option: a scheduled CSV export, which took days instead of weeks, and offered to revisit the module in planning for the next quarter.
Result. The VP agreed, the customer was satisfied, and onboarding shipped on time.
The lesson: say no to the solution, not to the person, and bring evidence and an alternative.
Key points
- Understand the underlying need before responding
- Show the trade-off in terms of goals and cost
- Offer an alternative and a path to revisit
Likely follow-ups
- What if the stakeholder insisted after your explanation?
- How do you keep trust when you decline many requests?
Common mistakes
- Saying a flat no without evidence or an alternative
- Saying yes to avoid conflict and breaking the plan