Strategy

How to say no to stakeholders without burning bridges

Practical scripts for engineering managers to decline or reshape requests: show the trade-off, offer options, and keep the relationship intact.

· 5 min read

An engineering team that says yes to everything says no by accident: to quality, to deadlines, to the work that mattered most. Saying no on purpose is part of the job. The skill is doing it in a way that leaves the other person feeling heard and the relationship stronger.

Understand before you answer

Before answering, ask what problem the request solves and what happens if it is not done this quarter. Often the request is a solution someone has already chosen; the underlying need may have a cheaper answer, or may already be on your roadmap under another name.

Make the trade-off visible

“No” sounds like a judgment of the request. “Yes, and here is what moves” makes it a decision about priorities — which belongs to whoever owns the priorities. Keep your roadmap visible enough that you can say:

  • “We can do this in March if we push the billing migration to Q3. Which matters more to the business?”
  • “This is a three-week project. The team is committed to the launch until the 15th. I can start it on the 18th.”

Offer options, not walls

  • Smaller: “We can't build the full dashboard, but we can export the data to a spreadsheet this week.”
  • Later: “Not this quarter, but I'll bring it to Q2 planning with your numbers attached.”
  • Elsewhere: “The data team owns that pipeline; I'll introduce you to their lead.”
  • Self-serve: “Here's the config flag — you can change it yourself.”

When the answer really is no

Say it clearly, early and with the reason. A vague “we'll see” that turns into a missed expectation does more damage than a clear no in week one. Thank them for raising it, explain how the decision was made, and tell them what would change it.

Keep score honestly

Track what you have declined and why, and revisit the list each quarter. Some declined requests become the right thing to do later. And the stakeholders you said no to well will be the ones who trust your yes.

Quick check

3 questions from the related lessons. Answers are explained, and the ones you get right count towards your progress.

Question 1

Q1.The CFO controls your budget but rarely thinks about your project. On the power/interest grid, you should…

Question 2

Q2.An initiative has a reach of 2,000, impact of 2, confidence of 50% and effort of 4 person-months. What is its RICE score?

Question 3

Q3.A vendor will accept no less than $80k a year. Your budget allows at most $95k. How wide is the ZOPA, in thousands of dollars?

Practice this in a lesson

Each engMBA lesson pairs a short explanation with practice questions that grade themselves. Free, with no signup.

See the full curriculum

Keep reading