Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

How to make a Product Roadmap that actually works

88 Aufrufe

Veröffentlicht am

This was discussed at the Workshop on "How to make a Product Roadmap that actually works" conducted by HelloMeets in Bengaluru.

Speaker & Presentation by:
Amit Tiwari, Senior Product Manager at Milaap

-Previously worked as Product Manager at ListUp & Software Engineer at Galleri5
-At Milaap, he leads a team of 2 product managers and a designer and has:
-Collaborated with the marketing team to enhance the accuracy of ads performance
Conducted user-research, usability testing and in-person interviews with the design team to understand the pain-points of campaign organisers in the campaign setup flow and led it's complete revamp
-Led the revamp of checkout flow to reduce drop-offs
-Implemented a rating and feedback mechanism in the major modules of the site to collect user feedback
-Led the work on quick campaign setup using WhatsApp, Messenger and voice platform
-Led the localisation of the campaign setup flow in regional languages

Presentation includes:
-What is a product roadmap and Why is it important?
-How to create a roadmap?
-How does he approach roadmap creation at Milaap
-What is feature prioritisation and why is it important?
-How to do prioritisation?
-How they approach prioritisation at Milaap?
-Case Studies from Milaap on:
The top-down approach of roadmap creation
Feature prioritisation both in the long & short term
Implementing user-feedback

Veröffentlicht in: Kleinunternehmen & Unternehmertum
  • Login to see the comments

How to make a Product Roadmap that actually works

  1. 1. Roadmap, Prioritisation, Feature Analysis
  2. 2. Table of contents 2 ● Roadmaps ● Prioritisation ● User feedback implementation and analysis
  3. 3. Roadmap 1
  4. 4. 4 High-level visual summary Maps out vision and direction Product offerings over time What is it?
  5. 5. 5 ● Prioritise tasks and initiatives ● Track progress toward goals ● Coordinate activities across teams ● Build consensus and understanding within teams ● Create transparency internally and externally Goals
  6. 6. 6 ● Organisational leadership ● Product owners and managers ● Developers For whom?
  7. 7. 7 Top Down
  8. 8. 8 When to create what?
  9. 9. 9 When to create what?
  10. 10. 10 When to create what?
  11. 11. Prioritisation 6
  12. 12. 12 Effort/Impact Matrix
  13. 13. User Feedback Analysis
  14. 14. User Feedback Implemented during the first week of November in the support widget and withdrawal request creation modules 14
  15. 15. 15
  16. 16. An essential product feature that allows end- users to provide their feedback To capture the pain- points about the most critical product modules Analyse the feedbacks to improve the given modules 16 1 2 3
  17. 17. 17 Usability Efficiency
  18. 18. 18 Conversion rate < 20% Average rating < 3 20-30% conversion rate Average rating > 4 Good + Enough feedback to form categories from feedback which can be incorporated as predefined options in next iteration Poor Good Great
  19. 19. 19 QuickSight Sheets Rapidminer Heap
  20. 20. Support widget conversion funnel 20
  21. 21. 21 ● Praise for Milaap ● Complaints about support ● Issues about various modules ● Asking for funds Support widget feedback
  22. 22. Withdrawal conversion funnel 22
  23. 23. Withdrawal sentiment 23
  24. 24. 24 The Good ● Praise for Milaap ● Easy/Convenient process ● Good step-by-step process ● Good checks and vetting process Withdrawal feedback
  25. 25. 25 To Improve ● Review time for emergencies ● Clarity on USD transfer rates ● SWIFT code searching ● Arranging for interim bills ● Update withdrawal videos Withdrawal feedback
  26. 26. 26 ● Remove the feedback option from the support widget ○ Very less conversion ○ No actionable insight ● Increase frequency of asking for feedback in the withdrawal module ○ Every withdrawal is different ○ Need more feedback To do
  27. 27. 27 Premise: Experiment Of the 4 and 5 rated feedbacks are actually negative 20% ● Undetailed ratings show bimodal distribution instead of normal ● Median is not an accurate reflection of the product quality ● Detailed ratings are biased towards the high end of the scale ● 5-pointer scale minimises differentiation Reference: http://www.lifewithalacrity.com/2006/08/using_5star_rat.html
  28. 28. 28 ● Forces users to think binary ● Provides differentiation The Experiment Replace 5- pointer rating with a binary rating system
  29. 29. 29 ● Submit the rating only when coupled with feedback ● Show user’s name while writing the feedback Other Suggestions
  30. 30. 30 Thanks! Any questions? You can find me at amit@milaap.org

×