Don’t promote stars into managers
A popular engineering thread warned that pushing top individual contributors straight into management often breaks teams because the role requires enabling others, not just producing. (x.com) The conversation also flagged common traps—maintenance debt accumulation and chaotic planning—and pointed people to concrete work-plan templates and PMI findings as ways to prevent those failures. ( )
A lot of teams break the day they “reward” their best engineer with a manager title, because the job stops being writing the cleanest code and starts being clearing the road for six other people. Reforge’s guide on the jump from individual contributor to engineering manager calls it “a wholly different job,” not a bigger version of the old one. (reforge.com) That mismatch is why many companies now keep two ladders: one for managers and one for senior builders like principal engineer, engineering fellow, or distinguished engineer. LeadDev notes that those roles can shape architecture and strategy without taking on performance reviews, hiring, and conflict resolution. (leaddev.com) The trap is easy to see inside a sprint board. A star individual contributor wins by personally finishing the hardest ticket; a manager wins by making sure the right work reaches the right people in the right order. Reforge describes that as curating work, delegating it, and adding just enough process to unlock delivery instead of slowing it down. (reforge.com) When that shift does not happen, maintenance debt starts piling up. Teams keep shipping features because the new manager still thinks like the fastest firefighter in the room, while the quiet work of fixing brittle systems, updating dependencies, and reducing recurring toil gets pushed aside until outages and slowdowns force it back onto the calendar. (reforge.com) Planning usually falls apart next. Engineering managers sit between product, finance, marketing, data, and the engineers doing the work, and Reforge says collaboration breakdowns at that intersection create bottlenecks, friction, and missed deadlines. (reforge.com) That is why the best management advice in this debate sounds less like “be more technical” and more like “make the work legible.” The Project Management Institute’s resource library emphasizes agendas, collaborative leadership, communication, and team enablement, which are management muscles rather than coding muscles. (pmi.org) The Project Management Institute’s 2024 Pulse of the Profession report makes the same point from the planning side: teams perform equally well across predictive, hybrid, and agile approaches when organizations give them flexibility, resources, and the skills to adapt. The report says hybrid project delivery rose from 20% in 2020 to 31% in 2023, which is another way of saying rigid one-style management is losing ground. (globalprojectperformance.com) So the practical fix is not “never promote your stars.” It is to stop treating management as the only prize, give top individual contributors a real senior technical path, and hand new managers concrete planning tools before they inherit a team calendar, a hiring plan, and a backlog full of old promises. (leaddev.com) (pmi.org) The companies that get this right stop asking, “Who is our strongest engineer?” and start asking, “Who can make eight engineers stronger?” Those are often different people, and teams run better when the org chart admits it. (reforge.com)
