How a Lean and Structured Team Topology amplifies an Organisation's Productivity
summary
A 15‑team product org maps every team type against desired architecture using Team Topologies and an inverse Conway approach, then runs small working groups, visual charters and PRFAQ communication to change team boundaries. Remote and co‑located pilots use Miro boards and a developer‑facing internal platform. Results: deployment frequency moves from once a week to multiple times per day, cycle time improves ~67%, and a survey‑based radar plus a simple formula reports cognitive load falling (~68%).
AI-written summary · about
chapters (22)
- 0:00Introduction and story setup
- 1:35Frustration with team dependencies
- 3:20Ferrari pit stop analogy
- 4:04Organization background and challenges
- 8:03Symptoms of team entanglement
- 9:31Introduction to Team Topologies
- 10:54Conway's Law explained
- 12:43Understanding cognitive load
- 13:45Four team types in Team Topologies
- 16:13Team type analysis in organization
- 17:57Interaction modes between teams
- 18:18Inverse Conway maneuver
- 19:45Kickoff and team topology mapping
- 21:54Defining team charters and shared understanding
- 23:18Designing desired architecture
- 25:00Challenges in execution and staffing
- 25:42Change management and communication
- 27:29Remote team transformation example
- 28:53Key takeaways and lessons learned
- 31:41Purpose and motivation in teams
- 32:22Measuring KPIs and improvements
- 33:48Conclusion and Q&A
related talks
54mThe value of Org Topologies in the era of DIY-frameworks
44mInsights on How Team Topologies Drive Organizational Success
40mEnabling teams for happier and more productive engineers
30mThe Art of Team Design
37mPlatform as a Product for modern IT needs
30mTeam as code
45mLessons learned from introducing Team Topologies
46mBalancing individual team flow with cross-team collaboration