The value of Org Topologies in the era of DIY-frameworks
summary
Org Topologies provides a 16-box map to plot team ecosystems and close the horizontal flow vs vertical value gap, claiming org change requires deliberately sub‑optimizing teams to optimize the whole. Case evidence: a Ukrainian B2B restaurant vendor reshuffles ~50 R&D people into six cross‑component teams in nine months and reduces architectural complexity; Padok groups teams into three business contexts over years; Woft converges 14 teams into one bounded context, removes middle management and keeps one CEO product owner. Tools: mapping, component mentorship, gradual shared‑code rollout (descaling/simplification, shared code ownership).
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:32DIY frameworks era explained
- 3:41Org Topologies concept overview
- 5:48Case study: FlowTech challenges
- 13:15Local vs global optimizations
- 24:35Systems thinking in org design
- 30:17Discussion on local optimizations
- 33:32Real-world examples of Org Topologies
- 47:19Five principles for business agility
- 49:58Q&A and closing remarks
related talks
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
44mInsights on How Team Topologies Drive Organizational Success
45mSystems Thinking by combining Team Topologies with Context Maps
45mTowards Architecture Organization Topologies
45mLessons learned from introducing Team Topologies
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
41mSystems Thinking by combining Team Topologies with Context Maps