How to identify the efficiency gaps AI can fill

Most leaders believe the hard part of adopting AI is the technology: which model, which vendor, which platform. It isn't. The hard part is the diagnosis, and almost nobody does it. The efficiency gaps AI can fill have a shape you can test for. They are repetitive, latency-bound, the judgement inside them is pattern-matching rather than novel, and someone owns them. Skip that test and you pick the work that is loudest or most impressive, ship three months of build, and end up with a half-finished agent aimed at the wrong gap. This is a guide to doing the diagnosis properly. It is short on theory and long on signals.

The companies that get this wrong do not have an AI problem. They have a diagnosis problem. They have not looked carefully enough at where the real gaps sit, so they optimise for what will demo well at the next board meeting. The build that follows is technically fine and commercially pointless.

An efficiency gap is a queue, not a number

An efficiency gap is the distance between how long a piece of work takes now and how long it could take if the right capability sat inside the workflow. That is a practical measure, tied to what the team could ship this quarter, not an idealised best case in a slide.

The framing matters more than it looks. Strategy decks talk about efficiency as a percentage. Operators experience it as a queue: the inbound forms that pile up, the triage that waits, the scorecard synthesis that gets done on Friday afternoon in a hurry because it sat all week. The gap is the queue. If you want to find one fast, ask the team a single question: what is the work that stacks up between Monday and Friday, that we end up clearing at the last minute? That work is almost always sitting in a gap.

This is also why the right unit of analysis is the workflow, never the role. A role is forty workflows in a coat. Some of those forty are deeply human and some are queue-clearing drudgery, and AI has nothing useful to say about the role as a whole. Audit the workflows underneath it. Exposure lives at task level, which is exactly where the gaps are too.

The efficiency gaps AI can fill have a shape

Not every gap is AI-shaped. Plenty of efficiency problems are organisational, or a broken process, or a missing hire that no model will replace. The gaps AI can actually fill share four signals, and the discipline is to score all four before you commit any engineering time, not just the two that feel most painful.

Take them in turn, because each one kills different work. Repetition is the amortisation test: a workflow that runs four times a year cannot pay back a build, so the impressive quarterly reporting pack loses to the dull daily triage queue every time. Latency is where the value hides: the work itself is fast, the waiting is the problem, and collapsing the wait is where hours come back. Judgement shape is the one people get wrong most, because they overestimate how much novel thinking a workflow really contains: is this expense out of policy? is pattern-matching and AI does it well, while should we change the policy? is novel and AI does it badly. Contestability is the quiet killer. It has nothing to do with whether the work is AI-shaped and everything to do with whether you can ship. If the change needs three teams to agree, the gap is real but the build is not yet possible. Park it and pick something you can actually own.

The 30-minute audit you can run this week

You do not need a consultant for the first pass. You need a whiteboard, half an hour, and the operating leader of the function. Not IT, and not an outside adviser: two of the four signals rest on judgement only the person running the work holds, so if they are not in the room the audit is guesswork.

The output is a table you can put in front of anyone. Here is the shape it takes, with a few illustrative rows so you can see how the scoring separates candidates from noise:

Read down the verdict column and the discipline does the work for you. The board pack is the one everyone wants to automate because it is visible and painful, and it is exactly the one to leave alone: four runs a year will never pay back the build. The triage queue is dull, invisible above team level, and the strongest candidate on the sheet. That inversion is the whole point of scoring rather than choosing by feel.

Then pick one. Just one. The smallest, most boring, most obviously winnable. That is the first build, because confidence compounds across a team and the second build is easier once the first one has shipped. Ambition does the opposite: an over-scoped first build that stalls teaches everyone that AI is a distraction. For the fuller version of this exercise, the 30-day operating diagnostic and the workflow assessment framework carry the complete scoring rubric. The 30-minute version is enough to find the first candidate.

Ordinary automation, or an agent?

Once a workflow is circled, one design question decides most of the cost and most of the risk: does this need an agent, or does it need ordinary automation? People reach for an agent by default because it is the interesting answer. It is usually the wrong one.

This distinction is where budgets get saved or wasted. A tool like n8n runs fixed-path automation for roughly £20 per builder seat per month, is SOC 2 and ISO 27001 compliant, and self-hosts if your data cannot leave the estate. Most of the queue-clearing wins on the audit sheet are exactly this: deterministic, auditable, boring, and done in a fortnight. Reserve the agent for the workflow where the path genuinely branches on what the model reads. And when you do build extraction into it, build it model-only. Regex fallbacks look like a safety net and behave like a trap: one run of a fragile pipeline can produce hundreds of plausible-looking wrong outputs before anyone notices. If the model cannot do the extraction, the answer is a better prompt or a human step, not a regex that fails silently.

What to do once you have a gap

Finding the gap is half the work. Designing the workflow that fills it is the other half, and it is where projects quietly go wrong. Three things to get right before you write a single prompt.

Decide what the AI is allowed to decide. Drafting, triaging, summarising, surfacing. Almost never deciding. The teams that move fastest are the ones that settled early on what they would never let a model sign off. That is what governance means at this level: setting the boundaries the work runs inside so it can move faster, safely, rather than a policy document nobody reads.

Design the human checkpoint. Someone clicks something. The audit log captures who and when. Nothing ships to a customer or an employee without a human in the loop, at least through the first quarter. The checkpoint is not a lack of trust in the model. It is what lets you defend the workflow when someone asks who approved a given output six months from now.

Pick the smallest viable shape. One workflow, one team, one model. Not a platform, not a fleet of agents. The recurring failure modes when teams skip this are catalogued in why AI pilots stall at production: a manual data pipeline, a hacked integration, governance living in a Slack thread, and nobody who owns the workflow on the Monday after launch. If the workflow really does need more than one step the model runs end to end, that is agent territory and a different conversation, not another prompt.

The win, when it lands, rarely shows up as fewer people. In one defence-tech engagement the systems the team built and owned reclaimed 83 hours a week and handled 70% of routine queries, with zero critical issues two months on. Nobody was made redundant. The same team cleared far more volume, and the measure that caught it was queue length, not the org chart.

The gaps most companies skip, and why

Three reasons the diagnosis gets skipped, and all three are worth naming so you can catch yourself doing them.

The first is that diagnosis is unglamorous. Nobody wants to be the leader who spent a quarter mapping workflows while a competitor shipped an agent. Resist it. The competitor's agent is almost certainly aimed at the wrong gap, and you will find that out when they quietly switch it off.

The second is that the gaps that matter sit inside the boring functions, not the headline ones. Operations, finance close, onboarding, internal Q&A. Sales-floor AI gets the press. The compounding value is upstream, in the queues nobody demos.

The third is that the people who know where the gaps sit are usually too busy filling them by hand to map them. The diagnosis has to be carved out deliberately, with the operating leader, away from the queue for half an hour.

That is the work. Run the four signals over the boring functions, pick one gap, build the smallest viable thing, ship it, then do it again. Six months in you have a portfolio of workflows the team owns. Two years in you have an AI operating system rather than a drawer of stalled pilots. The starting point is not a strategy deck and not a tool shortlist. It is one process, mapped properly, which is exactly what a Grain Audit is for.