What Career Professionals Can Learn from The Impostor Phenomenon
Years into a steady career, it is easy to assume the self-doubt from your first job would have faded by now. Instead, a strong performance review gets explained away as a lenient manager, a big project win gets credited to a helpful colleague, and a promotion gets read as the company simply needing someone available. The accumulated evidence of a solid career can sit right alongside a private conviction that it could all unravel the moment someone looks closely.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Explaining away a career's worth of wins
A strong performance review gets credited to a lenient manager, a major project win gets credited to a talented colleague, and a promotion gets read as the company needing to fill a seat rather than recognizing your work.
Crediting the manager or the colleague instead of the judgment calls and follow-through you brought erases the actual skill behind the result.
After a review or a win, name two specific contributions only you made before allowing any talk of a lenient boss or a lucky team.
The annual-review relief loop
Anxiety before a performance review or a big presentation often drives excessive preparation, the meeting goes fine, and the relief reads as "I dodged it again" instead of "the work and preparation held up."
Treating relief as a narrow escape leaves the same dread waiting at the next review, no matter how many reviews have gone well.
Right after a review goes well, write down the specific evidence that was cited before the relief fades into vague luck.
A workplace that rewards output over process
Many organizations measure results without ever asking what judgment produced them, and someone praised early in their career mainly for being naturally sharp can mistake visible effort now for a sign of decline rather than ordinary work.
Assuming that naming how hard a project was will make you look less capable keeps colleagues from ever learning what your real process looks like.
Once a month, tell a colleague specifically what was difficult about a project that turned out well, not just the outcome.
Letting the evidence actually land
Another strong year or another promotion rarely settles the doubt by itself, because the discounting habit adapts and finds a new reason each time, a helpful colleague, good timing, a manager who happens to like you. What helps is a smaller, repeatable habit: pausing right as a success is about to be waved off, and treating "I am not sure why that went so well" as a reason to look closer rather than dismiss it. Practiced across a career, this shifts what evidence is allowed to count, even when no single win feels conclusive alone.
A strong project result and a disappointing one can land in the same quarter, and the instinct is to erase credit for the strong result while treating the disappointment as proof the whole career has been a lucky run. When both show up together, address the disappointment first with a plain, factual review of what to adjust, then return to naming what the strong result actually required. Trying to weigh both at once usually lets the disappointment dominate the whole story.
Name one thing, honestly
- Which recent win at work have you already quietly reassigned to a helpful colleague, good timing, or a lenient boss? - Is there a moment in a review where solid evidence was presented and you still explained it away? - What would change if years of steady performance counted as proof rather than something still waiting to be tested?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Once a month, tell a colleague specifically what was difficult about a project that turned out well, not just the outcome.