Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (13)
Similar a Optimizing Product Management
Similar a Optimizing Product Management (20)
Más de Silicon Valley ProductCamp
Más de Silicon Valley ProductCamp (12)
Último
Último (20)
Optimizing Product Management
- 1. Optimizing Product Management Phil Burton Principal Consultant and Trainer, 280 Group The Product Marketing & Product Management Experts™ Consulting Contractors Training Certification Templates Books Recruiting www.280group.com Slides available at www.280group.com/optimize.pdf ©2011 280 Group LLC. All rights reserved. 1
- 2. Agenda • About • People • Process • Tools • Making it stick • Q&A • Drawing! ©2011 280 Group LLC. All rights reserved. 2
- 3. Drawing! Product Management Lifecycle Toolkit ©2011 280 Group LLC. All rights reserved. 3
- 4. The Product Marketing & Product Management Experts™ Consulting Contractors Training Certification Templates Books Recruiting ©2011 280 Group LLC. All rights reserved. 4
- 5. Optimal Product Management™ • Phase I: Assessment • Phase II: Training & Education • Phase III: Coaching, Mentoring & Seminars • Phase IV: Add’l certifications, portal, handbook Phase Phase Phase Phase I II III IV ©2011 280 Group LLC. All rights reserved. 5
- 6. Optimal Product Management People Learning Process Feedback Tools ©2011 280 Group LLC. All rights reserved. 6
- 7. People • Clarify roles • Right people • Baseline skill set ©2011 280 Group LLC. All rights reserved. 7
- 8. Roles and responsibilities ©2011 280 Group LLC. All rights reserved. 8
- 9. Roles and responsibilities Director of Product Management Portfolio Planning Strategic planning resource allocation PLC strategy pricing strategy competitive analysis (company & financial level) Product Management Product Marketing Inbound Outbound • Customer research and insights • Launch and marketing plans • Business case analysis • Features and benefits • Positioning • Messaging by market and role • Product Road mapping • Training • Market req. & prioritization • Sales tools • Whole product definition • Product Launch • Differentiation and desirability • Marketing program • Feature/cost/schedule tradeoffs • Success stories • Develop product req. w/ eng. & UX • Market analysis • Competitive analysis • Competitive analysis (product and market position) (price, promotion, and place) • Beta programs Product Management vs. Product Marketing White Paper: www.280group.com resources section ©2011 280 Group LLC. All rights reserved. 9
- 10. Right Person for the Job • Skills • Interest • Team fit • Needs ©2011 280 Group LLC. All rights reserved. 10
- 11. Baseline Skill Set • Match responsibilities • Communicate expectations • Training • Coach/Mentor • Reading • Quarterly review ©2011 280 Group LLC. All rights reserved. 11
- 12. Process • Can be a dirty word • Benefits • Not the end goal • “Lightweight” as possible • “Context” dependent • Buy-In Lightweight Product Process White Paper: www.280group.com resources section ©2011 280 Group LLC. All rights reserved. 12
- 13. Process: Context • Team • Size and maturity • Commitment • Dependencies • Development method Startups Large companies Founder-driven Dependencies Sales/Eng-driven Bureaucratic “Lucky” No process (chaos) Lightweight More formal All process (no work done) ©2011 280 Group LLC. All rights reserved. 13
- 14. Lightweight ©2011 280 Group LLC. All rights reserved. 14
- 15. More Formal © 2005-2011, Blackblot ©2011 280 Group LLC. All rights reserved. 15
- 16. What About Agile? • Still need other phases • Development phase changes • Even more critical • Get CLEAR on rules ©2011 280 Group LLC. All rights reserved. 16
- 17. Assessing Process • Identify the process(es) being used • Get clear on context • Compare against best practices • Identify strengths/weaknesses • Eliminate inefficiencies • Bolster weak areas ©2011 280 Group LLC. All rights reserved. 17
- 18. Tools • Map to the process • Productivity • Leverage • Consistency • Appropriate for “Context” – Templates – Software – “Just enough” ©2011 280 Group LLC. All rights reserved. 18
- 19. Product Manager’s Manual ©2011 280 Group LLC. All rights reserved. 19
- 20. Product Management Portal ©2011 280 Group LLC. All rights reserved. 20
- 21. Making it stick • Develop plan – Charter – Roles – Process – Tools • Management support • Communicate to peers • Be a broken record • Tie into reviews • Carrots & sticks • Quarterly PM summit • Sharpen the saw Product Management Manifesto: www.280group.com resources section ©2011 280 Group LLC. All rights reserved. 21
- 22. 280 Group Resources • Free templates • White papers • Product Management Manifesto • 280 Group Product Management 2.0 Newsletter • 280 LinkedIn Group • PM job hunting/listings • Product Management 2.0 Blog • 280 Group Press books Go to www.280group.com in the “Resources” section. 22 ©2011 280 Group LLC. All rights reserved. 22
- 23. Q&A brian@280group.com (408) 834-7518 Slides available at www.280group.com/optimize.pdf ©2011 280 Group LLC. All rights reserved. 23
- 24. Drawing! ©2011 280 Group LLC. All rights reserved. 24
Notas del editor
- Director of PM will prioritize markets and segmentsPM – understand customer needs and develop business cases for solving customer problems at the product levelPMM – understand features and benefits and how those tie to customer problem"marketing programs" means PR, advertising, direct, website, events, etc. -- the whole marketing mixWhoe Product Definition deals with the actual product, the packaging and out of box experience, and all necessary supporting srervices (such as support, accessoriesAs with anything that tries to assign tasks with roles, this is not set in stone. The goal is to list the most logical owner, but every company needs to determine how to split these tasks based on skill sets of its employees and where in the lifecycle a product is. So I think any framework comes with caveats.As far as the location of “markets” at the top and “customers” at the bottom. The Dir., PM, and PMM must understand both, but I was trying to suggest the Dir. Concerns themselves more with markets. Which markets and market segments to be in, which are growing, which are shrinking, which are changing, do we grow by taking our product to a new market or by creating new products for an existing market? The PM and PMMs are working very closely with customers and finding shared problems that make a market. But they start bottoms up and the dir, starts tops down. Let me know if this is lost or confusing.I think the side bars are clearer, but let me know. But the main internal interface for PM is development and the main internal interface for PMM is basically every other department. I’ve kept “inbound” and “outbound.” I’ve always found this notation helpful. It is not to say the boundaries are firm between all parties, but that primary inbound responsibility is the PM and primary outbound is the PMM. For me, inbound is what I call listening activities. Those things that feed into the product until it is built. Outbound is a broadcasting activity letting the world know about the product and stepping the target market through the awareness, consideration, trial, purchase, and evangelism cycle. However, I’d like to hear more thoughts on this. I think barbara and Jim makes some good points, there are some inconsistencies and is this label actionable? Is there a better label? Should there be no label?Pricing – I kept that with the director. I agree the PM needs to have input into it and target price is a design input. But if someone has to own it, I think it is the director. I have not added the term VOC but have the idea. Let me know you think VOC should be there.I’ve added competitive analysis to all three roles (Dir = company and financial analysis), (PM=product analysis), (PMM = price, promotion, and place analysis). Does this make sense?I was using the term “market requirement” and “PRD” which was inconsistent. I know use “market requirement” and “product requirement”. FYI – aim is introducing “customer requirement” which is the idea that each person has their requirements. When enough share the same thing it is a market requirement. s, warranty, value added services.)
- Director of PM will prioritize markets and segmentsPM – understand customer needs and develop business cases for solving customer problems at the product levelPMM – understand features and benefits and how those tie to customer problem"marketing programs" means PR, advertising, direct, website, events, etc. -- the whole marketing mixWhoa Product Definition deals with the actual product, the packaging and out of box experience, and all necessary supporting services (such as support, accessoriesAs with anything that tries to assign tasks with roles, this is not set in stone. The goal is to list the most logical owner, but every company needs to determine how to split these tasks based on skill sets of its employees and where in the lifecycle a product is. So I think any framework comes with caveats.As far as the location of “markets” at the top and “customers” at the bottom. The Dir., PM, and PMM must understand both, but I was trying to suggest the Dir. Concerns themselves more with markets. Which markets and market segments to be in, which are growing, which are shrinking, which are changing, do we grow by taking our product to a new market or by creating new products for an existing market? The PM and PMMs are working very closely with customers and finding shared problems that make a market. But they start bottoms up and the dir, starts tops down. Let me know if this is lost or confusing.I think the side bars are clearer, but let me know. But the main internal interface for PM is development and the main internal interface for PMM is basically every other department. I’ve kept “inbound” and “outbound.” I’ve always found this notation helpful. It is not to say the boundaries are firm between all parties, but that primary inbound responsibility is the PM and primary outbound is the PMM. For me, inbound is what I call listening activities. Those things that feed into the product until it is built. Outbound is a broadcasting activity letting the world know about the product and stepping the target market through the awareness, consideration, trial, purchase, and evangelism cycle. However, I’d like to hear more thoughts on this. I think barbara and jim makes some good points, there are some inconsistencies and is this label actionable? Is there a better label? Should there be no label?Pricing – I kept that with the director. I agree the PM needs to have input into it and target price is a design input. But if someone has to own it, I think it is the director. I have not added the term VOC but have the idea. Let me know you think VOC should be there.I’ve added competitive analysis to all three roles (Dir = company and financial analysis), (PM=product analysis), (PMM = price, promotion, and place analysis). Does this make sense?I was using the term “market requirement” and “PRD” which was inconsistent. I know use “market requirement” and “product requirement”. FYI – aipmm is introducing “customer requirement” which is the idea that each person has their requirements. When enough share the same thing it is a market requirement. s, warranty, value added services.)
- Director of PM will prioritize markets and segmentsPM – understand customer needs and develop business cases for solving customer problems at the product levelPMM – understand features and benefits and how those tie to customer problem"marketing programs" means PR, advertising, direct, website, events, etc. -- the whole marketing mixWhoe Product Definition deals with the actual product, the packaging and out of box experience, and all necessary supporting srervices (such as support, accessorieAs with anything that tries to assign tasks with roles, this is not set in stone. The goal is to list the most logical owner, but every company needs to determine how to split these tasks based on skill sets of its employees and where in the lifecycle a product is. So I think any framework comes with caveats.As far as the location of “markets” at the top and “customers” at the bottom. The Dir., PM, and PMM must understand both, but I was trying to suggest the Dir. Concerns themselves more with markets. Which markets and market segments to be in, which are growing, which are shrinking, which are changing, do we grow by taking our product to a new market or by creating new products for an existing market? The PM and PMMs are working very closely with customers and finding shared problems that make a market. But they start bottoms up and the dir, starts tops down. Let me know if this is lost or confusing.I think the side bars are clearer, but let me know. But the main internal interface for PM is development and the main internal interface for PMM is basically every other department. I’ve kept “inbound” and “outbound.” I’ve always found this notation helpful. It is not to say the boundaries are firm between all parties, but that primary inbound responsibility is the PM and primary outbound is the PMM. For me, inbound is what I call listening activities. Those things that feed into the product until it is built. Outbound is a broadcasting activity letting the world know about the product and stepping the target market through the awareness, consideration, trial, purchase, and evangelism cycle. However, I’d like to hear more thoughts on this. I think barbara and jim makes some good points, there are some inconsistencies and is this label actionable? Is there a better label? Should there be no label?Pricing – I kept that with the director. I agree the PM needs to have input into it and target price is a design input. But if someone has to own it, I think it is the director. I have not added the term VOC but have the idea. Let me know you think VOC should be there.I’ve added competitive analysis to all three roles (Dir = company and financial analysis), (PM=product analysis), (PMM = price, promotion, and place analysis). Does this make sense?I was using the term “market requirement” and “PRD” which was inconsistent. I know use “market requirement” and “product requirement”. FYI – aipmm is introducing “customer requirement” which is the idea that each person has their requirements. When enough share the same thing it is a market requirement. s, warranty, value added services.)
- Director of PM will prioritize markets and segmentsPM – understand customer needs and develop business cases for solving customer problems at the product levelPMM – understand features and benefits and how those tie to customer problem"marketing programs" means PR, advertising, direct, website, events, etc. -- the whole marketing mixWhoe Product Definition deals with the actual product, the packaging and out of box experience, and all necessary supporting srervices (such as support, accessorieAs with anything that tries to assign tasks with roles, this is not set in stone. The goal is to list the most logical owner, but every company needs to determine how to split these tasks based on skill sets of its employees and where in the lifecycle a product is. So I think any framework comes with caveats.As far as the location of “markets” at the top and “customers” at the bottom. The Dir., PM, and PMM must understand both, but I was trying to suggest the Dir. Concerns themselves more with markets. Which markets and market segments to be in, which are growing, which are shrinking, which are changing, do we grow by taking our product to a new market or by creating new products for an existing market? The PM and PMMs are working very closely with customers and finding shared problems that make a market. But they start bottoms up and the dir, starts tops down. Let me know if this is lost or confusing.I think the side bars are clearer, but let me know. But the main internal interface for PM is development and the main internal interface for PMM is basically every other department. I’ve kept “inbound” and “outbound.” I’ve always found this notation helpful. It is not to say the boundaries are firm between all parties, but that primary inbound responsibility is the PM and primary outbound is the PMM. For me, inbound is what I call listening activities. Those things that feed into the product until it is built. Outbound is a broadcasting activity letting the world know about the product and stepping the target market through the awareness, consideration, trial, purchase, and evangelism cycle. However, I’d like to hear more thoughts on this. I think barbara and jim makes some good points, there are some inconsistencies and is this label actionable? Is there a better label? Should there be no label?Pricing – I kept that with the director. I agree the PM needs to have input into it and target price is a design input. But if someone has to own it, I think it is the director. I have not added the term VOC but have the idea. Let me know you think VOC should be there.I’ve added competitive analysis to all three roles (Dir = company and financial analysis), (PM=product analysis), (PMM = price, promotion, and place analysis). Does this make sense?I was using the term “market requirement” and “PRD” which was inconsistent. I know use “market requirement” and “product requirement”. FYI – aipmm is introducing “customer requirement” which is the idea that each person has their requirements. When enough share the same thing it is a market requirement. s, warranty, value added services.)