Who's the Boss? How Tech Managers Can Work Well with Product
summary
Argues that engineering and product succeed when three concrete levers are used: create boundaries, realign routinely, and build trust daily. Recommends a one-time team charter session to set working agreements and roles, an org-level RACI matrix to stop ownership fights, and formal incident practices with an incident commander, on-call playbooks and blameless RCAs to prove reliability. Shows archetypes for EMs and POs so mismatched expectations get surfaced and claims these practices measurably reduce conflict and increase delivery predictability.
AI-written summary · about
chapters (16)
- 0:00Introduction to team dynamics
- 2:29Three pillars of collaboration
- 3:55Engineering manager roles explained
- 7:28Product owner archetypes
- 9:32Conflicts from unclear roles
- 10:15Creating team boundaries
- 13:49Why boundaries matter
- 14:12Importance of alignment
- 16:21Org structure impact on alignment
- 17:44Executive alignment routines
- 19:09Building trust in teams
- 20:35Trust during incidents
- 23:05Authenticity in collaboration
- 24:32Avoiding trust erosion
- 25:13Trust compounds daily
- 25:56Q&A on operations role
related talks
48mBuilding a Product and Engineering Relationship that Works
15mInfluencing your fellow execs
01h 01mHabits of a Highly Effective Technical Manager
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
09m"The Joys of Managing Engineering Teams"
15mThe Product Triangle
25mThe making of a manager's manager
44mA Match Made in Heaven - Instilling Harmony Between Product and Engineering