Nobody tells you how abrupt the shift is. One week you are doing the work. The next, your job is to make sure other people do it well. The skills that got you promoted, like technical depth, speed of execution, and individual output, are now secondary. What matters now is how clearly you communicate, how well you listen, and how effectively you remove obstacles for the people around you.
The biggest trap in the first 90 days is trying to succeed at the old job while also doing the new one. You cannot do both well. The sooner you accept that your output is now your team's output, the better.
Your job has completely changed
As an individual contributor, success was visible and immediate. You shipped things, solved problems, got feedback quickly. Management is slower and less direct. You are now working through other people, which means your impact is harder to measure and often delayed by weeks or months.
This is uncomfortable. The instinct is to jump back into doing, to pick up tickets, write the code, answer the support query yourself. Resist it. Every time you step in and do the work, you are signalling that you do not trust your team to do it, and you are depriving them of the space to grow.
Your new job is to set direction clearly, create conditions for good work, remove friction, develop people, and make the right calls when the team is stuck. That is it. The sooner you internalise the shift, the sooner you start getting good at it.
The first 30 days: listen more than you act
New managers often feel pressure to show results quickly. The best thing you can do in the first month is almost the opposite: ask questions, shut up, and learn. You do not yet understand the dynamics, the history, or the informal power structures. Acting too fast without that context is how you break trust before you have even built any.
Schedule a 1-1 with each person in your team within the first two weeks. Not a formal performance review, just a conversation. Ask them what is going well, what is getting in their way, and what they wish the team did differently. You will learn more in those conversations than in any amount of observation.
- Understand motivationsWhat does each person want from this role? What does growth look like for them? You cannot manage people well without knowing what they care about.
- Map relationshipsWho works well together? Where is there friction? Understanding the informal dynamics helps you see what is actually going on, not just what appears to be.
- Find the real blockersAsk what is slowing people down. The answers are rarely what you expect, and removing one real blocker can improve output more than any process change.
- Spot the unwritten rulesEvery team has norms that nobody has written down, like how decisions get made, who the informal leads are, and what is considered acceptable to raise. Learning these early prevents avoidable mistakes.
Building your operating rhythm
Good management is largely about consistency. The people on your team need to know when they will hear from you, what to expect from each interaction, and that the commitments you make will be kept. That requires a reliable rhythm, a set of recurring interactions that happen regardless of how busy things get.
Start with the basics: a regular 1-1 cadence for each person on your team (fortnightly at minimum, weekly for direct reports who are new or working through something difficult), a team meeting that has a clear purpose and does not overstay its welcome, and a way of tracking actions that does not live in your head.
- 1
Set your 1-1 cadence
Decide on a frequency for each person and protect the slot. It does not need to be long. 30 minutes is enough. What matters is that it happens. Use it to check in, give and receive feedback, and stay connected to what the person is working on and how they are feeling.
- 2
Take brief meeting notes
After each 1-1 or team meeting, capture the key points and any actions. A few sentences is enough. The goal is to have something to refer back to next time, not to produce a document.
- 3
Track your actions
Every time you commit to something, whether that is checking on a blocker, following up with another team, or providing feedback, write it down. A single action list you actually look at is more valuable than an elaborate system you ignore.
The tools that will save you time
Management creates a specific kind of admin overhead: notes from 1-1s, actions from meetings, goals to track, patterns to spot across people. Left unmanaged, this overhead grows until it either consumes your time or you stop tracking it, at which point things start to slip.
Manager Toolkit is built around exactly these needs. Catchups give you a place to log 1-1s with each team member, see what you discussed last time, and track actions through to completion. Meeting notes keep a record of team meetings with actions attached. Targets let you set and track development goals per person. The dashboard surfaces what needs your attention so you are not hunting for it.
The goal is not to create paperwork. It is to reduce the cognitive load of keeping everything in your head. A good system means you can walk into any 1-1 prepared, follow up on every commitment, and notice patterns before they become problems. Use Key Themes to tag patterns across conversations-if the same blocker keeps appearing, you will see it.
Manager Toolkit also includes a First 90 Days Journey-a guided pathway with milestones for each phase of the transition, so you always know what to focus on next.
Built for new managers
Get your 1-1s, actions, and team organised from day one. Free to start.