I fell into this trap for years, and not just with writing. You open a new tool, tell yourself you're building a system that will finally make you productive, and three hours later you have a beautiful setup and zero words written.
That's the setup tax. Every tool you add comes with one: accounts, preferences, integrations, templates, plugins, folders, workflows. You tell yourself you're building a system. What you're doing is avoiding the blank page.
Read also: How to stop overthinking and publish your first blog post
Configuring feels like progress
Configuration feels productive because it shows visible progress. You move a block, rename a folder, pick a font, and you can see the result immediately.
Writing doesn't work that way, especially early on. The output is uncertain, the page is blank, and there's nothing to point at until you've written something. So it's easy to keep tweaking the workspace instead, because that always feels like forward motion even when it isn't.
Tools that turn into a second job
I've tried most of them as a writer and blogger: Notion, Obsidian, Craft, various CMSs, AI tools, analytics, automation. Each one looked like the answer, and each one could become its own mini-project.
A tool meant to save you time can quietly become a second job:
Tweaking fonts, databases, tags, and dashboards is procrastination disguised as optimization
The more tools you stack, the more decisions you have to make before you produce anything
A perfectly configured workspace doesn't make an idea better. It makes the desk look tidier
For people who enjoy building systems, building the infrastructure can become more enjoyable than writing
There's a real difference between removing friction and building infrastructure. Only one of those helps you write.
Read also: Why most new bloggers fail, and how to avoid it
The tax compounds when you switch tools
It's common for writers to chase the "perfect system," not find it, and hop to the next tool hoping that one will finally click. Every migration means rebuilding your setup from scratch: reimporting content, relearning shortcuts, rebuilding habits you'd only just formed.
I don't think a perfect, unified writing system exists. I think it's a fantasy that gets propped up by whoever is selling the next tool.
Where automation helps
Automation is worth having when it removes repetitive work you were already doing. It becomes useless the moment you spend more time maintaining it than you would have spent just doing the task.
Ask honestly what there is to automate in writing a blog post. Not much, beyond publishing. Templates should speed up work you do often, not turn every piece of writing into a form you have to fill out before you're allowed to think.
Read also: Long-form vs. short-form blogging: What should you focus on?
A simple test
Two questions cut through most of this:
How long does it take you to go from having an idea to writing the first sentence?
How many decisions do you make before that first word?
If the answer to the second one is "a lot," you don't have a writing problem. You have a setup problem.
What frictionless looks like
When new bloggers ask me for advice, I tell them to keep it stupidly simple. Paper and a pen. Apple Notes. Anything that opens instantly and gets out of your way. Not even promoting this platform here, just removing the excuse to configure instead of write.
It's part of why I built TWO the way I did: open it and write, nothing to set up first.
You don't need to decide where every idea belongs before you write it down. Capture first, organize later, and don't optimize a workflow that hasn't survived real use yet.
Final word
Writing creates the asset. Configuration creates the environment around it. The environment is important, but it should never consume the time meant for the asset itself.
The goal was never the perfect setup. The goal is to write. Maybe the best productivity hack available to any of us is refusing to pay the setup tax in the first place.
