I almost didn’t write this one.
Not because I lacked time, or a topic, or a rough outline sitting in a folder somewhere. I had all of those. I just didn’t have the feeling that it was ready — that specific sense that there’s something real to say, and not just something to fill a Monday slot.
That feeling, I’ve learned, is not a signal that the post isn’t ready. It’s a signal that I haven’t resolved the thing I’m trying to write about yet.
Which is usually exactly when I need to write it.
The draft that keeps moving
Most writing procrastination isn’t about writing. It’s about the unresolved tension underneath the topic.
I have a draft that sat in a folder for three weeks. Every time I opened it, the outline was different. The position had shifted. I’d learn something new — about the business, about myself, about the thing I thought I understood — and the draft would move again.
That wasn’t writer’s block. That was me not knowing something yet. And until I knew it, the draft was going to keep moving.
The moment it stopped moving was the moment I’d actually resolved the underlying tension. Not figured out how to write about it. Resolved it. The writing came after that, and it came fast.
What “not feeling like it” is actually telling you
There are two different kinds of resistance in writing.
One is avoidance. You know the topic, you know your position, but there’s something uncomfortable about committing to it publicly. That kind of resistance usually has anxiety attached to it — not boredom.
The other is incompleteness. You haven’t worked the thing through yet. The position isn’t stable. You keep finding new angles, new caveats, new exceptions. That kind of resistance feels like restlessness, not fear.
The boredom signal is more useful than most people give it credit for. When you’re bored with your own draft, it’s usually because you’re writing about something you’ve already resolved. The interesting part is the edge where you don’t know yet — and that’s also the edge where you don’t feel like it.
The discipline case is usually wrong
The internet has no shortage of advice about publishing consistently. Build the habit. Ship on schedule. Treat it like a muscle.
That advice isn’t wrong, exactly. But the reason it matters has nothing to do with discipline.
The real value of writing regularly is compression. Vague thinking collapses under the pressure of having to commit to a sentence. You can’t coast through a paragraph when you know someone is going to read it. The friction is the point.
You also can’t fake your way through that compression. If you don’t know what you think, a post won’t hide it. The draft will just move to a different folder and wait.
Why the friction might be the point
I used to think the best posts were the ones that came easily. They were fluent, they were confident, they had a clear position and a clean landing.
They’ve aged the worst.
The posts I’m proudest of are the ones where I was clearly working something out on the page. Where the conclusion wasn’t obvious when I started. Where the writing forced me to resolve something I’d been carrying without knowing it.
Those posts usually felt the worst to write. Not during — after. That slightly exposed feeling, like you said something truer than you meant to.
That’s usually when it’s working.
What I’m sitting with
There’s a version of this post I didn’t write. The one where I made it sound tidier than it is — where I wrapped the idea up in three clean principles and gave it a name.
I’m not sure what to do with that one yet.
Maybe next week.