The New Operations Leader's First 90 Days : A UK B2B Playbook

Contents

The arithmetic is brutal. By the end of your first ninety days in a new operations role, the people who hired you will have formed a first opinion about whether you are the person who is going to change things. You will probably have a board update scheduled in that window. You will not yet have the relationships, the budget, or the data you need to execute a large transformation. And the team is watching.

This is not a problem you solve with a strategy document. You solve it with one visible, measurable, defensible win inside the window, with your name on it.

This playbook is for new COOs, operations directors, heads of claims, practice managers, programme leads and anyone else who has just taken ownership of a UK B2B operation and is being asked to change it. It is deliberately specific about what to do, in what order, and what not to waste the first ninety days on.

The shape of the window

You have three phases, and the mistake almost every new operations leader makes is to let phase one absorb the entire window.

• Days 1 to 30 : Listen, map, name the pressure. You are reconstructing how the operation actually works, as distinct from how it is documented. You are meeting the people whose trust you need. You are identifying which of the four trigger pressures is the real one driving your mandate.
• Days 31 to 60 : Pick the pilot and build internal cover. You are choosing one workflow, agreeing the pass/fail, and lining up the internal stakeholders you need on your side.
• Days 61 to 90 : Ship it and report numbers. You are running the new workflow in parallel with the old one. You are measuring the difference. You are walking into the board update with a delivered outcome, not a plan.

If you try to do the "listen" phase for sixty days instead of thirty, you will arrive at day ninety with nothing to show, and you will spend the rest of your tenure playing catch-up.

Days 1 to 30 : Listen, but listen structurally

The common mistake here is to do coffees. Coffees are fine. They are not a diagnostic. By the end of day thirty, you need to have answers to five structural questions.

1. Which of the four trigger pressures is your real mandate?

Your board will have told you why they hired you. The reason they actually hired you is often narrower, sharper, and more political than what they said in the interview. By the end of week four, you should know which of the following is the real one :

• Growth has broken the existing system. Volume is outrunning the process.
• Margin has tightened and inefficiency is now visible. Cost-per-case has become a board conversation.
• Compliance pressure has risen. A regulator, an insurer or an auditor has changed the bar.
• You are the change. The board wants operational reset and you are the mechanism.

You do not have to pick one. You do have to know which one your mandate really comes from, because it determines which workflow to pilot, and which stakeholders will back you.

2. Where does the tribal knowledge live?

Every operation has one or two people whose heads contain the real process. Find them in week one. Shadow them. Write down what they actually do, not what the SOP says they do. If they leave in the next six months, which they might, given they are probably the most burned-out people in the operation, you need what is in their heads to be written down before it walks.

3. What would your CFO actually ask you to prove?

The CFO conversation is the single most important one in the first thirty days. You need to know what number they want on a dashboard in ninety days, because that number is going to anchor your pilot. "Reduce cost-per-case on new-business onboarding by 15%" is a useful pilot target. "Transform operations" is not.

4. Who already believes the operation is broken?

There are two camps in every operation you inherit. The camp that has been asking for change, loudly, for at least a year, and the camp that has been successfully resisting it. Identify who is in which camp. The first camp is your early adopter group : they will give you the brutally honest list of what is broken, they will cooperate with the pilot, and they will be your first references internally.

5. What have the previous change attempts looked like?

If your predecessor tried something and it failed, find out why. It is rarely that the idea was wrong. It is usually that the motion was too big, the stakeholders were not lined up, or the readout took too long to materialise. Learn from their specifics. Avoid their pattern.

At the end of day thirty you should be able to write a single paragraph : "The real pressure is X. The workflow where it is most visible is Y. The number the CFO wants is Z. The internal sponsors are A and B." If you cannot write that paragraph, do not move to phase two yet. Stay in listening mode for another week.

Days 31 to 60 : Pick the pilot and build cover

The single biggest leverage point in your ninety days is the workflow you pick to pilot. Picking the wrong one costs you the window. Picking the right one buys you the next twelve months.

The criteria for a good first pilot

A good first pilot meets all of these :

• High volume, narrow scope. The team does this process many times a week. You can measure it.
• Team pain is real. The people who do the work hate doing it the current way. Adoption will be willing.
• The business cost is legible. You can translate improvement into a board-relevant metric : cost-per-case, cycle time, SLA compliance, audit readiness.
• It is reversible. If the pilot does not work, the old process still exists, the old data still exists, and the damage is contained.
• It does not require cross-functional miracles. Anything that needs three other departments to cooperate in the first ninety days is the wrong pilot.

