SkillsSkill 4 of 5
Own the work, including your mistakes
When you find your own mistake, measure what it changed, tell the person relying on it, then fix the cause.
Worked example
You find a mistake in your own report, and it flips the conclusion
The fix is easy. The hard part is what the mistake has already changed.
The question
At Larkhaven, a fictional grocery-delivery company, your internship project is a weekly orders report. On Wednesday you notice your filter has dropped weekend orders for three weeks. Your manager used the report to tell leadership that orders are flat, and presents again on Friday.
| Your report (weekdays only) | Weekend orders left out | Corrected total | |
|---|---|---|---|
| Week 1 | 6300 | 2400 | 8700 |
| Week 2 | 6250 | 2700 | 8950 |
| Week 3 | 6280 | 3000 | 9280 |
Invented data. Your report shows week 3 0.3% below week 1; the corrected totals show 6.7% growth.
- Your manager’s slide, last FridayOrders flat for three weeks. Hold off on adding weekend drivers.
“Your report has left out weekend orders for three weeks. Your manager told leadership orders are flat and presents again on Friday. What do you do?”
Your turn
Say your answer out loud, or jot notes below. Both work. Or skip to the worked answer.
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Measure what the mistake changed
What would you do here? Open the move you’d make.
Note that the report missed weekends and fix the filter.
Tempting, but it misses something. That fixes the bug, not the consequence. The corrected totals turn “flat” into 6.7% growth, which matters for the weekend-driver decision.
Recompute: week 3 is 9,280 against 8,700, up 6.7%, not flat; weekend orders grew from 2,400 to 3,000.
The strong move. It shows the conclusion flips, and that weekend orders, up 25%, bear directly on holding off on weekend drivers.
Call it a small data issue: the weekday numbers are still accurate.
Tempting, but it misses something. The weekday numbers are right; the conclusion isn’t. Weekend orders are more than a quarter of every week’s corrected total.
See how a strong candidate says it
“With weekends back in, week 3 is 9,280 against 8,700 in week 1, up 6.7%, not flat. Weekend orders alone grew from 2,400 to 3,000, which bears directly on holding off on weekend drivers.”
Why it works: It shows you understand the consequence, not just the bug.
Step 2: Tell the person relying on it, today
What would you do here? Open the move you’d make.
Tell my manager today, well before Friday: what was wrong, the corrected numbers and the decision they affect.
The strong move. Your manager presents again on Friday. Telling them on Wednesday gives them time to correct the slide.
Fix it quietly in next week’s report with a footnote.
Tempting, but it misses something. The “flat” message would reach leadership a second time on Friday, and the weekend-driver decision would rest on wrong numbers.
Email leadership directly so they hear the correction fast.
Tempting, but it misses something. Your manager presented the numbers and owns that conversation. Going around them surprises the person who has to fix the slide.
See how a strong candidate says it
“I’d tell my manager today, well before Friday: what was wrong, the corrected numbers, and that the weekend-driver decision rested on them.”
Why it works: Waiting for next week’s report would let a wrong conclusion reach leadership twice.
Step 3: Fix the cause, not just the numbers
What would you do here? Open the move you’d make.
Correct the three weeks and move on; it won’t happen again now you know about it.
Tempting, but it misses something. Knowing about it doesn’t stop a similar filter dropping other days. A check makes it visible next time.
Ask an analyst to take over the report so it’s done right.
Tempting, but it misses something. Handing it off gives up ownership at the moment it matters. You can fix the filter and add the check yourself.
Fix the filter, reissue the three weeks with a note, and add a check that my weekly total matches the order system’s.
The strong move. With that check, a week that drops 2,400 orders can’t slip through quietly again.
See how a strong candidate says it
“I’d correct the filter, reissue the three weeks with a note, and add a check that my weekly total matches the order system’s.”
Why it works: Owning the work includes making the same mistake harder to repeat.
Step 4: Own it plainly
What would you do here? Open the move you’d make.
Say it simply: “My filter dropped weekends. Here are the corrected numbers and the check I’ve added.”
The strong move. It takes responsibility in one line and moves straight to the fix and the decision.
Explain that the report template made the weekend filter easy to miss.
Tempting, but it misses something. Even if true, it sounds like blame. Your manager needs the corrected numbers before Friday, not the history of the bug.
Apologize at length so your manager knows you take it seriously.
Tempting, but it misses something. A long apology makes the conversation about you. The useful part is 9,280, not 6,280, and the check that prevents a repeat.
See how a strong candidate says it
“I’d say it simply: “My filter dropped weekends. Here are the corrected numbers and the check I’ve added.” No blaming the template, no long apology.”
Why it works: It keeps attention on the fix and the decision, which is what the manager needs.
The answer, in short
- Decision
- Tell your manager today, with the corrected numbers and the decision they affect; fix the filter, reissue the report and add a check.
- Because
- Corrected, orders grew 6.7% and weekend orders 25%, which reverses the “flat, hold off on weekend drivers” message going to leadership.
- What would change it
- If the report hadn’t reached anyone or shaped a decision, a correction noted in the next report would be enough.
A real interviewer may ask: “Tell me about a mistake you made.” Use a real one: what happened, what you did and what changed. Don’t memorise an invented story.
Common traps
- Quietly fixing next week’s report.
- Calling it a small data issue when the conclusion flips.
- Blaming the template or the data.
- Apologising at length instead of bringing the fix.
Check your answer
- Did I measure what the mistake changed?
- Did I tell the person relying on it in time?
- Did I fix the cause, not just the numbers?
- Did I take responsibility plainly?
Want feedback on how you’d answer? Practice “Own the work, including your mistakes” with an AI interviewer on Socratify.
Last reviewed Nov 9, 2026