Saying No by Trading Off
Never say no. Say yes, name what it displaces, and hand the prioritisation back.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
Saying no makes people feel rejected and makes you look uncooperative, which is why people-pleasers say yes to everything and drown. The workaround is to never issue a no at all: accept the request, state exactly what it will displace, and ask the requester to choose. You get the outcome of the no — protected bandwidth — while the requester feels in control and sees you as a thoughtful guardian of priorities.
Origin
Wes Kao learned this from Alex Peek, her design counterpart at altMBA (now its CEO), who was uniquely good at declining work in a way that felt good to the person asking. Lenny adds a closely related version — 'prioritise and communicate' — taught to him by a former manager.
Core principles
- 01The reason we want to say no is bandwidth; the reason we can't is fear of looking uncooperative. Trade-offs dissolve both.
- 02Reframe the conversation from 'are you a team player?' to 'how do we make sure the right things get done?'
- 03Handing the choice back gives the requester control, which is why the no doesn't sting.
- 04Prioritising without communicating is invisible; communicating without prioritising is just a no. Do both.
- 05The right approach depends on the relationship — an ongoing one (manager, colleague, friend) is different from a cold internet ask.
How to run it
- 1
Say yes to the request itself
Open by affirming you can do the thing. This removes the yes/no, team-player/not-a-team-player frame entirely.
- 2
Name the specific displacement
State exactly what will be delayed or de-prioritised: 'Yes, I can design this PDF for you — that means the thing I was going to work on today, redesigning this page on the site, will have to wait until later this week.'
Pro tip Be concrete about which project and by how long. Vague 'I'm busy' is just a no with extra steps.
- 3
Hand the decision back
Close by asking them to choose: 'Does that sound good to you, or do you want me to prioritise the original design project?'
Pro tip This is the step that makes the requester feel in control rather than rejected.
Watch out Skip this and it reads as a complaint about your workload, not a prioritisation conversation.
- 4
For accepted work, prioritise AND communicate
Lenny's complementary rule: don't silently slot the new work into your list, and don't just refuse. Tell them where it lands — 'this will be third in my priority list, does that seem reasonable, should I do this sooner?'
- 5
Adjust for relationship type
Use the trade-off method with people you have ongoing dynamics with — managers, colleagues, friends. Cold internet requests from people who don't know you are a different situation and warrant a different response.
In the wild
At altMBA, Kao would repeatedly throw design work over the wall to Alex Peek. Rather than refusing, he would say yes and name the trade-off — this PDF means the site page redesign waits until later this week — then ask which she'd prefer.
→ Kao, the person being told no, came away feeling in control and thinking he was exceptionally thoughtful about keeping the most important projects prioritised. She reverse-engineered the technique and adopted it.
A manager taught Lenny a two-by-two: you can prioritise without communicating (invisible), communicate without prioritising (a bare 'no time for this'), or do both — slot the request explicitly at number three and tell the requester where it sits and why.
→ The same protective effect as the trade-off method, expressed as an explicit prioritisation contract.
Common mistakes
Saying no outright
A bare no makes the asker feel irked or miffed, and puts you in a frame where you look uncooperative. The trade-off gets you the same protected bandwidth without ever using the word.
Saying yes to everything
The people-pleaser default. You take on more than your bandwidth allows, which costs your mental health and your ability to do great work without feeling overly stretched — and the work still isn't the right work.
Silently absorbing the work
Prioritising the request internally without telling anyone where it sits means the requester has no idea when it lands, and you have no protection when it slips.
Is it for you?
Best for
Anyone with ongoing working relationships — designers, engineers, PMs, ICs — who is over-asked and can't decline without guilt
Not ideal for
Cold requests from strangers on the internet, or situations where the answer is a genuine hard no on principle rather than a bandwidth constraint
From the transcript
“Alex would always talk about trade-offs”
“does that sound good to you or like do you want me to you know prioritize the original design project you wanted me to work…”
“you're not exactly saying no but you're talking about trade-offs”
“you protect your bandwidth you protect your mental health you protect your you know ability to do great work without feeling overly stretched”
From the episode
Persuasive communication and managing up
Wes Kao (Maven, Seth Godin, Section4)