Becoming a First-Time Manager: A Practical Guide to the First Year
Becoming a first-time manager means moving from being responsible for your own work to being responsible for other people.
You become responsible for their work, development and wellbeing. It is less a promotion than a change of job.
Many new managers were chosen because they were good at the work.
The first year is mostly about learning that the work has changed.
This guide covers:
- what changes
- what to stop doing
- how to run one-to-ones and give feedback
- how to make it safe for your team to speak up
- how to learn from the hard parts
- how to work with your own manager
What actually changes when you become a manager?
Linda Hill followed 19 new managers through their first year.
She concluded that becoming a manager is an identity transformation, not just the acquisition of new skills.
Her book on that study first appeared in 1992 and was revised in 2003.
The practical point is that the difficulty is rarely a missing technique.
It is that the things that made you feel competent and valued have changed.
In practice, four shifts come up again and again:
- From doing to getting work done through others. Your own output matters less; the team’s matters more. New managers can feel unproductive for months. The hours that used to feel like real work are gone.
- From expert to manager of experts. You may no longer be the best person at the task. Someone on your team may soon be better than you were.
- From control to influence. The title gives you less control than you expected. People still decide how hard they try, what they tell you and whether they stay.
- From peer to boss. If you were promoted from within the team, relationships change. Conversations stop when you walk in. Friends become people whose pay you influence.
What should you stop doing first?
Start by looking at where your time actually goes.
Take last week’s calendar and sort it into three piles:
- hands-on work you did yourself
- work with and for your team
- work upward or across the organization
You may find the first pile is still the biggest.
Then pick one task to hand over.
A good first candidate is something you still do well, that someone on the team could own. It should also help them grow.
Avoid handing over only the tasks nobody wants.
People notice, and they learn nothing from it.
A handover that sticks has four parts:
- The outcome, described so the other person can tell when it is done.
- The deadline, and how much it matters if it slips.
- The decisions that are theirs, and the ones they should bring to you.
- A check-in point, agreed in advance, so you are not tempted to hover.
Expect the first result to be different from how you would have done it.
Decide beforehand what good enough looks like.
The urge to take the task back is normal. Resisting it is most of the skill.
How do you run one-to-ones and give feedback?
Regular one-to-ones with each person on your team are where most of your work with people happens.
A simple structure works: their topics first, then current work and priorities, then development or feedback.
Keep the rhythm reliable.
A cancelled one-to-one sends a message about whose time matters.
For feedback, a widely used practice framework from the Center for Creative Leadership is SBI.
You describe the situation, the behavior you observed, and its impact.
“In yesterday’s client call (situation), you answered the pricing question before checking with finance (behavior), and we now have to go back with a different number (impact).”
It keeps feedback about what someone did rather than who they are.
It works just as well for positive feedback.
Feedback also has to flow toward you.
Your team sees your management every day; you mostly do not.
Ask one person at a time, about one specific thing, soon after it happened.
“What is one thing I could do differently that would make your work easier?”
That question gets more honest answers than “any feedback for me?” asked in a group meeting.
When you get an answer, thank them, and do not argue in the moment.
How do you make it safe for your team to tell you things?
Amy Edmondson’s research on work teams describes psychological safety as a shared belief that the team is safe for interpersonal risk-taking.
In a study of 51 manufacturing teams, it was associated with team learning behavior.
Psychological safety does not mean everyone is comfortable, or that standards drop.
It means people raise problems, ask for help and admit mistakes. So you hear about them while they are still small.
As a new manager you shape this more than you might think:
- Your first reaction to bad news. If the first few seconds are irritation, people learn to wait. Thank the person for raising it, then ask what they know.
- Your own mistakes. Saying “I got that wrong” in front of the team makes it easier for them to do the same.
- Who gets heard. Notice who speaks in meetings and who does not. Ask the quiet ones directly, often in their one-to-one.
How do you handle your first difficult conversation?
Many first-time managers have one conversation they are putting off.
It may be a performance problem, a former peer’s behavior, or a decision the team will not like.
Delay usually makes it harder.
Prepare three things.
First, the facts, in the situation, behavior and impact shape above.
Second, the outcome you need from the conversation.
Third, what you want to understand from their side, because you rarely have the whole picture.
Write your first two sentences and say them aloud once.
Then stop rehearsing and plan to listen.
Know where your role ends.
If the situation involves misconduct, discrimination, health or a possible legal issue, involve your manager or HR before you act.
A better script is not the answer to a formal problem.
How do you keep learning during the first year?
Much management learning happens on the job.
Morgan McCall, Michael Lombardo and Ann Morrison studied how successful executives developed.
They found that it came mainly from challenging assignments, from other people (especially bosses) and from hardships.
But experience alone does not guarantee learning.
Two frameworks help turn it into learning.
David Kolb’s experiential learning cycle describes four stages:
- a concrete experience
- reflecting on it
- drawing a general lesson
- trying that lesson out in a new situation
Susan Ashford and Scott DeRue describe a similar cycle they call mindful engagement.
You approach a challenge with a learning goal and act by experimenting and seeking feedback. Then you reflect on what happened.
In practice:
- Choose one stretch assignment in the next few months: a first hire, a project with a difficult stakeholder, a budget, a reorganization.
- Name what you want to learn from it, as a capability rather than a result. “Learn to run a hiring process without second-guessing the panel” rather than “fill the role.”
- Ask one person to watch and tell you how it went.
- Write a short note afterwards: what happened, what you noticed in yourself, what you will do differently.
How do you work with your own manager?
Your manager is one of your main sources of learning and one of your main constraints.
Find out how they prefer to hear news, in writing or in person, and how often.
Learn what they worry about, and take something off their plate.
Bring problems with a proposed solution.
Ask directly for the decisions and support you need.
Agree what success in your first six months looks like, so you are not guessing.
If you disagree with them, say so privately and early, with your reasoning.
Then commit to the decision that is made.
Your team will watch how you talk about your own boss.
What does this look like for different new managers?
Three illustrative examples, composites rather than real people or case studies.
An engineer promoted to lead the team she was part of.
- Situation: five former peers, one of whom also applied for the role. She still writes much of the hardest code.
- First moves: a one-to-one with each person, starting with the colleague who applied. She asks what they need from her now. She hands over code review for one service to a senior engineer. There is a clear standard and a check-in every two weeks.
- What she learns: her week feels less productive for two months, and the team’s output does not drop.
A sales lead given a team of six, two of them more experienced than him.
- Situation: he is tempted to step into every difficult deal himself.
- First moves: he uses SBI to give one experienced rep specific feedback on a lost deal. He asks each rep, one at a time, what he could do to make their week easier. One answer: stop rewriting their proposals.
- What he learns: the experienced reps need him to clear obstacles, not to coach them on selling.
A nonprofit program coordinator stepping into the director role as the founder leaves.
- Situation: a small staff and a large volunteer group, many of whom joined because of the founder.
- First moves: she asks the board chair what they expect in the first six months. She picks one stretch assignment (the annual funding application) with a learning goal. A board member will give feedback on it. She also holds a first difficult conversation with a long-serving volunteer whose role is changing.
- What she learns: volunteers raise problems only when she asks them directly. So she adds a short question to every volunteer check-in.
How do you use this with your mentor?
A mentor who has managed people and sits outside your reporting line is a good place to work through the first year.
Some ways to use this guide together:
- At the first meeting, describe your team and what has changed. Rate your confidence in leading it on a 1 to 5 scale. Write a goal you can check; setting goals with your mentor shows how.
- Bring evidence, not summaries. Last week’s calendar, the feedback you owe someone, the note you wrote after a hard conversation. Preparing for a mentoring meeting covers what to bring.
- Rehearse. Ask your mentor to play the team member while you open a feedback or difficult conversation.
- Debrief the hard parts. After a stretch assignment or a difficult conversation, walk through what happened. Then talk about what you would do differently.
- Be clear about limits. Your mentor can help you think and prepare. They cannot manage your team, speak to your boss for you or replace HR.
If your organization is setting up a program for new managers, the guide to leadership mentoring programs covers program design.
Sources
- Hill, L. A. (2003). Becoming a Manager: How New Managers Master the Challenges of Leadership (2nd ed.). Harvard Business School Press. First edition: (1992). Becoming a Manager: Mastery of a New Identity.
- McCall, M. W., Lombardo, M. M., & Morrison, A. M. (1988). The Lessons of Experience: How Successful Executives Develop on the Job. Lexington Books.
- Ashford, S. J., & DeRue, D. S. (2012). Developing as a leader: The power of mindful engagement. Organizational Dynamics, 41(2), 146-154. doi:10.1016/j.orgdyn.2012.01.008
- Kolb, D. A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Prentice-Hall.
- Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. doi:10.2307/2666999
- Weitzel, S. R. (2000). Feedback That Works: How to Build and Deliver Your Message. Center for Creative Leadership. Practice framework (SBI); a second edition appeared in 2019.