Long-lived teams are damaging to your organisation
summary
Argues that stable long-lived teams often stop adding value and lists six failure modes with concrete examples: Blockbuster, Kodak and a time‑sheet product that outgrows its team and creates API backlog at HMRC. Recommends using a Conway’s‑law lens plus Team Topologies and Domain‑Driven Design to spot architectural misalignment, knowledge lockup, echo chambers and burnout. Advises quarterly checks on value, track dependencies, involve enterprise architects, intentionally rotate people (not wholesale quarterly churn) and measure flow and dependencies before reshaping teams.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:10Blockbuster’s downfall
- 4:20Six problems with teams
- 9:54Long-lived teams defined
- 12:04Value loss in teams
- 13:05Architectural misalignment
- 15:09Skills mismatch in teams
- 17:38Knowledge lockup
- 19:45Why teams persist
- 21:50Bringing work to teams
- 25:01Overcoming team inertia
- 27:05Self-critical evaluation
- 28:51Tracking dependencies
- 30:16Skills bottlenecks
- 31:20Knowledge sharing
- 32:45Cultural shift
- 33:27Breaking echo chambers
- 34:30Fixing toxic teams
- 35:12Healthy team traits
- 37:20Support for team change
- 39:06Summary
- 39:50Q&A
related talks
46mLeading Distributed Teams
33mBuilding Sustainable Teams to Handle Uncertainty
30mThree value inhibiting dysfunctions of enterprise software development
41mYour Systems Aren't Stuck - Your Teams Are
58mReturn of the rockstars? Building great teams in challenging times
21mAutonomous Teams
39mTeam Topologies, Software Architecture & Complexity
25mTransforming legacy software