← ccPlanning Academy · Communication track

Saying no with data

Deep-dive lesson · about 10 minutes · short quiz at the end

ccPlanning academy · communication · deep dive

Saying no with data

The planner’s hardest conversation — pushing back without becoming the blocker.

The big idea

Planners are the bearer of constraints.

“We can’t cover that with the heads we have.” “That target isn’t achievable.” Saying no is half the job — and done badly it makes you the office pessimist. Done well, it makes you the trusted voice of reality. The difference is entirely in the delivery.

Reframe 1

It’s not “no” — it’s a trade-off.

A flat “no” ends a conversation and a relationship. “We can do that, and here’s what it costs / what gives” continues both. You’re rarely refusing — you’re surfacing the price of a choice the requester can’t see. That makes you a partner, not a gate.

Reframe 2

“Yes, if…” beats “no, because.”

“No, because we’re understaffed” sounds like an excuse. “Yes, if we add four heads or move the deadline two weeks” sounds like a plan. Same answer — but one hands the decision and the levers back to the requester instead of slamming a door.

The data does the disagreeing

Let the numbers carry the “no.”

“I don’t think we can” is your opinion against theirs. “At this volume and AHT, hitting 80/20 needs 14 more agents than we’re funded for” is arithmetic. Depersonalise the pushback — it’s not you versus them, it’s both of you versus the maths.

Show the cost of yes

Make the invisible trade-off visible.

Requesters often don’t see what their ask displaces. Quantify it: “Pulling people for that project drops Saturday service to 60% — about 300 abandoned calls.” Once the cost is concrete and on the table, the decision becomes theirs to make with open eyes — which is exactly where it belongs.

Offer the menu

Bring options, not just objections.

The strongest pushback comes with a way forward: “We can hit the deadline with overtime at £X, or hit it free by descoping Y, or hold quality and slip a week.” Three viable options turn you from the person blocking the road into the person who knows the routes.

Tone

Firm on facts, soft on people.

You can be immovable on what the numbers say and still be warm, collaborative and respectful about it. Aggression makes enemies of allies; caving makes you useless. The sweet spot is calm certainty: “I really want to make this work — here’s the honest position.”

When you’re overruled

Disagree, commit, and document.

Sometimes the decision goes against your advice. Make your case once, clearly; if overruled, commit professionally and record the risk you flagged. No sulking, no “I told you so” later — just a calm note so the decision and its rationale are on record. That protects everyone and preserves trust.

Rewrite the refusal

From blocker to partner, one sentence

Ops asks you to release ten agents for a project this week. Blocker: “No, we’re too short.” Partner: “We can — but it drops Saturday service to ~60%, around 300 abandoned calls. Or we do it free by moving it to the quiet week, or protect service with £X of overtime.”

Same constraint. The first makes you the office pessimist; the second hands back a costed choice and three routes. You didn’t refuse — you made the price visible.

The takeaway

Turn “no” into a costed choice.

Reframe refusals as trade-offs and “yes, if”; let the data do the disagreeing; quantify the cost of the ask; bring options. Be firm on the facts and warm with the people — and when overruled, commit and document. That’s how a planner pushes back and keeps the relationship.

Now test yourself ↓

1 / 10

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: pushing back without becoming the blocker

Planners are the bearers of constraints — “we can’t cover that with the heads we have,” “that target isn’t achievable” — and saying no is half the job. Done badly it makes you the office pessimist; done well it makes you the trusted voice of reality. The entire difference is in the delivery, and the delivery is learnable.

Reframe the refusal

A flat “no” ends a conversation and strains a relationship; “we can do that, and here’s what it costs or what gives” continues both. You’re rarely actually refusing — you’re surfacing the price of a choice the requester can’t see, which makes you a partner rather than a gate. The phrasing matters: “yes, if we add four heads or move the deadline two weeks” sounds like a plan, where “no, because we’re understaffed” sounds like an excuse — same answer, but one hands the decision and the levers back. And let the numbers carry the disagreement: “at this volume and AHT, 80/20 needs 14 more agents than we’re funded for” is arithmetic, not opinion. It’s not you versus them, it’s both of you versus the maths.

Cost the ask, bring options, hold the tone

Requesters often don’t see what their ask displaces, so quantify it — “pulling people for that project drops Saturday service to 60%, about 300 abandoned calls” — and once the cost is concrete the decision becomes theirs to make with open eyes. Strengthen it with a menu, not just an objection: overtime at a price, descope for free, or hold quality and slip a week. Throughout, stay firm on the facts and soft on the people — calm certainty beats both aggression (which makes enemies of allies) and caving (which makes you useless). And when you’re overruled, make your case once, commit professionally, and quietly document the risk you flagged: no sulking, no “I told you so,” just a record that protects everyone and preserves trust.

The principle to remember: turn “no” into a costed choice. Reframe refusals as trade-offs and “yes, if”; let the data disagree; quantify the cost; bring options; be firm on facts and warm with people — and when overruled, commit and document.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. How should a planner reframe saying “no”?

A flat no ends the relationship; a trade-off makes you a partner surfacing the price of a choice.

2. Why is “yes, if…” better than “no, because…”?

‘Yes, if we add heads or move the deadline’ sounds like a plan, not an excuse.

3. What does “letting the data disagree” achieve?

‘At this volume, 80/20 needs 14 more agents’ is arithmetic, not your opinion against theirs.

4. What’s the strongest way to push back?

Making the trade-off visible and offering a menu turns you from blocker into route-finder.

5. What should you do when overruled?

Disagree, commit and record — calmly noting the risk protects everyone and preserves trust.