THE DIRECT ANSWER

Say the fact you hold first, such as the hours you have against the hours the request needs. Then say what you can say yes to now and what waits, ask who decides, and ask for the answer in writing. A polite pushback is a specific proposal, not a flat no, and it stays a proposal until the person who decides confirms it.

What does it mean to push back politely?

It means answering a request with something specific instead of a flat no or a vague yes. You show you heard the request, say the fact that stops you from simply agreeing, say what you can do now, and leave the choice to the person who decides. Polite here means the other person can see what they are choosing between.

Start from what was asked, in their words, and not from your reading of it. Then you reply to the request itself and not to what you assumed it meant. The pushback script builder has a first step for exactly that.

Which fact do I say first?

Say a fact you hold: a number, a time or a record. Saying you are swamped gives the other person nothing to answer. Saying you have five hours free and the work needs seven does. Say where the fact came from: their words, a record, or your own assumption. An assumption is a question to ask, not a fact to state.

In the fictional Fixed Deadline case, Friday noon is fixed for a client demo. The parts take core 3h, handoff 1h and polish 3h, so core and handoff are 4h and all three are 7h. When you ask Alex, the delivery lead, “How many hours do you have before Friday noon?”, the answer is “Five hours. Nothing extra has been approved.” Five hours against seven is the fact to say first, and Alex’s answer is where it came from.

Which move fits what I am pushing back on?

The pushback script builder sorts a pushback into four kinds and gives each kind three of its five moves. Pick the kind that matches what is wrong with the request:

  • Scope, when something new was added to work that is already agreed: “Which one moves?”, “Yes, if” and “In writing, please”.
  • Deadline, when the date does not fit the time you have: “Not yet, because”, “Which one moves?” and “Yes, if”.
  • Capacity, when your hours or your list are full: “Not yet, because”, “Yes, if” and “Who decides?”.
  • Decision owner, when nobody has said who can approve it: “Who decides?”, “Yes, if” and “In writing, please”.

What can I say yes to?

A scoped yes says what is in and what is out, with a time you can keep. It stays a proposal until the person who decides confirms it, so write it as a proposal. The builder asks who is asking, whether a manager, a peer, a client, someone on another team or a handover, because the wording of the questions follows who is asking.

In the Fixed Deadline case the date does not fit the hours, and the worked example below answers it with four of the builder’s five moves: not yet, a scoped yes, who decides, and in writing. The case’s own plan for it is “Core + handoff by Friday noon; polish decided separately”: core 3h plus handoff 1h is 4h of the 5h, and the demo owner decides when polish happens. Do not cut the handoff to make room. In the case’s words, “The demo needs the handoff too. Cutting it isn’t your decision.”

Who do I ask to decide?

Write one name for the person who can say yes and have it hold, or Unknown. Never two names, and never a tool. Mark how you know: their words, a record, or your assumption. The person who asked is not always the person who can approve.

In the Fixed Deadline case you don’t yet know who that is, and the case lists it among the things to ask: “Who owns the Friday noon commitment?” In the AI version of the case, Otto, a fictional AI planning assistant, opens with “All three parts can be ready by Friday noon.” Those three parts are seven hours of work against five free hours. A tool’s yes is not an approval, so the pushback goes to the person who decides, not to the tool.

How do I follow up in writing?

After they answer, write what you understood: what was agreed, who decides and by when. The builder’s last step, “Their reply”, takes what they said, a yes, a scoped yes, not yet or no, and drafts that message with blanks left in brackets.

A yes or a scoped yes stays a proposal until the person who decides confirms it. With a not yet, nothing is agreed and nothing changes on your side. Write what was said, not why you think it was said.

Where can I draft it?

Use the builder for the words, and the case for a safe place to try the questions first.

AUTHORED FICTIONAL EXAMPLE

A conversation you can rehearse

Authored fictional example, the Fixed Deadline case. Friday noon is fixed for a client demo. Five hours are free before then and nothing extra is approved. The parts take core 3h, handoff 1h and polish 3h. Someone asks you to have all three ready by Friday noon, which is 7h against 5h. You do not yet know who owns the Friday noon commitment.

A first reaction

“I’m too busy for all three. It can’t be done by Friday.”

A more specific response

“Friday noon stays fixed, so I can’t say yes to all three parts yet. I have five hours free before then, and the three parts need seven: core 3h, handoff 1h, polish 3h. What I can say yes to now is core and handoff, which is four of the five hours. Polish waits for a decision. Who owns the Friday noon commitment? Once I know, I will send this to that person and ask for a confirmation in writing. I will reply again by Wednesday 16:00.”

The first reaction is a refusal with no fact, so the other person cannot tell what is possible or what to decide. The second says the fact first, offers a scoped yes that keeps the handoff, asks the case’s own question about who owns the commitment, and asks for a confirmation in writing. It does not decide when polish happens, and it stays a proposal until the owner confirms it.

Before you act

  • Write what was asked, in their words.
  • Start with a fact you hold, a number, a time or a record, and say where it came from.
  • Say what you can say yes to now and what waits.
  • Ask who decides: one name or Unknown, never a tool.
  • Give a time you can keep for your next reply.
  • Ask for the answer in writing, and write down what was said, not why.

Common questions

What if the request comes from my manager?

The builder’s wording follows who is asking. For a scope or deadline pushback to a manager, the script asks which one moves: the new request or something already on your list. It is a question about priorities, not a refusal, and it still starts with the fact you hold.

What if I do not have the numbers?

Use a time or a record, or say what you are missing. The builder compares hours only when you fill in both and the work needs more than you have, and it leaves out a claim that has no number behind it, so a script never says something does not fit without the numbers that show it.

What if they say not yet or no?

Write it down as it was said. With a not yet, nothing is agreed, so you wait for the person who decides to confirm and say when you will check back. With a no, plan to the work already agreed and say so in writing, so you both hold one version.

What if an AI tool wrote or approved the request?

Check the builder’s AI box and take the request to the person who decides, not to the tool. In the fictional Fixed Deadline case, Otto, a fictional AI planning assistant, says all three parts can be ready by Friday noon, which is seven hours of work against five free hours.

What this does not claim: the cases and the example are fictional and authored, and no measured outcome is claimed, including that pushing back this way leads to a yes, an agreement or a better working relationship. Your role, your organization and the request itself decide who can say yes.

Source basis: an original scenario-based practice framework. The example is fictional, and no external research finding or measured effectiveness is claimed. Read the editorial method.