When The Deadline Comes From Someone Who Will Not Do The Work

When a deadline comes from someone who will not do the work, arguing about whether it is realistic goes nowhere. Answer with a trade instead of a refusal. Show what fits inside the date, show what does not, and hand the decision back to the person who set it. They keep their date, you stop being the obstacle, and the scope becomes the thing under discussion, which is where it belonged.

"We cannot do that by then" invites a debate about your team's ability. "Here is what fits by then" invites a choice.

Why refusing rarely works

The person setting the date usually has a reason you cannot see: a customer commitment, a board meeting, a season, a contract. From where they sit, the date is not a preference, it is a constraint.

So a flat no reads as your team not understanding the business. And a reluctant yes is worse, because it commits you to something you know will not happen and moves the argument three months later, when it costs more.

The trade avoids both. It accepts the date as fixed and treats scope as the variable, which is normally the truth anyway. It also keeps the conversation off effort, which is rarely the real reason a date slips.

Build the two lists

Go away for a day and produce two lists.

Fits by the date. The pieces you are confident about, with the reasoning attached. Keep this list honest and slightly conservative, because you are going to be held to it. Where the list includes work the team has never done before, say so rather than quoting a number that only sounds confident.

Does not fit. Everything else, each with a short note on what it would need. Not "no time", but the actual constraint: this needs the finance team's sign-off and they book three weeks out, or this depends on the supplier's release which lands in June.

Then a third short list is worth adding: things that could fit if a specific decision goes your way. A pre-approved budget line, a reviewer freed up, a feature dropped. This is the list that gives the other person something to do besides accept or reject.

Present it as a choice, not a complaint

Take both lists to the person, quickly, and say the shape out loud: the date holds, and here is what lands on it. If you want the rest, one of these has to change.

Give them options that are real, and no more than two or three. Ship the smaller thing on the date and the rest six weeks later. Or move the date by a month and ship it whole. Or add a second team, with the honest note that adding people mid-project buys less than it costs for the first few weeks.

Whichever they pick, write it down the same day and send it to them. The point of the exercise is a shared record of what was chosen, so that in three months nobody is remembering a different conversation.

Say what you need from them

Deadlines set from outside usually come with dependencies the setter controls and has not noticed. Approvals, access, decisions, budget, other teams' time.

List those explicitly, with dates. "For the March date to hold, we need the content by the sixth and the legal review booked for the twentieth." That converts a one-way instruction into a shared plan, and it means a later slip is visibly about the missing input rather than about your team being slow.

This is also your best protection. A date that depends on someone else's decision is not really yours to miss, but only if the dependency was on the record before the fact.

When the answer is still all of it

Sometimes the person hears the trade and says everything, on the date, anyway. Then you have a different job.

Do the arithmetic and put it in writing once, plainly, without drama. What you can do, what will not be finished, and what the likely consequence is. Send it, and then get on with the work. You are not going to win by repeating yourself, and the written record is what matters if the date does break.

Also decide privately what you will protect. Under pressure, something gives: usually testing, handover or documentation. Choosing that in advance, deliberately, is better than discovering in the last week that all three quietly vanished.

The habit worth building

Never respond to an imposed date on the spot. Say you will come back tomorrow with what fits. A day of thinking turns a defensive conversation into a planning one, and it gives you room to add buffer you can defend instead of a round number stuck on the end.

Do that a few times and something changes: people start asking you what fits before they announce the date.