1
0 Comments

Allowing our users to vote/prioritize features

this product

I've been polling our users using the 'sean ellis method' whereby we ask our users how they would handle being unable to use Polar and would they be disappointed.

I'm prioritizing this feedback to continually improve our product market fit.

There's more detail in this post if you're interested:

https://firstround.com/review/how-superhuman-built-an-engine-to-find-product-market-fit/

Here's the challenge I have at the moment:

  1. managing all the feedback is challenging and requires that I manually review every survey result.

  2. Since there isn't a list of all future roadmap options the users might actually REALLY like a specific feature.

I'm considering giving our paying users a list to a Trello/Kanban board listing the roadmap and allowing them to vote on issues.

I think there are some pros/cons with this solution though.

  1. votes aren't timestamped. Feature priorities change over time so it would be nice to have some way to TTL and expire the votes.

  2. I'm not really prioritizing the features based on the user interview so many of the votes might be 'poison' in that they're not the ideal user use case.

  3. Users could assume the roadmap position is a commitment from us to implement the features but this might not be the case.

Seems like we're in a tough situation here. Not sure of the ideal solution.