80. Good enough is good enough.

There’s nothing wrong with wanting to do your best. But striving for perfection when “good enough is good enough” is a waste of time. Don’t let unhealthy perfectionism keep you from cutting to the chase. Know when to let things go.

Consider the way new technologies come to market. The major software and electronics companies cut down on time and costs by putting products on the market before they’ve been completely debugged. Not only does this save the consumer money in the long run; consumer feedback teaches these companies more in a month than they’d discover through years of in-house testing. Sure, some users might grumble at flaws in the early models or releases. But by now, most consumers are aware of the practice and know to wait for the updated version.

You should know when your work is “good enough.” Before sitting on or delaying a project or document, ask yourself:

• Will anyone but me appreciate my efforts?

• Can I significantly improve this if I keep working?

• Does the possible gain in quality outweigh the lost time?

If you’ve answered “no” to the above, wrap it up and move on. If you’ve answered “yes,” map out what still needs to be done and do it—but nothing more.

As Alexander Hamilton said, “I never expect to see a perfect work from an imperfect man.” Accept your own imperfection. Do great work in spite of it.