Harmony in innovation - building stronger engineer-product relationships
summary
Argues that weak product–engineering ties, not Agile itself, break delivery and shows concrete fixes: a homegrown competency model (started in Google Sheets) + five whys to map symptoms, inclusive steps like inclusive early discovery and story mapping with legacy devs, flexible role Venn diagrams to create shared ownership, and running parallel dual-track agile after launch. Cites Google Cloud / DORA findings that lean product practices predict faster delivery and higher job satisfaction; gives a four‑year performance failure as a cautionary example.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:45Product mindset basics
- 2:47Agile challenges and silos
- 4:55Product mindset in practice
- 7:26Team dynamics for product focus
- 9:12Weak product mindset symptoms
- 13:27Symptoms competency model
- 16:35Strategies for product mindset
- 17:18Communication in product discovery
- 21:02Shared ownership in build
- 24:18Reinvigorating post-launch innovation
- 28:58Relationship-driven culture
- 30:05Research-backed benefits
- 31:52Inclusivity via product mindset
- 32:42Q&A
related talks
44mA Match Made in Heaven - Instilling Harmony Between Product and Engineering
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
29mBuilding alignment with Eng & Product
32mPanel discussion: The journey to building effective engineering teams
31mHarmonizing Across Product & Engineering (Cross Team Collab)
31mImproving engineering effectiveness: A journey for the entire organization
32mSynergy: Building Strong Engineering Teams
48mBuilding a Product and Engineering Relationship that Works