Categories of Technical Leadership
Four distinct responsibility categories in technical team leadership. Useful for role design, staffing, and understanding what "leading a team" actually involves.
| Category | Core responsibility | Key skill | Failure looks like |
|---|---|---|---|
| Overall direction | Mission, roadmap, priorities | Predictive models of domain + org | Getting caught by surprise; low-value work |
| People management | Coaching, hiring, performance | Empathy + understanding high performance | Chronic underperformance; low morale |
| Project management | Execution, unblocking, visibility | Organization + domain expertise | Blocked people; priority thrash; info gaps |
| Technical leadership | Technical quality, direction, mentorship | Domain expertise + communication | Accumulated debt; bogus results; fragile systems |
The insight is that these cluster differently in different people. Trying to find someone great at all four is a unicorn hunt. Deliberate splitting — EM/TL, PM/TL, people-manager/research-lead — lets people focus on their spikes.
Best project manager ≠ strongest technical IC. The key traits are organization and staying laser-focused on end goals. Technical leadership requires enough IC time to maintain honest feedback loops with the work.
Common splits:
- EM / TL: EM = direction + people + project; TL = technical (large tech, Anthropic inference)
- PM / TL: non-technical PM as "mini CEO"; TL as technical + secondary people manager (Wave)
- People manager / Research lead: direction + technical held by research lead; people + project by people manager (Anthropic interpretability: Olah + Carter)