The Most Expensive Business Problems Usually Don’t Start That Way
Most business problems don’t start with alarms going off.
They start with something small.
A new employee starts before everything is ready. A manager has an important conversation but never writes it down. Someone notices something odd on payroll and assumes it’s fine.
Nothing terrible happened that day, so everyone moves on.
That is often how a small process problem gets the chance to become a much bigger one.
THE MISTAKE MAY NOT BE THE BIGGEST PROBLEM
Every business makes mistakes. A missed step, wrong entry, or forgotten task does not automatically turn into a major problem.
What matters is how quickly someone catches it.
Imagine a payroll error causes an employee to receive an extra $100. Catch it on the first payroll, and you have a $100 problem to solve.
But what if nobody catches it?
The same error happens again. Six months later, you may need to figure out how many employees were affected, how much money is involved, when the problem started, and how to correct it.
However, the original mistake is still the same.
What changed is the amount of time it went undetected.
We spend a lot of time trying to prevent mistakes but catching them quickly can be just as important.
DOES YOUR PROCESS KNOW WHEN SOMETHING GOES WRONG?
Most business processes are built around how work is supposed to get done.
Step 1. Step 2. Step 3. Done.
But there’s at least one other question worth asking:
What tells us when the process did not work?
Completing an I-9 may be part of onboarding. But what tells you when one is missing?
A manager may be responsible for employee documentation. But who notices when it never gets completed?
Payroll may be reviewed before it’s processed. But would that review catch the same error twice?
This creates a detection gap. A detection gap is the time between when a problem starts and when someone notices it. The longer that gap lasts, the more opportunity a small mistake has to grow.
5 SIGNS YOU MAY HAVE A DETECTION GAP
1. The same problem keeps coming back.
Fixing the result is not the same as fixing the cause. If the same mistake keeps happening, something in the process may be allowing it.
2. You usually find problems by accident.
An employee asks a question. Someone happens to notice a strange number. A manager stumbles across a missing document. Those are good catches, but accidental discovery is not a reliable safety net.
3. Nobody knows who checks the final results.
Completing a task and checking that it was completed correctly are different things. If everyone assumes someone else is checking, errors can sit unnoticed.
4. One employee is the control system.
If your answer is, “Susan would notice that,” you may have more risk than you think.
Experienced employees often know what looks wrong. But what happens when Susan is on vacation, changes roles, or leaves the company? If one person is your only safeguard, some of that knowledge needs to become part of a permanent and repeatable process.
5. You can fix the problem, but you can’t tell when it started.
Imagine finding an incorrect payroll setting today. You know how to fix it going forward, but can you tell when it changed?
Yesterday? Three months ago? Last year?
If you can’t determine how long a problem has been happening, figuring out its true impact can be much harder.
LOOK FOR THE DETECTION GAP
Choose one process you rely on regularly and ask:
- What could go wrong?
- What would alert us that it happened?
- Who would notice?
- How quickly would we know?
- Could we tell when the problem started?
Those questions go deeper than asking whether your business has a process. They tell you whether the process has a way to catch itself when something goes wrong because the fact is that mistakes are going to happen at some point, and the faster you can catch the mistake the less costly it will be.
