At Anthroware we had a proverb: "Perfection is the killer of progress. But excellence is an unmovable standard." It was on the wall. We referenced it constantly — because constantly was how often we needed it.
Perfection, in practice, means waiting. It means not showing a prototype until every edge case is handled. It means holding a strategy document until every assumption is rock solid. It means delaying a launch because the onboarding flow doesn't feel quite right yet. It's the pursuit of something that can't exist — and in pursuit of it, you stop moving.
Excellence is different. Excellence isn't about the state of the work when you show it. It's about the direction, the concept, the integrity of the thinking. Work doesn't have to be perfect before you share it — but it has to be good. The direction has to be right. The reasoning has to hold. The intent has to be honest.
"Work doesn't have to be perfect before we show it to each other and even to clients — but it has to be good in concept, execution, and direction."
How to tell which one you're doing
Here's the test I use: would you be proud to show this? Not "is it done" — would you be proud? If the concept is right and the direction is clear, the answer can be yes even when the execution is rough. A wireframe can be excellent. A messy spreadsheet that captures the right model can be excellent. A two-slide deck that makes the argument cleanly is more excellent than a twenty-slide deck that buries it.
Perfectionists often hide behind excellence as the justification. "I just have high standards." Maybe. But if your high standards consistently produce work that nobody sees until it's almost too late to change course, that's not standards — that's avoidance dressed up as rigor.
What this costs you on a team
On a product team, perfectionism is contagious and expensive. Engineers who won't ship until the code is beautiful. Designers who won't share concepts until they're pixel-perfect. PMs who won't bring a strategy to leadership until every question is pre-answered. All of it delays the feedback that would actually improve the work.
The irony is that perfectionism tends to produce worse outcomes than a culture of showing early and iterating. Early feedback catches wrong directions before you've spent months on them. Rough work that's directionally right beats polished work that's fundamentally off. But you can only learn that if you show it.
Excellence as a non-negotiable
None of this is a license to ship garbage. Excellence is unmovable. That means you're not cutting corners on the thinking. You're not sharing something half-baked that wastes the time of everyone who reviews it. You're not calling a first draft "good enough" because you didn't want to put in the work.
The distinction matters because they require different interventions. A team with a perfectionism problem needs permission to show rough work — and to learn that rough work shown early is how good work gets made. A team with a quality problem needs a higher bar, not a lower one.
Know which problem you have. Then apply the right pressure.
