Before You Change Anything: A New Manager's First Ninety Days

The first ninety days in a management role are usually described as a period for making an impact. That framing is understandable, but it can be misleading. New managers are often appointed because they have demonstrated strong individual performance, yet the skills that earned them the role are not the same skills required to lead a team. The temptation to prove oneself quickly can lead to changes that are premature, poorly understood or quietly resented.

A more disciplined approach is to treat the first ninety days as a period of structured listening. This does not mean passivity. It means gathering evidence, building relationships and understanding the team's operating context before making significant alterations. In many cases, the best early decision is to change very little while you learn.

Why the instinct to change immediately is risky

New managers often inherit teams that are functioning reasonably well. A reorganisation, a new reporting process or a fresh performance framework may be introduced with good intentions, but it can disrupt established routines before the manager understands why those routines exist. Team members may interpret early changes as criticism of their previous work or as evidence that the new manager has not listened.

The risk is heightened in UK workplaces where teams often operate with informal norms and long-standing relationships. A new manager who arrives with a list of fixes can unintentionally signal that the team's experience is not relevant. Listening first is not a soft option. It is a way of reducing the risk of expensive false starts.

Weeks one and two: listen and establish the baseline

The first priority is to meet each team member individually. A one-to-one in the first fortnight should not be a performance review. It should be a structured conversation about the work, the team and what helps people do their jobs well.

Useful template questions include:

• What are you working on at the moment, and what is going well?
• What gets in the way of your work most often?
• Which parts of the team's current routines are helpful, and which feel outdated?
• What would you want a new manager to understand in their first month?
• What support from me would make the biggest difference to you?

Avoid promising outcomes in these conversations. Listen, take notes and thank people for their candour. If you hear the same issue repeatedly, note it as a theme rather than reacting immediately.

During these two weeks, make only changes that are necessary for safety, compliance or basic operational continuity. Everything else can wait.

Weeks three and four: map stakeholders and expectations

A new manager's effectiveness depends partly on understanding who else has an interest in the team's work. Stakeholder mapping is not a bureaucratic exercise. It helps you see where expectations align, where they conflict and where communication is already fragile.

List the individuals and groups who depend on your team or whose decisions affect it. For each, identify what they need, how often they need it and what they currently think of the team. Then arrange short introductory conversations. Useful questions include:

• What does your team need from mine over the next quarter?
• Where have things worked well between us previously?
• What would you like to see improved, and what should we avoid changing?
• How would you prefer to receive updates from my team?

This stage also includes clarifying your own manager's expectations. Ask what success looks like at the ninety-day mark, which decisions you are expected to own and where you should escalate. Without that clarity, you may spend early weeks optimising the wrong things.

Weeks five and six: diagnose the team's operating rhythm

By now you should have enough information to observe rather than guess. Look at how the team actually works: meetings, handovers, planning cycles, reporting and informal decision-making. Ask whether each routine serves a clear purpose or simply persists because it always has.

Resist the urge to cancel meetings in your first month. A meeting that looks inefficient from the outside may be the main place where a junior team member learns what is happening. Observe for a full cycle before recommending changes.

This is also the point to identify recurring friction. If three people mention the same approval bottleneck, that is worth investigating. If one person is frustrated about a process, it may be a personal preference rather than a team-wide problem. Distinguish between isolated complaints and patterns.

Weeks seven and eight: choose quick wins carefully

Quick wins are useful because they build credibility and demonstrate that listening leads to action. They are risky when they are chosen to make the manager look decisive rather than to make the team's work easier.

A good quick win has four characteristics: it is low risk, visible, within your control and supported by the team. Examples might include clarifying who approves a common request, removing a redundant report, or agreeing a clearer agenda for a weekly meeting. Avoid quick wins that require significant resource, cut across other teams or quietly increase someone's workload.

Before implementing, explain what you heard, what you propose and why. For example: "Several of you mentioned that the approval process for expenses is unclear. I am going to confirm the threshold and publish a short note so everyone has the same reference point. I am not changing the policy itself." This keeps the change modest and transparent.

Weeks nine to twelve: agree priorities and communicate them

In the final month of the first ninety days, move from listening to agreeing. Summarise the themes you have heard, set out a small number of priorities and be explicit about what you are not going to change yet. This prevents the team from assuming that every issue will be addressed immediately.

A useful structure for a team conversation is: what we heard, what we will do next, what we will leave alone for now, and how we will review progress. Keep the list short. Three or four priorities are usually enough for a quarter.

Common early missteps

New managers frequently make the same errors. Reorganising before understanding the work is one. Promising changes that cannot be delivered is another. Avoiding decisions altogether is a third: listening is not the same as indecision. Over-relying on one trusted voice, usually the most confident person in the room, can also distort the picture. And neglecting the relationship with your own manager can leave you exposed when priorities shift.

The strongest first move is often restraint. A new manager who listens carefully, asks good questions and makes a small number of well-judged changes will usually earn more trust than one who arrives with a completed plan. The first ninety days are not a race to leave a mark. They are an opportunity to build the judgement that will make later changes worth making.