Confessions of a product manager
•
2 likes•593 views
My top mistakes as a product manager which I learnt from.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Confessions of a product manager
Similar to Confessions of a product manager (20)
Recently uploaded
Recently uploaded (20)
Confessions of a product manager
- 1. CONFESSIONS OF A PRODUCT MANAGER FAILING IS EASY, MOVING ON IS HARD
- 3. INSPIRATION FOR PRODUCT X CASE STUDY 1:
- 5. INSPIRATION FOR PRODUCT X KAIZEN
- 6. INSPIRATION FOR PRODUCT X TEAM DYNAMICS
- 7. INSPIRATION FOR PRODUCT X MY SCRUM ROLES 2008 - 2011 2011 - 2012 2012 - 2015
- 8. GETTING LOST IN THE SOLUTION CONFESSION 1
- 9. GETTING LOST IN THE SOLUTION FRICTION
- 10. GETTING LOST IN THE SOLUTION START WITH WHAT
- 11. GETTING LOST IN THE SOLUTION START WITH WHY
- 12. START WITH WHAT VISION STATEMENT ▸ Product X is an integration platform, bringing information from different systems.
- 13. START WITH WHY VISION STATEMENT ▸ I believe in delivering great messages to my audience in their language. ▸ You can achieve this by increasing the quality of your content, keeping to your company style guides and branding, increase reuse and bringing information to your authors. ▸ Product X is a tool for your authors that connects your language tools, content repositories and terminology systems together to increase the quality of your content.
- 14. START WITH WHAT USER STORY ▸ As an editor, I want to create profiles for quality rules, so that I can group my rules.
- 15. START WITH WHY USER STORY ▸ As an editor, in order to adapt to different requirements of my teams, I want each team to have their own set of quality rules.
- 16. START WITH WHAT TECHNICAL TASK ▸ Abstract the data layer for other data sources.
- 17. START WITH WHY TECHNICAL TASK ▸ Why? We cannot force customers to switch databases. Migration of data is expensive and time consuming. ▸ How? Abstract the data layer making it easier to support new database providers. ▸ What? Support SQL Server and MySQL.
- 18. FOCUS ON THE PROBLEM LESSON LEARNT 1
- 19. FOCUS ON BUILDING THE RIGHT THING CONFESSION 2
- 20. Build it fast Build the right thing Build the thing right Sweet Spot
- 21. Build it fast (SM) Build the right thing (PO) Build the thing right (Team) Sweet Spot
- 22. Build it fast (SM) Build the right thing (PO) Build the thing right (Team) Conflict
- 23. Build it fast Build the right thing Build the thing right Everyone’s Responsibility
- 24. STRIVE FOR QUALITY LESSON LEARNT 2
- 25. TROUBLE AT PRODUCT Y CASE STUDY 2:
- 27. PAIN IS A SIGN OF LIFE Luis Muñoz - Being Luis MY FATHER’S LESSON
- 28. A PRODUCT IS ABOUT FEATURES, FEATURES AND FEATURES CONFESSION 3
- 29. PRODUCT Y SCRUM… BUT… ▸ PO is a messenger ▸ No feedback from team ▸ No technical debt payback
- 30. PRODUCT Y ROADMAP Q1 Q2 Q3 FEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5 FEATURE 6 FEATURE 7 FEATURE 8 FEATURE 9 FEATURE 10 FEATURE 11 FEATURE 12
- 31. PRODUCT Y ROADMAP IN Q2 Q1 Q2 Q3 FEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5 FEATURE 6 FEATURE 7 FEATURE 8 FEATURE 9
- 34. PRODUCT Y NEW ROADMAP Committed Projected Envisioned CUSTOMER PROBLEM AND SOLUTION CUSTOMER PROBLEM AND SOLUTION 2 CUSTOMER PROBLEM 3 CUSTOMER PROBLEM 4 CUSTOMER PROBLEM 5
- 35. LISTEN TO YOUR USERS, CUSTOMERS AND YOUR TEAM LESSON LEARNT 3
- 36. GETTING LOST IN THE SOLUTION… AGAIN CONFESSION 4
- 37. PRODUCT Y WHEN DO WE DECIDE WHAT TO BUILD?
- 38. PRODUCT Y WHEN DO WE DECIDE WHAT TO BUILD? Too Late
- 39. PRODUCT Y WHEN DO WE DECIDE WHAT TO BUILD? Refinement
- 41. THREE AMIGOS BENEFITS ▸ Single language ▸ Majority of team involved ▸ More effective stories
- 42. PRODUCT Y WHEN DO WE DECIDE WHAT TO BUILD? Too Late Refineme
- 43. DEATHLY HALLOWS DISCOVER WHAT TO BUILD Discovery Refineme Requests Ideas/Solutions
- 44. PRODUCT OWNER BENEFITS OF DISCOVERY ▸ Driven by problems ▸ Saying “No” ▸ PO has control
- 45. DEATHLY HALLOWS BENEFITS OF DISCOVERY ▸ Joint effort to create solution that is: ▸ Valuable ▸ Usable ▸ Feasible ▸ Just in time ideation ▸ Saying “No”
- 46. SOLUTIONS ARE THE RESPONSIBILITY OF THE TEAM LESSON LEARNT 4
- 47. VISION AND STRATEGY OF PRODUCT Y CASE STUDY 3:
- 48. DAYS OLD NO FEAR
- 58. MANAGING A PRODUCT WITHOUT A STRATEGY CONFESSION 5
- 59. NO STRATEGY PRIORITIES CHANGED VERY OFTEN
- 61. “PRIORITISING A FEATURE WITHOUT A STRATEGY IS LIKE PLANNING A JOURNEY WITHOUT A DESTINATION” MIND THE PRODUCT BLOG NO STRATEGY
- 62. “DELIVER SEAMLESS EXPERIENCES ACROSS ALL TOUCH POINTS” Gino Toro SINGLE VISION
- 63. SINGLE VISION DELIVER SEAMLESS MEDIA EXPERIENCES ACROSS ALL TOUCH POINTS ▸ Who are we selling to? ▸ What do they need? ▸ What can the product offer them? ▸ What value will they have?
- 64. STRATEGY SWOT ANALYSIS ▸ Strengths ▸ Weaknesses ▸ Opportunities ▸ Threats
- 65. STRATEGY 5 BASIC QUESTIONS ▸ Where are we now? ▸ Where do we want to be? ▸ What is stopping us getting there? ▸ What can help us get there? ▸ How can we change?
- 68. GETTING LOST IN THE SOLUTION… MISERABLY CONFESSION 6
- 69. CONTINUOUS DELIVERY TOO MANY REQUESTS TOO LITTLE TIME Discovery Refineme Requests Ideas/Solutions
- 70. CONTINUOUS DELIVERY THEME BASED IMPACT MAPPING Discovery Refineme Requests Ideas/Solutions THEME 1 THEME 2 THEME 3 Consolidate
- 72. IMPACT MAPPING MAKE AN IMPACT
- 73. IMPACT MAPPING WHY? SAVE TIME IN SEARCHING FOR CONTENT
- 74. IMPACT MAPPING METRICS? TIME TO SEARCH FAILED SEARCHES SAVE TIME IN SEARCHING FOR CONTENT
- 75. IMPACT MAPPING WHO? CONTENT EDITOR PROGRAM MANAGER SAVE TIME IN SEARCHING FOR CONTENT
- 77. IMPACT MAPPING WHAT? FILTERS SMALL REPOSITORIES FACETED FILTERS ASSIGNED TO ME PERSONAL SPACE TEAM SPACE
- 79. THERE IS ALWAYS A LESSON TO BE LEARNT LESSON LEARNT 6
- 80. THE PRODUCT MANAGER LESSON LEARNT
- 81. “SUCCESS IS NOT FINAL, FAILURE IS NOT FATAL; IT IS THE COURAGE TO CONTINUE THAT COUNTS.” Sir Winston Churchill THE PRODUCT MANAGER
- 82. Technology (DevOps) Business (Sales, Customers) Users (Users, Support, Design) Product Management
- 84. UNDERSTAND THE BUSINESS! EMBRACE THE TECHNOLOGY! LISTEN TO THE PEOPLE!