I have a question I ask at every first meeting. Not early in the conversation — after the pleasantries, after the broad picture of the business has been painted, after the owner has given me the polished version of how things work. When there is a moment of genuine engagement, I ask: “If I could wave a hand and fix one thing about how your operations work, what would it be?”
I have asked this question — or a version of it — in dozens of conversations. The answer takes, on average, about eight seconds to arrive.
The owner knows. And if they do not have an immediate answer, I ask again: “Not in management meetings. On the ground. What is the thing your team mentions most often when they talk about what slows them down?”
That one never takes more than three seconds.
The first meeting guide I use internally is explicit about this dynamic. The people closest to the work know exactly what is wrong. They have known for years. The question is not whether the intelligence exists — it is why it does not reach the surface.
The answer varies, but it usually contains one or more of these elements.
The first is resignation. They raised it once. Perhaps twice. There were reasons why it could not be fixed right now. The project plan was always a few months away. Eventually, people stop raising things that never get acted on. The energy it takes to make the case is real. The probability of anything changing is low enough that the calculation stops being worth it.
The second is self-censorship about scale. The person doing the manual work has usually made a rough estimate of what it would take to fix. The estimate almost always overestimates the complexity. “It would probably take months to sort that out” is a common gloss on a problem that, when properly examined, takes about three weeks to address. The scale feels too large to propose seriously, so it does not get proposed.
The third is the absence of a format. Most businesses do not have a natural channel for operational improvement ideas. There are team meetings, one-to-ones, review processes. These forums are not well designed for the conversation “I think we’re wasting fourteen hours a week on this.” That kind of observation requires specificity, measurement, and a degree of courage that the standard meeting format does not support.
What happens when someone external asks the question is striking enough that I notice it consistently.
The first time I meet with a team — not the management, the people who actually do the work — the answers come quickly and with relief. Not defensiveness. Not suspicion. Relief. Someone is asking. Someone is writing it down. Someone has turned up specifically to listen to the answer and take it seriously.
There is a conversation I can describe with enough precision that I am confident it represents a consistent pattern rather than a single occurrence. I was speaking with an operations coordinator at a business I will describe as a mid-sized construction management company — 28 people, good revenue, recognised efficiency problems at the margins. Her title was Operations Coordinator. She had been in the role for four years.
Within ten minutes of sitting down, she described, unprompted, four processes that she personally found to be wasteful or unnecessary. She had the hours on two of them. She had a view on the fix for three of them. She had been doing this job for four years and not one of those processes had changed.
She was not bitter about it. She was, if anything, slightly embarrassed to be saying it out loud to a relative stranger. But when I asked whether she had raised these things, she said: “I mentioned one of them in my review last year. We talked about it for a bit. Then nothing happened.”
That was the whole reason nothing changed. Not neglect or incompetence — just the absence of a mechanism that converted operational intelligence into operational action.
There is a calculation I run, loosely, for businesses where this dynamic is evident. It goes like this.
An operations coordinator, administrative manager, or equivalent with four years in a role will typically have identified somewhere between three and six processes they consider meaningfully inefficient. The team around them — if the business has more than 15 people — will have a partially overlapping, partially distinct list. If you aggregate that list across a typical operations team in a 30-person business, you are usually looking at somewhere between ten and eighteen identified inefficiencies. Of those, industry benchmarks for businesses that have undertaken formal operational reviews suggest that between six and ten will be addressable with a proportionate investment of time.
The average addressable item in a business of that size carries a cost of between £8,000 and £25,000 per year in recoverable staff time, depending on frequency, seniority, and nature of the task. Apply the lower end of that range to six items and you have roughly £48,000 per year sitting inside the heads of your operations team. Unused. Already identified. Already articulated internally, at least in private.
That number is not a promise. It is a benchmark drawn from what operational reviews in businesses of that scale typically find. It might be lower for your business. It might be significantly higher. The point is that the gap between what your team knows and what has been acted on is unlikely to be zero, and it is unlikely to be small.
The reason I ask the question the way I do — “what would you fix if you could?” rather than “what are your efficiency problems?” — is deliberate.
“What are your efficiency problems?” is a management question. It invites a guarded answer. The person hears: audit. They give you the version they would give in a performance review.
“What would you fix?” is a different question. It invites imagination. It implies agency. It does not presuppose that what exists is the right baseline to be measured against. And it consistently surfaces things that more formal review processes miss.
The most useful intelligence in your business about how it actually works — and where it wastes money — is sitting in the heads of the people who do the work. Surfacing that intelligence is not difficult. It requires asking, listening, and taking the answers seriously. The problem, for most businesses, is that nobody has specifically gone looking.
The question worth sitting with: when did someone last ask your operations team what they would change — and actually write the answer down?