Operations Leadership & Org DesignTemplate3 min readUpdated September 2026

The First 90 Days of a New Operations Manager: A Working Plan

A 30-60-90 day plan for a new operations manager moves in three steps: learn how work really flows in the first 30 days, fix one or two visible problems by day 60, and own a running operating rhythm by day 90. The plan should end with the manager presenting a 12-month priority list, not just a list of completed tasks.

The plan below is written for a small or mid-sized company. Adjust the specifics to your industry, but keep the order, since learning before fixing is what prevents expensive mistakes.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What should happen before day one?

The plan starts before the start date. The median time to fill a nonexecutive role is 44 days according to SHRM's 2025 benchmarking1, so by the time someone joins, the team has been waiting for help for over a month and expectations run high. Set them straight early.

Before the first day, do these things:

  • Write down the three outcomes you hired them for, taken from the job description.
  • Set up accounts, tools and calendar invitations so they aren't waiting on IT.
  • Prepare a short reading pack: org chart, top customer list, vendor list, recent metrics and any existing process documents.
  • Book the first two weeks of meetings with team leads, key vendors and two or three customers.

How should the first 30 days go?

The goal is to see the business as it actually works. Resist fixing anything yet. The new manager should:

  1. Shadow each function for at least half a day, and follow one order or job from start to finish.
  2. List the top ten recurring processes, and note who does each one, how long it takes and where it breaks.
  3. Sit in on customer calls or read recent complaints to learn where the customer feels friction.
  4. Collect baseline numbers for the outcomes they own, such as on-time delivery, backlog, or cost per job. Record how each is measured today, even if the method is rough.
  5. Hold one-on-one conversations with every direct report and with each executive they support.

By day 30, they should share a short written summary of what they found: what works, what's fragile, and three things they'd look at first. Don't ask for solutions yet, ask for observations.

What belongs in days 31 to 60?

Now the manager picks a small number of changes and proves they can deliver. Choose one problem that customers or staff would notice within a month, and one that removes recurring firefighting.

A useful pattern is to run each change as a small experiment. Define the problem in a sentence, agree the measure with the executive sponsor, make the change for a defined period, and review the result. Say the problem is late deliveries caused by handoffs between sales and scheduling. A daily ten-minute handoff review, tried for four weeks, is a change you can measure and reverse.

In the same window, the manager should begin documenting. Pick the two processes that break most often and write them up as short procedures the team can follow. If you keep procedures in a shared workspace like Notion or a training tool like Trainual, they'll stay findable.

How do days 61 to 90 turn into ownership?

This phase is about rhythm and direction. By now the manager knows enough to set the operating cadence: a weekly team meeting with a fixed agenda, a monthly review of key numbers, and a clear way to raise problems. Build the cadence deliberately instead of letting meetings accumulate.

By day 90, the manager should present:

  • Results from the changes made, including any that didn't work and what they learned.
  • An updated view of the top risks, such as key-person dependencies or single-vendor exposure. The business continuity plan template is a useful lens here.
  • A proposed 12-month priority list with owners, rough effort and expected impact.
  • A recommendation on what to hire, buy or stop doing.

That presentation is the real deliverable. It tells you whether you hired someone who can set direction.

What checkpoints keep the plan honest?

Put these on the calendar in advance:

  • Weekly 30-minute one-on-one with the person they report to, focused on what they learned and where they're stuck.
  • Day 30 review, covering their written findings and whether the baseline metrics are agreed.
  • Day 60 review, covering what they changed, what happened, and what they'd do differently.
  • Day 90 review, covering the 12-month proposal and clear expectations for the next quarter.

If the manager reports to you, your part matters too. Introduce them to the team, be clear about what decisions they own, and don't reverse those decisions in private. A new manager who gets overruled twice in the first month usually stops making decisions.

For onboarding tasks beyond the operations role, borrow from the 30-day employee onboarding checklist, and use a tracker such as Asana to hold milestones and owners for each phase.

Executive Capability Standard

What Good Looks Like

A written 90-day plan with learning, fixing and owning phases, agreed baseline metrics, scheduled reviews, and a 12-month proposal as the final deliverable.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read the role's first-year outcomes and decide what a new hire would need to learn before they could deliver each one.
2. Do Manually:Write a three-phase plan with specific actions and a review date for each phase, and share it before day one.
3. Delegate:Assign a manager or executive sponsor to run weekly one-on-ones and the three reviews.
4. Automate:Track milestones and owners for each phase in a task board so progress is visible without a status meeting.
5. Buy:Use an onboarding platform once you're hiring often enough that each plan should be generated from a template.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Trainual

Fits when you want the new manager's playbooks and the processes they document kept in a searchable training library.

Visit Trainual→
Asana

Fits when you want the 30-60-90 milestones and their owners tracked on one board.

Visit Asana→

Frequently Asked Questions

What is a 30-60-90 day plan?

It's a written plan that divides a new hire's first three months into three phases with specific goals. Typically the first phase is learning, the second is contributing early wins, and the third is taking ownership. It gives both the manager and the new hire a shared definition of progress.

Should a new operations manager change things in the first month?

Usually not. The first month is for observation, so they understand how work actually flows before changing it. Small fixes for obvious problems are fine, but larger process changes made without context often break something. Save changes for days 31 to 60.

Who should write the 30-60-90 day plan?

The hiring manager should write the first draft, based on the outcomes for the role, and the new hire should refine it in the first week. Co-writing it builds ownership, and it lets the new hire flag anything unrealistic before it turns into a missed expectation.

What if the new operations manager is falling behind the plan?

Talk about it early, and look for the cause. Common reasons include unclear priorities, missing access, or a plan that assumed too much. Adjust the plan if it was unrealistic, and coach on the skill gap if it wasn't. Waiting until day 90 makes the conversation harder.

Sources

Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.

  1. Median time-to-fill, requisition open to offer accepted (SHRM 2025). SHRM 2025 Recruiting Executives Benchmarking data brief (PDF), 2025.

Related Guides