Articles in this section

Receptive's reports & the RICE methodology

Avatar
Hannah Chaplin
  • Updated
Follow

Intercom's RICE methodology is becoming increasingly popular among product managers. Here's how Receptive supports it:

Reach

You can segment all the data out in Receptive so you understand reach in three ways:
 
1. You can see exactly how many customers/prospects/internal team members want a feature request and how important it is to them.
 
2. You can segment all the prioritized requests to understand the level of reach for each stakeholder group. Examples include what matters to large customers, small customers, sales team, leadership, customers in a certain location, etc. See more tagging ideas here. 
 
3. You can set a custom reach estimate using tags. Examples:

Impact

Our "effort vs value" chart is a great way to gauge impact. If you hover over a feature on the chart, you get a hard value for effort (from the sliders / value out of 100) and the value. The value calculation comes from the SmartList algorithm and is normalized - a feature with a value of 100 is going to give you the maximum impact.

Remember you can segment the data with one click too - selecting from the "Prepared Reports" list lets you see which requests will have the highest impact for your internal teams, customer base as a whole, churned users, highest to lowest paying customers etc...

Confidence

Receptive is all about gathering prioritized demand from your customers, market and internal teams so you can make data-driven product decisions. You can be confident in your data because you know that you are working with up-to-date and relevant information, not +1 votes from a customer feedback forum or spreadsheet. 

Effort

We combine feature value with development effort so you can make great decisions on where you place those all important scarce development resources.  

 

Related articles

Comments

0 comments

Please sign in to leave a comment.