Once you've integrated with Receptive, you'll be gathering vital product demand data from your customers, teams and the market (your sales team will be adding features on behalf of prospects).
But what do you do with it all? How do you decide what makes it onto your product roadmaps?
Chances are, your roadmap is already full for the foreseeable future, so the thought of piling more and more onto it probably doesn't feel too good.
Fortunately, Receptive is designed to enhance and augment your existing roadmaps, rather than replace what's already there.
We cover this in more detail in The Receptive Workflow, but the general gist is that you use Receptive to research items that are on your roadmap before you start building them, so you know exactly what your users are expecting from that particular feature or improvement.
As spaces start to appear on your roadmap, you can then start using Receptive's reporting feature to surface some of your users' highest priorities, and you can fill any gaps in your roadmap with these requests.
Ultimately, Receptive makes it easier to research anything that's currently on your roadmaps, and then fill in any gaps for the future.
Related links:
Receptive product roadmap overview
Roadmaps: a product team's friend or foe?
What is the best way to manage a roadmap and a backlog?
Comments
0 comments
Please sign in to leave a comment.