How to be a good IT Product Manager - part 2 - talking to Developers
0 likes76 views
The document discusses the responsibilities and goals of product management, particularly in the IT sector, emphasizing collaboration and problem-solving to meet customer needs. It outlines the steps involved in understanding customer problems, validating them, and building effective solutions while stressing the importance of team dynamics and clear communication. Ultimately, it advocates for product managers to actively engage with their teams to foster successful product development and avoid common pitfalls.
How to be a good IT Product Manager - part 2 - talking to Developers
- 1. PRODUCT MANAGEMENT with focus on a few words about HOWTOTALKTO DEVELOPERS
- 3. IT EDUCATION VS PRODUCT MANAGEMENT technology coding efficiency project management
- 4. product goal customers / market process schedule team project management product management GOALS
- 5. product goal customers / market process schedule team project management product management GOALS
- 6. PRODUCT MANAGEMENT customers sales marketing the lab product manager
- 7. PRODUCT MANAGEMENT How to become an effective information hub?
- 8. PRODUCT MANAGEMENT Let’s focus onThe Lab today the lab
- 9. Why are IT jobs cool?
- 10. creativity
- 11. problem solving
- 12. technology
- 13. compensation
- 16. What are the goals of an IT company?
- 17. What are the goals of an IT company? to solve customer problems and pains to sell IT solutions to become rich
- 18. What are the goals of an IT company? to solve customer problems and pains to sell IT solutions to become rich
- 19. How are the problems solved?
- 21. #2validate problem with other sources product manager sales market
- 22. #3check if the problem can be solved product manager the lab
- 23. #4forge the solution proposal product manager
- 24. #5solution is built the lab
- 25. #6solution is validated product the lab customers
- 26. #7solution is ready the lab customers sales marketing
- 27. Easy, right?
- 29. What is a relay race?
- 30. What is a relay race?
- 31. What is a relay race? well defined connection point well defined handoff artefact team members run the race alone
- 32. What is a relay race in IT? well defined connection point well defined handoff artefact team members run the race alone project execution schedule release requirements document
- 33. What is a relay race in IT? well defined connection point well defined handoff artefact team members run the race alone oh, s#!t…. project execution schedule release requirements document
- 34. well defined connection point well defined handoff artefact team members run the race alone oh, s#!t….relay race too short forThe Lab to understand the pain not taking all the conditions into account no place for trial and error
- 35. oh, s#!t….relay race well defined connection point well defined handoff artefact team members run the race alone too short forThe Lab to understand the pain not taking all the conditions into account no place for trial and errorno collaboration
- 36. Consequences?
- 37. s#!tty motivation need for micromanagement s#!tty product Consequences?
- 38. What are the goals of an IT company? to solve customer problems and pains to sell IT solutions to become rich
- 39. What are the goals of an IT company? to solve customer problems and pains to sell IT solutions to become richFAIL
- 41. collaboration
- 44. #1collaboration on problem definition customers product manager the lab
- 45. #2validate problem with other sources product manager sales market
- 46. #2 sales market collaboration on problem definition product manager the lab
- 47. #3check if the problem can be solved product manager the lab
- 48. #3check if the problem can be solved product manager the lab
- 49. #4forge the solution proposal product manager #5build the solution the lab
- 50. #3build and evolve the solution’s shape product manager the lab
- 51. #6solution is validated product the lab customers
- 52. #4continuous validation product the lab customers
- 53. #7solution is ready the lab customers sales marketing
- 54. #5product maturity product the lab customers sales marketing
- 55. Takeaways
- 56. #1PM should be a member of The Lab product manager the lab
- 57. #2solution definition comes from allThe Lab members product manager the lab
- 58. #3PM should sit, work and participate inThe Lab’s day product manager the lab every day
- 59. #4PM is notThe Lab’s manager product manager the lab
- 60. User Story FTW!
- 61. User Story FTW! prevents the relay race imposes collaboration
- 62. so…
- 63. If you are a PM product manager work with your Lab!
- 64. If you work inThe Lab invite your PM to collaborate! the lab
- 65. If you see a relay race raise the alarm!
- 66. If that does not work find a better company to work for.
- 68. Collaboration be open be honest don’t bulls#!t anyone don’t be a smartass
- 69. THANKYOU