Structure eats process for breakfast
summary
Claim: changing team rituals never overcomes mismatched organization design. Evidence: a product initiative still loses 80% business case value from idea to market when incentive schemes reward pipeline not outcomes, and restructuring around markets cuts stakeholder load by 70%. Tools actually used: lean product canvas, product discovery, team topologies, starter kits mixing scrum/kanban/product trios. How to act: run vertical slice pilot to validate dependencies, make platform teams operate on market terms, iterate structure not just processes — examples show measurable impact.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:10Hidden elephants in org structures
- 8:28Structural dysfunctions examples
- 14:52Leadership confusion in agile
- 16:16Business vs tech unit clash
- 17:42Unstable team structures problem
- 19:06Silver bullets fail in agile
- 21:33Structural changes enable success
- 22:15Conway's law and org design
- 25:24Validating changes with real cases
- 28:38Step-by-step structural advice
- 33:14Mindset change through action
- 34:41Pretending changes are in place
- 36:47Bypassing middle management
- 38:11Team-level agile starter kit
- 40:21No single agile framework rules
- 41:02Key takeaways and closing remarks
related talks
39mDesigning an Organization, Lessons from scaling technical orgs
33mFeature Teams vs. Platform Pain
28mOrganizing for Outcomes
07mProduct Org Design: Flow Follows Form
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
44mInsights on How Team Topologies Drive Organizational Success
49mThe Good, the Bad and the Very Ugly in Structuring IT Organizations
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity