Every technology organization has a silent failure mode. Engineers who can design systems of extraordinary complexity stall when the work stops being technical. They are promoted because they are excellent — and then asked to do a job that excellence at engineering does not automatically confer.
This chapter names the gap. It is the distance between what made you valuable as an individual contributor and what will make you valuable as a leader of people, platforms, and bets. Companies keep pretending the distance is small. Careers, teams, and products pay for that pretense.
You will see the typical path — engineer, senior, tech lead, manager, director, executive — and the specific place most people get stuck: the moment influence, not output, becomes the scarce resource. The rest of the book is a way across.
Lessons
- Technical excellence is necessary and insufficient.
- The gap is a curriculum problem, not a personality problem.
- Organizations that cannot name the gap cannot close it.
Questions
- Where has your technical strength started to hide a leadership weakness?
- Who around you is stuck in the same place — and who got through?
- What would your team lose if you kept doing the work yourself?
Map your last promotion
- Write the skills that earned your last step up.
- Write the skills the next step actually requires.
- Circle the three that do not overlap. Those are the gap.