Organizing for Outcomes
summary
Every organisation is currently delivering exactly the results its incentives and structure produce, so changing labels alone fails; top-down one‑size reorganisations and cost‑cutting backfire. The working pattern that proves useful is long‑lived value streams (team‑of‑teams) aligned to bounded customer value, measured with OKRs and a balanced set: better, value, sooner, safer, happier; adopt three equal leads—value outcome lead / team outcome lead / architecture outcome lead—break dependencies instead of managing them, start small, iterate, and expect the first designs to be wrong.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Why outcomes matter
- 3:54Outcomes over structure
- 7:42History of org design
- 11:58Role-based silos today
- 14:47Incentives drive outcomes
- 20:36Value stream org
- 23:45Communities of practice
- 25:11Patterns and anti-patterns
- 27:19Key learnings
related talks
31m How to align the organisation for outcomes and performance
39mDesigning an Organization, Lessons from scaling technical orgs
49mDesigning Business Outcomes (#noprojects)
19mThe Why, How & What of an Outcome centric team
07mProduct Org Design: Flow Follows Form
29mFrom Agile to Outcome-Driven
54mThe value of Org Topologies in the era of DIY-frameworks
46mPainful outcomes - 7 mistakes I made in the shift to value led development