The Product Triangle
summary
Defines how engineering, product and program managers split who decides what and why accountability means justify actions and decisions, not punish. Calls out the messy gray zones that appear around ~120 people (Dunbar number), shows Apple’s model of engineers + design + EPMs handling execution, and gives a concrete exercise: write down 10 responsibilities for each role, compare notes with peers, then agree a simple protocol so ownership and scheduling, roadmaps and feature voice are unambiguous.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:45The Product Triangle
- 4:01Accountability
- 13:36What's one great piece of career or life advice that you've received?
related talks
27mWho's the Boss? How Tech Managers Can Work Well with Product
48mBuilding a Product and Engineering Relationship that Works
27mScaling Engineering & Product Teams
38mExamining the Product Owner Role
30mWhat Product Leaders Do
29mReaching Success Through Product Engineering
31mFrom Engineer to Engineering Manager
01h 05mTransformed: Moving to the Product Operating Model