An engineer moves into a technical leadership role and finds their old approach no longer works. What changes?

What changes

• The unit of output stops being your own work. An individual contributor is measured on what they build; a technical leader is measured on what the group builds, which means the highest-value activity is frequently unblocking someone else rather than writing anything.
• Depth is traded for breadth, deliberately. You will know less about each thing than the person doing it, and the skill becomes asking the question that reveals whether they have thought about it rather than knowing the answer.
• Decisions are made with less information than you are used to, because gathering it fully no longer scales. That is uncomfortable and it is the job.
• Communication becomes the bottleneck. A correct decision that is not understood does not get implemented, and the translation into each audience's vocabulary is now part of the work rather than an overhead on it.

The specific traps

• Continuing to do the interesting technical work, which starves the team of it and starves the leadership role of attention. The signal is that you are the bottleneck on something and enjoying it.
• Reviewing everything, which becomes a queue and does not scale. Delegate the decision, not just the task, and accept a worse decision made faster by someone closer to it.
• Solving problems rather than building capability. A team whose problems are always solved by one person does not develop, and the leader becomes permanently necessary — which is a failure disguised as indispensability.
• Losing technical credibility entirely. Enough contact with the work to ask good questions is necessary; the balance is difficult and it is worth being deliberate about.

What the role is actually for

Making the expensive decisions well, and making the cheap ones fast by devolving them. Plus the things nobody else is positioned to do: seeing across teams, connecting engineering to the business, and spending credibility on the small number of occasions where the answer must be no.

The measure

Whether the group makes better decisions when you are not in the room. A team that cannot proceed without the leader has a leader who has been solving rather than enabling — and that is measurable by simply being absent for a fortnight.