Perfectionism Doesn't Produce Excellence. It Produces Burnout.

Jun 10

Key Points

Perfectionism isn't about standards. The standard keeps moving because it's designed to keep the work unfinished.
The exhaustion you're calling burnout isn't coming from your schedule. It's coming from chasing a finish line that moves every time you get close.
The block doesn't attack low-stakes work. It goes where the consequences are.
The Constrained Client Appointment test reveals within one week whether the problem is structural or something else entirely.
If strategy, more time, and better systems haven't fixed it, that's not a failure. That's accurate information about what's actually running.

Transcript

Jennie Hays (00:00)
You finished the draft. You looked at it and thought, okay, that could work. But then you went back to look at it one more time. You made one change. Just one. But then that change opened into ten different directions, and then you started questioning whether it even sounded like you, and the whole thing fell apart. That was three weeks ago. And the draft is still not published.

Your standard has been raised four times. And you're more depleted now than you were when you started with something that you'd already finished. Most people call that perfectionism. That explanation has never actually helped you though, has it? Because if perfectionism was just about high standards, lowering your standards would have fixed it by now. But it didn't.

Which means there's something else underneath it. And it's not what all the courses, the coaches, or even your mama told you that it was. By the end of this video, you're gonna know exactly what it is.

Here's what most professionals get wrong about perfectionism. They think it's about standards. It's not. You already know what a finished, functional version of this thing that you're creating looks like. You've produced it before. You've done something similar. For clients, you do it all the time. The standard is not the problem.

The standard keeps moving. And it moves only in one specific direction, forward, just out of reach. And the part that doesn't get set enough? Most people assume the standard moved because you always set the standard too high. It wasn't. Last month that standard was good enough. Last week it was close enough.

Yesterday it almost worked. The target moved. That's not a quality problem. It's a pattern. It's a block. That's not a high standard, it's a moving target. And a moving target is almost impossible to hit. And that's on purpose.

The exhaustion you're calling burnout isn't from working too hard or from a life that's genuinely too full. If that's what's happening, rest and removal from the situation are the only things that are actually going to work.

But this video isn't for that. This is for the other kind of burnout. The kind where you've had the rest, you've had the space, and you came back just as stuck as when you left. That exhaustion is not coming from your schedule. It's coming from chasing a finish line that moves every time you get close to it.

And if you've ever wondered why every productivity system and every program you've tried eventually just stops working, that's why. The target moved again. And it's going to keep moving until you understand what's actually making it move. But the moving target isn't random.

It shows up in very specific patterns, recognizable at every stage of your project. Before you start, when the forms still need updating, and you're not quite ready yet. Early on, when the whole weekend disappears into reading what you already wrote.

And right at the end, when you've been thinking about that one thing you wanted to change, and you open it to fix that one thing, and an hour later you've restructured the whole thing. The work isn't sitting still, and neither are you. You've been at this for weeks, maybe months, and you're no closer to done. You're just more tired.

Now here's a reframe that changes how you're going to look at all of this.

Perfectionism isn't the brain trying to produce excellence. It's the brain trying to avoid exposure. And here's why that matters. While the work is unfinished, it still can become anything. It can still be the very best version. You get to imagine how good it could be. Finished means finding out, it means visible.

Invisible means it can be judged. And when it's judged, it means the verdict comes in, which creates a very strange problem because the moment that you've been working toward so hard is also the moment that that block is trying to prevent. And the brain, when it's running that protection pattern, will do almost anything to avoid that verdict.

So it uses you against yourself and it raises the standard. It finds the next flaw, decides it needs another revision, or you need a credential, or there needs to be one more piece in there because it needs to be good enough. Not because it isn't good enough, but because finished

Is the moment that protection ends and visibility starts. Now I'm Jennie Hays and I'm the execution block specialist. And before I did this work with blocks, I spent 25 years as a paramedic. And what that career teaches you is how to identify the actual problem underneath the obvious one. The obvious problem in this case is the work isn't done.

