Solving The Value Equation
summary
Argues that software value depends on reducing distance to realized value — social, structural and temporal gaps — and that measuring output (anecdote: functions trimmed to 15 lines) triggers Goodhart's law and proxy failures. Recommends breaking systems into customer-facing pieces, using DDD, Conway’s Law and Wardley mapping to decide which components to make standalone (examples: AWS spun out and sold; Tesla/SpaceX battery capabilities reused as products). Frames strategy as building a value ladder so components compound and synergize.
AI-written summary · about
chapters (24)
- 0:00Introduction to value equation
- 1:05Measuring developer productivity
- 3:58Effort output outcome impact
- 6:29Distance to realized value
- 8:54Dimensions of value
- 12:46Aligning with customer needs
- 13:49Goodhart's law and interference
- 17:28Friction in processes and architecture
- 22:46Breaking down big problems
- 27:30Scaling and product complexity
- 29:18Customer facing teams
- 31:46Maximizing independent value
- 33:14Agile culture and quality
- 36:04Organizational capabilities
- 40:37Investing in the right things
- 43:05Multi-purpose value creation
- 44:31Value chains and tradeoffs
- 46:37Q&A on growth and maturity
- 53:16Stability versus sustainability
- 58:15Future of agile practices
- 1:00:53Defining value in depth
- 1:07:08Startups and venture capital
- 1:12:05Final thoughts for young coders
- 1:25:13Closing remarks
related talks
49mMaking Value Visible
01h 01mSoftware Architecture, Team Topologies & Complexity Science
45mValue
15mOptimizing the engineering value stream
01h 08mGetting More from Technology
43mArchitecting Independent Value Streams
43mChange Your Focus
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed