Admitting a mistake at work — without spiralling
You spot it an hour after you sent it: the wrong figure, the missed attachment, the thing that's now sitting in someone's inbox. Before you've even decided what to do, your whole nervous system has filed it under 'career-ending', and the gap between what actually happened and how it feels is enormous.
Why a small error can feel enormous
The mistake is rarely the hard part. The hard part is the wave that arrives with it — the heat in your chest, the certainty that you've been found out, the urge to either disappear or over-explain. For a rejection-sensitive brain, a minor slip gets read by the body as proof of something much larger: not "I made an error" but "I am the error." That mismatch is why a typo in an email can ruin an afternoon.
It's worth knowing this is a wiring pattern, not a measure of how bad the mistake was. ADHD and autistic adults often carry years of feeling scrutinised, so criticism — even anticipated criticism — can flood fast, before any reasoned read of the situation arrives. Naming that flood for what it is doesn't make it vanish, but it does buy you the half-second you need to respond to the actual mistake instead of to the feeling about it.
Try it: you catch it before anyone else
Practise this moment
You realise you sent a client the wrong figures an hour ago. Nobody has noticed yet. What do you do?
In Spring Social you can practise the high-stakes moments privately, choose a response, and see how it tends to play out. This is one of 1,000 scenarios.
What people reach for instead — and why it backfires
The instinct under threat is to hide it, and a buried mistake almost always surfaces later, bigger, with your silence attached to it. The next instinct is to over-apologise — paragraph after paragraph of sorry — which makes colleagues manage your distress instead of the issue, and can read as bigger than the error warranted. Some people swing the other way and blame-shift in the same breath they admit it, which lands as defensiveness even when the point is fair. And many simply freeze, letting hours pass while the window to fix it cleanly closes. Each of these is the feeling driving the response, rather than the situation.
A cleaner way to own it
Flag it early — the sooner you raise it, the smaller it stays and the more it reads as diligence. Keep it factual rather than catastrophic: what happened, what the impact is, and what you're doing about it, in plain sentences. Lead with the fix, not the feeling — "here's the corrected version and what changed" does more for you than any amount of apology. Apologise once, briefly, and then move forward; a single clean "sorry about that" is complete. And afterwards, separate the error from your worth: you made a mistake, which is a thing that happened, not a thing you are. If the same error keeps recurring, that's a signal to change a process — a checklist, a second pair of eyes — rather than to try harder at being perfect.
Common questions
Will admitting it make me look incompetent?
Usually the opposite — an early flag with a fix attached reads as accountable. What damages credibility is an error someone else uncovers after you've hidden it.
How do I stop spiralling once it's done?
Once the fix is sent, the work part is finished. The replaying is a separate loop you can name ("this is RSD, not new information") and set down.
What if it was partly someone else's fault?
Fix it first; never blame-share in the moment. Owning your part cleanly protects you, and any process problem can be raised calmly, on its own, later.
Spring Social includes 1,000 situations like this one, with clear response options and supportive feedback you can practise in private.