In a hurry? TL;DR
- 1Prioritize completing projects over achieving flawless outcomes; 'done' is better than 'perfect'.
- 2Avoid over-analyzing minor details that can stall overall progress and momentum.
- 3Embrace a 'good enough' solution now over a 'perfect' solution that arrives too late.
- 4Recognize perfectionism can be a disguise for procrastination; take action even if imperfect.
- 5Focus on functional completion, especially in time-sensitive situations, to maintain initiative.
- 6Apply the 'perfection is the enemy of progress' principle to software MVPs and first drafts.
Why It Matters
This idea is useful because accepting "good enough" can be the key to actually finishing what you start instead of getting stuck trying to make it perfect.
Winston Churchill’s maxim suggests that the pursuit of a flawless result often prevents any result from being achieved at all. It is a call to prioritise momentum and functional completion over the paralysing trap of idealism.
Key Takeaways
- Over-analysing small details can halt large-scale momentum.
- The phrase is a variation of Voltaire’s earlier observation that the best is the enemy of the good.
- In high-stakes environments, a good plan executed now beats a perfect plan executed next week.
- Perfectionism is often a form of procrastination disguised as high standards.
Why It Matters
Understanding this trade-off is the difference between a finished project and a permanent work-in-progress.
The Cost of Flawlessness
While the sentiment is often attributed to Churchill, its roots stretch back to the 18th-century French philosopher Voltaire. However, Churchill gave it a rugged, pragmatic edge. To him, perfection was a luxury that leaders in crisis could rarely afford.
The core tension lies in the diminishing returns of effort. The final five percent of refinement often requires more time and energy than the initial ninety-five percent of the work. For Churchill, especially during the Second World War, waiting for the perfect conditions or the perfect hardware meant losing the initiative to the enemy.
Churchill famously applied this logic to military engineering. When discussing the development of tanks and landing craft, he pushed for designs that were good enough to win the day rather than waiting for silver-bullet technology that might arrive too late to matter.
Historical Context
Churchill used versions of this phrase during his tenure as First Lord of the Admiralty and later as Prime Minister. It was a rebuttal to bureaucrats and engineers who wanted to delay production to fix minor aesthetic or marginal technical flaws. He understood that in a theatre of war, a functional weapon in the hand is superior to a perfect blueprint in the desk.
Practical Applications
- Software Development: Releasing a Minimum Viable Product (MVP) to gather user data rather than building a feature-heavy ghost ship.
- Creative Writing: Completing a rough first draft to establish structure before attempting to polish individual sentences.
- Decision Making: Using the 70 percent rule, where a decision is made once 70 percent of the information is available, rather than waiting for total certainty.
Similar Perspectives
- Voltaire: The best is the enemy of the good.
- Sheryl Sandberg: Done is better than perfect.
- Salvador Dalí (Contrast): Have no fear of perfection, you will never reach it.
Is perfectionism always bad?
No, in fields like neurosurgery or aerospace engineering, high precision is required. However, for most creative and administrative tasks, total perfectionism acts as a bottleneck.
Did Churchill invent this phrase?
He popularised this specific phrasing in English, but the sentiment exists in various forms across cultures, notably in Italian proverbs and French literature.
How do I stop being a perfectionist?
Set strict time limits for tasks and focus on the minimum requirements for success before adding embellishments.
Related Content
- The Pareto Principle: Why 20 percent of effort delivers 80 percent of results
- Analysis Paralysis: How overthinking kills productivity
- The Art of the Rough Draft: Why your first attempt should be bad
Historical Context
This quote, often attributed to Winston Churchill, particularly during his leadership in the Second World War, reflects the pragmatic and urgent decision-making required in high-stakes environments. While variations of the sentiment existed before him, Churchill's articulation gained prominence in a period demanding swift action and tangible results over idealised, unattainable goals. It speaks to the pressures of wartime leadership where delays for absolute perfection could have catastrophic consequences, emphasizing the criticality of momentum in the face of adversity.
Meaning & Interpretation
The quote means that striving for absolute perfection can, paradoxically, hinder real advancement or completion. It suggests that if one waits for everything to be flawless before moving forward, nothing will ever truly be accomplished. Instead, it advocates for a practical approach where achieving 'good enough' or 'functional' results promptly is preferable to endlessly refining something that may never reach an elusive state of perfection. It implies that progress often requires compromise and the willingness to accept imperfect but viable solutions.
When to Use This Quote
This quote is highly relevant in project management and innovation, where teams can get bogged down in minor details at the expense of launch deadlines. It applies to creative endeavors, encouraging artists or writers to finish and release work rather than endlessly tweaking it. Businesses can use it to justify agile development or minimum viable product strategies. Essentially, it's pertinent whenever an obsession with flawlessness leads to paralysis, delayed action, or missed opportunities, prioritising actionable progress over an unachievable ideal.
