You were prepared. You were more prepared than anyone else in the room. You read the deck twice, wrote three versions of your update and rehearsed answers to questions nobody ended up asking. It went fine. Someone even said good point. Then, on the walk back to your desk, the usual thought showed up right on time: that was close.
Here is the uncomfortable part. All that preparation isn't protecting you from being found out. It's the reason you still believe there's something to find.
The feeling has a name, and a history
In 1978 two psychologists, Pauline Rose Clance and Suzanne Imes, described a pattern they kept seeing in high-achieving women. These women had degrees, honors and promotions, and they were privately sure they had fooled everyone. They called it the impostor phenomenon. It isn't a clinical diagnosis and it doesn't appear in the DSM. Later research found the same pattern across genders, professions and levels of seniority. Plenty of people who look the most competent from the outside report it.
At its core is an attribution problem. When something goes well, the person with impostor feelings credits luck, timing, charm, a forgiving audience or sheer effort. They credit almost anything except ability. When something goes badly, it's proof. The scale is rigged, and it always tips the same way.
That explains why the feeling survives success. The more interesting question is how it keeps itself running, and that's where meetings come in.
The cycle that keeps it alive
Clance described what she called the impostor cycle. A task comes up that could expose you, like a presentation, a status update or a meeting with someone senior. Anxiety arrives. You respond in one of two ways. You overprepare, or you procrastinate and then make a frantic last-minute push.
The task goes well, as it usually does for capable people. You feel a short wave of relief. Then comes the quiet accounting. If you overprepared, the success belongs to the overpreparation: I only got through because I rehearsed for four hours. If you procrastinated, it belongs to luck: I pulled that off at midnight; I got away with it.
Either way, the conclusion is the same: my ability had nothing to do with it. So the next time a task comes up, the anxiety returns at full strength, and the only strategy that has ever "worked" is to do the same thing again, maybe a little harder.
Each turn of the cycle looks like evidence of competence from the outside. From the inside, it confirms the fraud.
Why the evidence never gets through
Clinical psychology has a precise name for what the extra rehearsal is doing: a safety behavior. The idea is central to David Clark and Adrian Wells's cognitive model of social anxiety. A safety behavior is something you do to prevent a feared outcome, and it has a hidden cost. It stops you from ever learning that the outcome wasn't going to happen.
Therapists often use a simple illustration. Someone is afraid they'll faint in a crowded shop, so they grip the shopping cart every time. They never faint. But they never learn that they wouldn't have fainted anyway. The cart gets the credit, and the belief stays intact.
In a meeting, the four-hour rehearsal is the cart. So is the fully scripted update, the habit of only speaking after you've checked your point against three sources, and the reflex to answer every question with let me get back to you when you actually know the answer. Each one keeps you safe in the moment. Each one also blocks the one piece of information that could loosen the feeling: I can handle this as I am.
Why meetings are especially hard on impostors
Meetings are close to an ideal environment for this kind of fear. They're live and public, and the script can break at any moment. A question you didn't anticipate can come from anyone. You're being assessed in real time by people whose opinion matters, and you can't see what's going on in their heads.
That last point matters more than it seems. In a meeting you compare your insides to everyone else's outsides. You feel your own racing heart and the blank half-second before you answer. You see only the calm faces around the table. Most of those people are running their own private commentary, but you can't see it, so the comparison always favors them.
There's also a cost that rarely gets mentioned. People who prepare heavily out of fear often contribute less in the moment. Their attention is on the script and their exits, so there's less of it for the conversation actually happening. The fear ends up making you a slightly worse colleague than you would be if you trusted yourself.
Preparation isn't the enemy. Its purpose is.
None of this means you should walk into meetings unprepared. Preparation is part of doing good work. The useful distinction is between preparation that serves the work and preparation that serves the fear.
One test helps: would this next hour change what I say, or only how safe I feel? Reading the data before a budget review changes what you say. Rehearsing your opening sentence for the ninth time only changes how safe you feel, and only for a while.
Preparation that serves the work usually has a natural stopping point: you know what you think. Preparation that serves the fear has no stopping point, because the fear was never about the material. However much you rehearse, it never feels like enough.
Running the experiment
The way out isn't reassurance. You've probably had plenty, and it slides right off. What works better is what cognitive behavioral therapists call a behavioral experiment. You write a specific prediction, drop the safety behavior, and see what actually happens.
The key word is specific. "It'll go badly" can't be tested. "If I don't rehearse my update, I'll lose my place and someone will have to rescue me" can be. Write it down beforehand, because memory is a generous editor. Once the meeting is over, your mind will quietly rewrite what you predicted so the feeling stays intact.
Start small. Pick a recurring meeting where the stakes are low, not the board presentation. You're not trying to prove you're brilliant. You're trying to collect one honest data point the fear hasn't been allowed to explain away.
Your next moves
- Write one testable prediction tonight. Pick a low-stakes meeting this week and write down exactly what you fear will happen if you prepare less. Rate how strongly you believe it, from 0 to 100.
- Cut one safety behavior, on purpose. Cap your prep at a fixed time (say, twenty minutes) or bring three bullet points instead of a script. Choose the behavior in advance so you don't negotiate with yourself on the day.
- Debrief within an hour. After the meeting, write down what actually happened, without interpreting it, and re-rate your original belief. Compare the two numbers.
- Say "I don't know yet" once, deliberately. When a question comes up that you can't fully answer, try: I don't know yet. I'll find out and send it by Thursday. Notice what the room actually does with that.
- Log one honest attribution. For something that went well this week, write one sentence that credits a specific skill of yours, not luck or effort alone. It will feel awkward, and that's the point.
Looking back at what actually happened
The impostor cycle depends on one thing: after a meeting ends, you replace what really happened with what you were afraid would happen. Putting the two side by side in writing breaks that habit. MeetingMortem was built for the honest look back afterward: what was said, what was decided, and how it actually went compared with the story you've been telling yourself. If you want somewhere to keep your predictions and debriefs until the evidence finally starts to add up, you can try it at meetingmortem.lumenlabs.works.