Most companies have processes that look perfect on paper. The steps are clearly defined, responsibilities are assigned and the necessary checks have been documented. The process may have been reviewed, approved and included in training materials. From a management perspective, everything appears to be in place.
Yet the same problems keep appearing.
Jobs take longer than expected. Important information gets missed. Employees develop their own ways of completing tasks, and supervisors spend time resolving issues that the process was supposed to prevent.
Sometimes, the work gets done despite the procedure rather than because of it.
It’s a familiar situation across manufacturing, maintenance, construction, utilities, logistics and field services. And it raises an important question: if a process is properly documented, why doesn’t it always work?
The answer often lies in the difference between designing a process and understanding how it performs under real working conditions.
Why Do Processes Fail in Practice?
Processes often fail because they don’t fully take into account the conditions, resources and decisions involved in carrying out the work.
A SOP might be technically correct but unnecessarily complicated. It may rely on information that isn’t readily available, assume that equipment or personnel will always be accessible, or require employees to complete steps that don’t fit naturally into their working day.
Sometimes the process was effective when it was introduced, but the business has since changed. New equipment, different customer requirements, additional systems or changes in staffing can all affect how work is carried out.
Over time, the documented procedure and the reality of the task begin to drift apart.
Thinking about an equipment inspection. The procedure requires several checks before a machine can be returned to service. The instructions are clear, but the necessary information is spread across different systems, the inspection form may be difficult to complete on site and supporting photographs have to be uploaded separately.
The inspector understands what needs doing. The difficulty is completing everything efficiently while working in the environment the process was designed for.
People may begin making notes to enter later, relying on memory or developing informal arrangements with colleagues. Some adaptations are harmless, but others create gaps in reporting, traceability or quality assurance.
The problem isn’t always a lack of training or a failure to follow instructions. Sometimes the process itself makes the right way of working unnecessarily difficult.
An effective process needs to work for the people carrying it out, not just the people reviewing it.
Five Warning Signs That a Process Isn’t Working
Process problems aren’t always obvious. People can become so accustomed to working around them that the difficulties are accepted as a normal part of the job.
However, there are several warning signs that suggest a process needs reviewing.
1. The Same Problems Keep Coming Back
Recurring issues often indicate that the underlying cause hasn’t been fully addressed.
Perhaps an inspection repeatedly identifies the same defect, a particular installation regularly requires a return visit or a maintenance task consistently produces incomplete reports.
Individual incidents may be resolved, but if the process contributing to them remains unchanged, the problem is likely to return.
Rather than treating every occurrence separately, look for patterns across jobs, locations, teams or equipment.
2. People Have Developed Unofficial Workarounds
Workarounds are one of the clearest indicators that a process may not reflect the reality of the task.
An engineer might keep a separate checklist because the official form is difficult to use. A supervisor may maintain a spreadsheet alongside the company’s main system because important information isn’t readily available.
These arrangements can help people get work done, but they may also introduce duplication, inconsistent information or risks that aren’t visible to management.
Not every workaround is evidence of poor practice. Sometimes it highlights a genuine opportunity to simplify the process.
However, workarounds that bypass essential safety or quality controls need to be solved quickly.
3. Tasks Regularly Take Longer Than Expected
If a job consistently exceeds its planned duration, the problem may not be employee performance.
The original estimate might overlook preparation, travel between work areas, access restrictions, equipment availability or the time required to complete supporting documentation.
It’s worth understanding where the additional time is going before adjusting targets or asking people to work faster.
A more accurate picture of the task can help organisations plan resources and set realistic expectations.
4. Important Information Is Missing or Difficult to Find
A process may appear complete while leaving important questions unanswered.
Were the necessary checks carried out? What happened when an unexpected issue arose? Was the correct equipment used? Has the customer approved the completed work?
If employees regularly need to chase colleagues, search through emails or reconstruct what happened after a job, the process may not be capturing the right information at the right time.
This can create unnecessary administration and make audits, investigations and customer queries more difficult.
5. Results Vary Significantly Between Teams or Locations
Some variation is inevitable, particularly when working conditions differ.
But if two teams carrying out comparable work consistently produce different results, it’s worth investigating why.
One team may have developed a more effective approach. Another may lack access to the same equipment, information or training.
Understanding those differences can reveal opportunities to improve consistency without assuming that every variation is a problem.
Before Changing the Process, Understand What’s Going Wrong
When a process isn’t working, the natural response is often to update the instructions.
Sometimes that’s exactly what’s needed. But rewriting a procedure before understanding the problem can simply produce a more detailed version of something people already struggle to follow.
A better starting point is to investigate how the process actually operates.
That means looking beyond the documented steps and understanding what employees need to do to complete the work.
What information do they need? Which systems or tools do they use? Where do delays occur? What happens when conditions differ from those anticipated?
Most importantly, what are people already doing to make the process work?
The answers may reveal that the problem isn’t the procedure itself.
Perhaps a task requires approval from someone who isn’t always available. Maybe the necessary information is stored in several different places. Or the process assumes equipment and resources will be available when they frequently aren’t.
Until those underlying issues are understood, changing the instructions may have little effect.
Six Practical Steps to Improve a SOP
Procedure improvement doesn’t always require a major transformation project.
For many organisations, meaningful progress starts with examining one recurring problem, understanding its causes and making a series of manageable changes.
The following six-step approach can help.
Step 1: Identify a Process With a Clear Problem
Start with something specific rather than attempting to improve an entire operation at once.
It might be a maintenance task that regularly overruns, an inspection with incomplete reports or an installation process that generates repeated customer queries.
Choose a process where the impact is visible and where improvements can be measured.
Be clear about the problem you’re trying to solve. “Our reporting needs improving” is difficult to investigate. “One in five completed inspection reports requires additional information before approval” gives you something more specific to work with.
Where possible, establish a baseline before making changes.
Step 2: Observe How the Work Is Actually Carried Out
Review the existing procedure, but don’t rely on it as the only source of information.
Speak to those that perform the task and, where practical and safe, watch the work taking place.
Look at the complete process, including preparation, access to information, equipment, approvals, checks and reporting.
Pay attention to activities that aren’t included in the written instructions but are necessary to complete the job.
The objective isn’t to catch people doing something wrong. It’s to understand what the process genuinely requires.
Step 3: Identify the Underlying Causes
Once you understand the task, compare the intended process with what actually happens.
Look for unnecessary duplication, unclear responsibilities, missing information, delays, difficult handovers and steps that depend heavily on individual knowledge.
Ask why the difficulties occur rather than concentrating solely on their consequences.
For example, incomplete reports may initially look like an employee performance issue. But it might show that the reporting requirements are unclear, the necessary information isn’t available during the task or employees are expected to complete documentation long after leaving the site.
It’s also important to distinguish between legitimate responses to changing conditions and practices that introduce unacceptable risks.
The aim is to understand the cause rather than treat every deviation in the same way.
Step 4: Involve Employees in Developing Improvements
The people carrying out the work are often best placed to explain which changes would make a genuine difference.
A supervisor may identify a need for clearer responsibilities, while an experienced technician might suggest a more practical sequence of checks.
Employees can also highlight unintended consequences that aren’t obvious during process design.
For example, removing a step might save time for one team but create additional work for the next.
Involving the people affected by a change helps ensure that improvements are realistic and don’t simply move the problem elsewhere.
Step 5: Test the Revised Process Before Rolling It Out
A change that looks sensible in a meeting may behave differently under normal working conditions.
Where appropriate, test the revised process with a small group, location or task type before introducing it more widely.
Check whether employees can follow the updated approach, whether it produces the intended results and whether any new difficulties have appeared.
Changes affecting safety-critical activities, regulated requirements or formal quality controls should follow the organisation’s established review and approval procedures.
Testing helps avoid replacing one ineffective process with another.
Step 6: Measure Whether the Change Has Worked
The final step is to check whether the improvement has delivered the expected result.
Useful measures will depend on the process, but might include task completion times, repeat visits, missing information, rework, quality issues or the number of exceptions requiring supervisor intervention.
Compare the results with the baseline established at the beginning, allowing enough time and comparable working conditions to make the findings meaningful.
Employee feedback is equally valuable.
A process may appear more efficient on a dashboard while creating additional work that isn’t being measured.
Reviewing both operational results and frontline experience provides a more balanced picture of whether the change has genuinely helped.
A Practical Example: Reducing Repeat Site Visits
Imagine a field service operation experiencing an increasing number of return visits because engineers haven’t captured all the information needed during the original appointment.
Each return visit creates additional costs, disrupts scheduling and delays completion for the customer.
At first, the problem appears to be inconsistent reporting. Managers might assume that engineers need reminding to complete their paperwork properly.
But when you investigate the process, a different picture emerges.
Engineers explain that the existing reporting form doesn’t clearly identify which photographs and measurements are required for different types of jobs. Some information is recorded on paper, while other details are entered into a separate system after leaving the site.
Different engineers have developed their own approaches, and the information captured varies considerably.
Using the six-step framework, the business can take a more structured approach.
Identify the problem: Establish how frequently missing information leads to return visits and which types of jobs are most affected.
Observe the work: Speak to engineers and review how information is captured during actual site visits.
Investigate the causes: Identify unclear reporting requirements, duplicated administration and gaps between the inspection procedure and the final report.
Develop improvements: Work with engineers to establish clearer reporting requirements, including which evidence is needed and when unexpected findings should be escalated.
Test the changes: Trial the revised process with a small group before introducing it across the business.
Measure the results: Monitor missing information, report completion and repeat visits to determine whether the changes have helped.
The important lesson is that the original problem wasn’t necessarily poor employee performance.
The process didn’t make the requirements sufficiently clear or easy to complete during the work.
By addressing those difficulties, the business has a better opportunity to improve reporting consistency and reduce unnecessary return visits.
This is an illustrative example, but the same approach can be applied to inspections, maintenance, quality checks, installations, training procedures and many other frontline activities.
How Do You Measure Whether a Process Has Improved?
Not every process needs a complicated set of performance indicators.
A few well-chosen measures can often reveal whether an improvement is working.
| Area | Questions worth asking |
|---|---|
| Completion | Are tasks being finished within realistic timescales? |
| Quality | Are errors, defects or repeat visits decreasing? |
| Consistency | Are comparable jobs producing more consistent results? |
| Reporting | Is the necessary information captured accurately and on time? |
| Exceptions | Are unexpected problems being identified and addressed appropriately? |
| Employee experience | Is the process easier to follow without compromising essential controls? |
The most useful measures are those that help you understand the process rather than simply judge individual performance.
For example, a rise in reported issues isn’t automatically a negative result. It may indicate that employees now have a better way to raise problems that previously went unreported.
And, faster completion isn’t necessarily an improvement if important checks are being missed.
The objective is a process that delivers reliable outcomes, not simply one that looks efficient on paper.
Why Small Problems Can Have a Big Impact
It’s easy to think that process improvement usually occur thanks to large-scale transformation programmes. But, many operational problems are caused by relatively small issues repeated across hundreds or thousands of jobs.
An unnecessary approval, a duplicated form or an unclear handover might add only a few minutes to an individual task.
Across multiple teams and locations, those minutes can become a significant administrative burden.
Small problems can also have consequences beyond lost time.
Missing information may delay customer sign-off. An unclear inspection requirement can lead to inconsistent reporting. An outdated procedure may mean employees rely on informal advice rather than an approved method.
Addressing these issues can improve the working experience for employees while giving managers greater confidence in the information coming back from frontline operations.
The challenge is identifying them before they become accepted as unavoidable parts of the job.
How Digital Tools Can Create Better Processes
Technology can make it easier to identify and address operational problems, but it isn’t a substitute for understanding how the work is carried out.
Digitising a complicated or ineffective procedure won’t necessarily make it more useful.
The opportunity comes from making instructions easier to access, capturing relevant information during the task and giving employees a straightforward way to report unexpected conditions or suggest improvements.
For example, digital operational workflows can help make reporting requirements clearer, capture photographs and supporting evidence, and reduce the need to reconstruct information after a job has finished.
That information can also help supervisors identify recurring issues and understand where a process may need reviewing.
However, collecting more data isn’t automatically an improvement.
Someone still needs to review the information, decide what should change, update the approved procedure and communicate those changes to the people carrying out the work.
Digital tools are most valuable when they support that wider process rather than simply replacing paperwork.
For a broader look at using frontline information to support ongoing improvement, explore our guide to Data-Driven Continuous Improvement.
Making Process Improvements That Last
One of the reasons ineffective processes persist is that reviewing them is often treated as a separate activity.
Procedures may be updated during scheduled audits, after a significant incident or as part of a formal improvement project.
Those reviews are important, but they don’t always capture the smaller problems employees encounter every day.
A more responsive approach makes it easier for frontline teams to highlight difficulties as they arise and ensures that feedback reaches someone who can act on it.
It also means checking that improvements remain effective after the initial change.
A revised procedure may work well during a trial but become less effective as working conditions, equipment or responsibilities change.
Regular feedback and appropriate performance measures help organisations recognise when further adjustments are needed.
The aim isn’t to constantly rewrite procedures. It’s to make sure they remain relevant, practical and reliable.
Frequently Asked Questions
Common warning signs include recurring problems, repeated delays, unofficial workarounds, missing information and inconsistent results between teams or locations. Reviewing operational performance alongside employee feedback can help identify where the process is creating unnecessary difficulties.
Start by identifying a specific problem and observing how the work is actually carried out. Investigate the causes, involve employees in developing improvements, test the revised process and measure whether the changes have delivered better results.
Review frequency should reflect the risks and requirements of the activity. Safety-critical and regulated processes may have defined review schedules, while other procedures can be reviewed when recurring issues, operational changes or employee feedback indicate that improvements are needed.
Good Processes Need to Work Beyond the Page
A process can be carefully designed, thoroughly documented and formally approved, yet still struggle when it meets the realities of everyday work.
That doesn’t mean procedures are unimportant. It means organisations need to look beyond the document to understand whether the process is delivering the results it was designed to achieve.
By observing how work happens, listening to frontline employees and investigating recurring difficulties, businesses can make improvements that are both practical and sustainable.
The most effective processes aren’t necessarily the most detailed or complicated.
They’re the ones people can follow confidently, that support good decisions and that continue to work when real life doesn’t go exactly to plan.
Further Reading
Why Real-World Work Rarely Follows the Perfect Process: Explore the human factors, changing conditions and operational decisions that explain why work doesn’t always happen exactly as intended.
The Work Execution Layer: Discover how organisations can improve the connection between business systems and the work carried out by frontline teams.
Digital SOPs & Digital Work Instructions: Explore how accessible, up-to-date instructions can help teams carry out work more consistently.