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

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" p