The full answer
Tell them early, plainly and with data: what the target was, what was achieved, why the gap exists, and what it would take to close it. Then give a clear recommendation, which might be to continue with a specific fix, narrow the scope to where it already works, change the approach, or stop, with the cost and likelihood of each. Never hide a miss or bend the metric after the fact.
1. Don't wait for the final meeting
If weekly results show you will miss, say so as soon as you know. A sponsor who hears bad news early can adjust plans; one surprised at the end loses trust in you.
2. Explain the result honestly
- The agreed target and the measured result, on the agreed evaluation set and in production.
- Results by category: often the system meets the target on most cases and fails badly on one.
- The reasons, from your failure analysis: data quality, missing information, an integration gap, a harder task than expected, user adoption.
3. Separate what was learned
Even a missed pilot answers questions: which parts work, which do not, and why. Present this as evidence, not excuse.
4. Give options with a recommendation
| Option | When it makes sense | Example |
|---|---|---|
| Continue with a fix | The cause is clear and fixable | "Scanned documents cause 60% of errors; a better parser takes two weeks and should add about 12 points" |
| Narrow the scope | It meets the bar on some categories | "Go live on order-status and returns, where accuracy is 96%; keep billing with people" |
| Change approach | The design was wrong | "Drafts for agents instead of automatic replies" |
| Stop | The value isn't there or the data doesn't exist | "The needed knowledge isn't written down anywhere; the first project is capturing it" |
Include the cost, time and confidence of each, and your recommendation with reasons.
5. Protect the relationship
- Acknowledge your part of the miss, if any, without excessive apology.
- Keep the metric as agreed. Changing it to declare success destroys trust.
- Offer something concrete: a smaller go-live, a fix plan, or a better-chosen next use case.
Example opening
"We aimed for 90% correct replies and reached 81%. On order-status and returns we're at 95%; on billing questions we're at 52%, because billing answers depend on data our integration can't yet see. I recommend going live on the first two categories next month, and fixing the billing integration as phase two, which should take about four weeks."
What interviewers look for: honesty, analysis before opinion, options with trade-offs, and a recommendation, not just a report.
Last updated 16 October 2026
Sources