The first 90 days in a new operations role are mostly a credibility exercise. You haven't earned the right to change anything yet — and the team you inherited is watching to see whether you understand the business or just have opinions about it. The leaders who get traction in year one almost always invest the first quarter in listening, mapping, and quietly fixing the small stuff. The ones who ship a reorg in week three almost always spend year two unwinding it.
This is the playbook we walk new operations leaders through. It assumes you've been hired to improve something, not to babysit the status quo — but it starts from the premise that you don't yet know what “improvement” means in this specific business.
Days 1–30: listen before you measure
Resist the urge to demand dashboards on day two. The numbers will still be there in week four, and you'll understand them better once you've heard people describe the work in their own words.
Run a structured listening tour
Book 30-minute conversations with everyone who reports to you, your peers on the leadership team, and the two or three operators downstream of your function who feel the consequences of how you run things. Ask the same four questions in every conversation:
- What works well today that you'd hate to lose?
- What's the most frustrating part of your week?
- Where do you think we lose the most time or money?
- If you had my job, what's the first thing you'd look at?
Take notes by hand. Patterns emerge fast — usually by the seventh or eighth conversation, the same three or four themes will show up regardless of who you're talking to. Those are your real priorities. Everything else is somebody's pet annoyance.
Read the artefacts, not the org chart
Org charts lie about how work actually flows. The truth lives in:
- The shared inboxes nobody owns but everyone uses.
- The spreadsheet that's emailed every Monday.
- The Slack channels with hundreds of messages and three pinned items.
- The recurring meetings that have been on the calendar for two years.
Each of those is a workaround for a structural gap. Map them privately and you'll have a more honest operating model than anything in the wiki.
Days 31–60: diagnose, don't prescribe
By week five you'll be tempted to start fixing things. Hold off on the big moves. Use this phase to convert your listening notes into evidence — and to pick the two or three problems worth investing in.
Build a one-page operating model snapshot
On a single page, write down: the inputs your function takes in, the outputs it produces, the key processes that turn one into the other, and the three or four metrics that matter most to your stakeholders. Then mark the parts that nobody owns, the parts where two people think they own it, and the parts where the metric doesn't match what anyone actually does.
This isn't a deliverable for anyone else. It's your map. Keep it on one page — the discipline of fitting it forces you to choose what matters.
Pick three problems worth solving
Resist the breadth-first instinct. By the end of week eight you should have three problems you're willing to publicly own:
- One quick win — something visible, achievable in weeks, and useful enough that the team feels it.
- One structural improvement — a process, role, or metric change that pays back over a quarter or two.
- One strategic question— the kind of thing that needs more diagnosis before you commit, but that you flag now so your boss isn't surprised when you raise it later.
Three is the right number. One is too small to signal intent; five is too many to actually finish.
Days 61–90: commit publicly to a small number of changes
You've listened, you've mapped, you've chosen. The last 30 days are where you earn the right to lead by doing.
Publish a 90-day note
Write a short, plain-language document for your boss and team that says: here's what I've observed, here are the three things I'm investing in, here's what I'm explicitly choosing not to fix yet. The “not yet” list is more important than the “yes” list — it tells the team you have priorities, not just energy.
Ship the quick win first
Whatever you said the quick win was, deliver it before day 90. Visibly. The credibility you build from a single shipped improvement is what funds the longer-term changes. People believe what they see, not what they're told you're planning to do.
Establish your operating rhythm
Before the quarter ends, lock in two rituals: a weekly one-on-one cadence with your directs, and a monthly review of the metrics you committed to in the 90-day note. Skip those rituals for a quarter and the rest of the playbook unwinds.
The mistakes we see most often
- The week-three reorg.You don't know the board yet. Wait.
- Importing the last company's playbook.What worked there worked there because of context you don't have here. Adapt, don't paste.
- Trying to win every stakeholder. Some of them benefit from the dysfunction. Be polite, be clear, and accept that part of the job is disappointing people on purpose.
- Skipping the listening tour because you're busy.If you're too busy to talk to your team in the first month, you've already made decisions that won't survive contact with reality.
The honest bottom line
The 90 days don't end with a transformation. They end with a new operations leader who has a credible map of the business, a small set of public commitments, and a team that believes the leader understands what they're asking for. From there, the next 90 days can be ambitious. Without that foundation, ambition just looks like noise.
If you're six months in and still relying on the playbook you brought from your last role, that's the signal to restart this process. You don't need a new job — you need the listening tour you skipped.