Tradeoff-Transparent Pushback
Never say no to a request — show the three things it displaces and let the asker decide
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 90%
Saying no is unpleasant and pushes junior people into a position they shouldn't have to hold. Lachs's alternative: because the data team shares its partner team's goals, any incoming ask can be placed against the current priority stack and the requester asked whether it genuinely outranks them. Most people, once shown the tradeoff, withdraw the ask themselves. The leader's job is to make this the operating model so juniors never have to be the ones refusing.
Origin
Jessica Lachs, DoorDash — developed as a self-described 'people pleaser' solving for how to protect a team's priorities without making refusal a personal act.
Core principles
- 01Shared goals with partner teams make prioritisation a joint problem, not a turf fight
- 02Don't say no — surface the tradeoff and let the requester weigh it
- 03Never suffer in silence trying to fit four things into three slots
- 04Leadership must establish the operating model so junior people aren't forced to say no
- 05Stay open: the requester may hold context you don't
- 06Occasionally just do the quick one to build goodwill
How to run it
- 1
Align goals with the partner team first
Ensure the data team carries the same goals as the team making requests. This makes every prioritisation conversation a shared 'how do we both hit our goals' rather than a defence of your own queue.
Watch out Without shared goals, the tradeoff conversation reads as obstruction.
- 2
Establish the operating model from the top
Leadership defines the rules of working — what gets prioritised, how tradeoffs are raised — so juniors invoke a norm rather than personally refusing a senior stakeholder.
Watch out If a junior analyst has to say no on their own authority, they will simply say yes to everything.
- 3
Answer every ask with the displacement it causes
Respond with the tradeoff, not a refusal: here are the three things I was going to do this week toward our shared goals — is this data pull more important than those, yes or no?
Pro tip Put the tradeoff front and centre. People frequently don't realise a tradeoff exists, and once they see it they often withdraw the ask themselves.
Watch out A flat 'no, I won't do that' is not the approach — it kills the conversation and the relationship.
- 4
Give your view, then invite the counter
State your position plainly ('I don't think your ask is more important than these three things') while explicitly leaving room for information you don't have. Then have the conversation.
- 5
Re-evaluate prioritisation on a cadence
Run a recurring prioritisation check — a weekly standup on 'here's what we're doing this week, do we like this order?' — or a less formal equivalent. Constant re-evaluation is the hygiene that keeps the team on the most impactful work.
Pro tip Occasionally just knock out a five-minute ask without ceremony; the goodwill is worth it. Reserve ruthless prioritisation for anything larger.
In the wild
A stakeholder asks for a quick data pull. Rather than refusing or silently absorbing it, the analyst asks whether it is more important than the three goal-aligned items already planned for the week. Faced with the explicit tradeoff, the stakeholder often realises the ask can wait.
→ The request is deprioritised by the requester rather than refused by the analyst — the queue is protected and the relationship is strengthened.
Alongside tradeoff transparency, the team demonstrates the value of longer-term work by pointing to the opportunities deep dives have surfaced, making the case that its time is better spent there than on the on-fire asks.
→ Business partners actively encourage the team to protect self-directed time.
Common mistakes
Suffering in silence
Trying to quietly absorb all four asks means quality drops on everything and the stakeholder never learns their request had a cost.
Flat refusal
'No, I won't do that' is, in Lachs's words, not a great approach. It forecloses the conversation and hides the possibility that the requester has context you lack.
Leaving the no to junior staff
Without a leadership-set operating model, junior analysts must personally refuse senior stakeholders — a position they will avoid by saying yes to everything.
Is it for you?
Best for
Data, design, and platform teams — and their leaders — who serve internal stakeholders and are drowning in ad-hoc requests they feel unable to decline
Not ideal for
Genuine incidents and emergencies, where the tradeoff conversation is the wrong response and the right one is to drop everything
From the transcript
“hey we've got a limited amount of time these are our goals what are the most important things that we are going to work on…”
“always share the tradeoffs don't kind of suffer in silence”
“it's really important for to establish a culture and to for leadership to really sort of establish the rules of working”
“I personally don't think that your ask is more important than these three things but maybe there's new information”
From the episode
Building a world-class data org
Jessica Lachs (VP of Analytics and Data Science at DoorDash)