Define what failed
State the original goal and the shortfall. A late delivery, poor adoption and an incorrect recommendation are different failures. Explain the impact in terms you can support, then identify your responsibility. Avoid blaming unnamed stakeholders or presenting a disguised success where you cannot name anything that went wrong.
Separate the warning from the hindsight
Explain what you knew at the time, what signal you missed and why it mattered. If you raised the risk but it was accepted, say what you did next. If you made the wrong assumption, own that assumption directly. The goal is to show your decision process, not to construct a story in which you were secretly right all along.
Show the change in your behaviour
Describe the immediate recovery and a later practice you changed. “Communicate better” is too broad to evaluate. A scheduled checkpoint with the receiving team or a prototype test before implementation is more concrete. If you have not yet applied the lesson, present it as a planned change rather than an established habit.
A worked example
This is a fictional teaching example, not a customer’s resume or a script to copy. Use the structure with facts from your own experience.
Built an internal request form that needed a second rollout.
Tell me about a project that did not go as planned.
Too vague
“People resisted change, so the project failed despite our hard work.”
More specific
“I built a request form assuming the receiving team could work from the submitted fields. After launch they kept asking for missing context, and people returned to chat. I had reviewed the form with requesters but not the receiving team. I paused the rollout, walked through real examples with them and revised the required information.”
Be ready for the follow-up
What did you change for the next project?
On the next handover change, I asked both the sender and receiver to walk through a sample before implementation. That exposed a missing approval step while it was still easy to change.
The story names an assumption, its consequence and a later behaviour change. Keep the focus on your responsibility while acknowledging that delivery involved a team.
Try a short resume drill
Read the question aloud and pause to form your own answer. Then advance the sample to explore the follow-up and feedback.
“Built an internal request form that needed a second rollout.”
Tell me about a project that did not go as planned.
Example answer“I built a request form assuming the receiving team could work from the submitted fields. After launch they kept asking for missing context, and people returned to chat. I had reviewed the form with requesters but not the receiving team. I paused the rollout, walked through real examples with them and revised the required information.”
Check your answer
- State the original goal and actual shortfall.
- Own a decision or missed check.
- Explain the immediate recovery.
- Give a specific later application of the lesson, if you have one.
Pick the least clear part and practise it again. Keep a few factual prompts rather than memorising the example word for word.
Now try it with your experience.
ResumeDrill turns the work on your resume into practice topics, questions and follow-ups.
Practise with your resume