What the first 90 days are for

The first 90 days get talked about as if every new leader walks in blind. Sometimes that’s true. Sometimes you already know the work, and the hard part is noticing what’s actually new.

I moved countries inside the same company. The office was different. The hours were different. The way people said good morning was different. The learning curve on the job wasn’t. I was on the same tools, with the same teams. A lot of the users in the new country were people I had already supported, or worked alongside, while I was still in the country I had just left. The first week felt natural. I wasn’t learning the estate. I was learning the room.

That’s the bit I want to hold onto here. The first 90 days aren’t always a blank map. They’re the time you sort what you already know from what only looks familiar, and from what you haven’t earned yet. The aim is small and specific. Be useful to the desk before you try to change it, and earn the right to lead people who were already doing the job the day before you arrived.

Day one without the map

You start on a Monday. The place already has its heroes, its scars and its in-jokes, and you don’t get any of them yet. Someone mentions “the old way” and the room goes quiet for half a second. Your first ticket triage looks fine on paper. Your first all-hands doesn’t land the way you practised it.

That’s normal. You’re an outsider leader, hired for what you did somewhere else and dropped into a team that already has its own version of the truth.

The first 90 days aren’t for transforming anything. They’re for earning the right to change things without becoming the person who “doesn’t get how we work here”.

Trust isn’t built at a town hall

I’ve spent 13 years moving between technical support, systems administration, network engineering and operations. Each move meant walking into a team that already had its own way of doing things, and I had to learn that way before I’d earned the right to change any of it. Now I lead a service desk spread across EMEA and APAC, and every year I watch new starters and new managers go through the same thing.

Process posts will tell you to map the value stream. That’s fine, but it’s only half the picture. What earned me trust early was simpler:

  • Listen where the work happens. Sit with L1 and L2 on real tickets, not a curated demo. Ask what they try three times before they escalate, and what they never write down because “everyone knows”.
  • Admit what you don’t know. “I need the map” goes down better than fake certainty. People forgive a new leader for not knowing things. They don’t forgive one who rewrites a runbook before living through a single Monday with it.
  • Protect whoever tells you the hard stuff. If the first honest message about a broken VIP path gets punished, all you’ll hear from then on is green.
  • Fix something that removes pain. Skip anything that only proves you’ve arrived. It might be a clearer handoff note, a named owner for a recurring failure, or screenshots that match the console people actually use. Keep it small, visible and useful to the desk.

Charisma won’t cover for a lack of credibility. Credibility is a pile of small promises kept in front of the people who pick up the queue at 2am.

Three ways outsiders go wrong

Three traps come up fast.

The reformer. You bring a framework from your last job and start renaming queues in week two. What the team hears is that their history doesn’t count. The pushback you get isn’t politics. It’s memory protecting itself.

The tourist. You spend 90 days in leadership meetings and vendor calls and never sit on the desk. You leave with a strategy deck and no allies for the first Sev1 that needs a calm voice.

The silent one. You wait until you “fully understand” before saying anything, but you never fully understand. Meanwhile the team decides you’ve got no point of view, or that you’re quietly building a case for a restructure.

What works is quieter than all three. Be curious, with a spine. Learn how things really run. Hold a few non-negotiables from day one and earn the rest. Mine are:

  • no pretending a green dashboard means everything’s fine
  • no shadow VIP path
  • RCAs that actually ship a change

The team already has leaders

Some of the most trusted people won’t have your job title. There’s the analyst who knows which vendor actually picks up, and the shift lead who can calm a VIP without opening a side channel. There’s also the engineer who’ll tell you the real story of the platform without polishing it.

Find them in your first two weeks. Ask who people call when the process fails. That informal map will be more accurate than the org chart for your whole first quarter.

Then do something a lot of leaders skip, and credit them publicly when a fix works. An outsider who takes the win doesn’t get a second honest conversation.

A rough shape for 90 days

This isn’t a programme. It’s a rough order of things.

Days 1 to 30: map and listen. Find out who owns what when it breaks and where tickets go to die. Find out where VIPs go when the main path feels slow, and which metrics look green but feel wrong. Write it down for yourself, and hold off on the transformation memo.

Days 31 to 60: fix one old problem with the people who live with it. Pick something the desk already hates and see it through with them. Make the change visible, and let the story be theirs as much as yours.

Days 61 to 90: agree what comes next. By now you’ve earned enough trust to talk about the bigger things:

  • recurring issues
  • knowledge that survives the night shift
  • why users are still angry when every SLA is green

People will hear “we” instead of “the new person”.

Jump to day-90 language on day five and you’ll get polite nods and quiet workarounds.

Try this

If you’re new in a role, or about to be, don’t open with a reorg slide.

Pick one place where things already hurt. Sit with the people who deal with it. Ask them what a good outsider would protect and what a bad one would break. Then keep one small promise in the next ten working days. It could be a clearer path, a named owner, or a runbook that matches reality.

That’s how you stop being “the new leader” and become someone the night shift still calls when it matters.