People, process, delivery and AI. Fixed properly, and measured.

Playbooks / Clarity · 2 min read

How to say no

Every yes to new work is a silent no to something already promised.

The problem

“We keep saying yes and missing everything”

In the model

Process · Clarity

In 30 seconds

  • Never answer on the spot. "Let me see what this moves."
  • Show what's already committed. The question becomes "what does this replace?"
  • Offer options, not refusals: yes if, yes but smaller, yes but later.
TODAY A B C AFTER A YES A B D (new) C slips Team capacity doesn't move when you say yes
Capacity is fixed. New work doesn't add to the bar. It pushes something out.

The situation

The team is full. Another request lands. You say yes. Three yeses later nothing ships on time and evenings disappear.

What's really going on

When you hide the trade-off, you make the decision for the person asking, and then fail to deliver both. A good no doesn't refuse. It hands the trade-off to the person who owns it.

What to do

  1. Pause. "Let me look at what this would move" buys an hour and signals cost.
  2. Show the list. Visible commitments turn "can you?" into "instead of what?"
  3. Give options. Yes if X moves. Yes, smaller. Yes, in March. Not now, and why.
  4. Shield the team. Route requests through you so engineers don't have to choose between helpful and focused.

How you'll know it's working

  • Delivery: commitments delivered against commitments made, last quarter, improving.
  • Interruptions: unplanned work as a share of the total, trending down.
  • Care check: nobody worked evenings or weekends to absorb a yes.

In the frameworks

  • Kanban: WIP limits are a structural no: stop starting, start finishing.
  • Shape Up: Appetite and the betting table: decide what a problem is worth, and bet on a few things instead of promising everything.
  • SAFe: WSJF and capacity allocation make the trade-off visible at train level.

In other industries

  • Healthcare Another service lands on a full clinic list. Ask which sessions it replaces.
  • Accountancy A partner promises a client a fast turnaround in busy season. Show the team's deadlines before anyone agrees.
  • Manufacturing A rush order hits a fully loaded line. Show which orders it pushes back, and let sales choose.
  • Small business Saying yes to every customer feels like survival. Ask what this job stops you doing.

The scripts

To your boss:

"Happy to take this. We're committed to A, B and C. Which should move?"

To an urgent stakeholder:

"If we start this week, payments slips about two weeks. Is that the right call? If so, I'll tell the payments team today."

To a good idea at the wrong time:

"I don't want to do this badly. Can it go to the top of next quarter instead?"

To a request bigger than it needs to be:

"What's the smallest version that solves the problem? Let's start there."

To an engineer who said yes without checking:

"Thanks for helping. Next time, bring it to me first, so you're not choosing between them and the sprint."

Avoid

  • "We're too busy." It starts a debate about how busy you are.
  • Saying yes and working evenings. It hides real capacity.
  • No without an alternative. It ends the conversation instead of moving it.

Try this week

Write your team's current commitments on one page. Share it before the next request arrives.

Think about it

What did your team quietly stop doing the last time you said yes?

More for Clarity

Leadership has a vision. My team has no idea how their work connects to it.From vision to the graduate's first dayProcess · Clarity→