Skip to main content

honeymallow

Why polishing your work is just procrastination in disguise

When perfecting your work becomes a way of avoiding it.

I had a book proposal sitting in my drafts folder for eleven months. Eleven months of “just one more pass,” “let me tighten the intro,” “I should probably restructure section three.”

When I finally sent it, the version I submitted was barely different from the one I had in month two. The editor replied in four days. I had spent almost a year polishing something that was already done.

What polishing actually feels like from the inside

The cruel thing about the almost-ready trap is that it feels like work. Real work. You are opening the document, you are reading through it, you are moving sentences around. There is effort happening. But effort is not the same as progress, and I had to learn that distinction the hard way after wasting significant time on projects that were already ready to leave my hands.

The feeling has a specific texture. It is a low-grade anxiety that shows up as productivity. Every time you open the file to “do one more thing,” you get a small hit of relief because you are still in control of the outcome. The moment you send it, that control disappears. Polishing is how you stay in control indefinitely.

The tell-tale signs you are past the point of useful revision

You read a paragraph, change three words, then change them back. That is the clearest signal I know. When you are making changes that cancel each other out over two or three sessions, you have crossed from editing into stalling. The work is not getting better. You are just moving furniture.

Another sign is that your revisions have stopped being about quality and started being about comfort. Early edits fix real problems. Late edits fix things that only bother you because you have read the piece forty times. Your hundredth read of your own work is the least reliable measure of its quality. Fresh eyes from someone else, or simply sending it out into the world, will tell you far more than another solo pass ever will.

Why finishing feels more dangerous than starting

Starting something new is low-stakes because failure is still hypothetical. Finishing collapses that comfortable ambiguity. Once you send the email, submit the application, post the video, you get real information back. And real information can include real rejection, real silence, real indifference. Polishing keeps you in a state where the project could still be perfect, because it has never been tested.

I noticed this most clearly when I started a ceramics class a few years ago. I would spend twice as long smoothing the surface of a bowl as I spent actually shaping it. My teacher finally said, “You are afraid to put it in the kiln because the kiln is the truth.” She was right. The kiln was where I would find out if it held together. Polishing was how I avoided that moment.

The version number problem

Here is something I started doing that changed my whole relationship with finishing things. I give every draft a version number and I set a hard limit before I begin. Three versions. That is it. Version one is the rough shape. Version two fixes the real structural problems. Version three handles language and clarity. After that, it goes out. No exceptions.

The limit forces you to be honest about what each pass is actually for. When you know you only have one revision left, you stop fiddling and start making real decisions. Constraints are useful here in a way that freedom is not. Unlimited revision time does not produce better work. It produces more revision.

One thing I picked up that nobody talks about enough: switch the font and the font size before your final read. Change your Google Doc from whatever you have been working in to something visually different, maybe Georgia at 13pt if you have been working in Arial at 11pt. Your brain stops reading what it expects to see and starts reading what is actually there. I have caught more genuine errors in five minutes of reading in a different font than in hours of reading in the familiar one.

How to actually decide it is done

The question I ask myself now is not “is this perfect” but “does this do the job it needs to do.” Those are completely different questions. Perfect is a moving target that you will never reach because perfection is defined by your anxiety, not by any real standard. Does it do the job is answerable. You can actually say yes or no.

I also started keeping a short list of what I call exit criteria before I even start a project. What would need to be true for this to be ready to send. I write that list when I am calm and clear, before I get deep into the work and before anxiety starts masquerading as discernment. Then I check the list at the end. If the criteria are met, it goes. My current feelings about the piece do not get a vote at that stage.

The last thing I started doing is scheduling send dates the same way I schedule deadlines. If I decide on a Tuesday that I will send a pitch on Friday, I put it in my calendar like a meeting I cannot cancel. The accountability is to myself, which is harder than it sounds but gets easier once you have done it a few times and seen that the world does not end when imperfect work goes out the door.


Most things I have sent out were better received than the version I thought I needed to reach. That gap between “the version I sent” and “the version I thought I needed” turned out to be almost entirely imaginary, which is a strange and useful thing to learn about yourself.

Holly