Say No Without Making Enemies, and Keep Your Energy

TL;DR Saying yes to everyone costs your evenings first, then promises you quietly break to people who aren't in the room, and then, if it goes on, your health. How to say no at work without making enemies: trade instead of refusing ("yes, and it moves X; which first?"), let the person who owns priorities choose, guard a long block of focus time, and take exhaustion and cynicism seriously.

Do this: Write down everything you have promised, with dates, and answer the next request with "Yes, and it moves X. Which first?"

Part 2 ended with Pip helpful, clear, and saying yes to everyone: Ollie's report, Bun's test data, Brock's review, the Admiral's "quick look", on top of her own feature. It's 22:10 on Wednesday. Again. Bun stops by her desk with a mop.

"You've been here till ten all week."

"I can't say no to the crew."

"You already are," says Bun. "You just haven't told them which thing."

Dev Voyage: Open Ocean, in six parts:

1. Working With a Difficult Boss Without Losing Yourself
2. Feedback Both Ways: Asking For It and Giving It
3. Say No Without Making Enemies, and Keep Your Energy (you are here)
4. Keep Learning: Bringing New Tools (and AI) Into Real Work
5. Talk to the Business: Working With PMs and Non-Engineers
6. Ask for the Raise: Showing Your Value Without Bragging

Every yes spends a promise

Pip wrote her week down on Thursday morning. It didn't fit.

Refund feature (mine)         due Friday
Brock: review PR #452         today
Bun: test data                Thursday
Ollie: report                 "when you can"
Admiral: "a quick look"       ?

A new yes takes time from a promise you already made, usually to someone who isn't asking right now. Saying yes to everything doesn't make you reliable. It makes you break promises without telling anyone. Greg McKeown's Essentialism is built on that idea: if you don't choose your priorities, someone else will.

Trade, don't refuse

A flat no damages a relationship. A trade doesn't, because it says yes to the person and shows the cost.

Yes, I can do that.
It would push <the thing I promised> to <new date>.
Which would you like first?

The next morning Ollie asked for a data export by Thursday. Pip tried it: "Yes. It moves the refund email templates to next Tuesday. Which first?"

Ollie thought for a second. "Templates. The export can wait till Monday. Thanks for asking!"

Ollie got to make a decision that was hers to make. That's the point: priorities belong to the person who owns them, usually the product manager or the lead, not whoever asked last. When two requests collide, put both people in one thread, name the owner, and ask them to choose.

Guard the afternoon

Paul Graham's essay Maker's Schedule, Manager's Schedule explains why developers lose whole days to small interruptions. A manager's day is cut into hours, so a meeting costs an hour. A maker needs half-days, so one meeting in the middle of the afternoon can cost the whole afternoon.

Pip's changes were small:

• A daily block, 13:30 to 16:30, in her calendar as "Focus: refunds", notifications off.
• Chat checked at 9:00, 13:00 and 16:30, unless something is on fire.
• Office hours on Tuesday and Thursday at 11:00 for anyone's questions.

The sign people miss

The World Health Organization's ICD-11 describes burnout as the result of chronic workplace stress that hasn't been managed, with three signs: exhaustion, growing mental distance or cynicism about the job, and reduced efficacy at it.

The second one is easy to miss. Pip noticed it when she rolled her eyes at a message from Bun, the person she liked most on the ship. That afternoon she told Kit.

If the three signs last for weeks, talk to your lead, and to a doctor if your sleep or health is suffering.

Try it

This week:

1. List everything you've promised, with dates.
2. Use the trade once: "Yes, and it moves X. Which first?"
3. When two requests collide, ask the priority owner to choose, in one thread.
4. Book one daily focus block, and tell your team.

On Monday Pip's plate had four things on it instead of nine. With her evenings back she noticed something new: she wanted to grow. Brock had mentioned an AI tool that writes test cases, the Admiral's team was talking about it too, and she couldn't tell if it was worth learning or just noise. Part 4, Keep Learning: Bringing New Tools (and AI) Into Real Work, is how she finds out without starting a war on the ship.

Read this with your AI

Read the post "Say No Without Making Enemies, and Keep Your Energy".
1. I'll paste my current list of promises. Help me see what a new request would push back.
2. Draft the trade message for the request I'm about to get, in my voice.
3. Suggest a focus-time plan for my week that I can propose to my lead.