Building High Performing Product Teams
summary
Explains how a remote product office grows from hiring five people to scaling to 50 to 150 and what actually changes: use employee surveys to surface dysfunction, publish a public cultural document with I statements so hires opt in, time-box debate then make a single decider, run formal performance processes to remove uncoachable disruptors, and prioritize emotional IQ over raw talent. Includes concrete examples of storming → norming interventions and metrics that shifted.
AI-written summary · about
chapters (16)
- 0:00Introduction and news
- 1:03High performance vs harmony
- 2:49Talent isn’t everything
- 3:53Leaders cast a shadow
- 5:17Emotional awareness matters
- 7:47Forming a high-performing team
- 10:58Team values and resilience
- 12:46Storming and conflict resolution
- 15:37Bonding and team-building
- 17:43Exiting storming with decisive action
- 18:47Norming and team success
- 20:13Handling new challenges
- 21:19Team camaraderie and values
- 23:02Embracing disruption
- 24:06Benefit of the doubt in teams
- 25:31Closing and acknowledgments
related talks
31mHow Great Tech Teams Build a Productivity Culture that Scales
25mKeeping Your Startup Heart While Scaling Up
45mFrom 5 to 100 in Product Development team in just 5 years
48mSoftware Teaming: Onboarding, Remote Work, Productivity — Four Years in an Team's Life
18mRethinking Team Building: how a 30-person Startup serves 50 Million Users
51mBuilding a High-Performance Team is Everyone's Job
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
21mThe Power of We: Unleashing the Collective Strength of Your Team