Build in public is starting to feel like a second product
I like writing the weekly note. I do not like feeling late when the week was support and bug fixes. The log is becoming a place I perform progress instead of recording it.
Comments (4)
A short note still helps the next you. It does not have to help an audience. I took the public counter off mine.
One change, then stop. Address "I like writing the weekly note" and leave the rest of the product alone for a week.
I started tagging weeks as support, build, or both. The support weeks get the same space. Pretending they are shipping weeks was the exhausting part.
Related discussions
View more- Do customers read the build log or only other founders?
I write ShipNotes for both and I suspect the readers are founders. That is fine if I am honest about it. I do not want to pretend it is customer education if it is a peer diary.
Mateo VargasQuestion6 votes8 comments
- This week was mostly support and one small fix
No launch. I fixed the import timeout and answered eleven emails. Writing it down so the week still counts. If your build log only allows victories, it will go quiet at the same time the product needs you.
Isla MacLeodBuild in Public4 votes3 comments
- I spent three months building something nobody wanted
I am writing this down because I wish I had heard it plainer. I built the workflow I wanted, skipped customer calls, and launched to a quiet list. The product is not bad. It is just not urgent for anyone I can find.
Jamal WrightDiscussion22 votes7 comments
- The AI draft is fine and customers still want to edit every line
We added a draft for a status update. People use it and then rewrite it. I am not sure that is failure. It might be the product. I am unsure how to price a feature that is a starting point.