Spin it up, shut it down
summary
Build a greenfield Status Pages product, spin a small redistributed engineering team, ship an MVP in months and reach 40 customers; choose a fresh team to get laser focus rather than saddling existing backlogs, use Vercel + Next js global caching to solve global traffic instead of overbuilding, embed senior infra help temporarily, verify with design partners, then sunset the team when signals show diminishing broad impact and hand ownership and roadmaps to the next team.
AI-written summary · about
chapters (22)
- 0:00Speakers and mission
- 1:04Why team lifecycle matters
- 2:31Starting a single-purpose team
- 4:40New team vs existing team
- 6:06Assembling the right team
- 7:49Balancing project and org needs
- 9:32Defining product strategy
- 10:35A week to avoid mistakes
- 11:37Setting team principles
- 13:21Design partners for feedback
- 14:04Forming stage with purpose
- 15:07Feedback-rich team culture
- 16:10Amplifying small wins
- 16:53Planning team sunset
- 17:56Avoiding over-engineering
- 19:00When impact fades
- 20:47Reading signals to pivot
- 22:09Shutting down a team
- 23:13Knowledge transfer and ownership
- 24:18Supporting new team
- 25:22Continuing innovation
- 25:43Key takeaways
related talks
10mStart with an exit in mind
24mBuilding a product in a tech scale up
59mTech leadership, one year after
31mManaging Growing Pains: Thinking Big While Being Small
25mCommon platform team mistakes and how to avoid them
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
50mMove Fast, Think Big
24mFrom Startup to Scale Up Designing for Growth from Day One