Run Circles, Not Relays
summary
Argues that integrated team practice—engineers in discovery, designers and product continuously pairing—reduces silos and de-risks work. Uses continuous discovery and dual-track scrum, runs product increments of about eight weeks, and reports a 16-month blended client engagement where a “Zillow for social services” concept is validated with open‑source data and a technical prototype that gives enough confidence to build. Recommends async reviews, UX checks before handoff, explicit success metrics up front, and team norms to surface issues early.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 0:33Gayles introduction
- 1:33The Little Mermaid
- 2:48Working in teams
- 4:17Engineers and product designers
- 5:17Integrated team
- 5:40Team members
- 6:22Crossfunctional vs Integrated
- 7:13Handoffs
- 10:44Collaborate
- 12:23Key Outcomes
- 14:26Principle Behind Integrated Teams
- 15:44Continuous Discovery
- 16:52Collaborative Team
- 17:06Discovery
- 19:26Definitional
- 21:01Example
- 23:06Build
- 25:20UX Check
- 26:08Conversation
- 26:51Measurement
- 27:17Geek Ale
- 27:27Empathy
- 27:46Challenges
- 28:41Suggestions
- 31:08Story
- 32:55Optimize
- 34:56Establish Team Norms
- 37:01Team Agreement
- 37:28Be curiously constructive
- 38:17Antipatterns
- 39:33Resources
related talks
32mStop Running in Circles: Applying Shape Up
22mOptimizing Product Development: Balancing Speed, Quality, and Process
18mAgile leadership and technical mastery, a harmonious alliance
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
33mBuilding Sustainable Teams to Handle Uncertainty
46mDynamic Reteaming
38mHarmony in innovation - building stronger engineer-product relationships