Ask a room full of new managers what scared them most in week one, and you'll hear some version of the same answer: getting caught not knowing something. That fear is aimed at the wrong target entirely. The people who actually derail in their first ninety days almost never fail because they lacked technical knowledge — they fail because they kept operating like the individual contributor they used to be, just with more meetings on the calendar.
The Fear Is Pointed at the Wrong Target
Michael Watkins named this problem two decades ago in The First 90 Days, still the reference text most executive coaches hand to first-time managers, and the core diagnosis holds up: new leaders default to the behaviour that got them promoted, which is usually deep technical competence, and they keep leaning on it long after it stops being the job. You were promoted because you were excellent at the work. Nobody warned you that being excellent at the work is now someone else's job to do, and yours is to make sure they can do it well.
This shows up in a specific, recognisable pattern. A new manager sits in on a project review, spots the flaw in someone's approach within thirty seconds, and says so — out loud, in the room, in front of the person's peers. It feels like leadership. It reads as something closer to micromanagement with extra steps, and the team notices within a week that every idea gets run through the filter of what the boss would have done instead. Andy Grove made the same point in High Output Management back when he was running Intel: a manager's output is the output of the people they manage, not their own individual contribution. If you're still generating your own output, you haven't started managing yet.
Week One Is Not for Fixing Anything
Nothing you touch in week one will be as broken as you think it is.
The instinct to prove yourself fast is understandable and almost always counterproductive. Don't touch the processes, the tools, or the team structure in your first two weeks unless something is actively on fire or genuinely unsafe — you don't yet have enough context to tell the difference between "this looks inefficient" and "this exists for a reason nobody's told you about yet."
What week one is actually for is listening — structured, deliberate listening, not the passive kind that happens by accident. Block thirty minutes with every direct report individually before the end of your first week, and ask three questions in every one of them: what's working that I shouldn't touch, what's broken that's been ignored too long, and what do you need from me that you haven't been getting. Write the answers down. You'll hear contradictions between people, and that's useful information in itself — it tells you where the previous manager's blind spots were. Two people will describe the same recurring problem in completely different terms, and neither of them will be wrong, they're just standing in different parts of the same building. By the end of week one you should have a rough map of where the actual friction sits, even if you don't yet have the standing to fix any of it.
The Skip-Level Nobody Books
One meeting new managers consistently skip, and shouldn't: a conversation with your own manager's direct reports, or with people two levels down from you, outside your immediate chain. It's uncomfortable to arrange and it pays off within a month, because it's the only channel where you hear what your own team actually thinks without your presence filtering the answer.
The First Team Meeting Sets the Tone for the Next Year
Most new managers use their first team meeting to talk about themselves — background, management philosophy, an inspirational line about "an open door policy" that everyone has heard before and nobody believes until it's tested. Spend that time differently. Say what you don't know yet, name the specific things you're planning to learn in the first month, and tell the team exactly when you'll circle back with what you've found. A team that hears "I don't have an opinion on the reporting process yet, I'll have one by week three" trusts that opinion far more than one delivered on day one with false confidence behind it.
Set one piece of process in that first meeting and only one: how you want to hear about problems. Some managers want a heads-up the moment something looks like it might go wrong; others want people to try solving it first and bring options, not just the problem. Neither approach is wrong, but leaving it ambiguous means half your team escalates too fast and burns your time on things they should have handled themselves, while the other half sits on real problems for two weeks because they weren't sure it was worth mentioning yet. Pick one and say it out loud.
Managing People Who Used to Be Your Peers
If you were promoted from within the team you now lead, the first ninety days carry a second problem layered on top of the first: the people you used to complain about deadlines with over lunch now report to you, and the dynamic has changed whether either of you admits it out loud. Book a one-on-one with each of them in your first week and say the obvious thing directly — the relationship is different now, here's what that means in practice, and here's what hasn't changed. Skipping that conversation doesn't make the awkwardness go away; it just means everyone pretends around it for three months instead of one honest ten-minute exchange.
This doesn't mean distancing yourself from people you were genuinely close with, and it doesn't mean pretending you're suddenly a different person. What it does mean is that the favour you'd have done for a friend without a second thought — covering a shift, letting a missed deadline slide, forwarding along office gossip — now needs to survive the same scrutiny you'd apply to anyone else on the team, because the first time it doesn't, everyone else notices and files it away.
The Feedback Loop You Have to Build Yourself
Nobody tells a new manager how they're doing. Your team won't volunteer it unprompted, your own manager is usually too busy to give more than a vague "seems fine" at the thirty-day mark, and the absence of complaints is not the same as things going well — it's often the opposite, because a team that's stopped bringing you problems has usually just stopped trusting you to fix them.
Kim Scott's framework in Radical Candor is built on exactly this gap: care personally, challenge directly, and — the part managers skip — ask for it back explicitly rather than waiting for it to arrive. By day thirty, ask each direct report one specific question: what's one thing I've done in the last month that made your job harder? Most people won't answer honestly the first time you ask. The safe answer is always some version of "nothing comes to mind," and taking that at face value is the mistake. Ask again at day sixty, once they've watched you sit with a piece of criticism without getting defensive about it. The second answer is usually the real one, once they've seen that the first answer didn't get held against them.
What Day 90 Actually Measures
Ninety days in, the useful question isn't whether you've hit some symbolic milestone — it's whether your team is making decisions without waiting for you to weigh in on everything. If every choice, however small, still routes through you for approval, that's not evidence of a tight ship. It's evidence that you haven't yet handed over the judgment calls that were the whole point of hiring capable people in the first place.
Watch for one specific signal: does someone on your team disagree with you in a meeting, in front of others, without flinching? The first time that happens and you don't punish it — even subtly, even just with a slightly cooler tone for the rest of the conversation — is usually the moment the team decides you're safe to be honest with. Everything else in the first ninety days is preparation for that one moment.