How do you decide what to build next?
by•
One thing I keep struggling with while building products is figuring out which features are actually worth spending time on.
I sometimes come up with ideas that sound great, but then I wonder whether anyone would really use them. I also don't want to spend days building something that people don't actually need.
I'm trying to get better at understanding user needs before jumping straight into coding.
For those who've built and launched products, how do you usually decide what to work on next? Do you talk to users, look at feedback, or just build your ideas and see what happens?
I'd love to hear what has worked for you.
22 views
Replies
The thing that's worked best for me is being the heaviest user of my own product first. I build for myself, use it every day, and the stuff that annoys me is usually next. After that, a few of my consulting clients have their teams on my products daily, so their requests come in fast and I can usually get them done the same day. So I almost never sit down and guess. The next thing is whatever a daily user just tripped over.
@hisashispace That's a great approach! Building for yourself first makes a lot of sense. I'll try focusing more on real user feedback instead of just building features that sound good.
@ankit_pandit_dev Glad it helped! Most of what I ship still starts with a request from someone who used it that day. Good luck with whatever you build next ☺️