Saying no

Every yes is a no to something else — usually your highest-leverage project. Seniors are not people who never help. They are people who allocate help on purpose.

Managers prefer explicit tradeoffs to silent overcommit and surprise delay. That is how reliability survives.

Walking through scripts that preserve relationships

• "I can take this after I ship X on Thursday — or Priya owns this area and might be faster."
• "I can do a lightweight version (spike or review only) this week, not the full implementation."
• "That is important; it is not on our quarterly goals. Want to raise it with the manager or PM for prioritization?"
• "I'm at capacity. If this is truly urgent, what should I deprioritize?"

The last line forces tradeoffs into the open.

Decline drive-by scope that does not match your growth goals unless you are deliberately banking goodwill or learning. Keep a short parking-lot note of ideas you refused — useful when someone later asks what you would do with more capacity.

Replace a vague yes with a timed yes, a partial yes, or an explicit tradeoff. That is the whole skill.

Common mistakes

• Vague yes to keep the peace. You have said no to your real project without naming it.
• Silent overcommit. Surprise delay is more expensive than an honest tradeoff today.
• Never helping. Allocation is the point, not a permanent closed door.

Check yourself

Someone asks you to take a full implementation this week. You are at capacity. What do you say?

"If this is truly urgent, what should I deprioritize?" — or a spike this week, full work after Thursday.

A request is real but not on quarterly goals. Next step?

Redirect to the manager or PM for prioritization rather than absorbing it privately.

Key takeaways

• Every yes spends the hours your high-leverage work needed.
• Use timed yes, partial yes, or an explicit tradeoff.
• Make deprioritization visible. Managers can work with that.
• Keep a parking lot of refused ideas for when capacity appears.

Further learning

Next: sustainable pace.