The script for saying no at work

Hi Everyone,

We've all said "let me check my calendar" when the honest answer to a request was already no. But saying no is often hard, especially when it's your boss, your biggest customer, or a peer you'll be in regular meetings with.

Today we're walking through a five-part script for saying no without damaging the relationship.

Why your soft no is backfiring

The instinct is to soften refusals with "let me check my calendar" or "my plate is full right now." That soft no usually costs you more than a clean one.

In a study of more than 14,000 real-world requests, Cornell researcher Vanessa Bohns found that people underestimated how often others would say yes by nearly half. People agree far more often than they need to, and the cost of declining is smaller than you'd think. Sezer's research on impression management found that humblebragging and fake excuses reduce both trust and perceived competence compared with straightforward honesty.

Serial deferrals are worse than a clear no. Telling someone "ask me again next month" two or three times creates false hope and wastes their planning time. You already know you should say no more often. The hard part is having the actual words.

The five parts

A no that keeps the relationship intact usually does five things.

• Validates the request or relationship
• Cites a principle: capacity, priorities, policy, fairness
• Draws a clear line
• Offers a bounded alternative: a narrower version of help, a different owner, or adjusted timing
• Reaffirms the relationship or shared goal

This gives the other person three things: respect (you took their ask seriously), clarity (they know where they stand), and a path forward (they're not left empty-handed).

Scripts for every direction

To your boss: "I'm excited about this project. Which of my current priorities — [A], [B], or [C] — should I pause to make room for it?" This turns a refusal into a prioritization conversation and puts the trade-off decision where it belongs.

To a peer: "Looking at my OKRs, I don't have capacity to co-own this. Would it still be helpful if I joined the kickoff and helped you identify a DRI from my group?" You stay collaborative while protecting your bandwidth.

To a customer: "I completely understand why you'd want [feature]. Right now, this falls outside our committed roadmap for the next two quarters. What we can do is [workaround] and keep you posted." Acknowledge, cite scope, offer a path forward.

To a direct report: "This sounds like a great stretch. Given my commitments, I can't lead it myself. Let's find the right owner and I'll support the handoff." You delegate without abandoning.

Deliver these in person or on a call, not over email. The same Cornell research found people overestimate how persuasive they are over email, which is part of why a refusal lands better on a call.

Try this today

Before your next meeting, pick one request you've been soft-declining or taking on without pushing back.

We built a prompt that turns it into a script for you. Open ChatGPT or Claude, paste in the saying-no script builder, and answer its questions one at a time. It writes your no around the five moves covered in this issue.

Make sure you deliver it in person or on a call, not over Slack or email.

Go deeper

👉 Lenny Rachitsky: On saying no — practical operator scripts for renegotiating commitments and filtering asks through your top priorities

👉 Kayako: How to say no to customers — B2B-specific templates with policy framing and positive flips

👉 Sunita Sah on HBR: How to get better at saying no — the defiance hierarchy and when you have a duty to refuse

👉 Darcy Eikenberg: How do I say no at work? — short, practical scripts for lateral and downward no's

Coming up tomorrow

In tomorrow's issue, we'll show you how to compress your strategy into three slides, which people will actually remember and use in real decisions.

That's it for today!

P.S. What request are you absorbing right now that you should have declined weeks ago?