Saying no to more work
Turn an impossible ask into an honest trade off, or hear a no and negotiate priorities.
Case study: Yes, yes, yes, burnout
Nikhil, a senior developer in Bengaluru, said yes to everything. A dashboard for sales, a bug for support, a demo for the Munich program manager, all in the same sprint. He worked until 1 a.m. for three weeks, missed two of the three, and got feedback that he was "unreliable". His teammate Tanvi got the same Munich request. She said, "Yes, I can do the demo. To fit it in, I'd move the search refactor to next sprint. Is that the right trade off?" The program manager agreed in thirty seconds, and the refactor moved without drama.
Takeaway: A good no is a yes with a trade off. Make the cost visible and let the right person choose.
Many of us find it hard to say no to seniors or clients, so we say "I'll try" and quietly overcommit. Global managers prefer an honest trade off. A clear "here's what moves if I take this" is seen as maturity, not refusal.
Saying no
Goal: Protect your existing commitments by making the trade off visible, and let Lukas choose.
Step by step
- Show you care. Acknowledge why the ask matters.
- Name your load. What you're already committed to, briefly.
- Offer the trade off. "Yes, and to do it, this moves." Or a smaller version.
- Let them choose. Ask which matters more, or who should decide.
Say this, not that
| I can see why this demo matters for the customer. | Starting with the goal shows you're on their side. | |
| Right now I'm committed to the search refactor and the release on the twentieth. | I'll try my best to manage. | "I'll try" sounds like yes and usually ends in a miss. |
| Yes, I can do the demo. To fit it in, the search refactor would move to next sprint. Is that the right trade off? | This is the "yes, and" no. It makes the cost visible. | |
| Or I could do a smaller version: a recorded walkthrough instead of a live demo. | Not possible. | A smaller version often solves the real need. |
| Which one matters more to you this sprint? |
Model conversation
- Lukas
- Hi, I need a live demo of the new search for a customer on Thursday. Can you do it?
- You
- I can see why this matters for the customer. Right now I'm on the search refactor and the release on the twentieth.
- Lukas
- I know you're busy, but this customer is important.
- You
- Understood. Yes, I can do the demo. To fit it in, the refactor would move to next sprint. Is that the right trade off?
- Lukas
- Hmm, the refactor is also important for performance.
- You
- Then another option is a recorded walkthrough. It takes me two hours instead of two days.
- Lukas
- A recording could work if it shows the filters.
- You
- Great. I'll send it Wednesday, and the refactor stays on track.
Hearing no
Goal: Respect the no, understand the constraint, and negotiate a priority or a smaller version that works for both.
Step by step
- Accept the no. Thank them for being honest instead of overcommitting.
- Understand the load. Ask what's in the way and what would have to move.
- Share the why. Explain the real goal, so they can help find a smarter way.
- Negotiate. Trade priorities, shrink the scope, or escalate to whoever decides.
Say this, not that
| Thanks for being straight with me, Meera. I'd much rather know now. | But this is a management priority. | Pulling rank gets a reluctant yes and a late delivery. |
| Help me understand what's on the team's plate this sprint. | ||
| Here's the real goal: the customer wants to see bulk upload before they renew. | The "why" often unlocks a smarter option. | |
| If we paused the settings page, could the team fit a basic version of bulk upload? | Offer your own trade off. It shows respect. | |
| If we can't agree, let's take both options to Arun and let him decide by Friday. | Just do it somehow. | "Somehow" means overtime and bugs. |
Model conversation
- You
- Hi Meera, could the team add bulk upload to this sprint? The customer wants it before renewal.
- Meera
- Honestly, no. We're at full capacity with the settings page and two critical bugs.
- You
- Thanks for being straight with me. I'd much rather know now. Help me understand what would have to move.
- Meera
- The settings page is the big one. It's about five days of work.
- You
- The real goal is that the customer sees bulk upload in the renewal demo. Could we pause settings for a basic version?
- Meera
- A basic CSV upload without validation is maybe three days. Settings would slip a week.
- You
- That works for me. I'll tell the settings stakeholders today, so it's not on you.
- Meera
- Thanks. That makes it much easier for the team.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.