You want to share your work in public because it feels honest and it seems to build trust. You have also seen build-in-public content go wrong: the founder who posts every revenue dip like a diary entry, the creator who turns a hard week into a play for sympathy, the consultant who accidentally airs a client's private situation to a few thousand strangers. So you hesitate. How much of your work or your life is too much to put online?
The good news is that this is a decision you can make on purpose, not a vibe you have to feel your way through every time. Useful journey content is not about how raw you are willing to get. It is about choosing the right material, framing it so a reader takes something away, and keeping a clear line around the things that are not yours to share. This post gives you a framework for exactly that.
Why build-in-public works (and when it backfires)
Sharing your process works because most people only ever see finished things. They see the launched product, the polished course, the booked-out coaching calendar. They rarely see the messy middle: the pricing you second-guessed, the feature you cut, the email that flopped. When you show that middle honestly, you do a few useful things at once. You make your work relatable. You teach by example. You give people a reason to follow along instead of just consuming and leaving.
It also tends to attract the right people. A solo founder who narrates real decisions draws an audience that cares about those decisions, which is a far better fit than an audience that showed up for a viral moment and has no idea what you actually do.
Build-in-public backfires when the content stops being for the reader and starts being for you. There are a few common failure modes:
- Navel-gazing. The post is a status update about your feelings or your day with no takeaway for anyone else. Interesting to you, inert for everyone else.
- Sympathy farming. A hard moment gets posted mainly to harvest comfort and reassurance from an audience. That is a job for friends, a peer group, or a professional, not a feed.
- Boundary bleed. You share something that involves other people (a teammate, a client, your family) without their consent, or you reveal details you will regret later.
- Performance creep. Vulnerability that worked once becomes a formula, and you start manufacturing rawness to keep the reaction going.
A quick note before we go further: vulnerability is not a reliable growth tactic, and you should not treat it like one. Some honest posts will resonate and some will land flat, and trying to predict or engineer that reaction is how people end up oversharing. Share because it is useful and true, not because you expect it to perform.
The boundaries framework: share, shape, or hold back
Here is the core of it. Before any piece of journey content, sort the material into one of three buckets.
Share is material you can post largely as-is. It is yours to tell, it carries a lesson or insight for the reader, and you would be comfortable with it being public a year from now. Example: the reasoning behind a pricing change you made, including what you got wrong the first time.
Shape is material with a real lesson buried in something too raw, too specific, or not fully yours. You do not throw it out. You change the form. You strip identifying details, generalize the situation, or wait until you have enough distance to draw a clean takeaway. Example: a conflict with a client becomes a post about how you now scope projects, with no mention of the client.
Hold back is material that should stay private. It involves other people who have not agreed to be part of your content, it exposes sensitive personal or financial information, or it is something you are still in the middle of and cannot yet talk about with any perspective. Holding back is not a failure of authenticity. It is part of having judgment.
Most founders default to a binary: post it or do not. The middle bucket is where the best journey content actually comes from, because it forces you to find the lesson instead of just venting the moment.
How to decide which bucket something goes in
Run the material through three questions:
- Is this mine to tell? If the story centers on someone else, it is not fully yours. You can use your own side of it, but the other person's details belong to them.
- Is there a takeaway for the reader? If you removed your personal stake, would anyone still get value from it? If not, it is a journal entry, not content.
- Will I be comfortable with this being public later? Imagine a prospective client, a future hire, or a journalist reading it next year. If that thought makes you wince, shape it or hold it.
If it clears all three, share it. If it fails the first or third, shape it or hold it back. If it fails the second, it is probably not worth posting at all.
Making journey content useful: the lesson behind the moment
The difference between a useful build-in-public post and a navel-gazing one is almost always whether there is a transferable lesson. The moment is the hook. The lesson is the gift.
A raw moment on its own sounds like this: "Spent all weekend rebuilding the onboarding flow because the old one was a mess. Exhausted." That is a status update. It tells the reader nothing they can use.
The same moment, with the lesson surfaced, sounds like this: "Rebuilt our onboarding this weekend. The old version asked for too much before showing any value, so people bailed on step two. The fix was simple once I saw it: let people do one useful thing before asking them to commit. If your signup feels like a chore, that is probably why."
Same honesty. Same vulnerability about a thing that was not working. But the second version hands the reader a principle they can apply to their own product. That is the move: name the moment, then answer the implicit question, "so what should I take from this?"
A useful rhythm for shaping a moment into a lesson:
- Moment: what happened, briefly and concretely.
- Tension: what was hard, uncertain, or wrong about it.
- Turn: what you figured out, decided, or changed.
- Takeaway: the principle a reader can apply to their own situation.
You do not need all four every time, and you should not force a tidy lesson onto something that does not have one. But if you cannot find at least a turn or a takeaway, that is a signal the material belongs in the shape or hold-back bucket.
This is also how journey content compounds. A handful of honest, lesson-driven posts over time become a body of work that demonstrates how you think. If you want to take it further, you can turn shared lessons into a trust sequence so the people following along have a natural, low-pressure path toward working with you.
Protecting yourself, your team, and your customers' privacy
This is the part that gets people in real trouble, so be deliberate about it. The general principle: other people's information is not your content. A few areas to be especially careful with.
A note on this section: privacy and legal obligations vary by where you operate, your industry, and any agreements you have signed. Treat what follows as general practice, not legal advice. If you have contracts, regulated client data, or anything sensitive, check with a qualified professional.
Team and collaborators. Do not post about a teammate's performance, a hire, a departure, or an internal disagreement without their explicit okay. Even praise can be unwelcome if someone is private. The safe default is to ask before you involve anyone by name or by recognizable description.
Clients and customers. Client work is often confidential by default, and sometimes by contract. Before you share a project, a result, or a story that involves a client, get permission, and anonymize when in doubt. "A coaching client" is safer than anything that lets people guess who it is. If you have a non-disclosure or confidentiality clause, follow it. Sharing a customer's situation without consent can damage trust far more than the post could ever build it.
Finances. Revenue numbers, salaries, runway, and funding details can feel like compelling build-in-public material, and some founders do share them. If you do, understand the trade-offs: you may attract scrutiny, set expectations you have to keep meeting, or reveal things investors, partners, or your own team would rather keep private. There is no rule that you must share numbers to be transparent. Decide on purpose, and consider whether a number obligates anyone other than you.
Family and personal life. The people in your life did not sign up to be content. Children especially cannot consent in any meaningful way. Keep family details vague or absent unless the people involved have genuinely agreed, and remember that what feels fine to post today can feel different to them later.
A practical habit: before you reference any person other than yourself, mentally ask whether they would be comfortable seeing the post. If you are not sure, ask them, or leave them out.
Handling failures and hard moments without trauma-dumping
Failures make some of the best journey content, because they are honest and useful in a way that wins rarely are. They are also the easiest to mishandle. The line between a valuable failure post and a trauma-dump is distance plus purpose.
Distance. Do not post from the bottom of the hole. When something has just gone wrong, you are too close to it to draw a useful lesson, and you are most at risk of posting for comfort rather than for the reader. Wait until you have enough perspective to say what you learned, not just how much it hurt. Sometimes that is a few days. Sometimes it is months. Sometimes the answer is that this one stays private.
Purpose. Ask why you want to post it. If the honest answer is "to feel better" or "so people tell me it's okay," that is a sign to take it to a friend, a peer group, or a professional instead. Your audience is not your support system, and leaning on them that way tends to make people uncomfortable rather than closer. If the answer is "because someone else heading into the same mistake could avoid it," you have a real post.
A failure post that works usually does three things: it states what went wrong plainly, without melodrama; it owns your part in it without excessive self-flagellation; and it points to what you learned or changed. A course creator might write about a launch that underperformed by explaining the wrong assumption they made about their audience's readiness, what they would test first next time, and how a reader can sanity-check their own launch. Honest, useful, and not a cry for help.
Hold back the moments that are still open wounds, that implicate other people, or that you would only be posting to be seen suffering. Those are real and valid feelings. They just are not content.
A simple pre-post boundary check before you hit publish
Before any journey post goes live, run it through this quick check. If anything trips a flag, shape the post or hold it back.
- Whose story is this? If it is not mine alone, do I have consent to share the parts that involve others?
- What is the takeaway? Can I state, in one sentence, what a reader gets from this? If not, it is a journal entry.
- Am I posting for them or for me? Is the goal to be useful, or to be reassured? Reassurance belongs elsewhere.
- Future-proof? Will I be fine with a client, a hire, or a stranger reading this a year from now?
- Sensitive details? Have I removed names, financials, client specifics, or anything regulated that should not be public?
- Distance? If this is a hard moment, do I have enough perspective to draw a clean lesson, or am I posting from the middle of it?
Keep this list somewhere you will actually see it before you publish. The whole point is to make the decision once, calmly, rather than improvise it every time you have the urge to share.
In Plain English
Documenting your journey means showing the real process behind your work so people can learn from it and trust how you think. The framework is simple: sort every potential post into share (post it largely as-is), shape (find the lesson and strip what is not yours or too raw), or hold back (keep it private). The test for usefulness is whether a reader takes a transferable lesson away, not how exposed you are willing to be.
This helps founders, creators, coaches, and consultants who want the trust that comes from being open without the regret that comes from oversharing. Use it whenever you are tempted to post about a decision, a failure, a client, or a hard week. Run the material through the three questions, surface the lesson behind the moment, protect anyone who did not consent to be in your content, and give failures enough distance before you talk about them.
What to do next: pick one real thing from your work this week, run it through the share/shape/hold-back framework, and write the version that hands your reader a takeaway. To put this into a larger, sustainable system for showing up as a founder, see the founder-led growth cornerstone and personal brand basics for entrepreneurs. If you want to make sure your story actually serves your goals, it helps to connect your story to your social strategy. And when you are ready to give the people following along a path forward, learn how to turn shared lessons into a trust sequence.
For more on showing up as a founder without burning out, explore the Creator & Founder Growth hub or the Community Building hub.