
When a colleague asks for something you cannot do, you have more options than “yes” and “no”. Engineers tend to pick one by reflex, and the reflex is often costly. This comparison lines up the four most common responses side by side, so you can see why saying no politely usually beats the alternatives, and when each of the others still has its place.
The four responses on the table
Imagine a developer asks you, in the middle of a busy sprint, to build a custom deployment report by Thursday. Four replies are realistic:
- The automatic yes: “Sure, no problem.”
- The blunt no: “No, I do not have time.”
- The foggy maybe: “I will see what I can do.”
- The polite no: thanks, a clear decline, a short reason and an alternative.
Let us compare them across four measures that shape daily teamwork: candour, effort, how fast the matter is settled and what happens to the relationship.
Comparison 1: the automatic yes
What it buys you: instant goodwill and a quick end to an awkward moment.
What it costs: the report must now be built, and your planned work moves aside. If you were already full, something gives: the report is late, or your own tasks are. The requester then experiences a broken promise, which is worse than a refusal.
When it is right: when the request truly fits within your capacity and plan, or when you have consciously decided it outranks what you were doing. A yes that you have thought about is fine; a reflexive one is not.
Comparison 2: the blunt no
What it buys you: speed and honesty. Nobody is left guessing.
What it costs: warmth. With no thanks and no alternative, the requester has nowhere to go and may feel dismissed. Repeated often, it makes people stop asking, including for things you would want to hear about.
When it is right: in a genuine emergency where there is no time for niceties, or with someone who has asked the same thing many times and received full explanations before. Even then, a one-line courtesy costs nothing.
Comparison 3: the foggy maybe
What it buys you: a postponed discomfort.
What it costs: almost everything. The requester waits, plans around your possible help, then asks again, usually more urgently. You carry an undeclared commitment that you resent. The eventual no arrives late and lands harder.
When it is right: only when you truly do not know yet, and then it should come with a fixed time to answer, which turns it into a different, honest message: “expect my answer before the end of tomorrow morning.”
Comparison 4: the polite no
What it buys you: clarity, protected focus and a requester who still feels respected.
What it costs: thirty seconds of thought and a short written message. Occasionally the other person is disappointed, which is a normal cost of limits.
When it is right: most of the time. Applied to the report request: “Thanks for asking, a deployment report would be useful. I cannot build a custom one by Thursday because the sprint is full. I can share the existing export today, and we can plan a proper report for the next cycle.”
Side by side
- Honesty: yes, low if you cannot deliver; blunt no, high; maybe, low; polite no, high.
- Warmth: yes, high at first; blunt no, low; maybe, medium; polite no, high.
- Time to a clear answer: yes, immediate; blunt no, immediate; maybe, never; polite no, immediate.
- Protects planned work: yes, no; blunt no, yes; maybe, partly; polite no, yes.
- Leaves the next step clear: yes, only if delivered; blunt no, no; maybe, no; polite no, yes.
The only reply that scores well on every row is the polite no, which explains why it is worth practising.
Does career stage change the answer?
Somewhat. Early in a career, the automatic yes is tempting because you want to prove yourself. Writing about the progression from junior to senior roles, such as a path from junior to senior engineer, shows that seniority is partly the ability to choose what deserves effort. Later, the blunt no is tempting because you are busy and experienced; the cost is the goodwill that later projects depend on.
People planning their growth, for example with a roadmap that maps skills, portfolio projects and exams to career growth, should add communication to the list, since few promotions are won on technical skill alone.
A note on requests from outside the team
Requests from outside your normal circle, such as a relative asking you to pick a mobile service for a trip, follow the same logic. A courteous pointer works: the directory at eSIMGlobo, an independent listing of mobile and connectivity firms drawn from official code registers, can be browsed without your help.
Choosing quickly in the moment
Run two questions before replying. First: does this fit my plan without displacing something I have already promised? If yes, accept willingly. If not, second question: do I know today that the answer is no? If yes, send the polite no. If genuinely unsure, send a “when will I know” message with a time attached, never an open-ended maybe.
What about saying yes with conditions?
A fifth reply deserves a short mention: the conditional yes. “I can do it if the deadline moves to next week.” This is a legitimate and often excellent response, because it states the trade-off in the open. It is really a close cousin of the polite no, with the alternative built in. The danger is hiding a refusal inside conditions you know the other person cannot meet, which is the foggy maybe in better clothes. Use it only when you would honestly deliver if the condition were met.
Verdict
The automatic yes and the foggy maybe feel kind but shift the cost to a later, worse moment. The blunt no is honest but cold. The polite no keeps honesty and warmth together, and it takes barely any longer to write. For your next request, draft all four replies in your head, then send the fourth.