Six months of "content strategy" turned out to be very well-organized procrastination.
It started as a real goal: build an audience. Being an engineer, my first move wasn't to write. It was to design a system for writing. I spent weeks studying how successful creators worked, reverse-engineering their posting schedules, and building an elaborate Notion workspace.
I had a spreadsheet for everything:
- Content pillars mapped to target audiences
- A color-coded editorial calendar running into Q4
- Projected engagement for essays I hadn't written
- A distribution matrix with the "ideal" posting time for each platform
- Story arcs meant to lead readers to a vague "value proposition"
The strategy was thorough, color-coded and ready for a board meeting.
It contained zero content.
Planning feels exactly like work. You get the satisfaction of solving problems without the risk of anyone reading what you made. You can spend twelve hours tuning a tag hierarchy and end the day honestly tired.
I was optimizing a pipeline that carried zero bytes of insight.
It fell apart when an engineer I respect, someone with a large and engaged audience, posted a sharp note about state management. He'd written it on his phone at the airport, before boarding.
No content pillars, no Notion database.
His whole editorial calendar was whatever problem he'd solved that morning.
The simpler rule
I deleted the workspace. All of it.
I replaced it with a rule so basic it felt embarrassing:
When a technical problem costs me real effort, I write down what fixed it.
Hit friction, fix friction, write it down.
It worked right away. I went from zero published essays to several notes a week. The replies changed too. People stopped just liking posts and started telling me about their own version of the same problem.
Writing it down right away works for a few reasons. It's fresh, so you still remember which Stack Overflow answer lied to you. It's honest, because you're not performing thought leadership, you're just relieved it compiles. It's useful: if a problem cost you three hours today, it'll cost someone else three hours tomorrow. And it never runs out, since software guarantees pain, so software guarantees material.
Strategy comes later
The more you strategize about content, the less you make.
Strategy matters when you're scaling something that already exists. It kills a habit that hasn't formed yet. Starting needs momentum, low friction and a little disregard for perfection. Strategy adds friction and calls it quality control.
I'm arguing for starting, not for posting noise. Build the habit of writing in public first. Plan once you have something to plan around.
A plain note published on a Tuesday beats a perfectly optimized piece that lives forever in drafts.
Sometimes the best thing you can publish is the admission that you spent six months building an empty pipeline.