THE PERFECTIONISM TRAP: WHY A GOOD RESULT CAN STILL FEEL LIKE A FAILURE

A client of mine stepped into a lead role for a stretch last year. Their lead handed them a hefty to-do list before leaving, one that seemed simple enough at the time, long but doable. Nothing about it turned out to be easy. Every day, new issues came to the team, and they solved them. Bugs other teams flagged got fixed, new requests arrived daily, and every single one was delivered.

Teammates praised the work, other leads praised it too, and meanwhile some items on that original list sat untouched.

Then their lead came back, and the praise was big, coming from several directions at once.

But in our next session, my client told me they felt like a failure. And the sad part is that they weren’t being modest; they meant it, because they were still holding on to the to-do list from day one and measuring everything against it. They weren’t measuring it against what the stretch actually asked of them, or all the unplanned work they did, but against a plan written before any of it started.

I see this constantly, and I’ve started calling it Plan Perfectionism. The outcome gets measured against the original intention, never against what actually happened. If the work didn’t unfold the way it was pictured, it counts as a loss, even when the result was really good and the feedback excellent.

My client could see the good outcome. They said so out loud, in the very same breath they used to call it a failure, because they hadn’t finished everything on that list. It just didn’t matter.

The plan was louder than the evidence.

If you’ve ever delivered something solid and still walked away feeling like you’d lost, you already know this pattern from the inside.

WHAT FINALLY MADE IT CLICK

What finally landed for my client came from their own world, and if you’ve spent any time around engineering teams, it might land for you too.

When something ships, good teams don’t sit down for the postmortem and ask whether they built exactly what the original ticket said. They ask what happened and what it can teach them. A feature that shipped differently than the spec but solved the real problem isn’t a failed deploy, it’s new information the plan simply didn’t have when it was written. That’s the whole reason blameless postmortems exist. Judging reality against a plan that was written with incomplete information gives you bad data and even worse morale.

My client runs this logic at work every week, and so do you, probably without even thinking about it. We just don’t run it on ourselves.

SO WHY DOES ‘FAILING’ FEEL SO TRUE, EVEN WHEN IT ISN’T?

The feeling of having failed was never really a mindset problem. It’s a prediction problem.

Your brain is always quietly running a model of what should happen next. When reality goes somewhere else, your nervous system doesn’t file that away as neutral information. It registers it as an error, and that error shows up as a feeling long before it ever becomes a thought. That’s why it feels so convincing in the moment, and why it’s so hard to argue with.

For someone caught in Plan Perfectionism, that feeling doesn’t just show up, it takes over the whole picture. The good outcome is sitting right there in plain sight, and still the feeling that the plan failed is louder. Almost every time, no matter what the evidence says, the feeling wins.

None of this is a character flaw. It’s wiring, and the thing about wiring is that you can’t work with it until you can see it.

WHAT THE LIST SHOWED THEM

​So I asked my client something simple: tell me three positive things that happened this past week as a direct result of your work. Then I asked for three positive things that happened as a direct result of their work during those months as interim lead. Nothing about the plan, just the evidence.

It took a few tries before the plan stopped sneaking back in. The first lists were really comparisons in disguise, “finished it, but later than I wanted,” “handled it, but not as smoothly as I’d hoped,” and every single line still had the original plan attached to it, following it around like a shadow.

Then I asked them for three unplanned projects that came up, that they handled well, and that had positive results. And right there, they saw the facts. They delivered, the team stayed intact through a hard stretch, and the feedback was strong from everywhere.

As they looked at that list, more memories came up; more unplanned projects and tasks that they and the team handled well, with positive feedback. All of that evidence was suddenly sitting next to the story they’d been telling themselves, that they had failed, and the gap finally became visible enough to work with. Maybe for the first time, they could really see it.

TWO QUESTIONS, IN THIS ORDER

When reality goes somewhere other than where you expected, the brain naturally falls into a binary trap, success or failure, and most of us skip straight to the wrong question: Did I get what I originally wanted? The answer is almost always ‘yes or no’, and that’s exactly what produces the false sense of failure or inadequacy. We rarely notice it happening, because it doesn’t feel like a question at all. It feels like a fact.

So the next time it happens, try asking these two instead, in this order:

1. What actually happened? This one pulls your brain out of its emotional story and back into what’s real. Just the facts, with no comparison to the plan.
2. How did I handle it? And how did it go? This one shifts your focus away from what you can’t control – the messy, unpredictable world around you – and toward what you can, which is how you responded.

That’s really all there is to it, and yet it gives you more than you’d expect. Recognizing how you handled what came at you builds self-efficacy, that quiet confidence that you can deal with whatever shows up, along with a real sense of agency. And honestly, it simply feels good, especially as you start noticing other positive outcomes you might have missed along the way.

The hard part isn’t understanding it. It’s catching yourself before the old question about the original plan sneaks back in and overrides the other two.

WHERE THIS MIGHT SHOW UP FOR YOU

Think about the last project, conversation, or quarter that didn’t go the way you planned, where you still delivered something real and positive. Did you let it count? Did you let yourself accept the success? Or did you fall back into the old story, where there’s only success or failure and nothing in between?

Once you can see a pattern, you get to choose something different, and that’s the heart of this work. You don’t have to erase the gap between the plan and what actually happened. You just stop letting that gap judge you on information it never had.

If this is a pattern you recognize in yourself or in the people you lead, try these questions and see what may come up. You might just be surprised.

And if you want to work through your own version of this live, let’s talk.

Book a session here →

With love and gratitude,

Miriam

P.S.: Oh, and feel free to share this post with anyone you think could benefit from it. It’s FREE!

Follow me for more FREE content