The actual problem is usually that something is making done feel unsafe. And that's what we're looking at

Camera 2 (06:15)
Now the block is patient. It's gonna find you every time the work is about to become visible.

Before you start, you know what needs to happen. The thing that's actually going to remove revenue for you, create that visibility. And right before you sit down to do it, there's something that's always going to need to happen first. The website copy? Not quite right. The offer page is going to need another pass. The framework needs a better name before you can present it to anyone.

You rewrite the intake form, you adjust the positioning, you build the template that'll make the work easier once you start. You paint the wall, you get the rug, you move the chickens.

None of these are wrong observations. None of them don't need to get done. The block doesn't give you wrong tasks. It gives you real ones with legitimate reasons at the exact moment that scary thing was about to happen. Work gets done, but the critical move doesn't. Perfectionism doesn't stop the work.

It keeps you busy doing everything that isn't the scary stuff. Now, if you push past that and you're in the middle of the project, you know, you find that you started with a clear scope. You knew what done looked like. Somewhere between the beginning and the end, though, done stopped being enough. Not because quality changed.

But because finishing means releasing, and releasing again, it means it can be judged. So the scope expands. A section gets restructured. Another draft, it gets rewritten from a different angle, because the first angle wasn't quite right. You're not avoiding the work. You're doing it. The problem is you're doing it over and over on the same thing.

Let's say you get past that and you get to the finish line. This is one of the most expensive moves that this block can make. One of my clients, we're gonna call her Sharon, she finished the draft. She wanted to get her her website up. ⁓ And she'd been working on this with another coach for a couple of years. She finished it. Not almost finished it, finished. She told me "I knocked it out in about an hour. I was fine with it".

That's a complete sentence. The thing was done. Period. Until one thought crept in. I need to change that word. Just one change. Something small. Something that she honestly felt would make it better. She opened it up in Chat GPT to tighten that one little thing. And chat did exactly what AI does. Here's A, B, C, and D.

Options, directions, possibilities. And suddenly she's questioning whether any of the original sounded like her voice at all. One reasonable edit, ten new directions. And everything that she'd finished in an hour no longer existed. When we talked about it, she said, I'm constantly churning. I could spend an hour on something that should take a sentence.

She wasn't describing a person who can't produce good work. She was describing a brain that can't tolerate leaving good work alone. That is not a quality problem. That's a completion problem. That is the block, not the quality, the completion. And where it's showing up doesn't really matter.

Because every time you put the work down and pick it up again, you pay a tax. You have to reread everything you wrote to figure out where you were, rebuild the context, remember what you were thinking, decide if it still works. The block brings you back, and now you're paying for it. The longer that you've been circling it, the higher the tax. And the higher the tax, the more exhausted you are before you've even written another word.

The block isn't just costing you hours. It's costing you compound interest on every hour you've spent re-entering the same

Jennie Hays (10:48)
And once you see this, something uncomfortable becomes very obvious. The work you're stuck on is almost never the low-stakes stuff. It's the work that actually will change something in your business if it's finished. That offer that would bring in some real revenue, the content that would put you in front of the right people, the thing that you've been saying you need to do for six months.

The block doesn't waste energy on tasks that don't matter. It goes where the consequences are. And that's worth sitting with. Now I've watched this pattern run in people who are genuinely excellent at what they do. The quality isn't the issue. It never was. And what I

Consistently is that the people most affected by this block are usually the ones whose work is really good. Not despite the perfectionism, but because of it and because of the expectation they've built around it. The bar you've set for yourself is not random. It's there for a reason. The block is just using that against you. Which brings us back to the question the video opened with.

Why does the work never feel finished enough? Because the answer is going to change everything about how you've been trying to solve this. The answer isn't that your standards are too high. The answer is that finishing triggers something the block is designed to prevent. For some people,

That's fear of judgment from others or from themselves. For some, it's the permanence of putting something out there and you can't take it back. For some, it's the exposure that comes afterwards. Someone sees it, they respond to it, and now you're visible in a way you have no control over. The perfectionism isn't about the work. The work

