From Startup to Scale Up Designing for Growth from Day One
summary
Historic wins and missteps make specific recommendations: don’t freeze in Jira dashboards and burndown theater—ticket obsession wastes founder time; rigid hierarchies (350 people with ~15% managers) create coordination nightmares; pure flat consent breeds indecision and burnout. Replace presence with company-specific principles and a one-line anchor like change mobility for good or promise of the zero plus policy examples such as common code access. Use a confidence rule (high confidence → build at quality; low confidence → build scrappy to validate, e.g., 5–50M estimated impact ranges).
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 0:23Setting expectations for growth
- 1:51Personal growth journey and mistakes
- 4:22People and projects as growth dimensions
- 6:08From gut instinct to structured playbooks
- 9:02The ugly side of micromanagement
- 11:53Why founders' behavior must scale
- 14:05Principles over mission statements
- 15:55Crafting clear strategy principles
- 18:23Dogmatic adherence to principles
- 19:06Scrappy vs quality design decisions
- 20:31Finding the anchoring topic
- 22:15Hierarchy vs flat structure balance
- 23:59Q&A session
