What a Product Manager Actually Does
- Defines the “Why” & “What”
- Discovers market problems (via user research/data).
- Prioritizes what to build (roadmaps) and why it matters (strategy).
- Owns the Product Lifecycle
- Ideation → Launch → Growth → Retirement
- Works with engineering, design, marketing, and sales.
- Balances 3 Key Forces
- User Needs (Pain points, UX)
- Business Goals (Revenue, growth)
- Tech Feasibility (Engineering constraints)
Key Responsibilities
| Area | PM Activities |
|---|---|
| Research | User interviews, competitor analysis, data analytics |
| Strategy | Vision, OKRs, roadmap planning |
| Execution | Writing PRDs (Product Requirements Docs), sprint planning |
| Coordination | Aligning engineers, designers, marketers |
| Launch | GTM strategy, pricing, beta testing |
Skills Needed
- Hard Skills: Data analysis, Agile/Scrum, prototyping (Figma), SQL basics.
- Soft Skills: Storytelling, negotiation, stakeholder management.
- Superpower: Saying “No” to 90% of ideas to focus on the 10% that matter.
PM vs. Other Roles
- Project Manager: Focuses on timelines/tasks (PM owns the outcome).
- Product Owner: Scrum-specific role (tactical; PM is more strategic).
- Engineer: Builds the how; PM defines the what.
Types of Product Managers
- B2C PM: Optimizes for user engagement (e.g., Instagram features).
- B2B PM: Focuses on enterprise needs (e.g., Salesforce tools).
- Technical PM: Deep in APIs/AI (common at Google/Microsoft).
- Growth PM: Hacks virality (e.g., Dropbox referrals).
Why Companies Hire PMs
“Without a PM, teams build things right (engineering focus) but not the right things (market focus).”
Example:
- Engineers might optimize app load speed.
- PMs ask: Should we build this app at all?
How to Become a PM
- Start Here: Transition from adjacent roles (engineering, marketing, UX).
- Learn Fast: Read Inspired by Marty Cagan, practice case studies.
- Build Evidence: Launch a side project (even a simple app/no-code tool).
