"Build in public" — narrating your company's progress openly — has matured from indie-hacker subculture into a mainstream distribution strategy. Done well, it converts work you're already doing into a compounding audience. Done naively, it leaks strategy, invites copycats, and burns hours performing progress instead of making it.
Why narration outperforms announcement
Announcements are static: here's a thing, please care. Narration is serial: it has characters, uncertainty, and open loops, and audiences bond with serial stories in a way they never bond with press releases. The follower of a journey has sunk attention into your outcome — by launch day they feel minor ownership, and minor owners show up. It also solves the cold-start content problem: you never wonder what to post, because the week's work is the post.
What to share: decisions, not just outcomes
The temptation is to share results — revenue milestones, user counts. Those posts do fine, but the durable material is decisions: what you chose, what you almost chose, and why. "We killed our best-loved feature and here's the reasoning" teaches something; "we hit a milestone" merely reports something. Decision posts also survive bad quarters — you can narrate judgment even when the numbers are flat, which matters because the numbers will sometimes be flat.
What to hold back
- Unearned strategy. Insights that cost you months of experimentation are assets. Share the lesson's existence; be thoughtful about handing over the recipe while competitors are watching.
- Other people's information. Customer names, partner terms, employee situations — none of it is yours to narrate without consent.
- Numbers you'll regret. Public metrics create public expectations. Share trends and lessons freely; commit to specific recurring numbers only if you're prepared to keep reporting them when they dip.
Surviving the boring middle
Every company's story has long stretches where nothing dramatic happens. This is where most build-in-public efforts die — the founder feels there's nothing to say and goes quiet, and the audience decays. The fix is reframing: the middle is boring as news but rich as craft. How you run support, what you cut from the roadmap, the small fix that took three days — specific, unglamorous material is exactly what other builders actually want to read. If it was interesting enough to argue about in Slack, it's interesting enough to post.
The compounding effect is real but slow: months of narration before strangers start arriving warm. Which is the same lesson as always — start before you need it.