Good enough is often excellent

How this pattern shows up in everyday work

It often starts quietly: an email you reread a fifth time before sending. A presentation that has been done for hours, except you are still adjusting font sizes and spacing. A project you want to show only once “nothing is missing at all” - a state that rarely arrives.

A telling sign is that the task itself stops being the focus, and worry about how the result will look takes over. The question shifts from “does this serve its purpose?” to “could someone find fault with this?”. That shift costs time that is often needed elsewhere.

Some people postpone tasks altogether when they feel they cannot do them to the standard they want. This can look like procrastination, when really it is a very high standard disguising itself as hesitation.

It also shows up in teams: over-thorough checking of other people's work, difficulty delegating anything without repeated review, or the sense that one small mistake could undo the whole impression others have formed.

Where the pressure comes from - societal and personal

Perfectionism is not simply a trait some people “just have”. A meta-analysis of 164 samples with more than 41,000 students found a steady rise in perfectionistic standards across birth cohorts between 1989 and 2016. That is a decades-long trend, not a personal failing of any particular generation.

The largest increase was in what researchers call socially prescribed perfectionism - not the standards we set for ourselves, but the sense that other people, institutions, or society at large demand perfection. In the study, this rise was notably larger than the rise in self-oriented or other-oriented perfectionism.

This matches much of what is felt at work today: comparison has become more visible, performance is documented and evaluated more often, and feedback arrives faster and more frequently. When mistakes become visible quickly and publicly, it is easy to learn that flawlessness feels like the safest strategy.

Alongside this, many people also carry a personal history: early experiences where affection or recognition seemed tied to achievement, or environments where criticism was louder than praise. Taken together, the era we live in and the history we bring with us explain this pattern more plausibly than the idea that someone simply “is” a certain way.

Why it is a pattern and not an identity

A pattern is something you do in certain situations - not something you are. The difference sounds small but matters: if perfectionism were part of your identity, there would be little to do except accept it or fight it. If it is a pattern, you can change it in specific situations without needing to change who you are.

Patterns form as a response to expectations, experiences and environments - they are learned, not innate. What has been learned can, at least in part, be unlearned or adapted situation by situation. That is a meaningful difference from statements like “I'm just a perfectionist”, which tend to fix behaviour in place rather than open it up.

It helps to talk to yourself differently: not “I am perfectionistic”, but “In this kind of task, I tend to set very high standards.” This phrasing leaves room for the fact that there are other tasks where this is not true - and that your relationship to certain kinds of tasks can shift.

This distinction also matters because it reduces shame. Noticing a pattern is an observation, not an exposure. There is no need for an elaborate explanation of why you “are like this” - it is enough to notice what is happening right now and make a small decision from there.

An experiment: define 'good enough' in advance

One effective lever is to define “good enough” before a task begins - not afterwards, once you are already judging whether it is sufficient. Ask yourself beforehand: how will I know, a week from now, that this piece of work has done its job? What needs to be included, and what does not?

Write these criteria down briefly before you start - three to five points are usually enough. They can be substantive (“the three main options are compared”) or formal (“this is understandable to someone unfamiliar with the topic”). Once these points are met, the task is finished in the agreed sense.

The value of this method lies in its sequencing: the criteria are set before you become emotionally close to the finished work. Right before submitting something, almost everyone finds it harder to judge objectively whether it is sufficient - closeness to your own work almost always skews judgment toward “more”.

For recurring tasks - status reports, meeting notes, internal presentations - it is worth setting a personal minimum standard once and then not renegotiating it every time. That saves energy for the tasks where extra care is genuinely warranted.

An experiment: time boxes and weighing effort against impact

A second, very concrete method is the time box: you decide in advance how much time a task gets, and you stick to it - even if you feel you could still improve something. A timer here is not a source of pressure but of relief: the decision about when to stop was made earlier, not in the moment of uncertainty.

It also helps to look deliberately at the ratio of effort to impact. For every additional step, ask: does this genuinely change the impact for the person receiving it, or does it only change my own sense of security? These two things are easy to confuse in the moment.

A simple image: the first 80% of a task often delivers most of its value. The final small adjustments cost disproportionate time but frequently barely change how the work lands or performs. This does not apply to everything - safety-relevant or legally significant tasks warrant care right to the end - but it holds true for much of everyday work.

If a time box runs out and you still feel the pull to keep going, that itself is useful information: it is worth asking what exactly you are trying to protect yourself from by investing more time.

Pausing before the revising begins

A brief, deliberate pause between “content is done” and “I'll go over it once more” can change a great deal. In that moment, a simple question helps: am I revising this because it serves the work, or because I feel uneasy about letting it go?

Both reasons are understandable, but usually only the first one should determine whether more time is spent. If the honest answer leans toward unease, it can help to send the work anyway and sit with the discomfort rather than soothe it through further revision.

A short walk, a glass of water, or deliberately looking away from the screen for five minutes can support this moment of pausing. The point is not to delay the decision indefinitely, but to avoid making it directly out of tension.

Over time, this brief pause becomes a signal in itself: noticing that you are building it in deliberately is already a sign that you are recognising the pattern, rather than simply acting it out.

Example wordings for everyday use

Talking to yourself, it can help to say internally: “This meets the criteria I set beforehand. It's done.” This phrasing is deliberately neutral - it does not judge “brilliant” or “inadequate”, but measures against a standard set in advance.

With a team or manager, a phrase like this can help: “I finished this within the agreed time. If any part needs more depth, let me know specifically where - then I'll prioritise that.” This signals openness to feedback without laying out your own uncertainty upfront.

When handing a task to someone else, a phrase like this helps: “It matters to me that X and Y are right. The rest is your call.” This makes your own standard transparent without extending it to every detail.

And when a mistake happens, a short, factual sentence often helps more than a long apology: “That was a mistake, here's how I'm fixing it.” This keeps the focus on the solution rather than making your own shortcoming the main topic.

What tends to feed this pattern

It rarely helps to equate perfectionism with ambition or diligence and defend it as a whole on that basis. Diligence relates to the task; perfectionism often relates more to one's own sense of security. Blurring the two makes it harder to see the pattern as something that can change at all.

It also rarely helps to constantly compare yourself with other people's seemingly effortless results - usually you only see the finished product, not the process, the drafts, or the support behind it. This comparison almost always distorts your own self-assessment.

It rarely helps to try to solve this purely through more organisation or more time-management technique. Perfectionism is rarely a pure organisational problem; it often concerns what your sense of worth or safety is currently attached to.

And finally, it rarely helps to look for this pattern only in yourself without considering the environment in which it arises. If a team or organisation genuinely expects unrealistic flawlessness, that is also a structural issue worth naming - not only something to work on internally.

A limit: what this reflection is not

This article is a reflection aid, not a diagnosis, a personality test, or therapy. It describes a common pattern in a work context, not a fixed trait that defines or labels you.

If high personal standards come with persistent exhaustion, significant anxiety, depressive symptoms, or a sense that you can no longer manage everyday life, that is a sign to seek professional support - for example through a general practitioner, a counselling service, or a psychotherapy practice. Self-reflection does not replace professional support when distress is serious or ongoing.

One small next step

You do not need to try every idea in this article at once. For the next task on your list, pick exactly one thing: set three criteria in advance for what “good enough” looks like - and once those three points are met, send it or mark it done, even if that feels unfamiliar.

Afterwards, quietly notice what happens - with the task, and with you. That is enough for a start.