How to Build in Public: Tell Your Story While It Is Happening, Stalls Included
How to build in public, step by step: what to share, how often to post, how to keep one story across updates, and what to do when a project stalls or you let it go.
Building in public is telling your story while it’s happening, including the parts that stall. The method fits in five steps, each one explained further down:
- Share what you did, not what you plan to do.
- Post on a rhythm you can keep, such as one post per milestone.
- Keep each project’s dated history in one place, and let each post point back to it.
- When something stalls, name it: parked, with a reason, or let go, with the reason kept.
- Put your work and your personal goals in the same record.
This guide from the meinpublic blog is for anyone sharing work or a goal while it is still in progress, founder or not. When we searched this question on Oct 18, 2026, several guides near the top came from scheduling tools for X, and they measure success in audience. This one measures it by whether your record is true and still going a year from now. meinpublic keeps that record as one public map per person, but it isn’t open yet, so every example below comes from the founder’s own records, and the method works wherever you post today.
Share what you did, not what you plan to do
An update that reports an action builds the story; an announcement can quietly stand in for the work. Gollwitzer, Sheeran, Michalski and Seifert tested this in When Intentions Go Public (Psychological Science, 2009). Students whose identity intention was noticed by others acted on it on 1.92 days of the week, against 2.70 days when it stayed private. In a second study, law students worked on cases for 41.52 minutes when their intention was noticed, against 45.65 minutes when it was ignored. The samples were small, 49 and 30 people, and the goals were about who the students wanted to become. Read it narrowly: being seen to intend something can feel like progress already. A dated action can’t.
Writing it down helps too. Harkin and colleagues pooled 138 studies with 19,951 people in a 2016 meta-analysis in Psychological Bulletin: monitoring progress helped people reach their goals, more so when the progress was reported or physically recorded.
What makes a good update:
- A step: what you shipped or fixed, with its date.
- A decision: what you chose and why, such as a price or a cut feature.
- A number you’re comfortable with: users or kilometres. Revenue is optional.
- What you learned, including from a setback.
- A photo. On its own, it is a complete update.
What to keep back:
- A client’s or customer’s private details.
- A person who hasn’t agreed to appear.
- A strategy a competitor could copy before you’ve used it.
- Deals and legal matters still in progress.
The first meinpublic build log entry is written this way. On Oct 15, 2026, the first commit landed and meinpublic.com was attached 3 hours and 12 minutes later.
Post on a rhythm you can keep
How often matters less than whether you can keep it up. A rhythm you hold for a year tells a story; a burst of daily posts that stops in month two tells a different one. Posting every day describes a small group: in 2021, when X was still Twitter, the Pew Research Center found that the top 25% of US users by volume wrote 97% of all tweets.
| Rhythm | When you post | In a slow month | Fits when |
|---|---|---|---|
| Per milestone | When something real ships | Nothing to write | The work moves in big steps |
| Weekly | The same day each week | One short line | You want a steady record |
| Daily | Every day | Posts with no news | The work moves daily, in minutes |
The meinpublic build log keeps the first rhythm, with no fixed schedule: one post per milestone, written when there is something real to tell.
If you miss one, write the next one. On meinpublic, once the app opens, the map will write its owner a letter every Monday, under 150 words. It says what moved and what went quiet, then asks one question you answer with one tap, such as Park it. A weekly rhythm then has something that notices when you miss it, without judging you for it.
Keep one story across updates
A post fades within hours, so keep each project’s dated history in one place and let each post point back to it. Pfeffer, Matter and Sargsyan found in 2023 that a tweet’s median half-life is about 80 minutes: half its impressions arrive in that time, and after 24 hours about 95% of tweets get no meaningful impressions. Someone who finds your project in month four can’t read months one to three in a feed.
Tiến started meinpublic over this problem, from the reader’s side:
There is no way I can learn about them with just posts, images, or the experience, education. Not to mention they might have 1000 posts.
Tiến, founder of meinpublic, Oct 16, 2026
A record that solves it has:
- one place per project;
- entries in date order;
- on each entry, its date and what changed.
The build log’s day-by-day section is that shape, one dated line per step, from the brief on Oct 13 to the live site on Oct 15. Put each update where your readers already are, and keep the record somewhere that lasts. How a profile, a personal website and a map compare as that place is in meinpublic vs. LinkedIn. On a meinpublic map, each node keeps a dated timeline, and its state comes from that history instead of being set by hand.
When something stalls, name it
A stall is part of the story, so give it an honest name instead of going quiet. Parked means you paused on purpose and can come back. Let go means you stopped on purpose, and the reason stays on the record. Neither means deleting anything.
| State | What it means | What a reader learns |
|---|---|---|
| In progress | Being worked on | That it moves, and when it last did |
| Parked | Paused on purpose, with a reason | Why it stopped, and that it can return |
| Let go | Ended on purpose, reason kept | What you decided, and what you kept |
| Live or finished | Shipped, or reached its end | The result, beside the stalls before it |
| Gone quiet | No update, no reason | Nothing: they have to guess |
The build log’s “What was parked” list is a real example. Each item has its reason:
- A founding list stored by the website, because the app will do the real sign-up.
- Stories, the podcast, topic hubs and “shipped this month”, because they need real members who agree to appear.
- A page for people building themselves, because Home already puts personal goals next to work.
When you park something, say what would bring it back, if you know. Plans in “if this happens, then I will do that” form helped people act across 642 independent tests in Sheeran, Listrom and Gollwitzer’s 2025 meta-analysis in the European Review of Social Psychology. “If the app opens, I restart this” is that kind of line. The argument for why honest states bring people back is in the essay Parked Is Not Failed.
Put work and personal goals in the same record
People come to understand you from everything you are doing, not only your product, so a health goal or a family goal can sit in the same record as your work. Tiến’s map on the About page, as of Oct 16, 2026, holds 7 nodes in 4 areas:
- Builder: three products in progress, meinpublic, maptoact and cendora.
- Health: Reach 60 kg.
- Family: Father: good habits, and Father: a nice life.
- Content: a Tech, farm & edu channel, still an idea.
A product page would show the first line. The other three are why a reader understands what his weeks look like. Share only what you’re comfortable with: on meinpublic, any node can be members only, or sealed until a date you choose.
What this method won’t promise
It won’t grow an audience for you, and meinpublic leaves out the things that would try to:
- no likes;
- no follower counts;
- no ranked feed;
- no audience of its own to lend, so readers arrive through the links you share.
The app isn’t open yet, so today the only real map is Tiến’s. What the method gives you is a record that stays true, stalls included, for whoever comes looking.
Questions
Can I build in public with no audience?
Yes. Before anyone reads, a record still shows you what moved, and it is there when someone does arrive. Harkin and colleagues' 2016 meta-analysis of 138 studies found that monitoring progress helped people reach their goals, more so when the progress was reported or physically recorded. Start with one dated update a week, and share the link wherever your few readers already are.
How often should I post when building in public?
As often as you can keep up for a year. The meinpublic build log keeps one post per milestone, with no fixed schedule; one update a week on the same day is another rhythm that holds. Posting every day describes a few people: Pew found in 2021 that the top 25% of US Twitter users by volume wrote 97% of all tweets.
What should I not share when building in public?
Keep back what belongs to someone else, such as a client's private details or a person who hasn't agreed to appear. Keep back what could hurt the work before it's done: a strategy a competitor could copy, and deals or legal matters still in progress. Everything else is a choice, and a personal goal can stay off the record entirely.
Do I have to share revenue to build in public?
No. Share the numbers you're comfortable with, and they don't have to be money: the meinpublic build log reports 3 hours and 12 minutes from the first commit to a live site, and Tiến's map has a health goal of 60 kg. What makes an update worth reading is that it reports something that happened, with its date.