Most businesses know something is making work harder. The difficult question is what is actually causing it.
However it shows up, most conversations with CoveOps start with something on this list.
The situations that usually bring me in.
- Growth or change has made the business harder to run.
- Too much still depends on the owner or a few key people.
- Important priorities are not turning into implemented change.
- Leadership cannot see or control performance with confidence.
- A significant operational or technology decision needs an independent view.
- The business needs senior operational oversight, without another full-time director.
- The business has just been through, or is heading into, an acquisition or merger.
Each of these shows up in the day-to-day signs below.
What this actually looks like.
Work takes too much chasing.
You might recognise
- Work regularly waits between people or teams.
- Staff have to ask around for updates.
- Customers chase because nobody can see the current status.
- Progress depends on someone remembering to follow up, or on a decision stuck waiting for approval.
What might be behind it
- Unclear handovers.
- No clear owner.
- Information spread across different systems.
- Decisions waiting on approval.
- No shared view of work in progress.
What changes when it's fixed
- Improve customer experience: faster, more consistent updates without customers having to chase.
- Free up capacity currently lost to chasing and following up.
- Save money on the admin cost of duplicated follow-up.
How we approach it
I follow the work from start to finish to identify where it waits, what information is missing, and what is actually causing the delay.
Too much depends on particular people.
You might recognise
- New starters take longer than they should to get productive.
- Big wins feel like heroics that happened because of one person, not something the business could repeat on demand.
- Several people touch a process, but nobody's clearly responsible for it.
- Work slows or stops when a key person is away.
What might be behind it
- The knowledge needed is spread across colleagues, documents and habit, rather than written down anywhere practical.
- Responsibility is spread across several people, so it's unclear who's expected to fix problems or improve things.
What changes when it's fixed
- Reduce risk from relying on one person's memory or availability.
- Free up capacity sooner, with new starters productive faster.
- Improve business management, with good outcomes that are repeatable, not one person's heroics.
How we approach it
I identify which workflows need to be clearer, or less dependent on any one person's memory.
Growth keeps adding cost and complexity.
You might recognise
- Every new customer or contract adds about as much admin as the last one, not less.
- Work queues up in the same place, again and again, no matter who's covering it.
- Adding people hasn't solved the problem.
What might be behind it
- The process was designed for a smaller business and hasn't kept pace.
- The problem actually starts earlier in the process than where the queue is visible.
What changes when it's fixed
- Save money, with each new customer or contract cheaper to onboard than the last.
- Free up capacity to grow without adding headcount at the same rate.
- Sharpen visibility into where queues are actually forming.
How we approach it
I look for what should get easier as volume grows, not just what's needed to get through today.
People cannot rely on the numbers in reports.
You might recognise
- Two reports show two different numbers for the same figure.
- Data gets collected but nobody's turned it into something that changes a decision.
- People decide on instinct because they don't trust what the system is telling them.
What might be behind it
- No single agreed source for a figure that matters.
- Nobody's decided what the data should actually tell you.
- Reports built for a stage the business has already grown past.
What changes when it's fixed
- Sharpen visibility with one trusted figure, not two conflicting ones.
- Reduce risk of decisions made on instinct instead of evidence.
- Save money currently spent reconciling conflicting reports.
How we approach it
I look at where the numbers actually come from, and check whether there's one figure everyone can agree on and use.
Systems create extra work instead of reducing it.
You might recognise
- A system that suited a smaller business is now held together with workarounds.
- People keep spreadsheets alongside the "real" system because the real one doesn't quite do what's needed.
- Adding a new customer or contract takes about as much admin as the last one, not less.
- Stock or inventory records don't match what's actually there.
What might be behind it
- The system hasn't been reconfigured as the business has grown.
- A step was never built to handle the current volume.
- Manual workarounds have quietly become the real process.
What changes when it's fixed
- Save money on the manual work needed to make the system do what it should.
- Free up capacity to take on more customers or contracts without adding headcount.
- Sharpen visibility, with stock and records you can actually trust.
How we approach it
I check whether the system already in place can be extended or better used, before assuming it needs replacing.
The same work gets done more than once.
You might recognise
- The same task gets entered, checked or explained more than once.
- The same customer or job details get typed into more than one system.
- A report takes real effort to put together but rarely changes what anyone decides.
- An exception gets worked out from scratch again because the last time isn't written down anywhere.
What might be behind it
- Systems and processes that were never connected, so people compensate manually.
- No agreed place for information to live once and be trusted.
- Reporting built for a stage the business has already grown past.
What changes when it's fixed
- Save money by cutting out duplicated data entry and rework.
- Free up capacity for higher-value work.
- Reduce risk of costly mistakes from conflicting or re-keyed information.
How we approach it
I map where the handoffs and duplication actually happen, and look at whether the systems already in place could be connected before anything new is bought.
Improvements are discussed but do not stick.
You might recognise
- Good ideas come up, then quietly go nowhere.
- AI or automation gets talked about, but nothing's actually been tried, or one attempt stalled.
- A new way of working gets agreed, then everyone quietly drifts back to the old one.
What might be behind it
- Nobody owns turning the idea into a practical next step with an owner and time allocated.
- Effort went into the wrong task first because nobody mapped what was actually suitable.
What changes when it's fixed
- Save money and free up capacity that stay realised, not just identified and forgotten.
- Improve business management, with a clear owner and plan for every change.
- Reduce risk of wasted effort on the wrong fix first.
How we approach it
I turn ideas into a prioritised, practical plan, and say clearly where something wouldn't help.
Exceptions derail the wider operation.
You might recognise
- A small exception causes far more disruption than it should.
- Whoever's around handles it their own way, so the outcome depends on who's on shift.
- Customers or staff get a different answer depending who they ask.
What might be behind it
- Most processes are built for the normal case, so exceptions get handled by whoever's around and willing.
- There's no agreed way to escalate or resolve a case that doesn't fit the pattern.
What changes when it's fixed
- Improve customer experience with a consistent answer, whoever they ask.
- Reduce risk of a small exception escalating into a bigger problem.
- Free up capacity currently lost to ad hoc firefighting.
How we approach it
I look at how exceptions currently get handled, and build a defined path for them so they stop derailing everything else.
Recognise more than one of these? Here's what that looks like in practice.
New ownership, but decisions and reporting still ran on individual memory
A growing business had recently changed hands. It was successful, with capable people, real customer relationships and plenty of knowledge built up over time, but the informal ways of working that had got it this far weren't enough for what the new CEO and board needed next: decision rights weren't always clear, and management information didn't yet give leadership real visibility.
This wasn't a case of anything being broken, it was a business moving into its next phase, with an opportunity to put stronger foundations under it before growth made the gaps costlier. I'd start by finding where responsibility and decision rights were genuinely unclear, not just assumed to be fine, and build structure around the business without pausing it or dismissing what had made it work. I'd measure it by whether decisions move faster and teams can act with confidence, not by how much new reporting gets produced.
Orders rekeyed by hand, no warning when something's late
A made-to-order firm was rekeying sales orders, purchase orders and supplier delivery dates into a shared spreadsheet, with no way of knowing something was late until a customer asked.
The rekeying was the visible symptom, the real question was why the order system and the spreadsheet weren't talking to each other. I'd start there: can the existing system raise the alert itself, or does a lightweight connection remove the manual re-entry without replacing anything. The fix, if it holds up, is proportionate to the problem, not a new system, and I'd measure it by how many overdue orders get caught before a customer has to chase.
The same person's details typed into four different systems
A business used four separate systems for HR, staffing and rotas, training records, and operations planning. The systems weren't connected. The same person's details, qualifications or availability had to be entered into each one separately, and would sometimes end up different, or missing entirely, on one of them.
With four systems doing overlapping jobs, the first question isn't which one to replace, it's which one should hold the trusted version of a person's details, and whether the others could pull from it instead of duplicating it. Replacing everything at once is rarely the answer, connecting what's already there usually is. I'd measure it by how often a record is out of date or missing when someone actually needs it, not a headline hours-saved figure.
Leads and follow-up scattered across calls, email, notes and spreadsheets
An owner-led service business had no single place leads landed, some came in by phone and got written on a notepad, others by email and sat in an inbox, and follow-up depended on the owner remembering.
I'd map where a lead actually enters the business and where it currently gets recorded, then look at whether an existing tool could hold that, even a simple one, properly used, before considering anything new. The measure that matters isn't the system, it's how many leads get a documented follow-up without relying on one person's memory.
Recognise the problem? Here's the most proportionate next step.
Biz Ops Deep Dive
Not sure what is causing the friction?
Explore a Biz Ops Deep Dive: a focused, evidence-based assessment of what's really going on and what's worth doing about it.
A Focused Project
Know the change you need and want it led through?
Discuss a focused project: hands-on delivery of a defined piece of improvement, from fixing a process to leading a system rollout.
Fractional Leadership
Need regular senior ownership across the business?
Explore Fractional Leadership: ongoing, part-time senior operational leadership without a full-time hire.
Your business does not need to be broken to work better.
If growth, complexity or years of workarounds have made the business harder to run, I can help you work out what to tackle first.