How to evaluate team effectiveness with a data first approach
summary
Argues for measuring product, process and people with concrete KPIs and follow-through: integrates marketing, finance and ad tooling to standardize definitions and drives 70% improvement in the growth funnel at Headspace; pauses releases to fix quality, invests months in automation and aims to cut incidents caused by quality from 70% down to 15%; standardizes sprint metrics and empowers teams to improve, producing 30–40% sprint efficiency gains at Cruise while using simple tools (spreadsheets, Google Forms) and biweekly demo cadences.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:30Measure team effectiveness with data
- 4:00Three themes for team measurement
- 5:29Strategic impact and product success
- 8:47Check-ins for follow-through
- 11:17Execution and operational metrics
- 14:33Execution improvements
- 16:21Knowledge sharing and alignment
- 17:26Team dynamics and talent composition
- 19:35Scaling communication strategies
- 21:02Key learnings and takeaways
- 22:07Closing
- 22:27Q&A: Team evaluation pitfalls
- 23:49Q&A: Tech and business goals
- 25:13Q&A: Data-driven culture shift
- 27:00Q&A: Keeping evaluation relevant
- 27:42Q&A: Cost of rapid prototyping
- 29:09Q&A: Data approach and engagement
- 30:55Q&A: Execution vs reviews
- 31:59Q&A: Personal passions
related talks
42mMeasuring Agile success
33mMeasuring Developer Productivity: the good, the bad and the data
41mRethinking Measurement for High-Performing Teams
43mMeasuring Developer Productivity: The Good, the Bad and the Data
23mMeasure for change
34mBuilding a Culture For Developer Productivity
47mCan We Measure Developer Productivity?
22mOptimizing Product Development: Balancing Speed, Quality, and Process