Lead essentials: the summary, the research and the vocabulary
This chapter is the compression of the rest of the book for someone interviewing for a team lead or tech lead role, plus two things the other chapters assume rather than teach.
The summary is what actually matters out of 280 pages, weighted by return per hour of preparation, organised around one distinction: a senior engineer optimises the artifact, and a lead optimises the system that produces artifacts. Answering lead questions with IC answers is the most reliable way to fail a TL loop, and the fix is usually reframing work you have already done rather than learning anything new.
The research is the small set of studies and named effects that convert an opinion into an argument. Goodhart's law, Project Oxygen, Project Aristotle, psychological safety, Westrum, DORA, normalization of deviance, Conway, Brooks, and a handful of named effects worth having ready. Each entry says what the study actually found, which in several cases is not what it is popularly claimed to have found, and the gap is a fast way to show you read the source.
The vocabulary is three pages on the terms that raise the register of everything else you say: the language of decisions and risk, of systems and failure, and of organisations and delivery. They are taught as families rather than as a glossary, because they form a system, and each entry includes how it misfires, because a term used loosely is detectable in one follow-up question.
There is also a page on speaking in numbers, with runnable Monte Carlo code, because the single most common lead question is a date question and the standard answers to it are all bad. Its headline result: summing the most-likely estimates for a six-task project produced a plan sitting at the first percentile of the real distribution.
The condensed lookup, including the full term table and answers to the questions that come up in nearly every loop, is the team lead cheat sheet.
What this chapter covers
- [done] The team lead summary: what actually matters
- [done] The research a lead should be able to cite
- [done] Speaking in numbers: p90 and Monte Carlo
- [done] The vocabulary of decisions and risk
- [done] The vocabulary of systems, failure and design
- [done] The vocabulary of organisations and delivery
Source: §2, §3, §13, §26, and the cross-cutting leadership material.