Your product has customers and traction and is now beyond MVP. There is so much that you could build how do you work out what and the priorities? This presentation covers four techniques for doing just that.
- Co-founder of ProdPad - Co-founder of Mind the Product global product management community consisting of mothly meetups, annual un-conference, annual conference and blog - I've been doing product in one form or another for about 15 years now. My first product was a realtime system for managing spacecraft operations
- Limited resources so need to choose wisely - Want to avoid featuritis - Don’t be driven by your competitors roadmap * Klout & PeerIndex
- Remove the UX bugs so you don’t overwhelm the cognitive resources of your users - If it stops or interrupts a user task or journey prioritise - Example of triangle
- Treasure trove of information to mine in your customer support tickets - Look for the trend in requests or bug reports - Use the number of requests as a proxy for priority - JIRA integration on ProdPad
- Talk to both current customers and customers who left + customer who left will be painful but more valuable - Discover the problems you aren’t solving - Look for trends not single points - ProdPad Management reports
- MVF: build only the min amount necessary to see if the feature has value to users - What they say & what they are two different things - Have an idea & data seems to support but otherwise large investment - Example: ProdPad Roadmap
How to prioritisize what to build next - Forward Labs Product Day