Do you have a particular WHY or reason for your side projects? If not, how are you personally staying disciplined, motivated, and focused on achieving your side project-related goals?
Every team I talk to has more feature requests than they can act on, and most of it doesn't come with clean data attached, just a support ticket or a Slack message from a customer. For those running product teams here, what's your actual process for turning scattered feedback into a prioritized roadmap? Curious whether people are doing this manually in spreadsheets, using a dedicated PM tool, or something else entirely.
I launched my first product here cold, with no audience and no pre-launch community.
It got real feedback, which I'm grateful for. But once launch day ended, traffic dropped to almost nothing, even though I've kept posting consistently.
My takeaway: solving a problem gets people to try your product, but it doesn't bring them to you. That part is distribution, and I skipped it.
For makers who've launched a second time: what did you do differently before relaunching?
I remember reading an essay by @rrhoover about how he moved from his native Oregon to San Francisco after university studies, where doors full of networking opportunities opened up for him.
I saw the same thing in my country after graduation. About 80% of my classmates went to the capital, where there are the most opportunities in marketing and tech. (Or they went abroad.)