Learning from industry: Product Management practices for the win
summary
Argues that roadmaps must minimize business risk by tying every item to company goals and OKRs, and recommends ditching timeline Gantt charts in favor of a lean now/next/later board that separates a discovery backlog from an execution backlog. Prioritize outcomes (NPS, revenue, referrals) over output, run cheap experiments (paper‑plane → speaking‑tube → phone) to validate assumptions before building, and publish a selective public roadmap so sales, marketing and ops can plan. ditch the timeline roadmap link to OKRs
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:30Product management basics
- 0:53Problem solving
- 1:28Project management
- 4:47Roadmaps
- 6:09Benefits of a roadmap
- 7:43Goal of a roadmap
- 9:25Output vs outcomes
- 10:56Ditch the roadmap
- 14:21Lean
- 19:21Strategy vs execution
- 21:01Support experimentation
- 24:23How might we test it
- 26:27How will it benefit the business
related talks
44mOutcome-based Product Planning
36mOk, I’ve Burned My Roadmap and My Backlog. Now What? Lean Product Management
42mBuilding Powerful Roadmaps
31mRoadmap Revolution: Turn Friction into a Business Accelerator
18mEffective backlog prioritisation for company happiness
34mFirst Principles in PMing: The Roadmap
33mAligning Goals & Processes between Engineering & Product
48mBuilding a Product and Engineering Relationship that Works