30-60-90 Day Plan for Operations Managers: Example, KPIs, First Week
9 min read ยท 2026-10-25
A 30 60 90 day plan for operations manager roles splits your first three months into three jobs: learn how the operation really runs (days 1-30), fix the problems that hurt safety, service or cost the most (days 31-60), and set up the routines that keep the gains (days 61-90). Your manager wants proof that you understand the floor before you change it, and that you can move the numbers once you do.
The plan below is built for an operations manager taking over a site or a group of teams, such as a distribution center, a plant shift structure or a service operations group. It gives you a first-week list, the people to meet, the metrics to baseline, quick wins that suit the job and a filled-in example. It also shows how to turn it into a one-page plan for an interview or your first check-in with your boss.
The roadmap at a glance
Goal: By day 90, you run a daily operating rhythm, report a KPI baseline everyone trusts, and have delivered three measured improvements, with next quarter's plan approved by your manager. Duration: 90 days (13 weeks)
Week one: safety, people and rhythm (Week 1)
Get safe on the floor, meet your team and see how a normal day runs.
- Complete the site safety induction and walk every area with the safety lead, including high-risk tasks and emergency routes.
- Hold one-on-ones with each direct report: what works, what breaks, and what they would fix first.
- Sit in on every recurring meeting: shift start huddles, the daily production or service review, the weekly ops review.
- Get access to the WMS, ERP or ticketing system and to the current KPI reports.
- Shadow one full shift from start to handover.
Milestone: Every direct report met, one full shift shadowed, and a written list of the meetings and reports you now own.
Learn and baseline (Weeks 2-4)
Understand the process end to end and put a trusted number on how it performs today.
- Map the main flow on one page, from order or request in to delivery out, with handoffs and queues.
- Pull 8 to 12 weeks of history for throughput, on-time delivery, cost per unit, overtime and safety incidents.
- Check how each KPI is calculated and fix definitions that teams read differently.
- Do a daily gemba walk (time on the floor watching the work) at different hours, including nights or weekends if you run them.
- Meet key partners: customer service, procurement, finance, HR, maintenance or IT, and your top suppliers.
Milestone: A one-page process map and a KPI baseline that your manager and finance agree on, presented at your 30-day check-in.
Diagnose and choose priorities (Weeks 5-6)
Find the few constraints behind most missed targets and agree on what to fix first.
- Rank problems by impact on customers, safety and cost, using the baseline and your floor notes.
- Find the bottleneck: the step where work waits longest or capacity runs out first.
- Pick three improvement priorities and one quick win, each with an owner and a target.
- Agree the list with your manager and tell the team what will wait.
Milestone: A signed-off priority list with three improvement projects, owners, targets and dates.
Quick wins and operating rhythm (Weeks 7-9)
Show visible progress and put routines in place so results stop depending on you.
- Launch a 10 to 15 minute daily huddle per team with a simple board: yesterday's results, today's plan, issues and safety.
- Deliver the quick win and measure it against the baseline.
- Write or refresh SOPs for the two steps with the most errors and train the leads on them.
- Start a weekly ops review with a fixed agenda and an action log.
Milestone: Daily huddles running in every team, one quick win measured against the baseline, and a weekly action log in use.
Improve and plan next quarter (Weeks 10-13)
Deliver the bigger fixes, prove the results and set direction for the next quarter.
- Run each improvement as a pilot on one line, shift or team before rolling it out.
- Compare results with the baseline every week and adjust.
- Review staffing, overtime and cross-training against forecast demand for next quarter.
- Set next quarter's targets with finance and your manager.
- Present a 90-day review: baseline, results, lessons and next steps.
Milestone: A 90-day review approved by your manager, with three improvements measured against the baseline and next quarter's targets agreed.
What your manager expects at day 30, 60 and 90
Most hiring managers judge an operations manager on three things: safety, service and cost. They do not expect big changes in month one. They expect you to learn fast, keep the operation stable and earn the trust of the people on the floor. A new manager who reorganizes shifts in week two often loses the team before the data comes in.
Use each checkpoint to prove one thing. At day 30, show that you understand the operation: a process map, a KPI baseline and the top problems in your own words. At day 60, show that you can make a change stick: a quick win, daily huddles and a priority list your boss signed. At day 90, show results against the baseline and a plan for next quarter.
Your first-week list
Week one sets the tone. Keep it on safety, people and listening. Here is a day-by-day list you can adjust to your site.
Do not promise changes this week. Write down every problem people raise, thank them and say when you will come back with a plan. Then come back on that date.
- Day 1: safety induction, a meeting with your manager to confirm priorities and how you will be judged, system access.
- Day 2: walk the whole operation with your most experienced supervisor, from inbound to outbound or from request to resolution.
- Day 3: one-on-ones with direct reports, using the same three questions for everyone.
- Day 4: shadow a full shift, including the start huddle and the handover.
- Day 5: read last quarter's KPI reports, the budget, open incidents and audit findings, then write a one-page summary of what you heard.
People to meet and what to ask
An operations manager depends on almost every other team. Meet them in the first three weeks, before you need anything from them. Ask each one the same core question: what does operations do that makes your job harder?
Keep your notes in one place and look for the same problem showing up from two or three sides. That overlap is often your best first priority.
- Your manager: top three priorities, budget limits, how often to report, what a great first 90 days looks like.
- Supervisors and shift leads: biggest daily headaches, strongest people, what was tried before and why it stopped.
- Frontline staff: where they wait, what they redo, which tools or equipment fail.
- Customer service or sales: top complaints, late orders, promises made to key accounts.
- Finance: how cost per unit and labor cost are calculated, and the budget variance so far.
- HR: open roles, turnover, absenteeism and training records.
- Maintenance, IT and procurement: causes of downtime, system issues, supplier performance.
Quick wins that fit operations
A good quick win is visible, cheap and inside your authority. It should fix something the team already complains about, so they see that you listened. Pick one, two at most, by week seven.
Avoid quick wins that change pay, shift patterns or headcount. Those need HR and finance, sometimes consultation with staff, and they rarely fit in 30 days.
- Match staffing to the hourly demand curve so the peak hour is not short of people.
- Clear an old backlog of open orders, tickets or returns with a short, focused push.
- Fix the top cause of rework at one station, such as a missing label check or an unclear form field.
- Put a visual board in each team area showing today's target and progress by hour.
- Drop one report or meeting nobody uses and give that time back to the floor.
Metrics to track from day one
Choose five to seven metrics, not twenty. Cover safety, service, quality, productivity and cost. For each one, write down the exact formula, the data source and who updates it. Disagreement about definitions is a common reason a new manager's numbers get challenged.
Keep the baseline period fixed so your day-90 comparison is fair. If volume swings a lot, report productivity per unit of volume rather than raw output.
- Safety: incidents and near misses per month, from the safety log. More near-miss reports early on can be a good sign of trust.
- On-time in full (OTIF) or SLA attainment: orders or tickets completed on time and complete, divided by the total.
- Throughput per labor hour: units, orders or tickets completed, divided by hours worked.
- Quality: first-pass yield, error rate or rework rate, from inspection or QA records.
- Cost per unit: total operating cost for the period divided by units, using finance's numbers.
- Overtime and absenteeism: hours as a share of planned hours, from timekeeping.
Example: a plan for a distribution center operations manager
Picture a new operations manager at a regional distribution center with two shifts, four supervisors and a late-shipment problem. Here is how the plan could look in practice.
Every block has an owner for each action and a milestone you can check. That is what makes the plan credible to a manager or an interview panel.
- Days 1-30, learn: shadow both shifts, map pick, pack and ship, and baseline OTIF, lines picked per labor hour and overtime. Owner: you, with the inventory control lead for data. Milestone: baseline agreed with the general manager and finance.
- Days 31-60, fix: the data shows most late orders come from the last two hours of the day shift. Release priority orders first, add a cutoff check at 3 p.m. and launch shift huddles. Owners: day shift supervisor and the WMS super user. Milestone: late shipments below the baseline four weeks in a row.
- Days 61-90, stabilize: cross-train six associates on packing, update the pick SOP and start a weekly review with customer service. Owners: training lead and both supervisors. Milestone: 90-day review approved, with next quarter's targets for OTIF and cost per order.
How to present it to your manager or in an interview
In an interview, keep the plan to one page or one slide with three columns: days 1-30, 31-60 and 61-90. Under each, put a theme, three actions and one measurable result. Use what you learned about the company during the interviews, such as a new site opening or a service problem, so it does not look generic. Say clearly that you will confirm priorities once you see the data.
Once you start, show the plan to your manager in week one and ask what they would change. Review it at day 30, 60 and 90 with the same layout, and add a status for each milestone: done, on track or at risk. Leave out long process detail. Leadership wants the baseline, the change and the result.
Common mistakes to avoid
- Changing shifts, layouts or processes in the first two weeks costs you the team's trust, so learn the operation and baseline the data before any major change.
- Taking existing KPI reports at face value leads to arguments later, so check each formula and data source in your first month.
- Spending the first month in the office hides how work really flows, so walk the floor every day at different hours and on every shift.
- Picking ten priorities spreads you too thin, so choose three improvement projects and one quick win and say openly what waits.
- Starting fixes without a baseline means you cannot prove results, so freeze the baseline period before you change anything.
- Building routines that only work when you are in the room makes the gains fade, so hand huddles and reviews to supervisors with a standard agenda.
Frequently asked questions
What should an operations manager do in the first 30 days?
Focus on safety, people and learning. Meet every direct report and key partner, shadow full shifts, map the main process and build a KPI baseline your manager agrees with. Hold off on major changes until you have the data.
What are good 30-60-90 day goals for an operations manager?
At day 30: a process map, a KPI baseline and a ranked problem list. At day 60: one measured quick win, daily huddles running and three approved improvement projects. At day 90: results against the baseline and next quarter's targets.
How do I present a 30-60-90 day plan in an operations manager interview?
Use one page or slide with three columns, each with a theme, three actions and one measurable result. Tie it to something you learned about the company in earlier interviews. Say that you will adjust priorities once you see the real data.
Which KPIs should a new operations manager track?
Pick five to seven that cover safety, service, quality, productivity and cost. Common choices are incidents and near misses, OTIF or SLA attainment, throughput per labor hour, rework rate, cost per unit and overtime. Agree each formula with finance and your manager.
Is the plan different for a plant and a service operation?
The structure stays the same, but the content changes. A plant plan leans on safety, downtime, yield and maintenance. A service or back-office plan leans on queues, SLAs, backlog and handoffs between teams.