Apologizing for a mistake
Own a mistake cleanly, fix it fast, and accept an apology without holding a grudge.
Case study: The script that ran on production
Deepak, a developer in Bengaluru, ran a cleanup script on the production database instead of staging. 4,000 customer records lost their phone numbers for two hours. In the incident call with the Tokyo client, he said, "Actually the staging and prod credentials look very similar, and the access should not have been there." All true, but the client heard excuses. His manager stepped in: "This was our mistake. We've restored the data from backup, and from today production access needs a second approver." The client relaxed immediately. Later, Deepak apologized properly to the QA lead, who said, "Thanks. Let's move on." And they did.
Takeaway: A good apology has three parts: own it, fix it, prevent it. Explanations come after, and only if asked.
Some of us over-apologize for small things, and then avoid owning big ones because it feels like losing face. Global teams trust people who say 'my mistake' quickly and pair it with a fix.
Apologizing
Goal: Take clear ownership, explain the fix, and show how it won't happen again.
Step by step
- Own it. Say 'I made a mistake' in the first sentence. No 'mistakes were made'.
- Name the impact. Show you understand who it affected and how.
- Share the fix. What you've done already, and what's still in progress.
- Prevent it. One concrete change so it doesn't repeat.
Say this, not that
| I made a mistake, and I want to own it. | Some mistake has happened from our side. | Passive language sounds like hiding. |
| I ran the script on production instead of staging, and four thousand records were affected for two hours. | Naming the impact shows you understand its seriousness. | |
| We've restored everything from the backup, and I've verified the data myself. | We are looking into it. | |
| To prevent this, production access now needs a second approver. | It won't happen again, I promise. | A process change is more believable than a promise. |
| I'm sorry for the trouble this caused your team. | Sorry, sorry, so sorry, sir. | One sincere sorry is enough. Repeating it shifts attention to your feelings. |
Model conversation
- You
- Kenji-san, thank you for joining. I made a mistake yesterday, and I want to explain it and what we've done.
- Kenji
- Thank you. Please go ahead.
- You
- I ran a cleanup script on production instead of staging. Four thousand customer records lost their phone numbers for about two hours.
- Kenji
- I see. Our support team got several calls.
- You
- I'm sorry for the trouble that caused them. We restored everything from backup by eleven, and I've verified every record.
- Kenji
- Good. How can we be sure it won't happen again?
- You
- From today, production access needs a second approver, and the script now asks for the environment name before it runs.
- Kenji
- That's reassuring. Thank you for being so clear about it.
Accepting an apology
Goal: Accept the apology sincerely, agree on any follow-up, and genuinely move on.
Step by step
- Thank them. Owning a mistake takes courage. Recognize it.
- Be honest. Don't pretend it was nothing if it wasn't.
- Agree the follow-up. Settle anything still open, then stop.
- Move on. Don't bring it up again in meetings or reviews.
Say this, not that
| Thanks for owning it. I really appreciate that. | Hmm, okay. Let's see. | A lukewarm reply leaves the other person anxious. |
| It did cost us a late night, but I'm glad we caught it early. | No problem at all, it was nothing. | Honest acceptance is more believable than pretending it didn't matter. |
| The second approver idea is great. Let's add it to the checklist. | ||
| Let's consider it closed and move forward. | Fine, but I'll remember this. | Saying it out loud releases both of you. |
| Honestly, it could have happened to any of us. | Kindness here builds a team where people admit mistakes early. |
Model conversation
- Ananya
- Hey, do you have a minute? I wanted to apologize for the production issue. That was my mistake.
- You
- Thanks for owning it, Ananya. I really appreciate you saying it directly.
- Ananya
- I know your team stayed late to retest everything. I'm sorry about that.
- You
- It was a long night, I won't pretend otherwise. But you fixed it fast, and that matters.
- Ananya
- I've also added a confirmation prompt to the script.
- You
- That's a great fix. Could we add it to the release checklist too, so everyone benefits?
- Ananya
- Definitely, I'll do it today.
- You
- Perfect. Let's consider it closed. These things happen to all of us.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.