Community
Start with answers already in the work. If yours is still open, send it.
Treat it as a change of craft, not a promotion. Start with Chapter 1 so you can name the gap, then Chapter 9 so you stop doing both jobs. Write a stop-doing list, name two people you will develop, and transfer work in writing. Mentoring (Chapter 3) and teamwork (Chapter 7) are the weekly practice, not a course you take once.
Only if they want the work on a bad Tuesday, not the title on a good one. The book’s opening line from Russell and Yao is the test: promotion is for business and leadership skills, not as a prize for code. Some superb engineers should stay on a technical leadership path and still practice communication, mentoring, and influence.
Ask better questions than you give speeches. Chapter 2 is the lab: engage marketing, sales, and finance until their vision and yours point at the same solution. Cut jargon. Use visuals. Brief in language a non-engineer can repeat. Understanding is not the same as a decision — give them a choice, not a lecture.
Constructive feedback is specific, about behavior, actionable, and respectful. Destructive feedback attacks the person or stays vague. Chapter 3 draws that line clearly. ‘In yesterday’s review you cut off two juniors. The room went quiet. I need you to facilitate, not win.’ Then ask how they see it. Do not sandwich. Do not wait for review season.
Use the ELBTG mentoring loop from Chapter 3: Establish clear goals, Listen actively, Build a tailored plan, Track progress and adjust, Give constructive feedback. The Mentoring Workbook is built for that loop. Mentoring is a partnership, not a downloaded lecture.
It is common. It is also the failure mode Chapter 9 exists to stop. You are doing two jobs and neither well. Write a stop-doing list this week. Transfer two pieces of work in writing, with names and support. If the organization requires a hero, it does not actually want a manager — and you should know that explicitly.
Some conflict is normal. Unhandled conflict is a tax. Chapter 8: name the issue without villains, find the root (goals, style, resources, respect), and close with a next step both can live with. Listen. Empathize. Do not hope it expires. Leaders who can hold a hard conversation keep talent.
Shared language, a curriculum of soft skills, reps on live work, and managers scored on the leaders they grow. ELBTG — Elevate, Learn, Build, Transform, Grow — is that spine. Pair the book with the mentoring workbook, a discussion guide, and a cohort. Hoping the next manager appears is not a strategy.
Two nested uses of the same letters. For the organization: Elevate engineers through soft-skills training; Learn technical and leadership skills together; Build leaders through mentorship and experience; Transform the team into a team of leaders; Grow the technology organization by empowering engineers to lead. For mentoring: Establish goals, Listen, Build a plan, Track and adjust, Give constructive feedback.
A mentor once gave him a leadership book. That one act set off a chain that has helped him mentor engineers across the globe. Giving a book says: I am invested in your growth, here is a focused resource, now go to work. The impact is larger than the object. It is an invitation into a practice.
Peter reads these. Not every question gets a public answer; the useful ones often become a field note.