How do you
decide what to
build next?
What should
I build
next?
Usability Testing
Customer Support Tickets
Customer Interviews
Minimal Viable Feature

Vs
Questions?
Get the tools

http://www.prodpad.com

Simon Cast
simon@prodpad.com
@simoncast

Learn more

http://www.mindtheproduct.com

How to prioritisize what to build next - Forward Labs Product Day

Editor's Notes

  • #3 - 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
  • #4 - Limited resources so need to choose wisely - Want to avoid featuritis - Don’t be driven by your competitors roadmap * Klout & PeerIndex
  • #5 - 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
  • #6 - 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
  • #7 - 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
  • #8 - 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