The first 90 days in an operations leadership role are the most consequential you will have in that organisation.

Not because of the decisions you make in that period — though some will matter. Because of the impressions you form, the relationships you build, the credibility you establish, and the framing you set for everything that follows. Get it right and you accelerate. Get it wrong and you spend the next eighteen months trying to recover from conclusions you drew in week two.

This is not a generic onboarding guide. It is a lean-informed framework for how an operations leader — COO, VP Operations, Plant Manager, Head of Supply Chain — should think about their first three months in a new role.

The Temptation to Act

The most common mistake new operations leaders make is moving too fast.

You were hired because the business has a problem. Everyone knows it. You know it. There is an expectation — sometimes explicit, often implicit — that you will act decisively and quickly. And you will have seen enough in your first two weeks to form views: the SIOP process is broken, the maintenance team is reactive, the warehouse layout is chaotic, the management reporting is three weeks behind reality.

The temptation is to fix these things immediately. To demonstrate that you are the leader they hired. To show pace.

Resist it. Not because the observations are wrong — they are probably right. But because you do not yet understand why things are the way they are. And in operations, understanding the why is the difference between a fix that sticks and a change that creates three new problems while solving one.

Days 1–30: Listen, Walk, Map

The first month has one job: understand the system as it actually operates, not as it appears on paper or in presentations.

Go to the gemba. Spend the majority of your first month on the floor, in the warehouse, at the supplier, in the call centre — wherever value is created and problems occur. Not touring. Observing. Asking questions that start with “help me understand” rather than “why don’t you.” The people doing the work know things that no report will ever tell you.

Map the value stream. Build your own mental model of how material and information flow through the operation. Where are the delays? Where is inventory accumulating? Where are the quality escapes occurring? Where do people spend their time firefighting? You are not creating a formal VSM at this stage — you are developing the operational intuition that will inform everything you do subsequently.

Understand the management system. How does the organisation know whether it is on plan? What meetings happen, at what cadence, with what data? What gets escalated and what gets absorbed? How are problems solved — through structured problem-solving or through heroic individual effort? The answers reveal the operating culture more reliably than any values statement.

Listen to the history. Every operation has a history of initiatives that were launched and abandoned. Lean transformations that started with fanfare and faded. ERP implementations that promised integration and delivered complexity. Restructures that disrupted without improving. Understanding what has been tried — and why it did not work — is essential before you propose anything new. The organisation has scar tissue. You need to know where it is.

Days 31–60: Diagnose and Build Trust

The second month moves from observation to diagnosis. You are now forming hypotheses — not yet conclusions — about the root causes of the performance issues you have observed.

Identify the constraint. In every operation, there is a bottleneck — a single step that limits the throughput of the entire system. Finding it, and understanding why it is constrained, is the most important analytical task of your first 60 days. Everything else should be subordinated to relieving it. Improvements elsewhere in the system are irrelevant until the constraint is addressed.

Separate signal from noise. Operations generate enormous volumes of data, most of which is not actionable. Identify the three to five metrics that genuinely predict operational and commercial performance. These will become the foundation of your management system. Everything else is context.

Build relationships, not alliances. The commercial leader who is frustrated with operations. The finance director who does not trust the cost data. The engineering team that feels their improvement ideas are ignored. The frontline supervisors who have been told that change is coming and are waiting to see whether this time is different. These relationships will determine your ability to deliver. Invest in them deliberately, not instrumentally.

Pick one visible quick win. You do not need a transformation programme in month two. But you do need one thing — one visible, meaningful improvement that demonstrates that you understand the operation and that you can deliver. This is not about politics. It is about building the credibility that will allow you to ask for the commitment and resource that larger changes require.

Days 61–90: Set the Direction

By day 60, you should have enough understanding to articulate a clear point of view: what is the operation’s primary constraint, what are the two or three systemic changes that would most improve performance, and what needs to happen first?

The third month is about translating that point of view into a plan that the organisation can execute and that leadership will back.

Build the improvement roadmap. Not a transformation programme with 47 workstreams and a Gantt chart that stretches to infinity. A clear, sequenced plan with three to five priorities, owners, milestones, and explicit decision points. The discipline of sequencing matters: what needs to happen before anything else can work? Start there.

Establish the management system foundations. If the tiered meeting structure does not exist, begin it. If the visual management boards are not maintained, fix them. If escalation is not happening, make it safe. These are not optional elements of operational excellence — they are the infrastructure without which nothing else can be sustained.

Communicate the narrative. By day 90, your team, your peers, and your leadership should be able to articulate the same answer to the question: what is the operations leader trying to achieve and how? Alignment on the narrative precedes alignment on the work. If people do not understand the direction, they cannot support it.

What to Avoid

Do not reorganise in the first 90 days. Structural changes before you understand the system create instability without insight. There will be a case for restructuring — there almost always is. But make it from knowledge, not from reflex.

Do not dismiss what exists. Every operation has things that work well, practices that have been earned through painful experience, people who carry critical knowledge informally. The instinct to start fresh is understandable. It is also expensive. Understand what you have before you replace it.

Do not over-promise. The credibility you are building in these 90 days depends entirely on the gap between what you say and what you deliver. Commit to less and deliver more. The reverse destroys trust faster than almost anything else a new leader can do.

The Underlying Principle

Lean thinking teaches that you must understand the current state before you can design the future state. This is not a methodological nicety — it is a hard-won truth about how change works in complex systems.

The first 90 days in an operations role are your investment in understanding the current state. The quality of everything you do after that depends on the quality of that investment.

Go slowly enough to understand. Then move.

Adam