For a couple of years now I’ve been juggling multiple products at once.
Every week I ship dozens of small changes. Bug fixes, copy tweaks, onboarding improvements, tiny UX wins, small refactors. All of it matters, but almost none of it ever gets seen.
Internally, the updates live in Notion, Git commits, Slack messages, or just in my head. Turning that into a "proper" public update always felt like extra work, so it rarely happened. Plus when you’re already stretched, anything that feels like extra friction is the first thing to get dropped.
That was the real problem.
I didn’t need better marketing. I needed a bridge between what was already happening internally and what the outside world could see. Why was publishing progress such a manual, fragile step when the information already existed?
That question is where my next unnamed project came from.
Not as a growth hack, but as a workflow. One source of truth. Internal changelog to public update. No rewriting. No marketing mode. Just honest shipping.
Now I use it to publish weekly updates across my projects. Some weeks are exciting. Some weeks are boring. Some weeks are just stability and cleanup.
But they’re real, and they add up.
The bigger lesson for me has been this: most founder content doesn’t fail because of a lack of ideas. It fails because of workflow friction. If something takes extra effort, it won’t happen consistently. Remove the friction, and consistency becomes the default.
My new unnamed project exists because I wanted a way to make progress visible without adding more work.