Tell Me About a Time You Recommended Stopping a Project People Had Already Put Months Into
Behavioral and LeadershipPrioritization and TradeoffsAsked atStaffPrincipalUpdated
They're checking whether you can call a stop when the evidence says so, despite sunk cost and the people attached to the work. Strong answers show the signal, how you made the case, and how you handled the team and the work left behind.
Rubric by Level
Junior
- Raised a concern that a task or approach was no longer worth finishing, with a reason.
- Accepted a decision to drop your own work and moved on cleanly.
- Names what you learned from the dropped work.
Mid
- Recommended dropping a feature or approach you had started, with evidence.
- Proposed where the time should go next.
- Kept the useful parts.
Senior
- Recommended stopping a project your team owned after its core assumption failed.
- Presented what continuing would cost from here, with sunk cost set aside.
- Told the team directly and credited the work.
- Salvaged what had value and cleaned up the rest.
Principal
- Stopped a major initiative with executive sponsorship and public commitments.
- Built a practice of setting kill criteria for big bets up front.
- Shows how you kept trust with the sponsors and the teams.
Red Flags
- Waited for the project to fail on its own.
- Announced the decision without talking to the team first.
- Can't name anything salvaged or learned.
Follow-Ups to Expect
- How did the team that built it react?
- What would have made you stop it sooner?
A Story Shape That Holds Up
The Project
What it was, who backed it, and how much had gone in.
The Signal
What told you it should stop.
The Case
How you made the recommendation, and to whom.
After the Stop
How the team landed, what you kept, and where the capacity went.