Without a definition of done, quality becomes a horizon: you can keep moving toward it, but you can never prove that the work is finished.
A “good enough” criterion gives you a visible stopping point. It does not ask you to care less. It asks you to match the effort to the purpose of the work.
Ask five questions before polishing
- Who will use this result?
- What decision or action should it support?
- Which mistakes would be unacceptable?
- What would improve it but is not essential?
- How much time is justified by the outcome?
Turn the answers into three lists:
| Category | Meaning |
|---|---|
| Required | Without this, the result cannot be used |
| Useful | Improves the result if time remains |
| Not now | Does not affect the current goal |
For an internal presentation, accurate numbers, a clear conclusion, and a next step may be required. Consistent illustrations may be useful. Elaborate slide animation may belong in “not now.”
Make the standard testable
“Make it professional” is too vague to guide a stopping decision. It invites another round of editing whenever the work feels uncomfortable.
A useful criterion can be checked:
- every number has a source;
- each slide communicates one conclusion;
- the file opens without errors;
- the intended recipient can identify the next step.
The test does not have to capture every quality you value. It only needs to distinguish a usable version from an unfinished one.
Match the standard to the cost of error
Good enough is contextual. A public legal document deserves more verification than an early internal memo. A checkout flow needs more testing than a temporary team prototype.
Ask what happens if the result contains a mistake:
- Is it easy to correct?
- How many people will see it?
- Could it affect health, money, safety, or trust?
- Is this a reversible draft or a final release?
Raise the standard where the risk is real. Do not apply the highest possible standard to every task by default.
Separate completion from improvement
Once every required item is complete, pause. Do not let the useful list quietly become a new set of obligations.
Make a separate decision:
Is the next improvement worth the time it will take, given the purpose and deadline?
If the answer is no, ship the current version. If an idea may matter later, put it in a next-version list. Capturing it reduces the fear that stopping means losing it.
A quick template
Before the next task, write:
This result is for:
It needs to help them:
Unacceptable errors:
Required:
Useful if time remains:
Not in this version:
Time limit:Review the template when the time limit ends. If the required conditions are met, the work is complete even if you can still imagine improvements.
If stopping remains difficult, read why perfectionists struggle to finish and how to stop endless revisions.