Back to home
The Operator's Playbook

Find the friction.
Fix what matters.

A practical guide to finding the operational friction in a growing business and deciding what to fix first.

This is the framework I use when I need to understand how work actually moves through a business — where it gets stuck, where ownership is unclear, where teams are creating workarounds and where better systems can create real capacity.

Before you change anything

Start by understanding the work, not the tools.

When a business feels messy, there is usually no shortage of things that could be improved. The temptation is to start fixing whatever looks most obvious: introduce a new tool, rewrite the SOPs, hire more people or add another meeting.

Sometimes those things are necessary. But they are rarely the best starting point.

I prefer to understand how work actually moves through the business first. What are people waiting for? Where does information get lost? Which decisions keep travelling upwards? What are people doing manually because the process has never been reconsidered?

Once those patterns become visible, it becomes much easier to separate the symptoms from the problems worth solving.

The framework

Six areas I look at first.

01

Is the business actually operating well?

Growth can make a business look successful while quietly exposing weaknesses underneath it. Before changing anything, look at how the business actually works.

  • Where does work regularly get stuck?
  • Which decisions still depend on one person?
  • Where are people spending time chasing information?
  • Which problems keep appearing despite being repeatedly fixed?
  • What are people doing manually that nobody has questioned in a long time?
02

People & ownership

A surprising amount of operational friction comes down to responsibility and authority not sitting in the same place.

  • Does every important recurring process have a clear owner?
  • Does the owner have enough authority to make decisions?
  • Are people clear on where their responsibility begins and ends?
  • Are decisions being escalated because they genuinely require senior input, or because nobody knows who can decide?
  • Is the business relying too heavily on individual knowledge?
03

Processes & systems

Good processes should make work easier to repeat, understand and improve. They shouldn't exist simply because someone once decided the business needed more structure.

  • Can someone explain the important processes without opening five different documents?
  • Are SOPs current and actually used?
  • Where have people created workarounds?
  • Are multiple systems being used to maintain the same information?
  • Could any process simply be removed rather than improved?
04

Customer experience

Customer support can be one of the best places to understand what is happening elsewhere in the business.

  • What questions keep appearing in customer support?
  • Which issues are symptoms of another process failing?
  • Are customers receiving clear information before they need to contact someone?
  • What are support agents repeatedly having to explain or work around?
  • Are recurring customer problems being fed back into the rest of the business?
05

Projects & delivery

Projects tend to slow down when priorities, ownership, decisions or dependencies are unclear. More meetings and more tools don't automatically solve those problems.

  • Does everyone know what the current priority is?
  • Who has authority to make scope and priority decisions?
  • Where are projects waiting for information or approval?
  • Are dependencies visible before they become blockers?
  • Is the team spending too much time reporting on work instead of doing it?
06

AI & automation

AI can create real operational capacity, but only when you understand the work before trying to automate it.

  • What repetitive work genuinely consumes meaningful time?
  • Is the underlying process clear enough to automate?
  • Is the information AI would need accurate and accessible?
  • Would AI remove work or simply move it somewhere else?
  • Where does human judgement still need to remain in the process?
The 30-day operational reset

Don't try to fix the whole business at once.

When I find a business with a lot of operational friction, I would rather identify the few problems creating the most downstream work than launch a huge transformation programme.

Week 1Observe and map where work gets stuck.
Week 2Clarify ownership, decision rights and the biggest sources of repeated work.
Week 3Fix the highest-friction process and remove unnecessary steps.
Week 4Measure what changed and decide what is actually worth improving next.
The operator's test

Is the business becoming easier to run?

That's ultimately the test I come back to.

Good operations isn't about creating more process, more meetings or more documentation. It is about creating enough structure that people can make good decisions, move work forward and solve problems without everything travelling through one person.

If the business is growing but becoming harder and harder to operate, something needs attention. The answer isn't always another hire or another tool. Sometimes it's a clearer owner, a better handoff, one reliable source of information or a process that no longer needs to exist.

The goal isn't to make the business look organised.

The goal is to make it easier for good people to do good work.