The Question Queue: Measuring and Reducing Interruption Load in UK SMEs

There is a particular kind of tiredness that comes from being interrupted rather than from being busy. Ask most owner-managers of a UK SME how their week went and they will describe a sequence of small, reasonable questions — none of which took longer than four minutes, all of which together consumed the days they had set aside for thinking.

The instinct is to treat this as a diary problem and reach for the calendar: block out Tuesday mornings, decline more invitations, close the door. Those measures help at the margins. But in most businesses we work with, a heavy interruption load is not primarily a scheduling failure. It is a symptom of two things sitting underneath: knowledge that lives in a person rather than in a document, and decisions that nobody has been formally authorised to make.

This article sets out a modest way to test that proposition in your own organisation.

The cost that never reaches a report

Interruptions are invisible to management accounts. There is no line for them, no variance to investigate, no month-end reconciliation that reveals them. Yet their effects are real and compounding: fragmented attention on complex work, decisions made twice because the first answer was verbal and unrecorded, and a slow drift towards a business where the most experienced people spend their day answering rather than improving.

There is also a quieter cost. When the answer desk is always open, staff learn to ask before they think. Judgement, which only develops through use, stays undeveloped. The managing director becomes more necessary each month, not less.

A one-week capture method

You do not need software for this. A single sheet of paper, or a shared spreadsheet, is sufficient — provided the discipline is genuine.

Ask every participant to log each approach that interrupts a piece of planned work. For a managing director or operations lead, that might be twenty to forty entries across five days. Four fields are enough:

• Who asked — name and role, not department.
• What they needed — a fact, an approval, a judgement call, or a sense-check.
• What they did next — acted on the answer, waited, or went elsewhere.
• How long it took — including the time to return to the original task, which is usually longer than the conversation.

Run it for one full week and include a Friday. Patterns that appear on Monday and Thursday often vanish by the end of the week, and you want to see the whole cycle.

Sorting the load into four causes

The value of the exercise lies in classification, not in the count. Read the log back and place each entry into one of four buckets.

Missing documentation. The answer exists and is stable, but it is not written down anywhere findable — the specification of a standard job, the cut-off time for despatch, the correct discount authority. This is a filing problem disguised as a people problem.

Unclear decision rights. Two people could reasonably answer and neither is certain they should. These entries tend to repeat with slight variations, and they are the most expensive because they consume senior time and still leave ambiguity behind.

Undocumented judgement. The question is genuinely situational — a customer's credit history, a supplier's reliability, the mood of a key account. This is where senior experience earns its keep, and it should not be automated away.

Genuine escalation. A risk, a complaint, a safety matter, a large sum of money. These should reach you quickly and without apology.

In our experience, the first two buckets usually account for well over half of the total. That is the finding worth acting on.

Three lightweight fixes

The temptation after an audit is to write a manual. Resist it. Manuals are read once and consulted never. Three narrower interventions tend to stick.

Published office hours

Set two or three fixed windows each week — say 11am to 12pm on Tuesday and Thursday — when anyone may bring a question without appointment. Outside those windows, the expectation is that questions arrive with a proposed answer attached. The effect is rarely a reduction in total contact, but a marked improvement in the quality of what arrives. People prepare when they know they will be asked to think.

A decision log

A single shared document, one line per material decision: date, question, decision, who decided, and the reasoning in a sentence. It takes under a minute to complete and pays for itself the first time somebody asks why a supplier was chosen two years ago. It also, quietly, makes decision rights visible — a name against a category of decision is a form of delegation.

A short answer playbook

Not a handbook, but a page per recurring question, written by the person who most often answers it. What is our lead time? Who approves a credit account? What do we do when a delivery is short? Ten pages will cover most of what currently walks through your door.

What to measure afterwards

Repeat the capture for one week roughly a quarter later. Three numbers tell you whether anything has changed: the total count of interruptions, the proportion resolved without reaching you, and the repeat rate — the share of questions you have now answered more than once on the same subject. A falling repeat rate is the clearest sign that knowledge has moved out of your head and into the business.

A word of caution

Interruption load is not the same as accessibility, and the two should not be confused. A leader who becomes unreachable has not solved a process problem; they have created a different one, usually discovered during a crisis. The aim is to make the route to an answer reliable and well-documented for the routine, so that your attention is genuinely available for the exceptional.

The questions will keep coming. The objective is that they arrive better formed, land in the right place, and leave a record behind.