Your First 90 Days as Operations Manager
Your strategy in brief: Your first month is about earning trust on the dispatch floor and understanding how on-time delivery is measured before you form any theory about why it dropped. Your warehouse background is an asset: you know shift pressure, tight timelines and frontline reality, so lead with that, not with "how we did it at a national chain." By Day 90 you'll present a clear, data-backed improvement plan that your dispatchers helped shape, so they'll want it to succeed.
Assumptions I made: You're a first-time people manager with 6 direct reports (the dispatchers), not the drivers. Dispatch runs on weekday business hours with some early or late coverage. Your company uses some kind of dispatch or routing software and tracks on-time delivery, but I don't know which tools or definitions, so the plan tells you to find out. Dates assume a Monday, April 7, 2025 start. If you're in the US, Memorial Day (May 26) and July 4 fall inside your 90 days, so plan around them.
Your 90-Day North Star
By Saturday, July 5, 2025 (Day 90) you should be able to point to:
- A trusted working relationship with all 6 dispatchers. You've had regular 1:1s, sat in on every role and shift pattern, and acted visibly on at least one thing the team asked for.
- A clear diagnosis of the on-time drop. You have a written explanation of what changed last quarter, backed by data and frontline input, that your Director of Operations agrees with.
- A 6–12 month improvement plan. It covers on-time rate and route efficiency, with 3–5 prioritized actions, owners, and the metrics you'll track. You've presented it to your Director and walked the team through it.
About your concern: winning over the team without seeming like the corporate outsider
The quickest way to look like an outsider is to arrive with answers. The quickest way to earn respect is to show you can do the hard part of their job and that you listen. Concretely:
- Spend real time in the seat. Shadow dispatch during the worst hours (morning load-out, late-day exceptions), not only the calm ones.
- Treat your 20-year dispatcher as your most valuable source of knowledge, not a threat or an obstacle. Ask them to teach you the history: which customers are tricky, which routes always run late, what's been tried before. Credit them by name when their insight shapes a decision.
- Talk about your warehouse experience as shared ground ("I've been on the receiving end of late trucks"), not as a template.
- Don't change anything significant before Day 30, except fixing obvious annoyances the team asks you to fix.
On the on-time drop: it may have little to do with dispatch. Driver availability, customer mix, new delivery windows, road construction season, equipment issues, or a change in how "on-time" is calculated can all move the number. Diagnose before you assign cause.
Phase Overview
| Phase | Theme | Main goals | You'll know it's working when... |
|---|---|---|---|
| Days 1–30 (Apr 7 – May 6) | Learn the floor and listen | Meet everyone, shadow every dispatch role, learn the tools and the on-time metric definition, start 1:1s | Dispatchers come to you with problems unprompted, and you can explain a typical day's dispatch flow without notes |
| Days 31–60 (May 7 – Jun 5) | Diagnose and build trust through action | Dig into on-time and route data, deliver 1–2 quick wins, map root causes with the team | You have a draft list of root causes the team agrees is accurate, and one quick win is in place |
| Days 61–90 (Jun 6 – Jul 5) | Plan and lead the improvement | Build and present the improvement plan, set team rhythms, agree on metrics with your Director | Your Director signs off on the plan and the team can explain the "why" behind it |
Days 1–30: Week-by-Week Checklist
Week 1: April 7–11 (Setup, introductions, first manager 1:1)
- Complete HR onboarding, system logins and building access. Confirm with HR any questions on pay, benefits or policies.
- Hold your first 1:1 with the Director of Operations (use the agenda below).
- Introduce yourself to the dispatch team as a group, using your intro script.
- Book a 30-minute 1:1 with each of the 6 dispatchers for Weeks 1–2. Frame it as "help me learn," not a review.
- Get a walkthrough of the dispatch and routing software from a dispatcher, not just IT, so you see how it's really used.
- Ask your Director how on-time delivery is defined (by appointment window? same day?), where the number comes from, and who reports it.
- Learn the basic norms: shift times, how dispatchers hand off, how drivers check in, and how you're expected to communicate (in person, phone, radio, chat).
- Start a running notebook with three columns: "What I'm seeing," "Questions," and "Ideas for later."
Week 2: April 14–18 (Shadow and learn the craft)
- Finish all 6 dispatcher 1:1s.
- Sit with a different dispatcher for at least 2 hours on 3 separate days. Include your longest-tenured dispatcher and the busiest shift.
- Ask your senior dispatcher for a "history lesson": the key customers, problem routes, and past changes that did or didn't work.
- Walk the yard or loading area during morning load-out and note where trucks wait or get delayed.
- Get access to on-time and route reports for the last 2–3 quarters. Just read them for now.
- Meet the Fleet/Maintenance lead and Driver Supervisor (see People to Meet).
Week 3: April 21–25 (Widen the view)
- Ride along with at least one driver on a typical route, ideally one with recent late deliveries. Check with your Director that ride-alongs are allowed first.
- Meet the Customer Service lead and ask which customers complain most about lateness, and why.
- Meet the Sales or Account Management lead to learn about any new customers, contracts or delivery windows added last quarter.
- Ma