Is where the block hides. That distinction matters because it explains why changing your standards has never solved it. Giving yourself more time, or just doing it, has never changed it. And why that next certification or revision or that next version didn't produce the relief you were expecting it to.

You weren't solving the right problem. The problem was never the work. It was never the standard. It was never the timing. It's the block. And the block has been keeping the work unfinished on purpose. Now, here's a test I want you to run this month. It's called the constrained client appointment.

Perfectionism thrives in open-ended time. The whole afternoon or even a whole weekend. My goodness, unlimited runway is exactly the environment this block needs to keep work in perpetual refinement. This will remove the runway. You are going to block one or two hours max. Not an afternoon, not a day.

And I want you to treat this time block like it's a paying client appointment. Now, what do you do for a paying client that you don't do for that thing that you keep scheduling and moving? Well, number one, you don't move it. You don't put a client on top of it. You don't move it for that doctor's appointment, or if you just don't feel like doing it. Now, if something actually forces a reschedule, something you really would normally take off if you had a client there.

Then this block goes earlier in the week, not push to next week. It has to be before the deadline. Now, during this appointment, which task you pick is hugely important. You need to do that task. The one you don't want to do, the one you know will make a difference, the one you keep redoing.

However, completion of the task is not relevant. The only measure of success is staying in the chair for the full time and working on that task. That's it. No finished draft, no polished version. It's time spent. I want you to set an alarm. And when that alarm goes off at the end of that time, you close the computer.

The discomfort you feel leaving it unfinished, that's part of the test. Now you're gonna run this, for four weeks. And what happens is gonna tell you a whole lot. If it's a structural problem.

If the issue is really just unmanaged time, the artificial constraint will force output. You're going to produce a functional, less than perfect draft, and the hard stop will actually relieve the pressure It doesn't have to be perfect today.

If the block is running underneath all of this, this structure usually fails. And it's going to fail in some recognizable way. You'll sit down for the hour and spend the first 45 minutes organizing your task list. You'll decide the kitchen needs attention the moment the work gets uncomfortable. You'll ignore the alarm entirely, unable to tolerate leaving the task in an unfinished state. Or you'll

You just won't start the timer at all because you just remembered you needed to update those other forms first. You might even just close the computer when the alarm goes off, feel relief for about 10 minutes, and then spend the rest of the week thinking about it, researching, talking about it, touching it in your head, even when you're not at your desk. The appointment was supposed to contain it. The block doesn't stay in a container.

If the constrained client appointment can't hold, the problem is not the schedule. The problem is a protection pattern running underneath. And that's not something a better calendar solves. Now if you ran this test and it didn't hold, or if you just listen to it and you're like, pfft, that's not happening, it's not failure. It's information.

It means that you have an active block in that area. The next step is just figuring out what it's protecting and why. Now that's not something a quiz resolves or freebie. It's got to be a conversation. And we can do that for free. It's a clarity call, the links in the comments. It's a diagnostic conversation, not a sales pitch. We're going to figure out what's actually going on and whether I'm the person to help you with it.

If you're not there yet and you're still just kind of figuring out which pattern is most active for you, what's going on, you can start at your next step, and I'll point you in the right direction. And that link is also in the comments. Because here's the truth of all of this. You are not broken. You're just blocked. And blocked is solvable.

You finished the draft.

You looked at it and thought: okay, that could work.

Then you went back one more time. One change opened into ten directions. You started questioning whether it even sounded like you. The whole thing came apart.

That was three weeks ago. The draft is still not published. The standard has moved four times. And you're more depleted now than when you started with something you'd already finished.

Most people call that perfectionism. And that explanation has never actually helped, because if perfectionism were about high standards, lowering them would have fixed it by now.

It didn't.

Which means something else is underneath it.

The Moving Target Isn't a Quality Problem

You already know what a finished, functional version of this looks like. You've produced it before. For clients, you do it all the time.

The standard isn't the problem.

