Your Staff May Not Be the Problem. Your Process May Be.
An employee makes a mistake. Management corrects the employee.
The mistake happens again.
Training follows. Supervision increases. Sometimes the employee is eventually replaced.
Then the same problem returns under somebody else.
At that point, continuing to treat the issue only as a people problem may be the wrong diagnosis. Business process problems often become visible through the employees doing the work, even when the underlying weakness sits somewhere else in the workflow.
The better question is not simply, “Who made the mistake?”
It is:
What allowed this mistake to happen, and could the same thing happen to another competent employee?
That changes the diagnosis.
A capable employee can still struggle when responsibilities are unclear, information arrives late, approvals are confusing, handoffs are weak or the organisation depends on informal workarounds to keep routine work moving.
The employee may still have a performance problem. But management should establish that rather than assume it.
When Business Process Problems Look Like Staff Problems
One mistake tells management very little.
The same mistake appearing under different employees tells management much more.
Consider a routine order process. One employee leaves out required information and is corrected. A second employee later makes the same omission. Then somebody else does it again.
Management can keep telling people to be more careful.
Or it can ask why the process keeps allowing the same error through.
Was the required information clearly defined?
Was there a point at which completeness should have been checked?
Did the employee have everything needed before starting the work?
Was responsibility for verification clear?
If the answer to those questions is uncertain, the problem is no longer only about the individual.
It is also about control.
Workarounds Can Hide a Weak Process
Some businesses appear organised because experienced employees have learned how to compensate for the system.
They know which manager has to be called personally before an approval moves.
They maintain their own spreadsheet because the official record cannot be relied upon.
They know who really handles an issue, even though the organisation chart says something different.
They understand which steps in the formal procedure are followed and which ones are quietly ignored.
The work gets done.
That does not necessarily mean the process works.
It may mean experienced people are carrying weaknesses that management cannot see.
The weakness becomes obvious when one of those employees is absent, transferred or leaves.
A sound process should not depend on private memory, personal relationships and unofficial shortcuts just to deliver routine work consistently.
Constant Management Intervention Is a Warning Sign
Managers should make decisions that genuinely require management judgement.
They should not have to direct every normal transaction.
When employees repeatedly ask:
“Who should approve this?”
“Can I proceed?”
“Where does this go next?”
“Who is responsible for this?”
the problem may not be a lack of initiative.
The authority may genuinely be unclear.
This often happens when responsibilities have evolved informally. The company has grown, more people have been added, departments have changed, but the flow of work has never been redesigned properly.
The result is predictable.
Management becomes part of the routine workflow.
If normal work regularly stops because a particular manager is unavailable, that is not just a staffing inconvenience. It is a process dependency.
The Failure May Be Between Departments
Many operational problems do not sit neatly inside one department.
They occur at the handoff.
Sales may believe it has completed an order correctly, but Operations receives incomplete information.
Customer Service may escalate a complaint, but nobody clearly accepts ownership.
Procurement may complete its internal activity while the requesting department still does not know when the requirement will be fulfilled.
Production may finish the item, but release or dispatch responsibility remains unclear.
Each department can say:
“We did our part.”
The customer can still receive a poor outcome.
The process therefore has to be examined from beginning to end, not only department by department.
Handoffs deserve particular attention because they are where ownership, information and timing often become blurred.
Rework Should Not Become Normal
Documents are returned for correction.
Orders are amended.
Customer information is requested again.
Invoices are queried.
Managers regularly send work back because something is missing.
Over time, people stop treating this as a failure.
It simply becomes “how we work.”
That should concern management.
Rework means the organisation is spending time correcting an output that should have been right earlier in the process.
The usual response is to tell employees to pay more attention.
Sometimes that is justified.
But “be more careful” is not a control.
Management should identify where the error could have been prevented, where it should have been detected and why neither happened.
That is the difference between correcting an incident and improving a process.
Dependence on One Employee Creates Operational Risk
Every company has people who are more experienced than others.
That is normal.
The problem starts when an important activity works only because one particular person is present.
If quotations are accurate only when one employee prepares them, complaints move only when one manager intervenes, or stock information makes sense only to the person who created the spreadsheet, the organisation has concentrated too much operational knowledge in individuals.
The immediate problem may appear to be staffing.
The deeper issue is continuity.
A good process does not remove judgement from experienced people. It makes sure routine work can still be performed by another competent person using clear responsibilities, reliable information and defined controls.
Repeated Training May Be Treating the Wrong Problem
Training is a common corrective action because it is visible and relatively easy to organise.
Sometimes training is exactly what is needed.
But training cannot fix an unclear approval route.
It cannot fix missing information.
It cannot fix two departments that both believe the other one owns the same activity.
It cannot fix a workflow that depends on verbal instructions.
And it cannot fix a control that takes place only after the failure has already reached the customer.
If different employees have been trained and the same operational problem keeps returning, management should stop assuming that more training will solve it.
That is the point at which a structured Process Improvement Review becomes relevant.
The purpose is to examine the actual workflow, responsibilities, evidence and controls to determine why the problem continues rather than prescribing another corrective action before the cause is understood. Astute positions this service specifically for recurring operational problems. (Astute Business Consulting)
People Problems and Process Problems Can Exist Together
Process thinking should not become an excuse for poor employee performance.
That would simply replace one bad diagnosis with another.
An employee may lack the competence required for the job.
Someone may knowingly ignore an established control.
Another employee may repeatedly fail to meet a clear standard even though the tools, authority, information and training are available.
Those are legitimate individual performance issues.
The point is narrower.
Management should first establish whether the employee failed inside a sound process or whether the process itself made failure more likely.
A useful diagnosis asks two questions:
Is the employee capable, supported and accountable?
Is the process clear, workable and controlled?
Both matter.
How to Tell Whether You Have a Staff Problem or a Process Problem
Do not begin with the person.
Begin with the work.
Is the expected result clear?
The employee should know what a satisfactory result looks like.
If the expected output changes depending on who is giving the instruction, performance will also vary.
Is responsibility clear?
There should be no uncertainty about who owns the activity, who approves it and who receives it next.
Where several people assume somebody else is responsible, delay is almost inevitable.
Does the employee have the required inputs?
People cannot consistently produce correct outputs from incomplete information.
Check whether the employee receives the right information, tools, authority and resources before the work begins.
Is the workflow understood?
A competent employee should know what happens next without repeatedly asking management for direction.
If the sequence exists only in people’s heads, the organisation does not yet have a reliable process.
Are the handoffs controlled?
When work passes from one person or department to another, the receiving party should know what is being transferred, what is expected and when action is required.
A handoff without clear acceptance is a common source of delay and blame.
Are errors prevented or merely discovered later?
A control is more useful when it prevents or detects a problem before significant rework, customer dissatisfaction or financial loss occurs.
Late detection is still better than no detection.
But it costs more.
Can another competent employee perform the same work?
This is one of the strongest tests.
If only one individual understands how to complete a routine activity correctly, the business has not fully converted knowledge into a working organisational system.
Start With a Diagnostic, Not a Conclusion
Where management is not yet sure what is causing inconsistent performance, it is premature to jump straight into redesigning processes or writing procedures.
Diagnosis comes first.
Astute’s Business Process Diagnostic examines areas such as how consistently work is done, who owns it, how activities are controlled and whether management has sufficient visibility into the process. The current diagnostic is specifically designed for established and growing businesses assessing process consistency and control. (Astute Business Consulting)
That makes it a sensible first step when management can see symptoms but has not yet established the cause.
Do Not Document a Bad Process
Another common response is:
“We need an SOP.”
Maybe.
But not yet.
Writing down a poorly designed process does not improve it. It simply gives the poor process a document number.
The work should be examined first.
Understand the actual flow.
Remove unnecessary steps.
Clarify responsibility.
Fix weak handoffs.
Decide where approvals and controls genuinely belong.
Then document the process employees need to follow.
This is also why process improvement should not be reduced to document production. Astute’s Process Excellence practice is structured around process diagnostics and redesign, roles and accountability, controls, documentation, KPIs and implementation rather than treating the procedure itself as the solution. (Astute Business Consulting)
Measure Whether the Process Is Actually Improving
Management also needs evidence that the process is getting better.
The right measure depends on the process.
For one activity, turnaround time may matter most.
For another, it may be the level of rework, incomplete submissions, customer complaints, missed deadlines or errors detected before release.
There is no value in measuring an activity simply because it is easy to count.
The measure should tell management whether the process is producing the result it was designed to produce.
That is the purpose of performance measurement.
The Question Management Should Ask First
When something goes wrong, the immediate question is usually:
Who made the mistake?
There are situations where that question needs to be answered.
But it should not be the only question.
Ask this as well:
What allowed the mistake to happen, and could the same failure occur under another competent employee?
If the answer is yes, management has learned something important.
The individual may still require correction, training or closer accountability.
But the process requires attention too.
That distinction matters because businesses lose time when they repeatedly treat symptoms while leaving the cause untouched.
Fix the Right Problem
Recurring errors, delays, rework and dependence on particular employees should be treated as management signals.
Not proof. Signals.
The job is to establish what sits behind them.
Sometimes the answer will be competence.
Sometimes it will be behaviour or accountability.
And sometimes management will discover that capable people have been trying to operate inside a process that is unclear, fragmented or poorly controlled.
The correct response depends on the diagnosis.
That is why the starting point should not be more training, another procedure or another warning.
It should be understanding what is actually going wrong.
Not sure whether the problem is your people, your process or both?
Use Astute’s Business Process Diagnostic to identify where inconsistent work, unclear responsibility, weak controls or management dependency may require closer examination. (Astute Business Consulting)
If the same operational problem is already recurring and management needs to understand why, consider a Process Improvement Review. (Astute Business Consulting)