Level up the whole party, not just the hero
summary
Argues that managers decide growth by concrete daily choices and shows how to do it: measure expertise as cursed knowledge, use proximal development and explicit skill trees, run work as initiative-based streams with designated initiative leads, and perform regular gap analyses against a career matrix. Gives a concrete failure (a level 36 Charizard soloing too early) and a repeatable fix: split tasks, pair learners with teachers, accept short-term slowdowns to build a resilient, cross-functional team.
AI-written summary · about
chapters (8)
- 0:00Balanced team leadership
- 4:38Balanced teams outperform heroes
- 8:09Well-rounded team definition
- 11:59Mapping team expertise
- 14:51Proximal development skills
- 18:00Stewarding growth vision
- 21:51Fair opportunity distribution
- 24:41Team autonomy vision
related talks
27mLevelling up as a Lead Developer
30mEquipping your team to support junior developers
06mStepping Up - Becoming a Leader in Your Team
30mFireside chat - Leading your personal growth
31mStories to get you to the next level
41mBecoming a Mid: Two Perspectives on Leveling Up
30mForging Your Path to Senior Developer
24mFrom Startup to Scale Up Designing for Growth from Day One