Tips on scaling your leadership outside of your comfort zone
summary
Leads a data migration from an Android-heavy background, rewrites a pipeline so client engineers can adopt it and customers avoid outages, and uses concrete practices: ask engineers what happens if we turn off X to build mental models, document decisions and follow up in 2–3 days with a decision note, schedule monthly project check‑ins, and prefer reversible gates over irreversible commits so small biases don’t compound into large failures.
AI-written summary · about
chapters (11)
- 0:00Scaling technical leadership
- 1:03T-shaped skills in leadership
- 2:25Engineers first for insights
- 3:49Obvious questions for mental models
- 5:14Documenting for trust and clarity
- 5:54Admitting ignorance and follow-up
- 6:56Avoiding bias from expertise
- 7:39Leveraging connections and support
- 8:42Reversible decisions reduce risk
- 9:45Comb-shaped engineers & closing
- 10:30Q&A
related talks
59mTech leadership, one year after
41mWant to make a change? Stop talking and start listening
29mNavigating the chaos of scaling
33mScaling yourself during hypergrowth
43mSweat the Small Stuff
26mScaling engineering organizations
24mFrom Startup to Scale Up Designing for Growth from Day One
14mHow to zoom out (and when to stop)