Goal
Become a good manager in my first year
You become a good manager in the first year by accepting that the job changed: from doing the work to getting better outcomes from the people who do it. Then build five habits early: a listening tour before any change, regular one-on-ones on each person's agenda, feedback that is immediate and specific in both directions, decisions delegated with stated intent, and a team that argues in the room and commits afterwards. None of it needs charisma. All of it needs a calendar.
What is really going on
The promotion came because you were the best at the work, and nobody told you the work is no longer the job. So the first months go to the tasks you know: the hardest ticket, the biggest client, the late-night fix. It feels productive and the team learns to wait. By Grove's arithmetic your output is now what they produce, and a week in which you finished everything and they finished nothing was a week of negative leverage.
The second failure is silence. The team were peers last month, you like them, and the honest sentence about the missed deadline or the presentation that lost the room feels unkind, so it is not said. Kim Scott calls it ruinous empathy and writes that it accounts for the vast majority of management mistakes she has seen. The person is denied the one thing they would need in order to change, and is surprised a year later by a review, a passed-over promotion or an exit.
The third is the queue. Tasks get delegated and decisions do not, so every choice still passes through you, and the team does what it is told and waits at the door. Meetings are polite, decisions are unanimous and quietly not carried out, and the argument happens in private messages afterwards. Each of these is fixable in a week, and the five books below are the fixes, in order.
Five ideas from five books
- 1
Redefine the job before you do anything else
Julie Zhuo's definition is the one to write on the first page: a manager's job is to get better outcomes from a group of people working together, through purpose, people and process. The measure is what the team produces because of what you did, not what you finished. A practical test is your calendar: if it is full of the tasks you used to do, the transition has not happened. Start by listing three things you did this week that were still the old job, and hand one over on Monday. Then, when something goes wrong, ask which lever failed (purpose, people or process) and fix the lever rather than the person.
- 2
Listen for two weeks before you change anything
Michael Watkins's rule for the transition is to learn before acting, because the first weeks are when you know least and are watched most. Book thirty minutes with every person on the team and ask the same four questions: what is working, what is not, what would you change if you were me, what should I not touch. Ask your manager what success looks like at ninety days and write it in their words. Then pick one early win the team already wanted, a blocker removed or a decision unstuck, and deliver it. It buys the credibility that the harder changes will need.
- 3
Make the one-on-one their meeting, and keep it
Andrew Grove treats the one-on-one as the subordinate's meeting: their agenda, their problems, most of the talking theirs, with you listening and asking one level deeper. He set the frequency by experience (weekly for someone new to the work, every few weeks for a veteran) and wanted each to last at least an hour. Never cancel one lightly, because a cancelled one-on-one tells the person they matter less than whatever replaced it. Grove's rule of thumb is that ninety minutes can improve the quality of someone's work for two weeks, which makes it among the highest-leverage hours you have. It is also where caring is proven, so that the hard feedback later lands on trust rather than on air.
- 4
Say the hard thing, early, to their face
Kim Scott's two axes are care personally and challenge directly, and the most common failure is caring without challenging: the silence that feels kind while someone fails slowly in public. Her sequence starts with asking for criticism before you give it, so the loop runs both ways. Then give it immediately, in private, specifically and about the work, with the reason you are saying it: because you want them to succeed. Praise in public the same day, naming exactly what was good. The test of whether it worked is plain: did it change what the person did next?
- 5
Delegate the decision, not just the task
David Marquet stopped giving orders on a submarine and got a crew of leaders. His mechanism was language: instead of asking permission, people say 'I intend to', with their reasoning, and the leader answers 'very well'. Pick one decision you currently approve, hand it to the person closest to it, and ask to hear the intention and the reason for two weeks. Then build the two pillars that make it safe: competence, by having people explain what they will do before they do it, and clarity, a goal so plain that the team can decide without you. Lencioni's commitment layer adds the closing ritual: decisions read aloud with owners and dates, and everyone, including those who lost the argument, committing.
Try this today — free
Today, write your new job in one sentence and list three things you did this week that were still the old job. Then book a thirty-minute one-on-one with every person on your team for the next two weeks, on their agenda.
Questions people ask
- What should a new manager do in the first month?
- Learn before acting: a listening tour with the same four questions for everyone, a conversation with your manager about what success looks like at ninety days, and one early win the team already wanted. Change nothing structural unless it is on fire. Start one-on-ones in week one; they are the channel everything else runs through.
- How often should I have one-on-ones?
- Grove's answer depends on experience: weekly for someone new to the work, every few weeks for an experienced veteran, and each for at least an hour, so the difficult issues have time to come up. A new manager usually starts weekly, because the team is new to them too. Cancel one only when you would cancel a client meeting. Grove's estimate is that ninety minutes can improve someone's work for two weeks, and the message a cancelled one sends is received accurately.
- How do I give feedback to people who were my peers?
- Ask for it first, in front of the team, and act on what you hear. Then give it the same day, in private, about the work and its effect, with why you are saying it. The silence that feels kind is the most common failure of new managers; the person it protects is you, not them.
- Should I still do some of the technical work?
- Only where it is the highest-leverage use of an hour, which is rare. Doing a task yourself when someone on the team could do it with a little help, and grow from it, has negative leverage even when you are faster. Teach it once instead, and spend the hour on a decision, a one-on-one or a meeting that leaves the team aligned.
- How do I know if I am doing well as a manager?
- By what the team can do because of you. A useful Friday question: what did the team handle this week without needing me, and where did I step into work they could have done themselves? Over the months the first list should grow and the second shrink. Your own output (tickets, reports, late-night fixes) is not the measure any more.