Tell me about a time priorities shifted mid-project and you had to replan.
answer
- the plan you were executing before
- the signal, not the feeling
- re-ranked against the goal
- what you cut and the trade named
- who you told first, then the number
basics
~20 sProbes whether you replan deliberately instead of quietly absorbing more work. Answer by naming the signal that changed, re-ranking against the original goal, cutting something explicitly, and telling the affected people before they read about it.
how to answer
5 beats- the plan you were executing and the signal that broke itSet the original commitment in a sentence or two, then name the concrete signal — a volume change, a new constraint, a decision above you. Keep setup to roughly fifteen to twenty percent of the answer; the shift is the trigger, not the subject.
- how you re-read the goal before touching the planShow that you went back to what the work was for and re-ranked the remaining items against that, rather than reacting in the order things arrived. Say what you deliberately did not do first, such as asking the team to absorb it.
- the call you made and what you cutName the specific thing you dropped or deferred and the trade it bought. Say whether you brought it as a proposal or a decision, and to whom. This beat and the next carry the bulk of your roughly sixty percent of action airtime.
- how you carried the change to everyone it touchedDescribe the sequencing: who heard it directly and before the announcement, what you wrote down, and how the revised plan became visible. Telling the person whose work you cut before the public message is the detail interviewers remember.
- where delivery landed, and what you would resequenceClose with the outcome after the reset — a date, a measure, what shipped — and one honest thing you would do earlier next time. Result plus reflection is the last twenty to twenty-five percent.
your answer
5 story prompts- Pick a moment when a plan you owned was invalidated mid-flight, ideally in the last two years.
- Name the exact signal that told you to replan, not the general feeling that things got busy.
- Identify what you dropped and who you told first — that pairing is the spine of the answer.
- This can be the same project as your unclear-scope story, re-angled to the moment it changed.
- Write down one number from after the reset, so the answer does not end on intentions.
draft and rehearse your own answer in a learn session
go deeper
Priorities move on every real team, so the signal here is whether you respond with judgement or with heroics. Interviewers look for someone who re-tests the plan against the underlying goal, makes an explicit trade-off instead of quietly piling work on, and carries the change to everyone it touches. A strong answer names the cost you accepted and who you told first.
We were six weeks into a hardening milestone on an open-source vulnerability scanner when the ground moved. The project absorbed a community fork that brought a whole new package ecosystem with it, and inbound reports went from about seven a week to 21 within a fortnight. My first instinct was to ask the team to soak it up. I did not. I took a day and went back to the sentence we had actually signed up to, which was that a maintainer can give any incoming report a verdict in the same week, and I re-ranked the four remaining deliverables against that sentence instead of against the order we had written them in. Two of them no longer served it: a reporter-facing status page and a rewrite of our severity scoring. I dropped the status page outright and deferred the rewrite. I brought that as a proposal rather than a decision — I showed the three maintainers who owned that work what I wanted to drop and what it bought them in return, which was not being underwater for the rest of the quarter. Then I over-communicated. I rewrote the milestone issue in place, posted a comment naming exactly what changed and why, and spoke to the two contributors whose work I had cut before that comment went up, not after. We closed four weeks later with a median verdict time of 44 hours against a much larger queue. What I would redo: I sized the fork's volume from a guess when a two-day sample was sitting right there.
The senior signal is re-ranking against the stated goal rather than the backlog order, a cut brought as a proposal to the people it hurt, and sequencing the private conversations before the public post. Remove the named cut and this becomes a story about working harder, which is a downlevel.
I lead the security programme across a family of open-source repositories, and I own a published roadmap that three sponsoring organisations and roughly forty volunteer maintainers read. Two quarters in, the ground shifted: downstream distributors began requiring machine-readable advisories, and a large part of the roadmap assumed a human-readable feed nobody would need much longer. I did not quietly re-plan. I named the shift in a public post — here is what changed, here is the assumption it invalidates, here are three options and what each costs in maintainer time. Then I killed the biggest item on the roadmap, a contributor analytics portal with a sponsor's name attached to it, and I had that conversation with the sponsor directly a week before the post went out, because being surprised in public is how you lose a sponsor. The mechanism mattered more than that one decision. I introduced a standing re-scoping review every six weeks with a fixed agenda: what did we learn, which assumption broke, what do we stop. Having a scheduled place for it meant a maintainer could raise a broken assumption without it reading as a complaint. Over the following two quarters we shipped the machine-readable feed, and the median verdict time on the flagship repositories moved from 52 hours to 19 while weekly report volume rose from 34 to 57. Two sponsors adopted the same six-week review internally. The cost I will name honestly: the portal had two volunteers' evenings in it and I gave them nowhere to land. I do that part first now.
This works because the repeatable mechanism outranks the single decision, the unpopular kill is handled with the funder before it goes public, and the closing cost is named without softening. Drop the standing review and it collapses into a large project story rather than programme-level ownership.
Your scope is your own work. Show that you noticed the change quickly, raised the conflict rather than silently dropping something, and asked which of two things should slip. Naming who you asked is the whole signal here.
Show the re-ranking, not just the reaction. Explain how you re-tested your remaining tasks against the actual goal, which item you proposed dropping, and how you confirmed the trade with whoever owned the outcome before acting on it.
You are replanning for other people. The bar is an explicit cut made as a proposal, a revised plan with dates the team can see, direct conversations with anyone whose work you dropped, and a delivery number after the reset — not before it.
Talk about how re-scoping happens repeatably: a standing review, a written record of broken assumptions, an announced change of direction rather than a silent one. Include the cost of the thing you killed and who you told before it became public.
saying these in an interview costs you the question
- Absorbing the new work with no cut and calling that flexibility
- Describing the shift as chaos inflicted on you rather than a decision input
- Replanning privately so the team learns about it from the ticket board
- No trade-off named — everything stayed in and somehow still shipped
- Letting the person whose work was cut find out after everyone else
- What did the change cost, and who paid it?Answer this literally rather than reassuringly. Name the work that was thrown away, the person whose effort it was, and what you did for them — reassigned it, banked it, gave them the next piece they wanted. Interviewers distrust replanning stories where nobody lost anything.
- How did you decide the new priority was genuinely more important?Show a test, not an instinct. Strong answers cite the goal or commitment the work was serving and explain how the new information changed what served it, plus who you checked that reasoning with. Saying leadership asked for it, with no reasoning of your own, is the weak version.
- How did the team react when you told them?Be honest about friction and specific about sequencing — who you told first, in what setting, and how you handled the person who disagreed. A story where everyone immediately agreed reads as sanded down; a story where you managed one real objection reads as lived.