Last month that standard was good enough. Last week it was close enough. Yesterday it almost worked. The target moved. That's not a quality problem. That's a pattern. A moving target is almost impossible to hit. On purpose.

The exhaustion you're calling burnout isn't from a schedule that's too full. If rest and removal are the only things that work, that's a different situation, and this isn't for that.

This is for the other kind. The kind where you've had the rest, you've had the space, and you came back just as stuck as before. That exhaustion isn't from your calendar. It's from chasing something that moves every time you get close.

How Perfectionism Shows Up in Business

Before you even start. You just need one more thing. One more certification. One more pass through your notes. Then you'll be ready. You won't be. But that's not the point.

Early in the project. You can't begin until the conditions are right. Not the right mood. The right setup. The right amount of uninterrupted time. You block off a whole weekend. You protect it. Saturday disappears into re-reading what you already wrote. Sunday evening arrives with genuine urgency. You get some done. Then you notice one section isn't quite right. Then it's 11 pm, and you're in a spiral.

The conditions were perfect. The execution block didn't care. Which means the problem was never the conditions.

Perfectionism Is a Completion Problem

Most people assume perfectionism shows up at the beginning. The blank page problem. The resistance to starting.

It doesn't. Not primarily.

The most expensive version shows up at the finish line. After the draft is done. After the offer is written. After the website is ready. Right before publication.

You finish a draft. It's solid. You know it's solid. You say "I'm fine with this" and mean it.

Then you go back for a review.

One change. Just one. And then another. And then you're restructuring the whole thing. The framework that was holding it together comes apart. You're looking at something worse than what you started with, and you have no idea how you got there.

One of my clients finished a draft. Not almost finished. Finished. She knocked it out in about an hour and was fine with it. Then one thought crept in: just one small change, something that would make it better. Her brain couldn't tolerate leaving a finished product alone. So she opened it in ChatGPT to tighten that one thing…not because the text needed it, but because she needed a reason to go back in. ChatGPT did what it does: here's A, here's B, here's C, here's D. She used the tool to manufacture new doubts. Suddenly she was questioning whether any of it sounded like her voice at all.

One reasonable edit. Ten new directions. Everything she'd finished in an hour no longer existed.

When we talked about it, she said: "I'm constantly churning. I could spend an hour on something that should take a sentence."

She wasn't describing someone who can't produce good work. She was describing a brain that can't tolerate leaving good work alone. That's the block. Not the quality. The completion.

Why the Standard Keeps Moving

Here's what changes everything.

Perfectionism isn't the brain trying to produce excellence. It's the brain trying to avoid exposure.

While the work is unfinished, it can still become anything. It can still be the best version. You still get to imagine how good it could be. Finished means finding out. Finished means visible. Visible means judgeable.

Which creates a strange problem. The moment you've been working toward is also the moment the block is trying to prevent.

So it raises the standard. Finds the next flaw. Decides you need one more revision, one more credential, one more thing before it's ready. Not because the work isn't good enough. Because finished is the moment the protection ends and the visibility starts.

The work isn't the problem. The work is the location where the block hides.

That distinction explains why changing your standards never solved it. Why giving yourself more time never solved it. Why "just doing it" didn't change anything. And why the next certification, the next revision, the next version didn't produce the relief you were expecting. You weren't solving the right problem.

Where Perfectionism Costs Entrepreneurs the Most

Nobody spends six weeks perfecting a grocery list. Nobody rewrites a text message seventeen times before sending it to someone they don't care about.

The block doesn't waste its energy on work that doesn't matter. It goes where the consequences are.

More visibility. More revenue. More responsibility. More exposure.

It's the offer that would bring in real revenue. The content that would put you in front of the right people. The thing you've been saying you need to do for six months. The work that would actually change something if it finished.

That's not a coincidence. The block is not random. It's not inefficiency. It's a protection pattern that knows exactly where to aim.

One Test to Run This Week

This is called the Constrained Client Appointment.

Perfectionism thrives in open-ended time. The whole afternoon. The whole weekend. Unlimited runway is exactly the environment it needs to keep the work in perpetual refinement. This removes the runway.

