The series

Becoming a Lead

A run of posts for the engineer who has just become responsible for other engineers, about the things that look like doing the job well and are quietly the reason you are not.

Every part of this is about the same thing, from a different angle.

You were promoted because you were good at the work. The habits that made you good at it are strong, practised and immediately available, and they are now the wrong ones. That is uncomfortable enough on its own. What makes it hard is that none of it feels like a mistake while you are making it. Keeping the difficult work looks like carrying your weight. Running a tight status meeting looks diligent. Handing something to someone you trust looks like exactly what you are supposed to be doing.

So the signal does not arrive as failure. It arrives late, from outside your own reasoning, usually from someone who had to be brave enough to tell you.

These are the ones I got wrong, what it cost, and what I would do differently. Read them in order if you have just moved into the role. Otherwise the titles are specific enough to go straight to the one you recognise.

  • Part 1 of 5

    The promotion is a career change, and nobody tells you

    You spent years getting good at one job, and on Monday you started a different one. Nobody announces the change. It took one of my reports to tell me.

    · 6 min read

  • Part 2 of 5

    What a one-on-one is actually for

    The most useful thing anyone ever told me came in a meeting I had designed to prevent it. What changed afterwards was not the agenda. It was who owns it.

    · 5 min read

  • Part 3 of 5

    Trust was not the hard part of delegating

    I handed over a monthly report to someone I trusted completely, and it still nearly went out wrong. The task went across. Everything I knew about it stayed with me.

    · 5 min read

  • Part 4 of 5

    Leading people you used to sit beside

    They went quiet, and I read it as the relationship cooling. It was the org chart arriving. I was the last person on that team to notice my job had changed.

    · 5 min read

  • Part 5 of 5

    Feedback without evidence is just doubt

    I told someone their approach worried me. I had not done the work to say why. The concern may well have been right, and that turned out not to matter at all.

    · 5 min read