Somewhere between the promotion announcement and the first team meeting, most new managers hit the same wall. The skills that got them promoted — being excellent at the actual work — are not the skills the new role actually demands. A first-time manager is suddenly responsible for other people’s output, other people’s development, and other people’s bad days, often with no formal handover and no manual. The first ninety days are where that gap either gets closed or gets papered over, and what happens in those three months tends to shape how a manager leads for years afterward.

We have worked with hundreds of first-time managers across Québec, and the pattern is remarkably consistent. The technical work rarely trips people up. What trips them up is everything around it: how to run a one-on-one that isn’t just a status update, how to give feedback without it landing as criticism, how to say no to a request from above without damaging the team below, and how to figure out, in real time, whether a problem needs to be solved by the manager or left for the team to solve themselves. None of this is intuitive, and almost none of it is taught before someone is handed the title.

Weeks 1–2: Resist the Urge to Prove Yourself

The single most common mistake in the first two weeks is trying to demonstrate value too quickly. New managers, especially those promoted from within the team, often feel pressure to show immediate impact — a new process, a reorganized workflow, a visible change that signals “things are different now.” That instinct is understandable, but it is almost always premature. A manager who has not yet mapped how the team actually works, what its real bottlenecks are, and how each person prefers to be managed is optimizing blind.

Instead, the first two weeks should be spent almost entirely in listening mode. That means individual conversations with every direct report, not just a group kickoff meeting. It means asking each person the same handful of honest questions: what is working well right now, what gets in your way, and what would you want a manager to know about how you like to receive feedback. It also means listening to peers and, where possible, the outgoing manager, to understand the history behind decisions that might otherwise look arbitrary.

Weeks 3–6: Establish the Rhythms

Once the listening phase has surfaced a real picture of the team, the next task is building the operating rhythm that will carry the rest of the manager’s tenure. This is where most of the invisible infrastructure of good management gets put in place: a consistent one-on-one cadence with each team member, a clear and predictable way that priorities get communicated, and an early, low-stakes opportunity to give feedback before any issue has had time to calcify.

One-on-ones deserve particular attention because they are the single highest-leverage habit a new manager can build. A one-on-one that is treated as a status update is a wasted half hour; a one-on-one used to surface blockers, check in on wellbeing, and build trust compounds in value every week it continues. New managers often abandon this habit under pressure, precisely when it matters most. Protecting that time, even during a busy stretch, is one of the clearest signals a team reads about whether they actually matter to their manager.

Weeks 7–10: Make the First Real Decisions

By the second month, a new manager usually has enough context to make decisions that actually change how the team operates — adjusting a process that isn’t working, reallocating a task that was landing on the wrong person, or addressing a performance concern that has been quietly tolerated for too long. This is also typically the point where the first real test of authority arrives: a decision that someone on the team disagrees with.

New managers frequently handle this moment in one of two unhelpful ways. Some avoid the decision entirely, hoping the issue resolves itself, which almost never happens and instead teaches the team that friction gets ignored rather than addressed. Others overcorrect by asserting authority too forcefully, which can work in the short term but tends to erode trust if it becomes the default style. The middle path — explaining the reasoning behind a decision, inviting genuine pushback before it is finalized, and then following through once it is made — is slower in the moment but far more durable over time.

Weeks 11–13: Take Stock and Adjust

The final stretch of the first ninety days is the right moment for an honest self-assessment, ideally supported by direct feedback from the team itself. This does not need to be a formal survey; a simple, direct question in a one-on-one — “what’s one thing I could do differently as your manager” — often produces more useful information than any anonymous form. The goal is not to catalogue every mistake from the first three months, but to identify the one or two adjustments that will have the most impact going forward.

It is also the point at which a new manager should start thinking beyond survival and toward a deliberate leadership style. Early on, most people default to managing the way they were managed, for better or worse. By the end of the first quarter, there is usually enough self-awareness and enough data from the team to start making that style a conscious choice rather than an inherited habit.

The Traps to Watch For

• Managing everyone the same way. A team is rarely made up of people who all want the same level of oversight, the same communication style, or the same kind of recognition. Treating every direct report identically usually means under-serving some and over-managing others.
• Confusing being liked with being trusted. New managers often prioritize popularity, especially when they were promoted from within a peer group. Trust is built by being fair and consistent, not by avoiding every uncomfortable conversation.
• Solving every problem personally. Jumping in to fix things feels productive, but it quietly signals to the team that their manager doesn’t trust them to handle their own work, and it makes the manager a bottleneck.
• Waiting for a “serious enough” issue before giving feedback. Small, early, low-stakes feedback is far easier to give and receive than the delayed, high-stakes version of the same conversation three months later.

Building Confidence Before a Crisis Forces the Issue

Most of what shapes a new manager’s long-term effectiveness gets decided quietly, in the ordinary weeks of the first quarter, long before any dramatic crisis puts their leadership to the test. It is tempting to think that confidence comes from surviving a hard moment — a difficult client escalation, a team conflict, a resignation nobody saw coming. In reality, managers who handle those moments well are almost always the ones who built a foundation of small, repeated wins in the ordinary weeks beforehand: a one-on-one where someone opened up about a real blocker, a piece of feedback that was received well, a decision that turned out to be the right call. Confidence built this way tends to be sturdier than confidence built by surviving one big test, because it rests on a pattern rather than a single data point.

This is also why the first ninety days deserve real institutional support rather than being treated as something a new manager should simply figure out. A first-time manager who is given a mentor, a peer group of other new managers, or structured training during exactly this window tends to build that foundation faster and with fewer unnecessary missteps along the way. Organizations that leave new managers entirely to their own instincts are, in effect, asking each one individually to rediscover lessons that have already been learned many times over by others in similar roles.

What to Do When the First Quarter Doesn’t Go Smoothly

Not every first ninety days goes according to plan, and it is worth saying plainly that a rocky start is not a reliable predictor of long-term failure as a manager. Some of the most respected leaders we have worked with describe their first quarter as genuinely difficult — a team that was skeptical of a new manager, a reorganization that landed awkwardly, a personal misstep that took real effort to repair. What distinguished them was not a smooth start, but how they responded once they recognized something wasn’t working: naming the issue honestly rather than pretending it away, asking directly for feedback even when it was uncomfortable to hear, and adjusting visibly enough that the team noticed the change.

If the first quarter feels rocky, the most useful question is rarely “how do I undo this,” and much more often “what is the smallest, most visible change I can make starting this week.” Teams are generally far more forgiving of an imperfect start than of a manager who seems unwilling to acknowledge that something isn’t working.

A Short Checklist for the First Day

New managers often ask what, concretely, they should do on day one, before any of the longer-term rhythms described above have a chance to take shape. A short, practical checklist helps more than a long list of principles at this stage: schedule an individual conversation with every direct report within the first week rather than relying on a single group meeting; ask the outgoing manager, if one is available, for an honest read on where each team member currently stands; resist committing to any specific changes out loud until there has been time to listen; and write down, somewhere private, the first impressions and questions that come up in week one, since they tend to be surprisingly useful reference points once the initial fog clears a few weeks later.

None of this happens automatically, and very few new managers get a genuine chance to practice these skills before they need them on the job. That is precisely the gap our Manager Development Program is built to close — not with abstract leadership theory, but with the specific reflexes a first-time manager needs in exactly this window. The organizations that invest in that first ninety days tend to see it pay back for years, in retention, in team performance, and in a manager who never had to learn the hard way.