Block one to two hours. Maximum. On your calendar, treated exactly like a paying client appointment. You don't cancel on a client because you don't feel ready. You don't reschedule to the following week. If something forces a reschedule, it moves earlier. Never later.

For this appointment, task completion is irrelevant. The only measure of success is sitting in the chair for the full time working on the designated task. Not a finished draft. Not a polished version. Time spent.

Set an alarm. When it goes off, close the computer. Mid-sentence. Mid-thought. Stop.

The discomfort of leaving it unfinished is part of the test.

Run this for four weeks. What happens will tell you everything.

If it was a structural problem, the artificial constraint will force output. You'll produce a functional, less-than-perfect draft. The hard stop will actually relieve the pressure because the appointment is back on the calendar next week.

If the block is still running, the structure will fail. In recognizable ways.

You'll spend 45 minutes reorganizing your task list. You'll decide the kitchen needs attention the moment the work gets uncomfortable. You'll ignore the alarm, unable to tolerate leaving the task unfinished. Or you won't start the timer at all, because you just remembered you need to update those forms first.

If the Constrained Client Appointment can't hold for four weeks, the problem isn't your schedule. It's a protection pattern running underneath it. And that's not something a better calendar solves.

If you ran the test and it didn't hold, or if you already know it won't, that's not a failure. That's accurate information. It means the block is active.

Figuring out exactly what it's protecting and why isn't something a quiz resolves. That's a conversation.

Because you're not broken. You're blocked.

Frequently asked questions

I've been told perfectionism is just a high-standards issue. Why hasn't lowering my standards helped?

Because the standard isn't actually the problem. If it were, a decision to accept "good enough" would hold. For most people, it doesn't. The standard moves again. That's not a quality issue. It's a protection pattern that uses quality as cover. Changing what you think about the standard doesn't reach where the pattern is stored.

I finish things easily for clients. Why is my own work so hard to complete?

That's one of the most important signals in this whole pattern. The block is specific, not general. It activates around work that carries personal exposure, personal judgment, personal consequence. Client work feels safer because the stakes read differently. Your own business visibility doesn't. That selectivity is diagnostic, not random.

What if the Constrained Client Appointment test just makes me feel worse because I can't stick to it?

Then you've learned something. The test isn't designed to fix the block. It's designed to distinguish between a scheduling problem and a protection pattern. If the structure holds, it was structural. If it fails, that's accurate data. Feeling worse isn't the same as failing. It means you have clearer information about what's actually running.

What's the difference between perfectionism and just having high standards?

High standards produce finished work. Perfectionism produces revised work. If your standard were simply high, you'd hit it and be done exactly the way you do for clients. What you're describing is a standard that moves every time you get close. That's not quality control. That's a block using quality as cover. The distinction matters because one responds to effort and the other doesn't. If you've already tried lowering your standards and it didn't hold, that's your answer.

I've tried accountability partners, deadlines, and productivity systems. None of it stuck. Is there something wrong with me?

No. But there is something important in that pattern. Accountability and deadlines are structural tools. They work when the problem is structural. When you genuinely just need external pressure or a system. When they don't hold, it means the interruption is happening at a different level than the structure can reach. That's not a character flaw. It's information about where the actual problem is. If you want to find out what's running underneath, jenniehays.com/your-next-step is the right place to start. If you already know it's a block, and you're ready to talk about removing it, you can book a Clarity Call directly at jenniehays.com/clarity-call.

About Jennie Hays | Execution Block Specialist

Jennie Hays is an Execution Block Specialist who works with entrepreneurs stalled at their next level. Her clients don't lack strategy. They're blocked from executing it, and that gap has a measurable dollar cost.

Through Rapid Block Resolution, Jennie identifies the specific internal interference slowing execution, removes the friction attached to it, and restores consistent forward movement. She solves the right problem first and builds independence, not dependency.

Because once the block is resolved, execution becomes natural.

Learn more at jenniehays.com

Jennie Hays