From the field

“I have given this to every senior engineer who asks about management. It names the thing we have been dancing around in promotion packets for years.”

“I expected another soft-skills lecture. It is not. It treats leadership like a craft with reps. I used the stop-doing list the week I finished chapter five.”

“Finally a book I can put under a tech-lead academy without translating it out of another industry. The ELBTG letters hang on our team wall.”

“The gap diagram did more in ten minutes than a year of 'you should be more strategic' feedback. My 1:1s have a vocabulary now.”

“Peter does not romanticize the CTO seat and he does not condescend to ICs. That combination is rarer than it should be.”

“We ran the discussion guide with a cohort of twelve high-potentials. The conversations were uncomfortably specific — which is to say, useful.”

“I stayed an IC on purpose. This book is the first one that didn't treat that choice as a failure. Influence without a title is a whole chapter, not a footnote.”

“Short enough to finish. Dense enough to underline. I have a stack of 200-page leadership books I never returned to. I returned to this one.”

“The workshop on 'why great engineers don't automatically become great leaders' should be mandatory before any IC-to-manager conversion.”

“We bought a box for the manager cohort and another for the staff-engineer track. Same spine, different conversations. That is good design.”