Some leaders draft the apology before they have made the mistake.
Priya told me she spends Sunday nights writing emails she might need to send on Monday. The mistakes are hypothetical. The apologies are ready anyway.
It is easy to call this low confidence or imposter syndrome and move straight to correcting the thought. But the draft may be doing something more specific: trying to get ahead of a verdict.
If you accuse yourself first, maybe no one else can surprise you. Maybe you can soften the judgment, explain the failure, or prove that you already know what they will say.
That can feel like preparation. It can also make uncertainty feel like guilt.
There are other versions of the same habit. Marcus, an engineering leader, told me that before a meeting he had looked up an answer to a technical question. When someone praised his decision-making, he dismissed the compliment because he had searched for the answer shortly beforehand.
He had found what he needed and used it. Yet he treated the act of learning as evidence that he did not belong in the room.
That standard is hard to satisfy: competence counts only if it arrives effortlessly. You are allowed to know, but not to look something up. You are allowed to lead, but not to need preparation. You are allowed to succeed, as long as you can prove that luck had nothing to do with it.
Under that standard, every success needs an explanation away. And every unknown becomes a possible exposure.
There is a useful distinction here. Concern can point to something real. Maybe there is a skill you need to build, a decision you need to check, or a risk that deserves careful preparation. Confidence does not make you competent, and calling a worry “just a thought” does not settle whether it is accurate.
But an imagined apology is not, by itself, evidence that you have failed. It may be evidence that you are trying to manage the judgment you fear before you know what the situation requires.
Dani, who leads a design team, initially said she did not know what she was doing. When I asked what it would look like to know, she realized she had never defined the standard. She was measuring herself against an image of competence she could feel other people had, but could not describe.
That is a difficult way to lead. The standard stays vague, so you can never know when you have met it. You can only keep bracing for the moment someone else decides you have not.
When the next apology starts forming, try separating the prediction from the facts. What happened? What do you actually know? Is there a real gap to address, or are you preparing to answer for a verdict you have already delivered against yourself?
You might write, “I’m thinking that I’ll have to apologize tomorrow.” That wording does not prove the thought is false or make a real problem disappear. It does make the prediction visible as a prediction, rather than treating it as a report from the future.
Then do the ordinary work: prepare, ask for help, learn what you do not know, and correct what needs correcting. If you make a mistake, take responsibility for the mistake that happened—not every mistake you feared might happen.
You do not need to pretend the risk is zero. You do need to notice when you are paying for a failure before it exists.
The apology draft may feel like control. But sometimes it is just fear, rehearsed until it sounds like responsibility.
