A day in the life of an operations leader

Operations · A day in the life · ~7 minute read

The operations leader’s day is integration — across customer outcomes, commercial pressure, frontline reality, and regulatory expectation. The job is not what the job description says; here’s what an honest day actually contains.

7:30am — the dashboard

Twenty minutes with the operational picture. Yesterday’s service level, complaints, vulnerable customer outcomes, headcount position, any incidents. Read it for patterns, not just numbers.

A discipline: read the verbatims sample (10–20) before the day starts. The leader who reads them stays grounded in customer voice; the one who reads only the dashboard runs on summaries and loses calibration.

8:30am — ops leadership team

Forty-five minutes. Function heads — planning, QM, MI, RT, technology, learning. Quick round, decisions taken, actions named.

The disciplined leader runs this as a decision forum, not a status meeting. People who don’t need to be there don’t come. Status is read in advance; the meeting is for the calls that actually need the group. Most ops leadership team meetings are 70% status, 30% decision; the disciplined ones invert that.

11:00am — the cross-functional meeting that wasn’t about you

Marketing planning meeting. They’ve called you in because something they want to do affects the contact centre. You weren’t there for the discussion; you’re there for the impact.

The disciplined leader translates between vocabularies on the fly. "What you’re calling a campaign launch is, for us, two weeks of double volume on Tuesdays. We can absorb if you give us six weeks lead time and the marketing calendar. We can’t absorb if you give us two weeks." Marketing didn’t know that. Now they do. The translation is the value the operations leader brings to the room they weren’t consulted on first time round.

13:30pm — the call from compliance

Vulnerable-customer complaint. Regulator is asking. Compliance is asking what evidence we can produce for the handling of the case six months ago.

The disciplined leader: doesn’t defend, doesn’t deflect, asks what’s being requested and what timeline. Gets the QM and complaint teams aligned on the same evidence package. The leader who treats compliance asks defensively makes them adversarial; the one who treats them as partner makes them allies. The next vulnerable-customer crisis will come; the relationship banked now matters then.

15:00pm — the difficult conversation with finance

Finance partner wants to flex headcount down 5% over the next quarter. The operations leader knows this risks SL, vulnerable-customer outcomes, and the regulatory posture they’ve been working to improve.

The disciplined response: don’t resist generically; show the trade-off explicitly. "5% down saves £X. The likely cost is Y in additional complaints, Z in vulnerable-customer outcome deterioration, plus the regulatory exposure. If the business judgement is the £X saving is worth those costs, that’s a decision the business can make — but make it knowingly." Finance respects the leader who names the trade-off explicitly; they cut faster from the leader who only says no.

17:00pm — the strategy work you didn’t get to

The hour you blocked for strategic thinking on the AI roadmap. It was consumed by the regulator and the finance conversation. The leader who lets this happen consistently never moves the strategic agenda forward.

A discipline: reschedule it for tomorrow, but also audit weekly — how many strategic hours are you actually getting? If it’s under 20%, the operating system isn’t working and something needs to retire from your calendar. The leader who never carves out strategic time is being run by the operation rather than running it.

The ops leader’s day — integration under pressure Through the day ▸ 7:30 — dashboard + verbatims sample ▸ 8:30 — ops leadership decision forum ▸ 11:00 — cross-functional translation ▸ 13:30 — regulator / compliance partnership ▸ 15:00 — finance trade-off named ▸ 17:00 — strategy you didn’t get to The disciplines ▸ Stay grounded in customer voice ▸ Run decision forums, not status meetings ▸ Translate vocabularies explicitly ▸ Compliance as partner, not adversary ▸ Name trade-offs to finance, don’t resist ▸ Audit strategic time weekly Integration is the value the seat brings; nothing else replaces it

The honest ops leader’s discipline

Stay grounded in customer voice. Run decisions, not status. Translate vocabularies. Treat compliance as partner. Name trade-offs explicitly. Audit your strategic time and act when it’s collapsing. The ops leader who does these things runs an operation that customers, frontline, finance, and regulators all respect; the one who doesn’t runs an operation that keeps surprising itself.

See also