I have edited a lot of writing in my life, including blog posts at midnight when my brain was running on spite and chamomile tea, articles for clients who changed their minds three times mid-draft, and most recently my own urban fantasy novel manuscript. I had to read it so many times that I started dreaming about my own sentences in ways that were not flattering to anyone involved.
Self-editing is one of those skills that nobody really teaches you. You’re expected to absorb it somehow — through school, through feedback, through osmosis — and then do it, presumably without wanting to throw your laptop into a body of water. But editing yourself is genuinely hard, and it’s hard in specific ways worth talking about.
So here’s what I’ve figured out from years of editing blog posts and one very long, very humbling book: how to make self-editing more effective.
The Problem With Editing Your Own Work
The reason self-editing is so difficult is that when you wrote the thing, your brain was developing meaning as it went — filling in gaps, connecting ideas, anticipating what came next. When you read it back, that same brain keeps doing the same thing. It sees what it meant to say, not always what it actually said.
This is why you can read a sentence five times and not notice the missing word your brain kept inserting for you.
For those of us with AuDHD brains, this can be even more pronounced. We’re already pattern-matchers. We’re already working fast and filling in context. So we need to slow down and actually see the page in front of us.
The good news is that there are concrete ways to do that.
Step One: Finish the Draft Before You Edit Anything
I know this sounds obvious. I also know I have never met a writer who consistently does it without needing a reminder.
Editing while you draft is a trap. You polish the first three paragraphs into something beautiful, only to never finish the piece because you keep circling back to perfect the opening. The draft never gets done, and the ideas waiting in the middle and the end never make it out.
Finish the thing even if it’s messy. Even if you know a section is weak or a transition is rough. Finish it and then leave it alone for a beat before you go back.
For blog posts, that beat might be an hour or a day. For longer work, longer — ideally a few days minimum, if you can manage it. The point is to create distance between the version of you who wrote it and the version of you who’s going to edit it.
Step Two: Read It Out Loud
I cannot overstate this one.
Reading out loud forces you to slow down to human speech speed, which is slower than your eyes moving across a page. It forces you to say every word. It catches rhythm problems, repetitive sentence structures, clunky phrasing, and missing words in a way that silent reading doesn’t.
When something sounds wrong out loud, it usually is. Trust that instinct.
For longer work, this is genuinely exhausting — I’m not going to pretend I read all 93,000 words out loud. But I read out loud during the revision passes that mattered most, and it caught things that three rounds of silent editing had missed.
If reading out loud is difficult for you — because of vocal fatigue, chronic illness, or any other reason — text-to-speech software does a similar job. Having your writing read back to you by a voice that isn’t yours breaks the pattern-completion problem just enough to help you hear what’s actually on the page.
Step Three: Edit in Separate Passes for Separate Problems
Trying to fix everything at once is a good way to fix nothing.
When I edit a blog post, I usually make at least three passes with different focuses. When I was editing the manuscript, I lost count — but each major pass had a specific job.
The structural pass is where you look at the big picture. Does this thing make sense? Does it do what you meant it to do? Is there anything missing that needs to be there, or anything present that shouldn’t be? For a blog post, this might mean asking whether your point is clear and whether your sections actually build on each other. For longer work, it means chapter structure, arc, pacing, and whether the throughline holds.
Don’t touch sentences during the structural pass. The sentence might be lovely, but if the whole section is getting cut, the lovely sentence goes with it.
The paragraph pass is where you zoom in one level. Do your paragraphs flow? Do transitions between them make sense? Is any one paragraph trying to do three different things? Does each paragraph have a clear point?
This is also where I look for repetition — places I’ve said the same thing twice, sometimes in almost identical sentences, because my brain lost track of what it had already said. I have the over-explaining and repeating type of autism, so I always need to proofread with that in mind.
The line pass is the close edit. Sentence by sentence. Word by word. This is where you catch typos, cut unnecessary words, fix clunky phrasing, and make your sentences do their jobs cleanly.
By the time you get to the line pass, the structure should be solid. You’re not making big decisions anymore — you’re just making the sentences as good as they can be.
Step Four: Know Your Patterns
Every writer has habits. Patterns they fall into without noticing. The trick is knowing yours.
Mine include: overusing “just” and “really” when I’m being conversational (I edit them out by the dozen), starting too many sentences the same way, and occasionally writing sentences that are doing so much work they need to lie down.
Yours are probably different. They might be passive voice when you’re tired, or run-ons when you’re excited, or a tendency to over-explain things you’re not sure you’ve made clear. Whatever they are, once you know them, you can look for them specifically.
A find-and-replace search for your filler words is genuinely useful here. I search for “just,” “very,” “really,” “that,” and “actually” in every draft. Most of them get cut. The ones that genuinely belong stay.
This got more interesting — and more useful — when I was working on the manuscript, because I had a lot of words and patterns to notice. Things that might slip past you in a 1,200-word post become obvious when you’re looking at a document that long.
Step Five: Get Distance From Words You Love
This is the hard one.
Sometimes you write a sentence you love. It’s good. You know it’s good. You’re proud of it. And it doesn’t belong in this piece of writing.
Maybe it’s a tangent. Maybe it takes the piece in the wrong direction. Maybe it’s just too clever for the moment it’s sitting in, and it draws attention to itself in a way that breaks the flow. Whatever the reason, it has to go.
“Kill your darlings” is advice that gets thrown around a lot, and I want to be careful about how I frame it. The goal isn’t to be merciless toward your own work; it is to be clear-eyed about whether something is serving the piece or serving your ego. Those are different things.
What helped me during the manuscript edit was a “cut but keep” document. Everything I cut that I wasn’t sure about went there instead of disappearing. It meant I could delete things without the anxiety of permanent loss, which made it easier to delete them.
Step Six: Check the Beginning and the End Last
The opening and the closing of a piece are doing the most important work — they’re what people read first and what they remember after they leave your website or close your book. So check them last, after you know what the middle actually does.
A lot of first drafts have openings that are really the writer warming up. The actual piece starts three sentences or two paragraphs in. Cutting the warm-up is usually an improvement, even when it doesn’t feel like one.
Closings have the opposite problem — writers run out of steam and end too soon, or they panic and add a tidy wrap-up that restates everything that just happened. Neither is satisfying to read.
A strong closing lands somewhere real. It leaves the reader feeling as if the piece arrived somewhere, not as if it just stopped. Look at your closing after the rest of the edit is done and ask honestly: does this land, or does it just end?
Step Seven: Let It Be Good Enough
Perfectionism and self-editing have a complicated relationship.
Editing is how you make something better. But there’s a version of editing that becomes procrastination, or becomes erosion — where you sand away at a piece until it’s technically correct but has lost whatever made it alive and specific. At some point, the draft is done. It’s not perfect. Nothing is perfect. It’s done, and it’s good, and it’s ready.
This was genuinely one of the hardest things about working on the manuscript. At a certain point, I had read it so many times that I couldn’t tell what was good and what was a ghost of what had been good before I edited it too many times. I had to make peace with that uncertainty and let it go.
Blog posts have a natural advantage here: the feedback loop is faster. You publish, you see how it lands, you get better. You don’t have to be perfect before you put it out. You have to be done.
Done is complete. Done is something a reader can hold. Perpetual revision is just a draft with anxiety and no landing.
The real lesson across all of it is that editing is a skill, and skills improve with practice. Every time you go back through a draft with fresh eyes and specific attention, you’re learning something about how you write and what your work needs. That learning compounds, and the editor you are six months from now will be sharper than the editor you are today because you’ll have seen more of your own patterns and made more decisions about how to handle them.
You don’t suck at this; you’re just learning it. And the fact that you care enough to go back through the draft at all means you’re already most of the way there.
Leave a Reply