30-60-90 day plan for operations managers
On this page
- What a new operations manager is really learning
- The 30-60-90 day plan
- The KPI baseline, done properly
- What "on track" looks like
- A filled example
- Working with supervisors who have seen managers come and go
- What the hiring manager owes the new operations manager
- Common mistakes
- Adapting the plan
- Questions people ask
An operations manager's first 90 days are judged on the floor, not in the office. The site's numbers will move with or without them, so a useful 30-60-90 day plan for the role separates what the new manager has learned about why the numbers look the way they do from what they have changed. It also has to account for shifts, supervisors who have seen managers come and go, and safety, which cannot wait for the day-30 check-in.
This plan is written for an operations manager running a site or a function with shifts, such as a warehouse, distribution center, production line, contact center floor or field-service operation. The general structure for any role is in the 30-60-90 day plan template for new hires.
What a new operations manager is really learning
Every operation has two versions: the one in the standard operating procedures and the one that actually runs. The gap between them is where the new manager's real work is, and it is invisible from reports. A picker who skips a scan because the handheld is slow, a supervisor who holds back two people from break to cover a late truck, a changeover that takes twice the documented time because a tool is always missing: these explain the KPIs better than any dashboard. The first month is about finding them, which means being on the floor, on every shift, asking why.
The 30-60-90 day plan
30-60-90 day plan — [Name], Operations Manager, [site / function]
Reports to: [name] Start date: [date] Shifts: [e.g. 2 x 10h, 5 days]
Direct reports: [supervisors / leads] Headcount on site: [N]
DAYS 1-30 — Learn the real operation; baseline the numbers
Goals:
- Work at least one full shift on every shift pattern, including nights
and weekends if the site runs them
- Complete site safety orientation and walk every area with the safety lead;
fix any immediate hazard found, same day
- One-to-one with each supervisor and lead; attend every daily start-up meeting
- Trace one order, job or unit end to end through every process step
- Reproduce the site's KPIs from source data and learn how each is calculated
Deliverables by day 30:
- A KPI baseline: last 13 weeks of each measure, with its definition and data source
- A floor-walk notebook: gaps between SOP and practice, with photos where useful
- A top-five problem list, ranked by impact on safety, service and cost
DAYS 31-60 — Run the operating rhythm; start one improvement
Goals:
- Run the daily operations meeting: yesterday's results, today's plan,
staffing, safety, blockers — in 15 minutes
- Own the weekly labor plan against forecast volume
- Pick one problem from the top five and run a structured fix with the
supervisors who own that area
- Hold the first round of supervisor one-to-ones with written notes
Deliverables by day 60:
- A daily meeting board or sheet the supervisors keep up without prompting
- An improvement plan with a baseline, a target and a measurement date
DAYS 61-90 — Own the results
Goals:
- Report the site's weekly KPIs to leadership with a cause for every miss
- Deliver the improvement and measure it against the day-30 baseline
- Close or update at least three outdated SOPs to match the improved practice
- Present a 6-month operations plan: capacity, staffing, equipment, risks
Deliverables by day 90:
- One measured improvement, held for at least two weeks
- A 6-month plan the site leader and finance partner have reviewed
Check-ins: weekly with manager; formal reviews at day 30, 60 and 90.The KPI baseline, done properly
The day-30 baseline is the most important deliverable in the plan, because every later judgment depends on it. It should cover the measures the site is already held to, not new ones. A typical set:
| Area | Example measures | What the new manager should be able to explain |
|---|---|---|
| Safety | Recordable incidents, near misses reported, open corrective actions | Whether near misses are actually reported or quietly handled on the floor |
| Service | On-time shipment or completion, on-time-in-full, backlog at shift end | Which customers or order types drive the misses |
| Productivity | Units per labor hour, lines picked per hour, jobs per technician-day | Whether the labor hours in the calculation include indirect time and temps |
| Quality | Order accuracy, inventory accuracy from cycle counts, scrap or rework rate | Where errors are caught today and how late in the process |
| Cost | Labor cost per unit, overtime hours, temp labor spend | How much overtime is planned versus reactive |
A strong baseline also says which numbers the manager does not trust yet, and why. A productivity figure that excludes temp hours, or an accuracy figure based on customer complaints rather than audits, is worth flagging before anyone is judged against it.
What "on track" looks like
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | Has worked every shift; the baseline explains the numbers with causes found on the floor; supervisors describe the manager as someone who asks before changing | Has not been on nights; the baseline is a copy of the existing dashboard; changes already announced without supervisor input |
| Day 60 | The daily meeting runs on time with supervisors reporting their own areas; the improvement has a baseline and a target | The daily meeting is a monologue; the improvement is a general "efficiency push" with no measure |
| Day 90 | One measured improvement held for two weeks or more; weekly KPI misses come with causes and actions | Numbers reported without explanation; improvements announced but reverted once attention moved |
A filled example
Operations manager: Dana Whitfield (invented), operations manager at a regional e-commerce fulfillment center, two shifts, four supervisors, around 120 staff at peak.
Day 30: Worked three day shifts, two night shifts and a Saturday. Traced orders from receiving to dispatch and found that pack stations on nights waited for replenishment because the replenishment task ran only on days. Her baseline showed night-shift lines per hour well below days, which the previous explanation had put down to staffing.
Day 60: Moved the daily meeting to a standing board at the pack area, run by supervisors. Chose night-shift replenishment as her improvement: a scheduled replenishment wave at the start of nights, agreed with the night supervisor who suggested the timing.
Day 90: Night-shift lines per hour closed much of the gap to days and held for three weeks; overtime on nights fell. Rewrote the replenishment SOP and presented a peak-season staffing plan with the finance partner.
Working with supervisors who have seen managers come and go
Supervisors and leads in an operation often have more tenure than their managers, and they have learned to wait out new ones. The fastest way to lose them is to arrive with a program from a previous site. The fastest way to earn them is to fix something that has annoyed them for months: the handheld that keeps dropping connection, the rota that always leaves one area short. The plan asks the new manager to pick the day-60 improvement from the top-five list with the supervisors who own that area. That is deliberate. An improvement the supervisors chose is one they will keep running after the manager's attention moves on.
What the hiring manager owes the new operations manager
- System access on day one: the WMS, ERP or MES, the labor management or timekeeping system, and the KPI reports with their underlying data.
- An honest account of the site's history: past incidents, any union or works-council relationships, supervisors with performance concerns, promises made to the team.
- Budget and authority limits: what the manager can spend on a quick fix, and who approves overtime and temp labor.
- A named finance partner for the labor plan and the 6-month plan.
Common mistakes
- Managing from the office. The reports show what happened, not why. A new manager who is rarely seen on the floor after week two loses the source of every useful insight.
- Skipping nights and weekends. The shifts with the least management attention often carry the biggest problems.
- Launching several improvements at once. None of them gets measured properly and supervisors cannot tell which ones matter.
- Treating safety as a later phase. Hazards found in week one get fixed in week one, whatever the plan says about waiting to change things.
Adapting the plan
- Production and manufacturing: add changeover time, OEE or downtime by cause to the baseline, and involve maintenance in the top-five list. The production supervisor screening questions cover the frontline leadership this plan relies on.
- Warehousing and distribution: add dock-to-stock time and cycle-count accuracy. The warehouse supervisor screening questions help when the new manager needs to hire leads.
- Business operations roles without a floor: replace shifts with a walk-through of each process the function owns, such as order-to-cash or procurement, and trace real transactions end to end instead of physical orders.
If the role is still open, the operations manager screening questions test for the habits this plan depends on: floor time, measuring before changing, and bringing supervisors along.
Questions people ask
Which KPIs should a new operations manager own in the first 90 days?
The ones the site is already measured on, usually a safety measure, a service measure such as on-time or on-time-in-full, a productivity measure such as units per labor hour, a quality or accuracy measure, and cost. Adding new KPIs before understanding the existing ones is a common early mistake.
How much time should a new operations manager spend on the floor?
Most of the first two weeks, including at least one full shift on every shift pattern the site runs, and a daily floor walk after that. An operations manager who learns the operation from reports misses the workarounds that explain why the numbers look the way they do.
When should a new operations manager start changing processes?
Small fixes to obvious safety issues should happen immediately. Process changes that affect how people work should wait until after the day-30 baseline, so the manager can measure whether the change helped and has the supervisors' support before rolling it out.
What if the site's KPIs get worse in the first 60 days?
Look at the cause before judging the manager. Seasonal volume, a staffing gap or a system change can all move the numbers. What matters is whether the new manager spotted the decline early, explained it, and had a response, rather than reporting it after the month closed.