Separate the missed expectation, your mistake, immediate repair, and the later evidence that something changed.
Find a failure with enough detail to discuss
Start with something that did not meet a real expectation: a missed deadline, an incorrect assumption, an unclear handoff, or work that needed to be redone. Name the expectation before describing the failure. Without it, the listener cannot tell what went wrong.
Pick an event you can discuss honestly and without exposing confidential information. The purpose of this exercise is to explain your judgment and learning, not to find a disguised achievement. “I worked too hard” is not useful unless you can explain a real consequence and your responsibility for it.
You do not need to claim that you alone caused everything. Separate your contribution from circumstances outside your control, and avoid using those circumstances to remove your own part.
Use a five-link chain to avoid a disguised success story
STAR organizes chronology. A failure answer also needs accountability. Use this original five-link check to locate missing information before practicing aloud.
| Link | Question to answer | Weak substitute |
|---|---|---|
| Expectation | What was supposed to happen? | It was a challenging project |
| Miss | What actually fell short? | We faced obstacles |
| Ownership | Which assumption or decision was yours? | Communication was poor |
| Repair | What did you do after discovering it? | I took responsibility |
| Prevention tested | What changed later, and how do you know? | I learned to be careful |
A prevention step can be untested. Saying “I added a review step, but the next cycle has not happened yet” is more accurate than claiming a recurrence was prevented.
A case where the repair did not erase the loss
“I sent a report using a filter from the previous month, so it excluded a new customer segment. I owned the final check and had compared the totals only with my own draft. After a colleague noticed the mismatch, I told the manager what was wrong, replaced the report, and identified which conclusions needed revisiting. The team had already spent part of a meeting discussing the incomplete version. For the next report, I checked the segment list against the source export before comparing totals. That check caught a newly added segment; I still needed to make it part of the documented review process.”
Why it is substantive: the account names an incorrect check, acknowledges wasted meeting time, and explains a later check that addressed the same failure mechanism. “I apologized” alone would not establish any of that.
What not to infer: the new check does not prove that all reporting errors are prevented. It addresses one identified problem. A follow-up could ask who reviewed the corrected conclusions or what would happen if the source export were wrong.
Built In discusses using a specific failure and the response to it. The report example and five-link audit here are original teaching materials. Built In: failure-answer guidance →
A fictional example: a handoff that failed
“I was responsible for handing a volunteer registration list to the check-in team. I sent the spreadsheet but did not explain which column showed confirmed attendance. At the start of the event, the team contacted people who had not confirmed.
“I had assumed the column names were clear. When the team raised the problem, I clarified the status definitions, marked the confirmed list, and helped correct the messages. Some confusion had already happened, so the correction did not undo all of it.
“For the next event, I sent a short handoff note and asked the check-in lead to walk through one sample record with me. That review caught a different ambiguous label before the event. I learned to check whether a handoff is understood, rather than treating sending the file as the end of my responsibility.”
This is a teaching example, not an atula customer story. Use your own facts, including the actual limit of what your later change proved.
Use follow-ups to test the story
Practice explaining when you first noticed the problem, who else was affected, why you chose that repair, and what you would do if the repair failed. Then ask yourself whether the same underlying mistake appeared elsewhere.
A partner can challenge one assumption: “Was the unclear column label the whole problem, or was responsibility for checking the list also unclear?” You do not have to defend the first version of your story at all costs. Use the question to make your explanation more accurate.
If practicing alone, write a follow-up on a separate card and draw it after your first answer. Keep the follow-up answer focused on the missing detail.
Check for three common problems
- No actual failure: Name the missed expectation rather than describing a success under pressure.
- No personal responsibility: Explain your part without taking credit or blame for everyone else's decisions.
- No observable change: Replace “I learned a lot” with a particular action you changed, or identify what still needs to be tested.
Finally, say the answer without reading the full text. Review whether the sequence is clear and whether every claim is something you can support. This exercise cannot predict an interviewer's evaluation, but it can expose gaps before the conversation.
Your practice worksheet
Use the prompts above and record your own evidence. The worksheet is a plain-text file you can edit or print; no account is needed.
Method and scope
Background reading: Harvard Mignone Center for Career Success: Interviewing. It covers preparation and interview formats. The examples, schedules, questions, and worksheets here are original atula practice materials, not an endorsed program or a validated hiring assessment.
Turn this into a real conversation.
Bring your own experience to live practice with atula. Work on your answer, then handle a follow-up.
Practice live with atula ↗Apply for early access. Availability is limited; applying does not start an immediate session.
Need to organize an example first? Try the STAR builder →