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. Write a 90-day plan that includes a stop-doing list, two people you will develop, and a public account of how decisions will get made. Tell your manager you will be worse at this job for a while. Then practice being a multiplier on live work, not in a course. The Transform and Grow chapters are the spine.
Only if they want the work on a bad Tuesday, not the title on a good one. Management is a different craft. Many great engineers should become staff or principal leaders instead. If your company has no such path, that is an organizational problem — do not solve it by sacrificing a superb IC to a job they will resent.
Be useful when it costs you something. Write the doc others can use. Make other people look right in rooms you do not run. Lose a debate without losing the relationship. Influence is accumulated evidence that following your framing will not embarrass anyone. Title is a lagging indicator of that evidence.
Open with the decision you need, the outcome it protects, and the risk if you wait. Architecture is the how. Put it third. Speak in options and a recommendation, then stop talking. If they want depth, they will ask. If you start in the how, you will be asked when it makes money — and you will feel dismissed for a problem you caused.
It is their meeting about them, not your meeting about status. Status belongs in writing. Use the time for growth, blockers only they will say in private, and feedback that is still warm. Leave with a next move. If you talk more than they do, you ran a briefing.
Be specific, timely, and about the work in the world — not their soul. 'In yesterday's review you cut off two juniors before they finished. The room went quiet. I need you to facilitate, not win.' Then ask how they see it. Do not sandwich. Do not wait for performance season. Strength is not a shield against standards.
Strategy is a written bet with a kill criterion. Start there. Name what you are not doing. Connect a quarter of work to a customer and a constraint. Sit in rooms where money is discussed until the language is no longer foreign. Elevation is a practice. The Business Acumen chapter is a working model, not an MBA.
It is common. It is also the failure mode. You are doing two jobs and neither well. Install a stop-doing list this week. Transfer two pieces of work in writing. Tell your manager the old job is colonizing the new one. If the organization requires a hero, it does not actually want a manager — and you should know that explicitly.
Shared language, a curriculum, reps on live work, and managers who are scored on the leaders they grow. A book can be the spine. An assessment, a cohort, a workbook, and a 90-day stretch assignment make it a program. Hoping the next manager appears is not a strategy.
Scope, influence, and technical direction without line management. You still elevate, learn, build, transform, and grow — the people you grow are often peers and the org, not direct reports. If staff is just 'senior but louder,' you do not have a path. You have a title.
Peter reads these. Not every question gets a public answer; the useful ones often become a field note.