Build-in-public is not just posting progress (I will not promote)

Post original

I used to think build-in-public meant posting updates. Built this today. Launched this feature and fixed this bug. That stuff is fine. But it is also the least interesting version of building in public. The posts people actually remember are not the updates. They are the ones that show the thinking behind the work. What tradeoff did you make? What did not work? What assumption changed? What did a customer say that made you rethink something? I notice the same with content. A polished "here is what we did" post often gets ignored. A post about why something was harder than expected usually gets more replies. Not because people want drama. Because decisions are more useful than announcements. "Added a new feature" is an update. "We almost built this feature, then realized users were stuck on something earlier" is a lesson. The second one gives people something to react to. I am not saying founders should share everything. Some things should stay private. Revenue, customer details, unfinished ideas. That needs judgment. But build-in-public works better when it shows the choices behind the result. People learn from the tradeoffs, the bad guesses, and why one decision won over another. That is what makes people feel like they are learning with you, not just watching you post. For people building something, what kind of build-in-public posts have actually helped you? Progress updates, numbers, failures, or something else?   submitted by   /u/armandionorene [link]   [comments]