Why one model can’t fit all creating fulfilling engineering organizations
summary
Panel claims that one-size frameworks fail and gives concrete alternatives: dynamic reteaming and self-selection (one company lets people choose among 16 teams), team topologies plus platform teams to fix inconsistent UIs and tighten shared engines, and Wardley mapping and DDD to locate value and split monoliths. Reported outcomes include faster flow, clearer ownership, an isolation pattern for new product discovery, and measurable ties to Dora‑style delivery performance.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:25Organic vs frameworks in orgs
- 2:06Building confidence organically
- 3:54Trust in self-selection teams
- 5:19Culture and performance
- 7:03Team roles in culture change
- 8:43Values as principles
- 10:43Starting org change
- 12:29Autonomy vs cohesion
- 14:15Red Gate’s values journey
- 15:38Tools to re-team
- 19:32Q&A: Conway’s law
- 19:54Team topology effects
- 23:07Org/arch changes impact
- 24:55Incremental small-team approaches
- 26:00Innovation via re-teaming
- 28:52Spreading team practices
- 31:44Knowledge sharing
- 32:46Anti-patterns and best practices
- 34:32Motivating resistant members
- 36:58Aligning teams to preferences
- 38:44Pull systems for change
- 40:35Encouraging team growth
- 40:55Closing & Q&A
related talks
58mTeam Topologies Panel
01h 00mPanel
47mFrameworks for Shaping High-Performing Teams
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
33mVersatile Organization Design with the unFIX Model
35mGuiding teams, and shaping a portfolio using Wardley maps & DDD
54mThe value of Org Topologies in the era of DIY-frameworks
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies