Insights on How Team Topologies Drive Organizational Success
summary
Shows concrete outcomes and practices: JP Morgan reorganizes into ~150-person value streams and cuts blocking dependencies by 60% dependency reduction; SAP creates an internal platform called hyperspace platform to reduce approvals where teams previously needed five tools and approvals from ten groups; a telecom groups teams into customer and platform tribes at ~4,000 staff to allow split/merge by strategy; a firm adopts an innovation sprint per PI to spread expert knowledge instead of new enabling teams.
AI-written summary · about
chapters (9)
- 0:00Intro
- 5:29No single approach will solve your problems
- 8:38Challenges for modern organizations
- 9:55Slow delivery due to high coupling between teams
- 15:05Lack of business agility due to organizational frictions
- 20:02Inconsistent user experience
- 26:33Slow time-to-market
- 32:36"We can't do that in my organization"
- 42:58Outro
related talks
54mThe value of Org Topologies in the era of DIY-frameworks
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
01h 01mSoftware Architecture, Team Topologies & Complexity Science
45mLessons learned from introducing Team Topologies
30mTeam Topologies Applied to Platform Engineering
30mTeam as code