The 5 Questions That Expose Broken Operations

This is not a data readiness checklist. It is not a technical assessment of your systems. Those have their place, but they are not what this article is about.

This is about the questions that, when asked in a leadership meeting, produce an immediate and visible discomfort. Not because the questions are complicated. Because the answers are.

Here are five of them. They are strategic, not technical. They do not require an audit or a consultant. They require honesty and about thirty minutes of conversation between the people who run the business.

Ask them. See what happens.

1. What would happen if our three most operationally critical people handed in their notice on the same day?

This is not a hypothetical designed to cause panic. It is a resilience test.

In most businesses, there are individuals whose departure would cause immediate operational disruption - not because they are irreplaceable in terms of skill, but because they hold knowledge that has never been captured anywhere else. They know how the pricing model works. They know which supplier needs a phone call instead of a purchase order. They know that the monthly reconciliation requires a specific sequence of steps that is documented nowhere.

If the answer to this question is "we would be in serious trouble," then your operation does not run on systems. It runs on individuals. And individuals leave, get ill, retire, and move on.

The follow-up question is: what would it take to capture that knowledge into structured processes and systems so that the operation is not dependent on any one person? That is not a technology question. It is an IT and process strategy question.

2. How many different answers do we get when we ask "what was our revenue last month?"

This question exposes data inconsistency. And in a remarkable number of mid-market businesses, the answer is: at least two, sometimes three.

Finance has one number. Sales has another. Operations might have a third. The differences are usually caused by timing (when transactions are recognised), scope (what gets included), or source (which system the number comes from).

The problem is not that these differences exist. It is that they are never resolved. Leadership receives a report that says one thing, and then someone in the meeting says "actually, my numbers show something different," and the next twenty minutes are spent debating methodology instead of making decisions.

If your business cannot produce a single, agreed revenue number from a single source in under five minutes, your data and systems integration is not ready for serious decision-making - let alone AI.

3. What percentage of our processes are documented accurately enough for a new starter to follow them without help?

The answer, in most businesses, is low. Surprisingly low.

There are usually process documents somewhere - in a shared drive, in a wiki, in a folder that someone set up three years ago. But they are outdated. They describe how the process was supposed to work, not how it actually works. And the gap between the two has widened over time as people adapted, built workarounds, and stopped updating the documentation.

The practical test is simple: could you hand your documented processes to a competent new hire and have them operational within a week? If the honest answer is no - if onboarding actually takes months and relies on shadowing experienced colleagues - then your processes are not captured. They are oral traditions.

This matters because anything you want to automate, improve, or apply AI to must be understood first. You cannot improve what you have not defined.

4. How much time do our teams spend each week moving data between systems manually?

This is the question that produces the most uncomfortable silence, because nobody has measured it - but everyone knows the number is high.

Every CSV export that gets imported into another system. Every time someone copies a figure from one screen and types it into another. Every email that contains information that should have been captured in a system but was not. Every spreadsheet that exists solely to bridge two platforms that do not talk to each other.

Add up those hours across the business. Include every department. Be honest about it.

In most mid-market companies, the total is somewhere between fifty and two hundred hours per month. That is one to five full-time employees' worth of capacity, consumed entirely by work that targeted business automation would remove.

That is not a technology cost. That is an operational tax - paid every month, invisible on the P&L, and completely avoidable.

5. If I asked each department head to describe their biggest operational bottleneck, would they give me data or opinions?

This is the question that separates businesses that measure from businesses that feel.

In an operationally mature business, the answer comes with data: "Our order processing takes an average of 3.2 days, with the bottleneck at the approval stage where 40% of orders wait more than 24 hours."

In most mid-market businesses, the answer comes with anecdote: "Things feel slow. We are always chasing. The team is stretched." These are real problems, genuinely felt. But they are not actionable because they are not measured.

If your leadership team cannot describe their bottlenecks with specifics - how long, how many, how often, at what cost - then you do not have operational visibility. You are managing by intuition. And intuition does not scale.

What these questions reveal

These five questions do not require any technology to answer. They do not require a consultant. They require honesty and about thirty minutes of conversation.

What they reveal is the gap between how a business thinks it operates and how it actually operates. That gap is where the waste lives - the time, the cost, the risk, the missed opportunities.

Most businesses know, at some level, that these problems exist. But because nobody has asked the questions directly, the problems remain vague, unmeasured, and unaddressed. They are felt but not quantified. And things that are not quantified do not get fixed.

Ask these five questions at your next leadership meeting. Write the answers down. You will have a clearer picture of your operational reality than most strategy documents could ever give you.

And if the answers make you uncomfortable - good. That discomfort is the starting point for genuine improvement.