“Tell Me About a Project That Failed”: How to Answer as a PM
“Tell me about a project that failed” is one of the questions project managers dread most, and one of the most predictable. Interviewers are not looking for a perfect record: they want to see how you judge, own and learn from a bad outcome. This guide shows how to pick the right story, structure your answer and handle the follow-up questions.
Why interviewers ask “tell me about a project that failed”
Every project manager has worked on projects that missed a date, ran over budget or delivered something nobody used. A hiring manager knows this. If you claim you have never had a project fail, they will assume you either have not run real projects or cannot see your own mistakes. Neither helps you.
The question tests four things at once:
- Ownership. Do you describe your own decisions, or only what the client, the vendor or the team did wrong?
- Judgement. Can you explain why things went wrong in a way that shows you understand how projects work?
- Recovery. What did you do once you saw the problem? Did you escalate early, re-plan, or wait and hope?
- Learning. What do you do differently now, and can you prove it with a later project?
It belongs to the same family as “tell me about a conflict with a stakeholder” and “tell me about a time you missed a deadline”. If you are preparing for a full interview loop, our guide to common project manager interview questions and how to answer them covers the rest of the list.
Choosing the right failure story
The story you pick matters more than how well you tell it. A good failure story is real, has a clear cost, involves at least one decision you made, and ends with a change you can point to. A bad one is either too small to count or so serious that it raises doubts about whether you should be hired.
| Usually works | Usually backfires |
|---|---|
| A go-live that slipped because you accepted an optimistic estimate without challenge | A “failure” that was really a success (“we delivered, just two days late”) |
| A project delivered on time but rejected by users because requirements were signed off too early | A story where the only cause is someone else: the client, your manager, a vendor |
| A vendor dependency you tracked but did not escalate soon enough | Anything involving safety incidents, legal breaches or hiding information |
| Scope creep you allowed because you wanted to keep a sponsor happy | A failure from last month with no lesson applied yet |
| A project cancelled after you raised the business case problem late | A story so old or so small it shows nothing about how you work now |
Pick a project where you had real responsibility. If you were a coordinator at the time, that is fine, but describe the part you owned: the plan, the tracking, the risk log, the supplier follow-up. Do not borrow a story where you were a bystander.
A simple structure for your answer
Most interviewers expect some version of the STAR format (situation, task, action, result). For a failure question, a slightly adjusted order works better, because the “result” comes in two parts: the failure itself and what you changed afterwards.
- Context (2–3 sentences). The project, its size, your role and what success was supposed to look like.
- What went wrong. The outcome, stated plainly, with the cost: weeks of delay, budget overrun, a feature that was not used.
- Your part in it. The decision or omission that was yours. This is the sentence most candidates skip, and the one interviewers listen for.
- What you did to recover. Escalation, re-planning, damage control, communication with the sponsor.
- What you changed. A specific practice you adopted, and a later project where it made a difference.
Aim for about two minutes. Spend no more than a third of that on the failure itself. The second half, recovery and learning, is what gets you the job.
Two example answers
An experienced project manager
Here is how a project manager might answer for an IT system migration. The details are illustrative; use your own.
Context: “I was managing the migration of a regional finance team to a new ERP module: around 60 users, a four-month plan and a fixed go-live date tied to the financial year end.”
What went wrong: “We went live five weeks late, which meant the team ran two systems in parallel through the year-end close. That cost overtime and a lot of goodwill with the finance director.”
My part: “The main cause was data migration. The integration partner gave us an estimate for data cleansing, and I put it in the plan without testing it against a sample of the real data. When we ran the first trial load, the error rate was far higher than anyone expected.”
Recovery: “I raised it with the sponsor the same week, with two options: keep the date and go live with partial data, or move the date and close year-end in the old system. We chose the second. I re-planned the cleansing with the finance team owning data quality and ran weekly trial loads until we hit the agreed threshold.”
What I changed: “On every project since, I run a trial load or a sample test on any estimate that depends on data we have not seen. On the next migration I ran, that test showed a similar issue in the first month, and we adjusted the plan before committing to a date.”
Notice what this answer does not do. It does not blame the integration partner, even though their estimate was wrong. It names one decision the candidate made, shows a fast and sensible escalation, and ends with a habit tested on a later project.
A career switcher
If you are moving into project management from operations, teaching, engineering or another field, you can still answer this question. Use a project you ran inside your current job, even if nobody called it a project. Our guide on how to become a project manager with no experience explains how to find these projects in your work history.
Context: “As a warehouse shift supervisor, I led the rollout of handheld scanners across three shifts, about 40 staff, over six weeks.”
What went wrong: “After launch, error rates went up instead of down for the first month, and one shift went back to paper forms.”
My part: “I planned the training around my own shift’s hours and assumed the other two supervisors would cascade it. I did not check that they had. The night shift got one short session.”
Recovery: “I set up short training sessions at the start of each night shift for two weeks, paired experienced users with new ones, and tracked error rates by shift so we could see where support was needed.”
What I changed: “Now I treat every group affected by a change as a stakeholder with its own plan, and I confirm training is done rather than assuming it. I used that approach for a later layout change and all three shifts were up to speed in the first week.”
This answer shows planning, stakeholder thinking and follow-through, which are the same things a hiring manager looks for in a junior PM.
Weak lines and how to fix them
Small wording choices change how your answer lands. Here are common weak lines and stronger versions.
“The client kept changing their mind, so the project failed.”
“I accepted three change requests without a formal impact review because I wanted to keep the sponsor on side. Together they added six weeks.”
“My biggest weakness is that I care too much about delivery.”
“I tracked the vendor dependency every week, but I waited too long to escalate when it started slipping.”
“I learned that communication is important.”
“I now send a one-page status note every Friday with red items at the top, and I agree escalation thresholds with the sponsor at kick-off.”
The pattern is the same each time: replace a general statement with a specific decision and a specific change.
Mistakes that cost candidates the job
- Picking a fake failure. “We delivered a day late” or “I worked too hard” sounds evasive. Interviewers hear it often.
- Blaming others. You can mention outside causes, but if no part of the failure was yours, it is not a useful answer.
- Too much detail on the problem. Long technical explanations eat your time. Keep the failure short and spend the time on recovery.
- No proof of learning. “I would do it differently next time” is weak. “I did it differently on the next project, and here is what happened” is strong.
- Making it up. Follow-up questions expose invented stories quickly. Use a real project and adjust only identifying details.
Follow-up questions to prepare for
A good interviewer will probe your answer. Prepare short responses to these:
- “When did you first see warning signs, and what did you do about them?”
- “What would you have done if the sponsor had refused to move the date?”
- “How did the team react, and how did you keep them motivated?”
- “Is there anything you would still do differently today?”
Have two failure stories ready, not one. Some interviewers ask for a second example, and a panel may ask a variation such as “tell me about a decision you got wrong”.
Make your CV and your story tell the same story
Your failure answer should sit comfortably next to your CV. If your CV lists only duties, the interviewer has no picture of the scale and results of your work, and your failure story has nothing to stand on. Rewriting your bullet points as outcomes helps here: see how to write achievements instead of tasks on a project manager CV.
Before the interview, reread the job posting and check which skills it stresses most: vendor management, stakeholder communication, budget control, agile delivery. Choose a failure story that shows the lesson closest to those needs. If you are not sure how well your experience matches the posting, you can check your CV against the job posting with our free fit check and see which gaps an interviewer is likely to probe.
Prepared well, “tell me about a project that failed” stops being a trap. It becomes one of the few questions where you can show, in two minutes, how you think when a project goes wrong, which is most of what a project manager is hired to do.
Want to know where you stand?
Paste a project manager job posting and your CV into our free fit check to see your score and main gaps in two minutes. For a full written review by a practitioner, the PM Fit Report gives you rewritten CV lines and the roles you can target now, within 48 hours.
Try the free fit checkGet my PM Fit Report — $39