Designing an Organization, Lessons from scaling technical orgs
summary
Claims that an entire org can be redesigned and that smaller changes can reliably stick with more discipline; proven across two scale-ups over four years (one physical product company, one digital team growing from ~50 to 120–200). Uses value stream mapping and a quantified value-based decisions (VBD) portfolio, applies team topologies and constraints like teams over stars and extreme ownership. Builds HR processes and a central workflow, discovers missing roles and interactions, records both successes and failures, and shows change only endures with explicit responsibilities and repeated enforcement.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:38Organization design beyond structure
- 9:59Scaling startups examples
- 14:14Three tenets of design
- 21:43Build vs build process
- 26:20Human systems work
- 30:11Values culture mechanisms
- 33:21Missing workflow pieces
- 35:28Summary
related talks
47mScaling Design Orgs Rapidly for Long Term Success
26mHow to Design Orgs That Scale
31mScaling
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
53mThe art of scaling an Engineering Organization
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
24mFrom Startup to Scale Up Designing for Growth from Day One
26mScaling engineering organizations