Own it in one plain sentence. Say what happened without excuses. Name the impact on the people it affected. Fix it, or propose the fix and a date. Then change the thing that let it happen so it does not repeat. Five steps, in that order, in less time than it takes to explain why it was not your fault.
The five steps, with words
1. Own it. "The report went to the client with last quarter's numbers. That was mine." Full stop. No "but."
2. Say what happened. "I copied the figures from the old sheet instead of the new one." Facts, not reasons.
3. Name the impact. "The client made a decision on wrong numbers and we have to tell them." This is the step people skip, and it is the one that shows you understand.
4. Fix it or propose the fix. "I've sent the corrected version and I'll call them at 2 to explain." A date and an action.
5. Change the system. "I'm adding a check against the source sheet to my list before anything goes out." This is what turns a mistake into a one-time event.
Why the order matters
People start at step two, explaining, which sounds like excusing. Or they jump to step four, fixing, which skips the owning. Start with step one and the rest land. It takes about forty seconds.
For managers
You can make this easy or hard. If owning a mistake brings a calm "thanks, what's the fix," people own them early, when they are cheap. If it brings heat, they hide them until they are expensive.
Where M-Tracker fits
Step five is where M-Tracker helps most. The check you promise to add becomes a line in the brief, and when the next piece of work is sent, M-Tracker checks it against that brief before it leaves. The fix stops depending on memory. And because the review goes to the person first, step one happens privately, before the work reaches anyone else.
Try M-Tracker free14-day trial. No credit card. No employee surveillance.
Questions people ask
What if it really was not my fault?
Own your part, even if it is small: "I should have checked the numbers before sending." Then describe the rest as facts.
Should I apologize?
Once, briefly, at step one. Repeated apologies become about you.
How do I teach this to a team?
Do it yourself, visibly, the next time you get something wrong.
Work you can trust, without redoing it.
Your team gets feedback before work reaches you, or your client.
Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy