Deep dive · Business

Product Management for Engineers

How a software engineer should think about products: problem framing, discovery and delivery, prioritization, metrics and experiments, strategy, and what a product manager actually needs to know and do.

6 pages≈ 6.1 h readingSources

01Discovery vs Delivery: The Four Product Risks and the Build-to-Learn Loop55 min02From Request to Problem: Framing, Jobs-to-be-Done and Opportunity Trees60 min03What to Build and When: Appetite, Cost of Delay, Backlogs and Roadmaps60 min04Metrics, Experiments and Goals: OEC, Guardrails, HEART, OKRs and Trust65 min05Who Decides and What Carries the Decision: Product Roles and Spec Artifacts60 min06Business Viability for a Developer Product: Stakeholders, Strategy, Pricing and Positioning65 min