Question and when it applies
Describe a real case where new information made an existing promise unreasonable. State the original promise, what changed, the cost of keeping it, the options you offered, who approved the new promise, and the outcome. This question is useful for engineering, product, data, operations, and program roles. Amazon describes behavioral interviews as evidence of past decisions; its Leadership Principles connect resource choices to customer value. Atlassian recommends ranked goals and a communication cadence. The focus is early, explicit renegotiation, not a surprise delay.
What interviewers assess
Interviewers look for evidence that you can recognize a material change, quantify impact, offer choices, obtain authority, and own the result. Strong answers name what was protected and what was postponed. Use real tickets, customers, dates, capacity, or quality signals; do not invent precision.
Questions to clarify before answering
- What new fact changed the priority?
- Who was covered by the original commitment?
- What would fail first if the plan stayed unchanged?
- What two or three executable options exist, and what does each cost?
- Who has decision authority?
- What are the new acceptance criteria, date, and owner?
- How did affected people hear the change?
- How was the outcome verified, and what happened to postponed work?
- Is the story actually about a missed deadline or saying no?
30-second answer framework
“I had committed to [result] by [date]. Then [new fact] made the old plan create [cost]. I used [evidence] to estimate impact and offered [option A] and [option B]. With [decision owner], I confirmed [new scope, acceptance, and date]. I owned [actions]. The result was [outcome], and [postponed work] was [completed, cancelled, or redefined]. I then added [mechanism].”
Deep answer, step by step
Step 1: Choose a true commitment change
Include the original promise, new fact, options, and your actions. A story with no trade-off or an unapproved date change does not show renegotiation.
Step 2: Quantify the cost of staying on plan
Explain the effect on customers, compliance, revenue, reliability, or capacity. Separate observed facts from predictions and show the evidence behind predictions.
Step 3: Offer options with costs
Compare at least two paths: narrower scope on the same date, full scope on a later date, approved resources, or pausing lower-value work.
| Option | Protected | Given up | Who confirms |
|---|---|---|---|
| Narrow scope | Core result and date | Non-core cases | Product owner |
| Move date | Full scope and quality | Original external date | Customer owner |
| Add resources | Date and scope | Budget and coordination | Resource owner |
Unauthorized staffing, unlimited overtime, or skipped controls are not executable options.
Step 4: Renegotiate explicitly
Share the original promise, evidence, and options. Ask for a decision and record scope, date, acceptance criteria, risk owner, and review time. Identify who communicates customer changes and how team capacity is released.
Step 5: Execute transparently
Split work, update dependencies, notify affected people, protect quality gates, and stop lower-priority work when agreed. Report progress, residual risk, and the next decision point directly.
Step 6: Verify the new promise
Use acceptance checks, customer confirmation, defects, cycle time, or capacity. State the cost of the new plan, such as fewer cases or temporary manual review.
Step 7: Close postponed work
Name whether it was completed, cancelled, or redefined. Give an owner and completion condition. Useful mechanisms include a priority-change log, commitment register, capacity check, and review cadence.
High-quality sample answer
This fictional example must be replaced with your evidence:
“I had promised invoice exports for four customers in two weeks. One week before launch, Finance confirmed that a regional tax rule was not approved. Keeping the scope could have sent an unapproved format.
I verified review status and usage, then offered three paths: launch only approved regions on time, delay everything a week, or add an approved specialist. I recommended the first path because it protected three customers’ close process while making the fourth date explicit. Finance, Customer Success, and my manager confirmed the new scope. I updated the release switch, notified customers, and checked validation daily. Three customers completed close on time, the fourth received a confirmed date, and no invalid format was sent. When approval arrived, we added the fourth region and documented a gate that blocks unapproved formats.”
Common mistakes
- Saying “priorities changed” without evidence.
- Announcing a delay without a decision owner.
- Offering one preferred answer instead of costly alternatives.
- Treating overtime as an authorized plan.
- Updating only a project tool.
- Ending at “we shipped” without cost or unfinished work.
- Leaving postponed work informal.
- Inventing precise numbers.
- Saying “we” throughout instead of identifying your contribution.
Follow-ups and how to answer
Follow-up 1: Why not keep the original commitment?
Connect the new fact to the harm of staying on plan. Explain why narrowing scope or moving the date was safer.
Follow-up 2: What if the other person rejects the new date?
Clarify authority, offer a smaller or staged outcome, document the risk, and escalate to the person who can decide.
Follow-up 3: How do you prevent priority churn?
Use ranked goals, a change entry point, and a regular cadence. State what is given up for every change.
Follow-up 4: What if postponed work was never done?
Say whether it was cancelled, disproved, or still delayed, and explain how remaining risk stayed visible.
Follow-up 5: What changed in your working style?
Name one observable practice, such as capacity checks before commitments, a risk register, buffers for external promises, or expiry reminders.