The Perfectionist
- 3 days ago
- 3 min read
Nadia was the best editor in every room she walked into.
Not by title — by habit. She could find the flaw in any deck, any proposal, any strategy document, any email. She could see the gap between what something was and what it could be — and she couldn't leave it alone.
Her team had learned this. They'd submit work, wait for the rewrite, and implement her version. Some of them had stopped putting in full effort on first drafts because — why would you? She was going to change it anyway.
When I asked Nadia about it, she had a ready answer: "My team isn't there yet. The quality bar is where it is for a reason."
I asked her what would happen if she sent their version — the version before her edits — to the leadership team.
She physically recoiled.
"I can't do that. It's not ready."
"When is anything ready?"
She thought about it for a long time.
"I don't know. It never feels ready."
That's the pattern. Perfectionism doesn't look like a problem from the outside. It looks like high standards. It looks like excellence. It looks like someone who cares more than everyone else about the quality of the work.
From the inside, it's different. From the inside, it's a machine that runs on the belief that if something leaves your hands at anything less than flawless, the world will see what you're afraid they'll see — that you're not as good as they think you are.
The thing about perfectionism is that it looks like excellence from the outside. From the inside, it's fear wearing a nicer outfit.
Nadia's team had three products ready to launch. All three had been delayed — twice each — for additional rounds of refinement. The refinements were real. The improvements were measurable. But the cost of those improvements was invisible on any dashboard: a team that had stopped innovating because innovation requires shipping imperfect things, a pipeline that was perpetually 90% done, and a VP who was working 60-hour weeks doing work her directors should have owned.
I told Nadia something she didn't want to hear.
Your standards aren't protecting your work. They're protecting you from finding out that good enough was always enough.
The silence after that was long.
Here's what I've learned about perfectionism after thousands of coaching hours: it's almost never about the work. It's about identity. The perfectionist has built their professional reputation on being the person who catches what everyone else misses, who elevates what everyone else accepts, who holds the line when everyone else compromises. Take that away and who are they?
That's why the 80% Rule is so hard. Not because 80% is bad work — 80% of what a perfectionist produces is better than most people's 100%. It's hard because 80% means letting go of the thing that makes you feel valuable.
Nadia tried it. One product launch. She told her team: "Ship the version you have. I'm not editing it."
The launch went fine.
Not perfect. Fine. The deck had two formatting inconsistencies she spotted from across the room. The messaging was 90% of what she would have written. The rollout plan was solid but not elegant.
And nobody noticed. Not the CEO. Not the board. Not the customers. The product launched, the numbers tracked, and the world did not end because Nadia's name was on something that was good but not perfect.
Her team, on the other hand, noticed something different. They noticed that their work shipped. That their VP trusted them to deliver. That the thing they'd built was out in the world doing what it was supposed to do. For the first time in months, they felt like their work mattered — because it actually reached someone.
One thing to try. Pick one deliverable this week — a deck, a document, an email, a plan — and define what 80% looks like before you start. Not 80% effort. 80% polish. The version that's complete and correct but not flawless. Then ship that version without a final pass.
Notice what happens. Not to the work. To you.
If the discomfort is about quality, that's worth examining. If the discomfort is about what people will think of you — that's the real conversation.
Here's the question: What are you actually protecting when you won't let something go? The work — or yourself?
Comments