Maturing your teams & your leadership
summary
A concrete account of what actually changes: a two‑and‑a‑half year visual rebrand that rebuilds spacing grids, design tokens and a home app; rationalizing 11,500 icons and shipping custom web fonts optimized to 68k over CDNs; a navigation change that irritates 300,000 customers; an AI feature that goes GA eight weeks into onboarding and ships despite UI debt. Metrics and engineering tradeoffs land alongside failures—wide integration plays that flop and a small customer overlap of 3% that reshapes go‑to‑market choices.
AI-written summary · about
chapters (19)
- 0:00Intro
- 7:30First reaction to the new colors
- 10:27Finding the right people
- 13:01The right conversations
- 14:40How did the team bring it up
- 15:41Identity protection
- 16:24Finding common ground
- 17:32I dont want to do this
- 20:15You start before you start
- 22:41Designing for clinicians
- 24:39Proxy wars
- 28:02The power of design
- 30:33Over frameworking
- 32:00Working with product managers
- 33:34When teams fail
- 34:59The hardest thing
- 36:17Heads down shipping
- 37:40Lockdown
- 38:50Collaboration
related talks
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
56mSmarter, Not Harder: Scaling without burning out in an always more landscape
11mDesign team of one
21mChange is Constant
51mThe subtle art of supporting mature products
21mGrow-thrive-make a difference: Leading through uncertainty
31mProduct excellence and developer productivity fireside chat
32mTransitioning from developing software to developing people
