Practise pushing back on a deadline with an AI executive
VirtualInterview.ai runs the conversation where a senior stakeholder wants your project sooner. An AI executive opens with the new date, and in about 8 minutes you have to find out what the date is for, explain the constraint, offer options and get a decision. The debrief scores discovery, constraint, options and decision against 4 goals.
Last updated
- Free account, no card
- Voice or typed answers
- About 8 minutes
Pushing back on a deadline: key points
- Find out what is driving the deadline before you push back. The date often matters less than the outcome behind it.
- Explain the constraint with facts: work remaining, capacity, risks and dependencies.
- Offer options rather than a flat no: reduce scope, add resources, accept more risk, or move the date.
- Ask the stakeholder to choose between the options so the trade-off is explicit and owned.
- Confirm the decision in writing and say how you will report progress.
Who should practise a deadline pushback
It is for engineering managers, product managers, project leads and consultants who either agree to dates they cannot hit or say no in a way that gets them overruled.
- A launch has been pulled forward for a board meeting or a customer.
- You are told "other teams move faster".
- Your instinct is to defend the estimate line by line.
- You need a decision on scope, people or date before you leave the room.
How to prepare for a deadline pushback
Prepare by understanding why the stakeholder wants the date, quantifying the work and risks, building two or three realistic options with their trade-offs, and planning how you will ask for a clear decision while keeping the relationship strong.
Step 1: Find the real driver
Is the date tied to a launch, a customer, a board meeting or simply a preference? Ask around before the conversation.
Step 2: Quantify the gap
Estimate the remaining work, available capacity and the shortfall in days or people.
Step 3: List the risks
Name what is likely to go wrong if the team rushes: quality, burnout, missed requirements.
Step 4: Build options
Prepare two or three: a reduced scope by the date, the full scope later, or extra resources. State the cost of each.
Step 5: Choose your recommendation
Decide which option you recommend and why, while being ready to accept another.
Step 6: Plan the close
Know how you will ask for a decision and confirm it in writing.
What you will hear in a deadline pushback, and how to respond
An impatient stakeholder will say the date is fixed, question your estimates, suggest the team works harder, compare you with others, and try to avoid choosing. Ask about the driver, show the numbers, offer options and ask for an explicit decision.
"The date is not negotiable."
Why it comes up: Sometimes true; often a starting position.
How to respond: Ask what depends on the date. If it is truly fixed, move the conversation to scope and resources.
Example: “Understood. Help me understand what is happening on that date, so we make sure what matters most is ready for it.”
"Can the team just work harder?"
Why it comes up: Overtime is the easiest answer for the person not doing it.
How to respond: Explain the risks of sustained overtime to quality and the team, and quantify how much it would really close the gap.
"Your estimates are always too cautious."
Why it comes up: It challenges your credibility.
How to respond: Show how the estimate was built and any past accuracy. Offer to review it together.
"Another team did something similar in half the time."
Why it comes up: Comparisons pressure you to match a number.
How to respond: Ask about the differences in scope and context, and explain what makes this project different.
"Just make it work."
Why it comes up: It avoids making a trade-off.
How to respond: Restate the options and ask them to choose. Make clear what you will deliver under each.
"I will need to escalate this."
Why it comes up: Escalation can feel like a threat.
How to respond: Stay calm and offer to prepare the options together for the escalation, so the decision-maker sees the full picture.
How the practice conversation runs
The executive states what they want, and the conversation runs through the ask, the real driver, the constraint, options and decision. They ask whether the team can push harder and compare you with other teams, with up to 4 pushbacks.
- Planned length
- About 8 minutes
- Planned exchanges
- 4, plus up to 4 pushbacks
- Who speaks first
- The VP Product
- Pressure levels
- friendly, standard, tough
- In the room
- Speak or type, redo an answer, see a sample answer
- Languages
- 50+ languages
The phases, in order
- The ask
- The real driver
- The constraint
- Options
- Decision
The AI VP Product you practise against
Graham Wells is the stakeholder (VP Product): senior, impatient and more interested in options than explanations. There is a reason behind the date, and the executive says what it is only when you ask what the date is for.
Your goals in the conversation
- Find the real driver
- Explain the constraint
- Offer options
- Get a decision
Setting up a deadline pushback
No field is required, and you may attach your notes. Each one you fill in brings the conversation closer to yours. You can also skip the form and describe the whole thing in one sentence.
For example: “My VP wants the new onboarding flow shipped three weeks early for a board meeting; the team is already at capacity”
Optional
- Project
- Their ask
- What makes the date hard
- Stakeholder
What the AI VP Product says
These lines are scripted: Graham Wells uses one when your reply calls for it and improvises everything else from what you entered, so the conversation differs each time.
Opening
“I need this three weeks earlier. Tell me how we get there.”
Pressure
“Can't the team just push a bit harder?”
Comparison
“Other teams manage to move faster. Why not yours?”
Commitment
“The board is expecting the original date. What do I say to them?”
How a deadline pushback is scored
It is scored by a leadership coach who observed the conversation, on discovery, constraint, options and decision. Above 60% you protected the plan and left with a clear decision.
Discovery · 25%
Finds out what is really driving the date
Constraint · 25%
Explains the constraint with facts, not complaints
Options · 30%
Offers concrete options with trade-offs instead of a flat no
Decision · 20%
Gets an explicit decision and confirms it
Report headline: “Decision on your terms”, “Compromise reached” or “Overruled”.
What it tells you to drill next
- Ask what the date is for.
- Bring two options, not a no.
- Confirm the decision out loud.
More: scoring methodology · sample report · pricing
Common mistakes in a deadline pushback
Pushback fails as a flat no or a reluctant yes. Both skip the two things that work: asking what the date is really for, and bringing options that let the stakeholder choose a trade-off.
Defending the estimate first
Ask what the date is for before you explain why it is hard.
A constraint in team jargon
Explain the limit in terms of risk to the outcome the stakeholder cares about.
One option
Bring at least two: less scope, more people, or a later date for part of it.
Leaving without a decision
Confirm what was decided out loud before the meeting ends.
Checklist before a deadline pushback
Before the conversation, know the driver behind the date, have the remaining work and capacity quantified, a list of risks, two or three costed options, your recommendation, and a plan to confirm the decision in writing.
- What depends on the deadline, and why.
- Remaining work, capacity and the shortfall.
- The main risks of rushing.
- Two or three options with their trade-offs.
- Your recommended option and reasons.
- A short summary you can share with others.
- A follow-up email to confirm the decision.
What this practice is not
It is rehearsal for one conversation with someone you work with. It is not HR or legal advice, and the AI counterpart is not a model of the real person.
- The counterpart's backstory is invented for the role-play; the real person will have their own.
- It does not know your project, your team's capacity or your organisation's politics beyond what you enter.
- The executive is a simulation; a real one may have constraints this role-play does not model.
It also does not feed you answers during a real interview.
Pushing back on a deadline: questions people ask
The questions people ask before they practise a deadline pushback with the AI VP Product, each answered from how this scenario is set up today.
How can I practise saying no to an unrealistic deadline?
Start the deadline pushback role-play and optionally enter project, their ask, what makes the date hard and stakeholder. The AI executive opens with the demand and responds to how you handle it.
What counts as a good outcome?
The debrief labels the conversation "Decision on your terms", "Compromise reached" or "Overruled". The top label needs the real driver found, the constraint understood, options offered and a decision stated.
Is it only about deadlines?
The scenario is written around a date, and the same structure fits a scope or headcount demand: enter what they are asking for and what makes it hard. For an unrelated conversation, use the custom scenario.
Is practising a deadline pushback free?
Yes, on the free plan: 2 sessions a month (your first session runs full length, later ones are 5-minute sessions), with a free account and no card. Pro is $20/month, and one-time credit packs start at $9.
Rehearse a deadline pushback before the real one
A free account, about 8 minutes and the AI VP Product on the other side.
Practise the pushback