How to Share Your Business Journey Online Without Oversharing

Not everything belongs online, even when you're building in public.

That might sound like a contradiction from someone who advocates for transparency in business. But there's a real difference between sharing things that are useful to your audience and sharing things that simply feel cathartic to post. The first builds trust. The second often erodes it — or worse, exposes information you can't take back.

After a year-plus of documenting my journey publicly, here's how I think about the line.

What's Worth Sharing

Milestone wins, with context. When something good happens — a launch goes well, you hit a revenue milestone, a piece of content gets traction — share it. But share the context alongside the number. What did you do to get there? What surprised you? What would you do differently? The lesson is what makes the win worth posting. The number alone is just a flex.

Honest setbacks that contain a lesson. This is where building in public separates itself from regular marketing. When something doesn't work, say so — and say why. Not to perform vulnerability, but because the failure is usually more instructive than the win. The post where I explained why a product launch fell flat got more engagement and more appreciation than any revenue milestone I've ever shared. People are hungry for honest accounts of what actually goes wrong.

Behind-the-scenes process. How you make decisions, what tools you use, why you built something a particular way, what a normal work week looks like — this kind of content is endlessly useful to people who are trying to do what you're doing. It doesn't require anything dramatic to happen. The process itself is interesting.

For what it's worth: I regularly share product updates and sales milestones from my MadeThis storefront. Not the specific dollar amounts in isolation, but the context — what drove a traffic spike, what a new product launch looked like, what I changed between version one and version two. That's the combination that's useful.

What Doesn't Belong Online

Specific customer complaints. Even anonymized, posting about a difficult customer creates problems. The customer may recognize themselves. Other potential customers may read it and wonder if you'd post about them. Your audience isn't your therapist, and a public platform isn't a support group. Handle support issues privately, learn from them, and share the pattern (not the incident) if it's genuinely instructive.

Revenue before you understand the context yourself. Sharing numbers before you understand what drove them is a common mistake. If you had a great month but you're not sure why, wait. Post the number after you understand the story. "I made $X last month and I'm not sure what caused it" isn't useful to anyone — and it invites speculation and comparison that you may not be prepared for.

Business decisions that could tip off competitors. Not everything needs to be documented in real time. If you're entering a new niche, testing a new product category, or making a strategic pivot, you don't have to announce it while you're doing it. Share the decision after it's made and you have something substantive to say about it. Building in public doesn't require live-streaming your strategy sessions.

Anything about a named third party without their consent. Colleagues, contractors, customers, collaborators — if they're not part of your building-in-public practice, don't make them part of it.

The "Teach, Don't Just Report" Principle

The filter I use for almost every post: am I teaching something, or just reporting that something happened?

"I hit $5K in revenue this month" is a report. It might generate a reaction, but it doesn't give anyone anything to use.

"I hit $5K in revenue this month — here's what changed: I went back to an old product, wrote a better sales page, and ran it to an email segment that hadn't seen it before. The lesson: don't assume a product is dead until you've tested new copy and new audiences" is a lesson. It tells the same story, but it earns the share.

Every time you're about to post something, ask: what does the person reading this take away that they can use? If the answer is nothing, you're reporting. If there's something actionable, you're teaching. Teach.

Where Dan Draws the Line, Specifically

I share: product launches, traffic milestones, lessons from failed experiments, process decisions, platform recommendations (including why I use the platform I use for my storefront), and honest assessments of what's working in my niche.

I don't share: specific customer interactions, competitor strategy analysis (writing about competitors publicly is almost always a mistake), exact earnings before I can contextualize them, or anything that makes me look like I'm doing better or worse than I actually am in ways I haven't thought through.

The north star is: "Is this useful to someone who's trying to build what I'm building?" If yes, share it. If it's just something I want to post for attention or validation, hold it.

That's a harder standard than it sounds. Some of the things I most want to post aren't particularly useful to anyone except me. Building in public means developing the discipline to share what serves the audience, not just what scratches the itch.

For a deeper look at how to share wins specifically without sounding like you're bragging, see my post on how to document your progress without looking like you're bragging. That's one of the trickiest mechanics of building in public, and it's worth thinking through carefully before you start.

The point of building in public is to be useful. Keep that as your compass and most of the oversharing problem solves itself.