When building in public starts replacing the product work
After 8 months of , the early stage felt useful because real choices, numbers, and mistakes brought honest . By the third month, making daily updates started taking more time than building the product itself. Writing threads, recording screencasts, and preparing became a major part of the work.
Some decisions started to be shaped by what would make a good update, not by what the product actually needed. By the sixth month, the activity felt less like and more like . The public process became the main thing, while the actual product became secondary.
The real question is where sharing work stops creating and starts becoming .
Key points
- can work well at first when it shares real numbers, decisions, and mistakes.
- Daily updates can slowly turn into a time-heavy content routine.
- Product choices can become distorted when they are made for better posts instead of better customer value.
- The public story can become more important than shipping the actual product.
- s need a clear limit on how much time public updates are allowed to take.