Building in Public Without the Noise

Building in public has become a content format. Founders post metrics screenshots, setback threads, "what I learned" carousels — not to think out loud, but to grow an audience.

That's fine. But it's not what I mean by building in public.

Two versions

Version A is a distribution strategy. You share progress to get followers, who become leads, who become customers. The audience is the point.

Version B is a thinking tool. You share because articulating forces clarity. The constraint of a public post makes you sharpen the idea. The audience is optional.

I practice Version B. This distinction matters because it changes what you share, how you share it, and what you get out of it.

What Version B looks like

• Writing about decisions before they're resolved, not after
• Sharing the reasoning, not just the outcome
• Naming the things that are uncertain — not performing confidence
• Being willing to update publicly when you're wrong

This is harder than sharing wins. It requires actually thinking on the page rather than packaging finished thoughts.

The signal-to-noise problem

Most build-in-public content is noise because it's optimized for engagement, not truth. Engagement rewards certainty, big claims, and emotional arcs.

Thinking requires the opposite: sitting with uncertainty, revising, saying "I don't know yet."

If you want to use building in public as a thinking tool, ignore the engagement metrics. Write for the three people who are working on the same problem you are.

They'll find it. That's enough.