Publicité

Webinar on "What we should know to Ask" The Art of Product management

Agile Transformation Minds (ATM)
8 Jul 2017
Publicité

Contenu connexe

Présentations pour vous(20)

Publicité

Webinar on "What we should know to Ask" The Art of Product management

  1. Anubhav Sinha | Product Owner | Agile Learner via
  2. Anubhav Sinha | Product Owner | Agile Learner and Doer What we should know to ASK! Date: July 08, 2017 via
  3. “Success is not a doorway, it’s a staircase” - Dottie Walters
  4. Brief about me
  5. Brief about me
  6. How this webinar is Designed:
  7. How this webinar is Designed: *All information shared are learning, views, and experience gained by the speaker. Please feel free to have interactive question session or can be done as per time or may be later using google drive or whatsapp group mode etc. ❏ Not to talk about Agile Scrum or talk about any agile canopy ❏ Not to talk about ‘how’ as we all know and practice well in real time engagements ❏ to get info about - WHAT TO ASK ❏ Flow of talk will help audience to correlate with HOW for their working engagement ❏ Correlate with B2B and B2C model ❏ Product management refers to Software Product Management
  8. Flow of the slide deck
  9. Flow of the slide deck History Brief How we see Product Management? What exactly PM is about How we sail our journey Measures to reach 1 2 3 4 5
  10. Presentation Overview Brief via
  11. Presentation Overview Brief Our webinar will help us to reach !!
  12. Brief we will quickly walk through this section
  13. History of Product Management
  14. History of Product Management 1980s - new thoughts 1990s - new concepts
  15. Before we move ahead, let’s have a look on history of product development
  16. History and Evolution 1930 Until 1920s:
  17. History and Evolution Inventors and Geniuses Developed Products, they had product and vision with TRIAL & ERROR experiments In this era, mainly innovations and product development where by Individual Contribution only Most products were not driven by consumer needs 1930 Until 1920s:
  18. History and Evolution Until 1920s: In this era, mainly innovations and product development where by Individual Contribution only Most products were not driven by consumer needs 1930 P&G started focusing on Product Market issues and root causes, implement awareness to RCs and identify solutions Inventors and Geniuses Developed Products, they had product and vision with TRIAL & ERROR experiments
  19. History and Evolution Until 1920s: Inventors and Geniuses Developed Products, they had product and vision with TRIAL & ERROR experiments In this era, mainly innovations and product development where by Individual Contribution only Most products were not driven by consumer needs 1930 In 1930s, First Time, new business Technique “Brand Management” was created P&G started focusing on Product Market issues and root causes, implement awareness to RCs and identify solutions
  20. History of Product Management ❏ In 1980s: Intuit started to use field studies
  21. History of Product Management ❏ In 1980s: Intuit started to use field studies A Financial Software company founded by Scott Cook, a former P&G PR employee, whose prior work at Procter & Gamble helped him realize that personal computers would lend themselves towards replacements for paper-and-pencil based personal accounting.
  22. History of Product Management ❏ In 1980s: Intuit started to use field studies A Financial Software company founded by Scott Cook, a former P&G PR employee, whose prior work at Procter & Gamble helped him realize that personal computers would lend themselves towards replacements for paper-and-pencil based personal accounting. Intuit was one of the earliest company to apply Brand Management in a software hi-tech company
  23. History of Product Management ❏ In 1990s: An article published by ‘Regis McKeena’, a consultant wrote an article “Marketing is Everything” in the year 1991, said that a Marketing Person must be an integrator
  24. History of Product Management ❏ In 1990s: An article published by ‘Regis McKeena’, a consultant wrote an article “Marketing is Everything” in the year 1991, said that a Marketing Person must be an integrator ❏ In 1990s: The role of product manager emerged to integrate Business, Customer and Technical know-how. a Technology and Marketing consultant
  25. History of Product Management ❏ In 1990s: Finding the ‘Product Market Fit’ was envisioned and identified by ‘Regis McKeena’
  26. History of Product Management ❏ In 1990s: Finding the ‘Product Market Fit’ was envisioned and identified by ‘Regis McKeena’ ❏ In 1991: concept came - Work with Customer, New Product Development, Production Team and identify new market segment
  27. History of Product Management ❏ In 1990s: Finding the ‘Product Market Fit’ was envisioned and identified by ‘Regis McKeena’ ❏ In 1991: concept came - Work with Customer, New Product Development, Production Team and identify new market segment ❏ First time - Customers and Partners was introduced to work for Sales & Profits
  28. Let’s Consolidate
  29. Let’s Consolidate ❏ Historically, Product management were done by Inventors and Geniuses ❏ Later, due to Technology complexity and competition, product development became more focused and organized ❏ Companies were forced to better understand ‘what a customer need is’ ❏ P&G was the 1st company to work with problem, market need, perform RCA to improvise product and take corrective actions ❏ 1980s - Intuit was the first financial tech company to work with field studies ❏ In 1990s - Product Market Fit, Work with customers and Partners comes in frame
  30. Let’s see now on Product Management via
  31. What is Product Management An organizational function within a company dealing with the planning, forecasting, and production or marketing of a products at all stages of the product life cycle.
  32. One side of the coin Another side of the coin
  33. Let’s now look for what part
  34. 2 Sides of Coin in Product Management
  35. 2 sides of the same coin
  36. 2 sides of the same coin ❏ Innovation starts with discovery ❏ Ideation comes only after the problem or opportunity is well understood ❏ Experimentation to be cost effective and quick ❏ It’s a series of divergence and convergence steps ❏ It’s an Iterative process Innovation Process Model
  37. 2 sides of the same coin
  38. A Product Flow Cycle via
  39. Let’s see Whose Area & Who does WHAT via
  40. Whose AREA !
  41. Who does WHAT !
  42. We have identified our area of talk which will assist us to identify How n WHAT for real engagements
  43. Let’s start to understand Tools, Techniques and Best Approach for product management via
  44. The Golden Circle
  45. The Golden Circle
  46. The Golden Circle
  47. What we extract out of Golden Circle
  48. What we extract out of Golden Circle
  49. As example -
  50. Let’s see Product Management Framework via
  51. 1 2
  52. Let’s visualize Product Management using Iceberg
  53. Let’s understand Business Model Inception via
  54. Business Model Inception
  55. Business Model Inception
  56. Business Model Inception (B2C)
  57. Business Model Inception (B2C)
  58. Business Model Inception (B2B2C)
  59. Business Model Inception (B2B2C)
  60. Business Model Inception (B2B)
  61. What we do in Product Discovery Workshops
  62. Product Discovery Participants
  63. What (refer to golden circle) pitch to get Why? (refer to Golden Circle)
  64. we miss to focus on other area as - problem, users, needs, and flow should be outwards
  65. Let’s focus on other area as - problem, users, needs, and flow should be outwards
  66. What we try to get out !
  67. What we try to get out ! Understanding, need, want
  68. Identify High Level Thoughts !
  69. Sample way - identify Target Segment
  70. What is Value Proposition Describe the benefits customers can expect from your products or services.
  71. How we can identify Value Proposition
  72. How we can identify Value Proposition
  73. How we can identify Value Proposition
  74. How we can identify Value Proposition
  75. Let’s see how to identify Product Vision via
  76. Product Vision Canvas
  77. Derived Product Vision
  78. SWOT Analysis
  79. SWOT Analysis
  80. SWOT Analysis
  81. SWOT Analysis - Buddy
  82. Persona Creation via
  83. Paper conceptualization Low fidelity Prototype High Fidelity prototype Mock-up Wireframes
  84. What does Persona include !
  85. Example - Who is the customer of a children book?
  86. Let’s take an example of B2B Enterprise Product
  87. Let’s take an example of B2C and B2B2C Product Development
  88. OYO ROOMS Persona
  89. OYO ROOMS (as product) Persona Different Users Different Platforms Different business model
  90. ZOHO
  91. ZOHO - User Persona Different Product Line Different Platforms Different business model Different User and Personas
  92. Flipkart - B2C model
  93. Flipkart - B2C model Online Platform is a B2C portal which provides shopping experience-opportunities to the Indian consumers ○ Flipkart website ○ The web app ○ The mobile app ○ Social websites ○ Affiliated networks like review websites, coupon websites, bloggers, etc. The various options for selling and buying through Flipkart are through:
  94. How we define and work to identify User Persona
  95. We should start with 3-5 User Persona
  96. How we build Persona
  97. How we build Persona
  98. How we build Persona
  99. How we build Persona
  100. How we build Persona
  101. How we build Persona
  102. Let’s have a look on floating jargons MVP, MVE, MVF, MLP
  103. What is MVP Wikipedia says “In product development, the Minimum Viable Product (MVP) is a product with just enough features to satisfy early customers and to receive feedback about the product and its continued development.”
  104. What is MVP “We have $5 million in funding and we have one try to get it right! How can you guarantee we won’t fail? Well, figuring out a Minimum Viable Product (MVP) is a great place to start. But how do we create a good MVP? And why MVPs? What “Viable” Means
  105. What is MVP
  106. what has to be for Minimum Viable
  107. What has to be for MVP
  108. What has to be for MVP
  109. on a personal note and exp. MVP is dead now we have MVE
  110. What is MVE The minimum viable experience (MVE) is a product which has complete customer journeys.It is task orientated and enables customers to start and complete a full process.
  111. What is MVE The minimum viable experience (MVE) is a product which has complete customer journeys. It is task orientated and enables customers to start and complete a full process.
  112. What is MVE The minimum viable experience (MVE) is a product which has complete customer journeys. It is task orientated and enables customers to start and complete a full process. A problem has been identified and a basic way is done to solve current problem with early entry, learning and validation MVP is already present, but we need a complete customer journey, as to-n-fro along with more needs
  113. what is MVF
  114. what is MLP
  115. what is MLP We will keep this ‘on-hold’
  116. Let’s have a look on Prioritization Techniques
  117. Prioritization Techniques
  118. Prioritization Techniques
  119. Prioritization Techniques
  120. Kano Model Kano Model, a paper was published and introduced in 1984, by Noriaki Kano, with a set of ideas and techniques that help us determine our customers (and prospects) satisfaction with product features.
  121. Kano Model Kano Model, a paper was published and introduced in 1984, by Noriaki Kano, with a set of ideas and techniques that help us determine our customers (and prospects) satisfaction with product features.
  122. Kano Model Must be: product features are simply expected by customers. If the product doesn’t have them, it will be considered to be incomplete or just plain bad. This type of features is usually called Must-be or Basic Expectations. Performance: product features behave as what we might intuitively think that Satisfaction works: the more we provide, the more satisfied our customers become. Attractive: There are unexpected features which, when presented, cause a positive reaction. These are usually called Attractive / Exciters / Delighters. These falls for MLP. Indifferent: Those features whose presence (or absence) doesn’t make a real difference in our reaction towards the product.
  123. Kano Model Must be: product features are simply expected by customers. If the product doesn’t have them, it will be considered to be incomplete or just plain bad. This type of features is usually called Must-be or Basic Expectations. Performance: product features behave as what we might intuitively think that Satisfaction works: the more we provide, the more satisfied our customers become. Attractive: There are unexpected features which, when presented, cause a positive reaction. These are usually called Attractive / Exciters / Delighters. These falls for MLP. Indifferent: Those features whose presence (or absence) doesn’t make a real difference in our reaction towards the product. examples - Confluence survey, Jira Survey,LinkedIn Survey, OLA survey, OLA survey at trip end etc.
  124. User Story Mapping
  125. MoSCoW Prioritization
  126. MoSCoW Prioritization
  127. Prune the Product Tree
  128. Prune the Product Tree https://www.prodpad.com/blog/product-tree-game/
  129. Scorecard
  130. Scorecard Goal is to prioritize feature over a set of criteria that have been negotiated with stakeholders and keep evolving. ❏ Start with a clear strategy that has been validated by user ❏ Select the features that are most relevant and related to overall vision-strategy ❏ Define a criteria and weights for scoring (keep evolving) ❏ Meet with stakeholders and fine tune criteria and weights
  131. Classification Ranking Feature Category Rank Total The process is simple: each feature is classified into some category, and then a ranking is produced. Categories must be sortable in some way, e.g. 1-2-3-4-5, High-Medium-Low.
  132. Feature Bucket The Feature Buckets technique by Adam Nash is also very popular. Adam believes that feature prioritization varies a lot across different product types and industries and that’s why he emphasizes that this technique was thought specifically for consumer internet products.
  133. Feature Bucket The Feature Buckets technique by Adam Nash is also very popular. Adam believes that feature prioritization varies a lot across different product types and industries and that’s why he emphasizes that this technique was thought specifically for consumer internet products. Metric Movers Customer Requests Delights Strategic
  134. Feature Bucket The Feature Buckets technique by Adam Nash is also very popular. Adam believes that feature prioritization varies a lot across different product types and industries and that’s why he emphasizes that this technique was thought specifically for consumer internet products. Metric Movers Customer Requests Delights Strategic Features that are included for strategic reasons These are features that have been requested directly by customers. They are usually incremental enhancements, but it’s important to consider them. Features that will move the target business and product metrics significantly. ex - AARRR Innovative features that are internally generated based on insights in design or technology. (refer to Kano model)
  135. Funnel Prioritization
  136. Key Takeaways
  137. Key Takeaways ❏ Prioritize at High Level ❏ Set goals, measure and adjust ❏ Don’t do it alone ❏ Quantitative vs. Qualitative ❏ External vs. Internal
  138. Key Takeaways ❏ Prioritize at High Level ❏ Set goals, measure and adjust ❏ Don’t do it alone ❏ Quantitative vs. Qualitative ❏ External vs. Internal scale goes something like this: You < Team < Stakeholders < Customers < Business Know what you’re getting out of the method and when to use it. These things are tools, not oracles. Prioritization should not be a solo effort. The objective is not to set priorities and ship them. The objective is to constantly be aware if what we’re doing is really adding value and working out as expected; when it’s not, we will at least have some clues as to what needs adjustment. all prioritization methods work with high-level features (themes) and user goals
  139. Let’s have a look on metrics What we want to measure !
  140. What to measure - B2B
  141. What to measure - B2B ❏ Time to activation - How long does it take for end-users to start using your solution ❏ Frequency of use - How often do they use the solution? Are there period of high activity ❏ Length of use - How much time do they spend using the solution? Are used logged in for full day? ❏ Task of completion - what is the main task, is it completed or not? How easy is it to completed the other task? ❏ Support Request - How many email requests, support request, new feature request received? How many support calls generated? Does it vary by user group? ❏ Feature Request w.r.t. business needs - internal or external request ❏ Availability - is solution available for all time? ❏ Feature usage - Are there features that are not being used (refer to 1st slide with remote)
  142. What to measure - B2C Marketing Customer Success and Product Engagement Business Success
  143. Are we measuring right things? ❏ Monthly Unique visitors ❏ CAQ (customer acq. cost) ❏ Organic Traffic vs. Paid Traffic ❏ Product Usage / adoption (sign-in freq, sharing etc.) ❏ % of users who perform similar actions ❏ % of users who perform specific actions ❏ Feature usage (usage vs. other features) ❏ Retention rate ❏ Quality (defects, iWish) ❏ Support ticket vs. closed ❏ Active users ❏ LTV (lifetime value) ❏ MRR (monthly recurring revenue) ❏ ARR (annual recurring revenue) ❏ ARU (average revenue per user) ❏ Conversion (site lead to conversion) ❏ ACV (annual contract value), ex - amazon-prime Marketing Customer Success and Product Engagement Business Success
  144. Are we measuring right things?
  145. Let’s have a look on
  146. How to identify MLP
  147. How to identify MLP work with The Golden Circle approach roll-out to market
  148. How to identify MLP work with The Golden Circle approach roll-out to market
  149. What Amazon Gained ! c c c
  150. Let’s view Learning and Trend What more we can measure !
  151. What more can be measured?
  152. What more can be measured?
  153. ‘Measure your PRODUCT PERFORMANCE, not your product management’
  154. “In a boxing game, Defeat is not declared when one fall down, it’s declared only when One fails to get up” - No one can defeat oneself, except himself / herself ! Conclude thought:
Publicité