How Do You Decide Which Feature Requests to Build Next? 🤔

Question

Deciding which features to prioritize can be tricky—after all, you want to keep your users happy but stay true to your product vision.

Vote on popular methods and share your approach! 🗳️

Evgenii Anikin · Accepted Answer

Balancing user needs with your vision is key

Bobr · Answer

The opinion of users is only an indicator that should be in your strategy

Sergey Koshevoy · Answer

Great question, Violetta! Deciding on feature priorities is definitely a balancing act. We use a mix of user feedback, impact on our product vision, and feasibility. High-request features get our attention, but we also evaluate each one’s alignment with our long-term goals to ensure we’re building sustainably. We’ve found that considering development feasibility also helps us deliver quick wins, keeping momentum and engagement high. Plus, we keep an eye on features that might drive revenue as it helps fund future improvements!

Rahul Mishra · Answer

Same as yours first point. Based on user votes and their feedback. Can you help me to prioritize feature list for my MVP ?
(Add "https:" to click the link before // without double quote)

//forms.gle/rgt2P1T7Ucmrk31B7

Abhishek Dutta · Answer

listen to ur users :)

mostly all the features are out there!

Answer

I look at impact first. If a feature aligns with our vision and makes a real difference, it's a go.

cathy morino · Answer

For me, it's a balance user demand meets product goals. Hard to ignore top requests!

Edward Knight · Answer

Popular request get priority here. It's the best way to keep my users happy and coming back.

How Do You Decide Which Feature Requests to Build Next? 🤔

Replies