How do you decide to add a feature or not?

Question

It would be amazing if someone had some great insights on this!👇

Pradeep Kumar M · Accepted Answer

Based on the most asked one from the customers and analyzing the scope of it.

Divine Rivers · Answer

This is our first launch so mainly based on the list of features we want th end product to have and denoting if they are a 'Must Have' or a 'Nice to Have'.

All 'Must Haves' are obviously added and only time-efficient 'Nice to Haves'  are included as well.

Maurizio Isendoorn · Answer

@divine_rivers1 I understand, thanks. I'll be notified about your launch :)

Domas Sakavickas · Answer

We mostly rely on customers' feedback. We do surveys, collect info from support chats and then making decisions

Answer

I work in customer support, where we closely monitor our monthly CSAT reports. Each month, we analyze any negative feedback, particularly when it's related to feature requests. If these issues pose a revenue risk, we document it and escalate this information to our product team for prioritization.

Additionally, we're actively gathering user feedback through surveys, emails, and directly on our platform to identify the most requested features. Product team then uses the action priority matrix to assess and demonstrate the potential ROI of these features before moving forward.

Maurizio Isendoorn · Answer

@sakozzy Interesting, thanks for your insights

Maurizio Isendoorn · Answer

@pradeep_kumar_m Good one!

Maurizio Isendoorn · Answer

@kateryna_ostapenko_ Sounds like a great strategy! Not only adding stuff but also eliminating frustrating elements

How do you decide to add a feature or not?

Replies