Typical candidates : new-business onboarding, claims intake, appointment scheduling, first-line triage, compliance sign-off, handover-to-billing, document generation. Atypical candidates that tend to fail in the first ninety days : full CRM replacement, core finance migration, anything that touches the contract register.

Define the pass/fail before you start

The most common failure mode in first-ninety-days pilots is that the pilot delivers but nobody agrees whether it passed. Fix this by writing down, before you start :

• The baseline number (how the old process performs today, measured on live cases)
• The target number you expect to hit
• The threshold at which you will call it a success, a learning, or a stop
• Who signs off that call, and on what date

If the baseline is "we do not currently measure this", your first week of the pilot is baseline measurement. That is fine.

Build cover inside, not outside

The pilot is a delivery project, but the surrounding motion is political. You need :

• The CFO nodding at the target number
• The ops team on the ground bought in, not because they have to be, but because the current way genuinely hurts them
• A senior sponsor above you who is briefed on the pilot in writing, so that when the board asks at day sixty "what has the new COO been doing", the answer is already in someone's head

Do not try to build cover by being visible. Build it by being specific about what you are going to deliver and when.

Days 61 to 90 : Ship and report

By day sixty you should have the pilot kicked off and the new workflow being built. The goal for days 61 to 90 is simple : run it in parallel with the existing way of working, measure the difference on live cases, not test data, and present the outcome.

Why parallel running matters

The temptation is to cut over to the new workflow and leave the old one behind. In UK B2B, this is nearly always wrong on a first pilot.

Parallel running means the existing process still exists as a safety net. It means the numbers you report are an apples-to-apples comparison on the same cases. It means a pilot that fails does not fail the business. And it means the board sees, in cold numbers, what the new way is worth compared to the status quo.

Yes, it costs the team slightly more effort for the two or three weeks of the run. That is a small price for a defensible readout.

The day-90 readout

The readout at day ninety has a specific shape. It is not a deck of strategy slides. It is :

• The workflow you piloted, in one sentence
• The baseline number and the new number, measured on live cases
• The cost to produce the new number, fully loaded
• The recommendation : scale, extend, or stop
• The scope and cost of phase two, if scaling

A readout of this shape, with real numbers, will do more for your position than any strategy document. It turns you from "the new COO" into "the COO who already delivered something", and that shift is the whole point of the ninety-day window.

Why this playbook is UK-specific

A common source of advice for new operations leaders comes from US-style transformation playbooks. Most of them do not translate cleanly to UK B2B, and it is worth being explicit about why.

• UK buying is slower and more risk-averse. A plan that relies on rapid procurement of new tooling will stall at your first supplier onboarding. Plan for slower external motion.
• Peer validation matters more. When you are arguing internally for phase two, the question that will come up is "who else in our sector has done this and did it work". Plan your pilot so you can answer that question.
• Reversibility is a political asset. UK boards are more comfortable with reversible, low-exposure decisions than with bold, one-way-door transformation plays. Position the pilot as reversible from day one.
• Retention is longer once you are in. Once a decision has been taken and survived the first cycle, it tends to stick. That is why phase one has to work, but phase two is where the real return lives.

The common mistakes

A handful of mistakes turn up repeatedly. Worth naming them :

• Spending the first sixty days listening. You will not have more information at day sixty than at day thirty. You will have more comfort, which is not the same thing.
• Launching a big programme instead of a small pilot. Large programmes are slow, visible, and failure-intolerant. Small pilots are fast, contained, and failure-tolerant. Start where you can fail cheaply.
• Picking the workflow that is worst rather than the workflow that is most improvable. The worst workflow is usually worst for a reason, often cross-functional or political. Pick the workflow where the team is already motivated and the change is within your gift.
• Reporting effort instead of outcomes. "The team has been working very hard" is not a readout. "We processed 400 cases through the new workflow with a 38% reduction in cycle time" is a readout.
• Trying to build it internally from scratch in 90 days. You will not. Your team is already at full capacity running the existing operation. Use a partner for the pilot and keep the internal team focused on using it, not building it.

How a pilot fits inside this playbook

If you want a turnkey way to run the phase two to three motion described above, we run a thirty-day, fixed-scope, reversible pilot that is built precisely for this window.

You pick the workflow at day thirty-one. Week one is discovery. Week two is build. Week three is parallel run on live cases. Week four is the readout. By day sixty-ish you have the day-90 board readout already in hand.

See how the 30-day pilot works →

And if you are still in the first thirty days and working out which trigger pressure is really driving your mandate, the operations pressure map walks through the four trigger moments in detail, with the matching case study for each.

The ninety-day window is short. It is also enough, if you are specific, narrow and measured. A single delivered pilot beats a comprehensive strategy every time.