Understanding yourself

Am I a perfectionist?

If you hold yourself to standards that are difficult to meet, find it hard to let go of mistakes, and struggle to feel satisfied with finished work — you might be a perfectionist. Here's what's actually driving it.

The work is done. Anyone looking at it would say it's good — better than good, actually. And you're sitting with the awareness of everything it isn't. The places it could be more precise. The things you'd change if you had another pass at it. The gap between what you produced and the version of it that exists in your head — the version that would have been right — that gap is where your attention keeps going, even as the finished thing sits there being perfectly adequate by any reasonable external measure.

Perfectionism gets discussed as though it's primarily a productivity problem — the thing that makes you procrastinate, that stops you from shipping, that keeps you revising past the point of diminishing returns. That's a real part of it. But it's the surface layer. Underneath is something more fundamental about how you relate to standards, to error, to the gap between what is and what should be. Understanding that deeper layer is more useful than the generic advice to lower your standards or let things go.

So — are you a perfectionist? And if you are, what does that actually mean about how you're wired?

The signs — what perfectionism actually looks like

You notice what's wrong before you notice what's right. Walking into a room, reading a document, looking at finished work — the errors, the gaps, the things that could be better register before the things that are good. This isn't negativity. It's a calibration — your quality-detection system is sensitive to the downside in a way that other people's simply isn't.

You find it genuinely hard to feel finished. The project that's done could always be more done. The email that's ready to send could always be more precise. The conversation that went well could have gone slightly better. The internal signal that says "this is complete and good enough" arrives later than most people's, if it arrives at all.

Mistakes stay with you longer than they should. Not in a dramatic way — just a background awareness of things that went wrong, things you said that weren't quite right, errors that have already been corrected but that still register when you think about the thing they were part of. The filing system that closes errors cleanly doesn't work the same way for you as it seems to for other people.

You have high standards for others too — not always expressed, but present. The quality of other people's work, the care they bring to things, the gap between what they produced and what they could have produced — you notice this in ways that can make you a difficult person to work with if the noticing comes out, and a quietly frustrated one if it doesn't.

And you find it hard to show work before it's ready. The draft, the rough version, the thing that isn't finished yet — sharing that produces a specific discomfort. Not because you're precious about it. Because what you're showing would misrepresent what the finished thing will be, and being misrepresented by your own incomplete work feels worse than the inconvenience of waiting until it's ready.

What perfectionism actually is

Perfectionism isn't wanting things to be perfect. That's the surface behaviour. The underlying thing is a specific relationship with standards — a deeply internalised sense of what correct, accurate and properly done looks like, combined with a sensitivity to the gap between that standard and current reality that other people simply don't have in the same way.

It's also a relationship with error. For a perfectionist, mistakes aren't neutral events to be corrected and moved past. They're information — about the quality of the process, about whether enough care was taken, about the gap between intention and execution. They require processing before they can be filed. The processing is the thing that looks to other people like dwelling or being hard on yourself. From the inside it's simply finishing the accounting before closing the ledger.

And it's a relationship with completion. Most people have a point at which something is done — good enough to move on from, finished in the sense that matters. Perfectionists have a different completion threshold. The point at which something is truly done is set higher, and reached less often, and the gap between what's been produced and that threshold is present more consistently. This isn't a choice. It's a calibration difference that runs deeper than preference.

There's a name for how you're wired

The DISC personality framework identifies four core behavioural traits — Dominance, Influence, Steadiness and Conscientiousness. Perfectionists almost always score highly in Conscientiousness — the C trait.

C types are oriented toward accuracy, quality and correctness at a fundamental level. This isn't a value they chose — it's a processing orientation that shapes how they experience everything. When they look at their work, they're not just assessing whether it's finished. They're measuring it against an internal standard of what it should be, and the measurement is precise and automatic. The gap between current state and correct state is immediately visible to them in a way it simply isn't for other types.

This orientation is the reason C types produce work of exceptional quality. The same sensitivity that makes completion difficult makes the work genuinely good. The thoroughness that makes letting go hard makes the output reliable. The difficulty celebrating finished work exists because the quality standard that drove the work is still running — still aware of everything the finished thing isn't — even after the thing is done.

If you also score in Dominance — the D trait — there's a related pattern. DC types are driven by both results and quality, which produces a specific kind of tension: the D wants to be done, to move forward, to ship. The C wants it to be right. That internal conflict — between momentum and quality, between done and correct — is one of the most recognisable experiences of a high DC type. The perfectionism doesn't just delay completion. It sits in friction with a drive toward action that makes the delay more frustrating.

The two kinds of perfectionism — and which one you have

Adaptive perfectionism produces high standards that drive excellent work without systematically undermining the person holding them. The standards are high but flexible — they distinguish between the things that genuinely warrant precision and the things that don't. The perfectionist can close a file when it's good enough in context, even if it's not good enough in the abstract. The quality orientation serves the work without consuming the person.

Maladaptive perfectionism applies the same high standards to everything, regardless of whether the stakes warrant it. The email gets the same scrutiny as the report. The inconsequential error gets the same processing time as the significant one. The gap between current reality and the internal standard produces a persistent low-level dissatisfaction that doesn't lift even when the work is objectively excellent. The quality orientation has stopped serving the work and started consuming the person.

Most perfectionists sit somewhere on the spectrum between these — adaptive in their best conditions, maladaptive under pressure or fatigue or in domains where the stakes feel particularly high. Understanding where the line sits for you — what triggers the maladaptive version — is more useful than trying to become less of a perfectionist generally.

What to do with this

Develop the skill of context-appropriate standards rather than trying to lower your standards globally. The question isn't "can I be less of a perfectionist?" It's "does this specific situation warrant the full standard, or will a reduced one serve it just as well?" Most situations fall into the second category. The situations that genuinely warrant the full quality orientation are fewer than the perfectionist tendency suggests — and being selective about where you deploy it preserves the standard for the things that deserve it.

Create explicit completion criteria before you start. The reason perfectionist projects don't end is often that "finished" was never defined in advance. If the completion criteria are set before the work begins — specifically, measurably, in a way that doesn't expand as the work progresses — the gap between current state and done becomes closeable. Without those criteria, finished is always a moving target that the quality standard keeps pushing further away.

And separate the error from the verdict. A mistake is data about a specific output. It isn't a judgment about your capability, your care, or your worth. The C type's tendency to process errors as information about themselves — rather than information about the specific thing that went wrong — is what makes mistakes stick around longer than they should. Noticing when the processing has shifted from "what went wrong here" to "what does this say about me" is the move. The first is useful. The second is where the cost accumulates.