Lesson 8
Saying No and Pushing Back Politely
4 min read
Why this matters
Developers get more requests than they can finish: new features, "quick" fixes, extra meetings, tight deadlines. If you say yes to everything, you'll miss deadlines and burn out. Saying no clearly and politely is a professional skill, and good managers respect it.
The core skill
The structure: acknowledge, explain, offer
A polite no has three parts:
- Acknowledge the request. Show you understand it's important.
- Explain why you can't, in one sentence.
- Offer an alternative.
I understand this feature is important for the demo.
Unfortunately, I'm already working on the security fix, which has to
ship this week.
I could start on the feature on Monday, or Jun might have time sooner.
The alternative is the most important part. It changes your answer from "no" to "not like this, but like this".
Pushing back on a deadline
Push back means to resist or disagree with a request or plan. When a deadline isn't realistic, explain the trade-off. A trade-off is what you lose when you gain something else.
We can deliver by Friday, but only without the export feature.
If we need everything, I think the end of next week is more realistic.
Which is more important to you?
Asking "Which is more important?" gives the decision back to the person who owns the priorities.
Saying no to the solution, not the person
Sometimes you disagree with how something should be built. Focus on the problem, and use I or we, not you.
- Sounds personal: You're asking for something that will break the database.
- Focuses on the problem: I'm worried this could overload the database. Could we add pagination first?
Using "unfortunately" and "I'm afraid"
These words prepare the listener for bad news. They make your no sound polite.
Unfortunately, we can't change the API before the release.
I'm afraid I won't be able to join the meeting tomorrow.
I'm afraid here doesn't mean you feel fear. It's a polite way to introduce bad news.
Useful phrases
Saying no
- I'm afraid I can't take this on right now. (take on = accept a task)
- Unfortunately, I don't have the capacity this sprint.
- I'd love to help, but I'm fully booked until Thursday.
Explaining
- I'm currently focused on the release.
- If I take this on, the migration will slip. (slip = be late)
Offering alternatives
- What I can do is look at it next week.
- Would it work if I gave you a smaller version first?
- Could we move it to the next sprint?
- Maybe Ravi could help. He knows that code well.
Pushing back
- I see your point, but I have some concerns about the timeline.
- What's the priority here? Speed or completeness?
- That's not realistic for Friday, but we could ship a first version.
Common mistakes
"No, I can't." Correct, but very direct. Add a reason and an alternative: "Sorry, I can't this week. I could do it on Monday."
"It's impossible." This sounds final and negative. Explain what is possible: "That's difficult for Friday, but we could ship the core part by then."
"I'm afraid I can't finish it until the deadline." Use by for the last possible moment. Until is for something that continues up to a time: "I'm afraid I can't finish it by the deadline."
"Sorry, sorry, I'm really sorry, but maybe I can't do it, sorry." Too many apologies make you sound guilty. One is enough: "Sorry, I can't do it this week."
Formal vs. casual
- To a stakeholder in another department: "Thank you for the request. Unfortunately, our team is fully committed to the Q4 release. We could consider this for the January planning. Would that work for you?"
- To your manager: "I can take it, but then the migration will slip by a week. Which should I prioritize?"
- To a teammate: "Can't today, sorry, I'm deep in the release. Tomorrow morning?"
Exercise
Think of a request you got recently that you didn't really have time for. Write the reply you should have sent, using acknowledge, explain and offer.
Then write a short message pushing back on a deadline, with a clear trade-off and a question about priorities.
Hint: check your message for you sentences. Can you rewrite them with I or we?
Recap
- Acknowledge, explain, then offer an alternative.
- Use unfortunately and I'm afraid to introduce bad news politely.
- Explain trade-offs and ask about priorities.
- Focus on the problem, not the person.
- Apologize once, not many times.