Optimizing for Speed
summary
Claim: maximize speed by deliberately reinventing org structure in short “hops” instead of blitzscaling. Concrete practices: build cross‑functional segment teams that minimize stakeholders and external dependencies, empower them with first-principles thinking, measure with KPIs, and support people with 360 reviews, learning plans, assessment days and regular one‑on‑ones. Evidence: Bitrise grows to ~100 people, serves 100,000+ developers, sent a marketer to speak to 400 developers in Singapore, and repeatedly promotes people (content writer → product marketer), showing the model preserves agility and scales performance.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 3:07What is Y Combinator
- 3:54Bitwise
- 5:29Continuous Change
- 6:26Lessons Learned
- 7:43Needs to Change
- 8:41The Challenge
- 9:43The Pressure Cooker
- 10:40Continuous Reevaluation
- 11:14ScaleUp
- 12:01Product Pivot
- 13:01Pivoting
- 14:31Speed over Efficiency
- 16:19Risks for investors
- 17:04What we do
- 17:24Evolving
- 19:16Planning
- 19:50Big Picture
- 20:14Agile vs Blitzscaling
- 21:29Uncertainty
- 25:31Amazon Pizza Rule
- 26:09Performance Improvement
- 27:06Change
- 27:33Hiring
- 28:13Feedback culture
- 29:14Knowledge gaps
- 30:27Hiring people who dont understand the journey
- 31:13First principle thinking
- 32:11Make something people want
- 33:29Great people teams
- 33:51Support structure
- 34:46Product marketing
- 36:04Culture
- 37:32Recap
- 38:31Questions
related talks
47mMoving Fast at Scale
22mOptimizing Product Development: Balancing Speed, Quality, and Process
30mMoving Fast At Scale
45m"Moving Fast at Scale"
36mHypergrowth - lessons learned from tripling the size of a tech team
39mDesigning an Organization, Lessons from scaling technical orgs
39mLearnings from fast growing
33mScaling yourself during hypergrowth