John Brewton sat at his desk, thirty days into a daily posting schedule, staring at a piece with three likes. He kept going. He was wrong about why.
Brewton preached the lesson most content creators preach: show up every day and the platform will find your people. "Social media algorithms reward presence, not perfection," he wrote earlier this year. "In the first 90 days, you're training the algorithm to understand what kind of content you create."
It sounds right. It is not.
The Cost of the Advice
The research on this is worth reading. Brewton's own story proves the opposite of what he claims.
In his first 30 days, he posted into a void. Three likes. Sometimes one. Sometimes zero. His count did not move. Then one post broke through: a piece on Andy Grove's management lessons from High Output Management. Intel's team found it and shared it across their network. The piece took off.
Then nothing like it happened for six months. His own words: "That's the part nobody tells you."
He kept posting daily through all six of those months. The volume stayed flat. The results did not. Something other than frequency caused that one post to travel.
Alesia Zakharova, a PhD researcher, studied this exact question. She pulled 30 posts from Substack writers with between 1,300 and 1,500 subscribers. Each writer had one post that far outperformed the rest, with likes ranging from 862 to over 2,000. She ran all 30 through a structured analysis and looked for shared patterns.
The finding: 30 out of 30. Every single post that broke through held something the reader could pull out, save, and reuse on its own. A list. A set of prompts. A framework applied to a real problem. No exceptions. Zero.
Frequency did not predict distribution. Structure did.
The Structural Flaw
Brewton's one hit proves Zakharova's finding from the other side. His Andy Grove post was built as a set of reusable management lessons a reader could hand to a direct report on Monday morning. It was a tool, not a diary entry. He built a resource layer by accident, then failed to see what he had done.
The problem is not that consistency advice is lazy. The problem is that it confuses maintenance with growth. Posting on schedule keeps your current readers warm. A resource layer is the only thing that moves a post to people who have never heard of you. These are two different jobs. Frequency solves one. Structure solves the other.
What to Build Instead
Distribution is not a frequency problem. It is a structure problem. A post travels only when it holds something the reader can detach from the writing and use after they close the tab.
Once that is clear, three moves follow from it.
Move 1: The Save Test. Before you publish, ask one question. Can a reader pull one piece out of this post and use it without reading the rest? If the answer is no, the post will earn likes from people who already know you. It will not reach anyone new. That question changes how you build every piece, because it forces you to put something concrete inside the writing rather than around it.
Move 2: The Detach Build. Write the reusable piece first. Start with the list, the prompt set, the three-step method. Then write the story around it. Most people do the reverse: they write their thoughts and hope something useful shows up by the end. Flip the order. Build the tool first, then build the housing.
Move 3: The Share Frame. Ask why a stranger would send this to a peer. Not why they would like it. Why they would forward it. Brewton's Andy Grove post traveled because a manager at Intel could hand it to a new team lead and say: read this before your next one-on-one. Your post needs that same reason to move from one inbox to the next.
What the System Shows You
Running this for 90 days does something the daily-posting advice never did:
You start to see which posts have legs and which ones die in place
You see that your most polished prose sometimes gets less traction than a rough list with ten concrete steps
You notice that saves and forwards matter more than likes
You stop measuring volume and start measuring architecture
The Feedback Loop
At the end of each month, ask three things.
→ Which post got saved or shared the most, and what was the resource inside it?
→ Which post felt like progress but left no trace in your numbers?
→ Which format produced a reusable layer with the least friction to build?
That is the difference between advice that sounds right and a system that proves itself.
Where You Stand
Most people who have been posting on schedule already have the discipline handled. The missing piece is not effort. It is structure.
Every post you write from here is either built to travel or built to stay where it lands. Frequency decides neither. Structure decides both.
