Product Managers = Change Managers
2 min readJan 7, 2020
Commons sense is one of the most undervalued virtues in business; hence I wrote these ideas down not to forget.
- Ideas are cheap, bringing them to reality is expensive. Change is expensive. Successful Product Manager do that effortlessly.
- “No” it’s a conversation starter. Always ask why.
- Use a strict prioritization framework, eg.: I) What’s best of the user II) What’s best for the client III) What’s best for the service provider.
- There are three metrics buckets: quality, quantity, efficiency. B2B funnel metrics are unique to each industry.
- You cannot do traditional A/B testing in enterprise software, especially with sensitive data such as finance and healthcare. Also, there are no existing frameworks (2019), and the N is too small.
- Use strategy to identify hypotheses to test. Craft as an experiment, you might not need A/B test anyway.
- People hire their own kind. There are three types of PMs: Pioneer, settler, town planner.
- Hire for Hungry, Humble, Brilliant, Resilient. Treat each candidate with a personal story for a high close rate.
- Every org is flawed: it’s all about what you want to optimize.
- Product Management can be home for multiple functions, product operations/support, economic research, or at least incubate them if you need those insights to develop the product. In large organizations, PMs are closer GMs.
- It’s easier to create Engineering Product mgmt Design teams along the user journey when the product is mature.
- Pillar of designs: Research, Content, UX, System. Design reporting into product dev/management minimizes potential for parallel roadmaps.
- Quant research identify problems, qual research solutions
- Spend 20% of your time with customers/using the product/insight gathering.
- Ongoing product refinement/support is like operating the Toyota optimization process.
- The saddest thing for PMs is not have enough engineers: don’t overhire PMs.
- PM’s work is never done.
All views are my own.