What It Is
The practice of strategically driving product development, from conception through launch and iteration. Product Managers (PMs) are the “CEO of the product”—though without direct authority over engineers.
Core Responsibilities
Strategy:
- Define product vision and roadmap
- Prioritize features
- Understand market and competition
- Set success metrics (OKRs/KPIs)
- Make build/buy/partner decisions
Execution:
- Write product requirements (PRDs)
- Work with engineering on feasibility
- Coordinate with design on UX
- Manage stakeholder expectations
- Make trade-off decisions
Customer Understanding:
- User research and interviews
- Analyze usage data
- Gather feedback
- Identify pain points
- Validate assumptions
PM Archetypes
Technical PM: Engineering background, can read code, focuses on API/platform products
Business PM: MBA background, focuses on metrics, go-to-market strategy
Design PM: UX-focused, pixel-perfect, user experience obsessed
Growth PM: Metrics-driven, experiments constantly, activation/retention expert
Product Manager vs Product Owner
Product Manager (PM):
- Strategic, outward-facing
- Market research
- Multi-sprint roadmap
- Business outcomes
Product Owner (PO):
- Tactical, team-facing
- Backlog prioritization
- Single sprint focus
- Defined in Scrum framework
Distinction blurred in practice; many orgs used titles interchangeably.
Frameworks & Methods
Prioritization:
- RICE (Reach, Impact, Confidence, Effort)
- ICE (Impact, Confidence, Ease)
- Kano Model (basic, performance, delight features)
- MoSCoW (Must have, Should have, Could have, Won’t have)
Discovery:
- Jobs to Be Done (JTBD)
- Customer Development (Steve Blank)
- Design Thinking
- Lean Startup (Build-Measure-Learn)
Roadmapping:
- Now-Next-Later
- Theme-based (not feature-based)
- Outcome-driven (not output-driven)
The “Influence Without Authority” Challenge
PMs must convince engineers, designers, sales, marketing, executives—without being anyone’s boss. Success required:
- Clear communication
- Data-driven decisions
- Relationship building
- Credibility through domain expertise
- Negotiation skills
Breaking Into Product Management
Common paths:
- Engineer → PM (technical credibility)
- Designer → PM (UX understanding)
- Business Analyst → PM (requirements expertise)
- Consultant → PM (problem-solving skills)
- Customer Success → PM (customer knowledge)
Hardest for career switchers—chicken-and-egg problem of needing PM experience to get PM job.
PM Interview Style
Product Sense: “How would you improve Google Maps?” Execution: “How would you prioritize these features?” Technical: “Explain how YouTube’s recommendation algorithm works” Metrics: “What KPIs would you track for Instagram Stories?” Strategy: “Should Amazon enter the grocery delivery market?”