Transitioning from Project to Product: An Experience Report
summary
Company reorganizes into a single Product Development group around four product value streams, introduces a new product value stream lead role distinct from product manager, and measures work with flow distribution, flow efficiency, flow time, flow load and flow velocity. After one year this reduces product-vs-engineering conflict, increases customer focus, and speeds investment decisions, though finance runs dual reporting and many organizational details (career ladders, dependencies) still require active change.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:10Flummoxed
- 4:13Symptoms
- 5:55Mindset
- 7:16Team Structure
- 10:15What Happened
- 11:10Product Value Stream Lead
- 11:55Summary
- 16:25What makes a good product manager
- 18:32Other considerations
- 19:37intentionality vs perfection
- 20:10Simon Says
- 21:45Dependencies
- 28:26Conversation Changer
related talks
07mProduct Org Design: Flow Follows Form
27mScaling Engineering & Product Teams
13mMoving Beyond “Getting It Done”
40mFrom Promises to Value, Lessons from the Product Frontline
01h 05mTransformed: Moving to the Product Operating Model
50m'Product Managers Are Ruining Product Management!?' Streamlining Chaotic Product Development Turned Us into a Stuffy Bureaucracy — How We Overcame Corporate Sickness to Build a Youthful Team
30mHow we built a Product Engineering culture at Great Expectations
52mShifting into continuous delivery