Your First 100 Days as a New Manager
Updated: Sep 18
You got the promotion. For a week or two, that felt like the whole point - very satisfying, genuinely deserved, possibly a small celebratory dinner involved. Then Monday came round again, your calendar filled up with one-to-ones you don't quite know how to run yet, and it hit you: nobody actually told you how to do this part.
That's normal. Almost nobody is properly prepared for the jump into management - it's treated as a reward for doing the old job well, not as a different job in its own right. It is a different job. Here's how to think about the first stretch of it.
What's actually changed
The title changed overnight. The skills you actually need don't arrive that fast. Michael Watkins, whose work on leadership transitions is still the standard reference on this after two decades, calls this a transition trap: relying on what made you good at your old job, in a role where those same instincts can quietly work against you. The attention to detail that made you an excellent individual contributor can tip into micromanagement the moment you're responsible for other people's work instead of just your own.
It's a quieter shift than it sounds. Your work used to be the visible product - you could point to what you'd made, fixed, or delivered. Now the team's work is the product, and being helpful means making things clearer for other people rather than doing the task yourself. You used to be judged on your own output. Now you're judged on outcomes you don't directly control. That's a genuinely strange adjustment, and it's worth naming rather than quietly struggling through it.
There's a second trap worth naming early: the pull to act before you actually understand what's going on. New managers often feel they need to prove themselves fast, so they start changing things in week two - before they've properly understood why things are the way they are, which, to be fair, is sometimes 'nobody's quite sure, we've just always done it like this.' Watkins calls it the action imperative, and it's one of the more common ways good people get off to a rocky start.
Why this period matters more than it feels like it should
It's tempting to treat the first few months as a quiet settling-in period before the real work starts. Watkins' central argument - and it's held up well - is closer to the opposite: small decisions made early on have a disproportionate effect on how the rest of your tenure goes. People form their view of you as a manager early, and it's slow to shift once it's set.
There's a telling pattern in how executive search consultants talk about this. When they ask candidates what they'll do in month one, the weaker answers start with 'I'll change' or 'I'll implement.' The stronger ones start with 'I'll listen,' 'I'll observe,' 'I'll build relationships.' The difference isn't caution for its own sake — it's that you genuinely cannot make good decisions about a team or a process you don't understand yet, no matter how good your instincts were in your last role.
The first 30 days: three questions worth asking yourself
Observe before you act. Meet people properly, not just to tick a box - a five-minute hallway hello does not count as "getting to know the team," however efficient it might feel. Resist the urge to change anything meaningful yet, even if you can already see three things you'd do differently on day one. You will still be allowed to fix them in week six.
Three specific questions are worth carrying through this period, more useful than a generic "get to know the team" instinct:
"What does this team actually exist to do?" - obvious on paper, but teams often carry quietly conflicting assumptions. One person thinks speed matters most, another thinks quality does, a third thinks the real job is keeping a demanding stakeholder calm. Left unspoken, that mismatch makes a team feel messy even when everyone's trying hard.
"What's working better than people admit?" - new managers are trained by instinct to hunt for problems. Strengths matter just as much, and disturbing something that's quietly working well is a classic, avoidable early mistake.
"What's harder than it needs to be?" - look for the friction: unclear handoffs, meetings people dread, an approval step nobody can actually explain.
Work out what situation you've actually walked into, too. Watkins' STARS framework is a useful shorthand - are you stepping into a team that's fundamentally healthy and just needs steady leadership, or one that's genuinely struggling and needs a proper turnaround? Treating a struggling team like it's fine, or a stable team like it's in crisis, are both common and avoidable mistakes.
Days 31 to 60: put the working agreement in writing (or at least out loud)
Once you've actually listened, patterns start to show up. This is where you set expectations - and new managers often avoid it because it feels controlling. It isn't. Unclear expectations aren't kind. They just move the discomfort further down the road, usually into a surprise conversation nobody enjoys.
It doesn't need to be a formal document, a proper conversation covers most of it. Four things are worth being explicit about: how you'll communicate (what deserves a message versus a meeting versus nothing at all), how decisions actually get made (which ones are yours, which belong to the team, which need input but not consensus), what "good" looks like in practice (with real examples, not just the word "quality"), and how you'll give and receive feedback, small and often. Rather than saved up for one big uncomfortable conversation later.
This is also usually where you need to have the conversation about former peers, if you're now managing people who were recently on your level. Don't pretend nothing's changed. It has. You can still be warm, you just can't be the same kind of insider you were before. A simple, slightly awkward sentence tends to do more work than an elaborate one: "I know this has changed things a bit. I still want us to work well together, and I also need to be fair and clear in the manager role." Say it anyway. Awkward clarity beats comfortable confusion.
Days 61 to 100: a few careful changes, not a relaunch
Look for a small number of early wins. Not sweeping change - visible, credible progress on something that matters, small enough to deliver properly and real enough that people notice. Trust gets built through consistent small proof, not through a big opening statement of intent. Nobody has ever been won over by a first-week email titled "My Vision For This Team."
A good change at this stage passes three tests: it solves a real problem (not just something you personally find annoying), it's small enough to actually finish, and it teaches you something about how the team responds to change. Resist the urge to remake the team in your own image - people don't need to work exactly like you to do good work, and flattening those differences isn't the job. Helping them contribute well is.
This is also where delegation starts to matter properly. Most new managers get it wrong in one of two directions - handing off a task with almost no context and feeling disappointed when it comes back wrong, or over-specifying every step until the other person is just a pair of hands rather than an owner. A handoff genuinely lands better when it's explicit about the outcome you actually need, why it matters, the boundaries to work within, when you'll check in, and - the bit people skip - exactly how much authority they have. Are they gathering options for you to decide? Making a recommendation? Owning the call outright? Say which one.
Have the conversations you'd normally skip
Sit down with your own manager and actually align on how success will be measured, not just assume you both mean the same thing by it - you'd be surprised how often you don't. Ask what resources you genuinely have. And don't only build relationships upward - the peer relationships outside your direct reporting line matter more than most new managers expect, and they're the ones most often neglected, usually because there's no calendar invite forcing you to bother.
One of the conversations people put off longest is a genuine performance concern - hoping, quietly, that it resolves itself. It rarely does. It's much easier addressed early, in plain, specific language, without diagnosing motives you can't actually know. Something like: "I noticed the last three updates came in after the deadline. That made it harder for the rest of the team to plan around it. For the next cycle, I need it by Wednesday at noon - is anything getting in the way of that?" That's a considerably easier conversation than the one you'd otherwise have two months later, when "a bit behind" has quietly become "not reliable."
"I've written separately about how to approach the conversation you've been avoiding, since it's the single thing new managers put off longest."
The part a framework can't do for you
None of this is complicated to read. It's harder to actually do, especially the first time, and especially when you're managing people who used to be your peers, or inheriting a team whose history you weren't part of. A framework gives you the shape of it. It doesn't tell you exactly what to say in your first one-to-one with someone who applied for your job and didn't get it, or how to handle the week everything you were told about the team turns out to be wrong.
That's usually where the real value of talking it through with someone else comes in -not another framework, just an honest sounding board for the specific, messy version of this you're actually navigating. If you want structured support through exactly this kind of transition, that's what Business Coaching is built for.
If this has resonated, Michael Watkins' "The First 90 Days" is worth reading in full - the ideas here are a small slice of a much fuller framework.
Frequently asked questions
Do I need to make changes right away to prove myself?
No - and doing so is one of the most common mistakes new managers make. Acting before you understand the situation properly tends to cost more credibility than it builds. Slower, informed action beats fast, uninformed action almost every time.
What if I'm managing people who used to be my peers?
It's one of the more common, and more excruciating, versions of this transition. It's worth naming directly with the people involved rather than pretending nothing's changed - most people respond better to honesty about the shift than to it going unspoken, even if the conversation itself is a bit awkward.
How long does it actually take to feel properly settled?
Longer than most people expect, and that's normal. This is genuinely a matter of months, not weeks - feeling unsteady at six weeks in isn't a sign you're behind, it's roughly on schedule. If you're still waiting to feel like you know what you're doing, join the club; it's a large one, and the coffee's decent.
Comments