Even the best-designed procedures can’t anticipate everything that happens during a working day. Understanding the difference between how work is planned and how it’s actually carried out can reveal a great deal about the people, processes and decisions that keep operations running.
On paper, most processes look straightforward. A job is assigned, the relevant instructions are followed, the necessary checks are completed and the work is signed off. Each stage has a clear purpose, and everyone understands what should happen next.
But anyone who has spent time on a factory floor, at a construction site, maintaining equipment or delivering services in the field knows that real work is rarely quite so predictable.
Equipment behaves unexpectedly. A replacement part doesn’t arrive. Site conditions have changed since the last visit. A task takes longer than anticipated, or an experienced colleague spots something that the written procedure doesn’t cover.
People have to make decisions, often with limited time and incomplete information. And sometimes, the way they get the job done looks quite different from the process originally designed.
That doesn’t necessarily mean the process has failed, or that employees are doing something wrong. It may simply mean the organisation hasn’t fully accounted for the realities of the work.
The Difference Between Work as Imagined and Work as Done
Human factors and safety researchers have long recognised a distinction between work as imagined and work as done.
Work as imagined describes how a task is expected to be performed. It’s reflected in operating procedures, training materials, process maps, risk assessments and management systems. These documents establish the intended approach, often based on the conditions and resources expected to be available.
Work as done is what actually happens when people carry out those tasks in real working conditions.
The distinction matters because the two are not always identical.
A maintenance engineer arriving to inspect a piece of equipment knows the procedure, assumes the machine is accessible, the necessary tools are available and the inspection can proceed in the expected sequence.
In practice, access might be restricted, another team may still be working nearby or the equipment may be in a different condition from the one anticipated.
The engineer still has a job to do, but completing it safely may require stopping, reassessing the situation, contacting a supervisor or following an approved alternative procedure.
The original process wasn’t necessarily badly designed. It simply couldn’t account for every possible situation.
The challenge for organisations is understanding where these differences occur, why they happen and what they reveal about the way work is really performed.
Why People Don’t Always Follow the Process Exactly
It’s tempting to assume that deviations from a procedure come down to poor training, a lack of attention or employees choosing to take shortcuts.
Sometimes those factors do play a part. But the reasons are often more complicated.
1. Working conditions are constantly changing
Procedures are generally developed around a defined set of circumstances. Real working environments are much less consistent.
A production operator might encounter unexpected material variation. A utilities engineer could arrive at a site where access arrangements have changed. An installation team may discover that the customer’s premises don’t match the original survey.
These situations require people to respond to conditions that weren’t anticipated when the process was written.
A procedure that works perfectly under normal circumstances may become difficult, impractical or even unsafe when those circumstances change.
2. People are managing competing priorities
Frontline employees rarely have just one responsibility.
They’re expected to complete work efficiently, maintain quality, follow safety requirements, respond to changing priorities and keep customers or colleagues informed.
Those expectations don’t always sit comfortably together.
For example, a technician may be under pressure to restore equipment quickly while also completing detailed inspection checks. A warehouse team may be dealing with an unexpected delivery at the same time as preparing an urgent order.
When demands compete, people make judgements about what needs attention first.
Good organisations recognise these pressures and make it clear that safety and essential controls must not be compromised to meet productivity targets.
3. Written instructions can’t capture every decision
Procedures are essential for consistency, particularly where safety, quality and compliance are concerned.
But even detailed instructions can’t anticipate every judgement a skilled employee might need to make.
Experienced workers often recognise subtle signs of a developing problem, understand how different conditions affect a task or know when something doesn’t look quite right.
That knowledge can be enormously valuable, especially when it helps people recognise when to stop, seek advice or escalate an issue.
The difficulty comes when important decisions remain invisible to the wider organisation.
If a technician identifies an unexpected condition and follows an approved alternative approach, is that information captured?
Can the next person learn from it?
Does the organisation know that the original procedure may need reviewing?
Without that feedback, valuable operational knowledge can remain confined to individual employees.
4. The easiest way isn’t always the official way
People naturally look for efficient ways to complete familiar tasks.
Sometimes this leads to sensible improvements. At other times, it can create informal workarounds that bypass important checks or introduce unnecessary risks.
The distinction is important.
A worker finding a clearer way to organise tools is very different from skipping an inspection because the required form is difficult to access.
Rather than treating every workaround as the same problem, organisations need to understand why it developed.
Is the procedure unnecessarily complicated?
Are the right resources available?
Has the working environment changed?
Or is there a misunderstanding about why a particular control matters?
Understanding the cause is far more useful than simply reminding everyone to follow the rules.
Human Judgement Is Part of the Process
There’s a tendency to think of consistency and flexibility as opposing ideas.
Standardisation is associated with reliability, while human judgement is sometimes viewed as a source of variation.
In reality, most successful operations need both.
Standard procedures establish expectations, provide essential safeguards and help people perform work consistently. Human judgement allows employees to recognise situations that fall outside those expectations and respond appropriately.
The aim shouldn’t be to eliminate judgement, but to establish where it is needed, what decisions employees are authorised to make and when they must stop or escalate a problem.
An inspection procedure, for example, might specify exactly what needs checking and what constitutes an acceptable result. But if an inspector encounters an unexpected defect, they may need to document the finding, isolate the equipment or request specialist advice.
That decision-making is not a failure of standardisation. It’s part of carrying out the work responsibly.
The most effective processes support employees in making those decisions rather than assuming every task will unfold exactly as planned.
What Happens When You Only See the Finished Job?
One of the difficulties with understanding real-world work is that management systems often provide a simplified view of what happened.
A job was scheduled. It was assigned to someone. The status changed to complete.
From a planning perspective, that may be enough to confirm that the work has progressed.
But it doesn’t necessarily explain what happened between those two points.
Was the task completed as expected?
Did conditions change?
Were additional checks needed?
Did the employee encounter an issue that should be addressed before the next job?
This is particularly important in organisations where work takes place across multiple sites, shifts or teams.
When the details of execution aren’t visible, managers may assume that the documented process accurately reflects everyday practice.
Over time, that can create a growing difference between the way work is managed and the way it actually happens.
It’s also one reason organisations are increasingly looking beyond their traditional planning and management systems to understand the execution of frontline work.
Why Listening to Frontline Teams Matters
The people carrying out a process every day are the first to know where it doesn’t reflect reality.
They know which instructions are difficult to follow, which tasks regularly take longer than expected and which situations require additional support.
Yet that experience doesn’t always find its way back into process design.
Sometimes employees don’t have an easy way to raise issues. Sometimes the information is shared informally but never documented. And sometimes people are reluctant to mention workarounds because they worry they’ll be blamed for not following the procedure.
That last point is especially important.
If organisations want an accurate picture of how work is performed, employees need to feel comfortable explaining what happens when things don’t go to plan.
This doesn’t mean accepting unsafe practices or overlooking deliberate breaches of essential controls. It means creating an environment where problems can be discussed, investigated and addressed fairly.
When people can explain why a process is difficult to follow, managers gain information that wouldn’t necessarily appear in a performance report or audit.
They may discover that a procedure needs updating, a particular task requires better equipment or employees are regularly compensating for a problem elsewhere in the operation.
Those insights can lead to more effective improvements than simply issuing another instruction.
Technology Should Support the Reality of Work
Digital technology has an important role to play in helping you understand and support frontline activities.
But digitising an existing procedure doesn’t automatically make it more effective.
If a process is confusing, impractical or based on unrealistic assumptions, putting it onto a tablet or smart glasses won’t necessarily solve the underlying problem.
The real opportunity comes from using technology to make instructions easier to access, capture relevant information as work happens and provide a clearer connection between frontline teams and the people responsible for managing processes.
For example, digital operational workflows can help employees follow the correct steps, document unexpected conditions, capture photographs and raise issues without relying on separate paperwork.
That information can then help supervisors and process owners understand where the planned approach works well and where further investigation may be needed.
However, technology should never encourage employees to continue with unsafe work simply to complete a digital checklist. Clear stop-work and escalation arrangements remain essential.
The objective is to support people in carrying out work safely and consistently, while making it easier for organisations to learn from the reality of their operations.
Better Processes Begin With Better Understanding
Every organisation needs procedures. Without them, consistency, quality, safety and accountability become much harder to maintain.
But a procedure is a description of how work should happen, not a guarantee of how it will happen.
Real-world operations involve changing circumstances, competing demands and decisions that can’t always be anticipated in advance.
Recognising that complexity isn’t an argument against standardisation. It’s an argument for making processes more realistic, more responsive and better informed by the people who use them.
When organisations understand the difference between work as imagined and work as done, they can begin to identify where procedures need strengthening, where employees need additional support and where valuable knowledge is being lost.
The goal isn’t to design a perfect process on paper. It’s to create processes that work reliably in the real world.
Further Reading
The Work Execution Layer: Connecting Business Systems With Frontline Work: Explore why planning and management systems don’t always provide a complete picture of how work is carried out, and how organisations can improve visibility between their systems and frontline operations.