Debugging Product Teams
summary
Claim: debugging a product team uses a systems approach with a repeatable cycle — map systems, observe and ask, hypothesize and intervene — not platitudes. Tools and data are concrete: org and industry maps, PRs, Slack, retros, one‑on‑ones, CI metrics, kanban vs scrum experiments. Examples show specific failures (power imbalances, huge surprise PRs, burnout at home) and concrete interventions (coaching, removing a toxic member, changing process). Talk runtime is ~30 minutes.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:38Systems approach to product teams
- 2:34Assumptions
- 4:16caveats
- 5:23debugging process
- 6:11map the systems
- 9:25example map
- 11:21observe
- 12:39internal problems
- 16:54intervention
- 19:42external factors
- 23:17TLDR
- 24:54Outro
related talks
27mDebugging product engineering organizations
20mDebugging: Techniques for Uncertain Times
57mDebug your thinking
35mDebugging as an experimental science
38mFrom the Exorcist to Hercule Poirot
32mPanel discussion: The journey to building effective engineering teams
23mSkills for debugging complex problems
38mTools and methods are killing your products