Your output is now your team's output

You will be able to describe what a manager's job produces and audit your own time against it.

Most new managers get the job because they were good at the old one. You wrote the cleanest code, closed the most cases or kept the angriest client happy, and someone decided you should now do that through other people. Nobody mentions that the skills which got you promoted are not the skills the new job runs on.

Here is the shift in one sentence. As an individual contributor, your output was your own work. As a manager, your output is the output of your team, plus whatever you influence beyond it. Andy Grove, who ran Intel, put it close to that in High Output Management, and Julie Zhuo says much the same in The Making of a Manager: your job is to get better outcomes from a group of people working together.

That sounds obvious until you look at your calendar. In the first months, most new managers keep doing their old job and add the management on top. They take the hardest tickets themselves because it is faster. They rewrite a report instead of explaining what was wrong with it. They stay late fixing things, feel productive, and wonder why the team is not getting any better.

The trap is that doing the work yourself feels like progress, and managing does not. A one-on-one where someone talks through a problem produces no visible output. Explaining a task you could finish in twenty minutes takes forty. The payoff comes weeks later, when that person can do it without you, and by then you have forgotten it was your doing.

So the first change is in how you judge a good day. A good day is no longer one where you shipped a lot. It is one where someone on your team got unstuck, made a decision they would have escalated last month, or knew exactly what mattered this week because you told them. Your work becomes conversations, decisions and clarity, and the results show up in other people's work.

Zhuo describes three things a manager works through: purpose, people and process. Purpose is whether the team knows what it is trying to achieve and why. People is whether you have the right people in the right roles and whether they are growing. Process is whether the way the team works together helps or gets in the way. When something goes wrong on your team, it is almost always a problem in one of these three, and naming which one tells you where to start.

There are things you should keep doing yourself. Most first-time managers lead small teams and still carry some hands-on work, and that is fine. The test is whether your own work is crowding out the work only you can do: the one-on-ones, the hard feedback, the decisions about priorities. If those are slipping because you are busy being the best individual contributor on the team, you have the balance wrong.

Expect this to feel uncomfortable for a few months. You will be slower at things you used to be fast at, and you will lose the daily proof that you are good at your job. That is normal. The managers who struggle longest are the ones who keep reaching for the old proof instead of building the new kind.

Your task for this lesson is a calendar audit. Look at the last two weeks and mark every block as either doing, which is work you would have done in your old role, or managing, which is one-on-ones, planning, feedback, hiring and unblocking others. Add up the hours in each column. Then pick one recurring piece of doing that someone on your team could take on, and write down who.

Mark every calendar block from the past two weeks as doing or managing, total each column, and name one recurring task to hand over.

Course

• First-time manager