Digitalising the Wrong Process
Why Technology Cannot Repair Process Design by Itself
A maintenance request once handled on one paper form now takes four screens, two approvals and a notification. The software has changed, but the technician still waits for the same clarification.
Digital transformation can make a process easier to record and track without making it clearer to perform. Technology can connect information and automate steps, but it cannot decide whether the underlying process is logical or well designed.
Before digitising a process, has the factory understood what it is digitising?
1. The Factory Often Digitises What It Already Does
Consider a maintenance request: an operator reports a problem, a supervisor reviews it, and Maintenance calls back for clarification before creating a work order and checking spare availability.
The factory digitises the sequence. The form becomes an app, notifications are automated and the spare-parts database is connected. Yet questions remain: who decides urgency, who owns the request between Production and Maintenance, and what happens when the asset is unclear or the spare is unavailable?
The interface may improve while the operating logic remains unresolved. Digitisation can preserve unnecessary steps, unclear decisions and informal dependencies.
2. A Process Can Be Documented and Still Be Operationally Weak
Processes often accumulate additions: a form after an incident, an approval after a quality issue, a spreadsheet to track a gap, or email to connect departments. Over time, nobody reviews the complete flow.
A process map may show a neat sequence while the actual task involves duplicate entry, calls, waiting, clarification or local checklists absent from the formal description.
HSE recommends task analysis and user involvement, with procedure format and detail suited to the user, task, environment and consequences of failure. HSE guidance on procedures.
A process should first be understood as work, not merely as fields, approvals and screens. This also means identifying which steps serve a necessary purpose and which have accumulated through habit.
A useful process review should distinguish essential controls from unnecessary administrative steps. An approval may be essential for risk or authority; another may exist because responsibility was never made clear. Understanding that difference matters before either is automated.
3. The Shadow Process
Most factories have two versions of important processes: the designed process described by the SOP or system, and the shadow process people use to keep work moving.
The shadow process may include calls, messages, spreadsheets, verbal approvals, local checklists, duplicate entry and personal judgement. A technician calls because a request lacks machine context; a planner keeps a spreadsheet because material status is not visible; an operator uses a local checklist because the formal workflow misses a handover.
These activities reveal what the formal process has not captured: missing information, unclear ownership, legitimate exceptions, slow approvals or an interface that does not fit the task.
Informal steps are not automatically the solution. They are clues to what the formal process needs to address.
Some local actions may be sensible controls or legitimate responses to changing conditions. Others may duplicate work or conceal a missing decision. The review should establish which is which rather than copying every workaround into the new system.
4. The Shadow Process Test
Before changing a digital workflow, follow one real transaction from start to finish—such as a maintenance request, inspection, approval or production change.
Map:
Trigger → Information → Decision → Responsibility → Handoff → Exception → Completion
Then add what happens outside the formal flow. Who gets called? What is entered twice? Where does someone wait? Which decision depends on personal judgement? Which step exists because another system cannot provide what is needed?
The difference between the designed and actual process is often the most useful finding. This is not about catching employees; it is about understanding what the task requires in practice.
5. Understand the Workaround Before Removing It
If people repeatedly leave the formal process, understand what the behaviour accomplishes. The system may lack context, approvals may be slow, information may sit elsewhere, exceptions may be unsupported or the interface may be difficult to use.
HSE guidance on managing human failures recommends understanding why people act as they do and considering how design can reduce conditions that make errors more likely. HSE guidance.
What problem is the workaround solving?
Removing a workaround without fixing its cause can make the task harder or create another workaround. Address the design gap, not just the visible behaviour.
6. Redesign Before You Configure
Technology projects often begin with fields, permissions, notifications and reports. A stronger sequence is:
Understand the work → Map the actual process → Identify the gap → Redesign what needs changing → Determine what should be digitised
Define the process purpose, trigger, required information, decisions, responsibilities, handoffs, exceptions and completion criteria. Remove steps that serve no necessary purpose and clarify who owns each decision.
Only then decide what should be automated or connected. Some steps may need a different sequence, clearer decision criteria or a named owner before any software is configured.
What can the software automate?
is a weaker starting point than:
What should this process accomplish, and what is the clearest reliable way to do it?
7. Factory OS: Coordinate the Process That Should Exist
Factory OS is not simply a digital layer placed over existing workflows. In the BRIGS concept, it structures operational and safety activities, including information, workflows, maintenance processes and workplace controls.
A maintenance workflow creates value when roles, decision points, asset identity, information requirements and escalation paths are understood. The digital system can then connect them, route approvals and keep completion evidence with the task.
Factory OS should coordinate a deliberately designed process, not preserve an unclear one.
For example, a request can be connected to a clearly identified asset, include the information needed for triage, show its current status and make the next responsible role visible. Exceptions can be routed for review instead of disappearing into messages or informal follow-up.
8. Factory UX: The Workflow Is Experienced by a Person
A workflow is not experienced as a process map. The technician sees a screen, the operator receives a notification and the supervisor approves a task.
A technically functional workflow can still confuse people if the next action, required information or responsibility is unclear. Factory UX connects the digital interaction with the physical work it supports. Screens, forms, instructions and notifications should make the next step understandable and request information relevant to the task.
A digital process is usable when people understand what is required, complete the action and can see what happens next.
9. Management of Change Matters
Digitalisation changes how work is performed: responsibilities, approval timing, information and sequence can all change.
For processes covered by OSHA's US Process Safety Management standard, specified changes to chemicals, technology, equipment and procedures require formal management-of-change review. This includes safety impacts, procedure updates, authorisation and informing or training affected employees before startup. OSHA 29 CFR 1910.119(l).
This standard has a defined US scope; it is not universal law. The broader lesson is that a new digital workflow is an operational change, not just a software release.
Its impact on responsibilities, controls, training, information and the actual task should be examined before implementation.
10. Examine the Whole Operating System
Before choosing technology, examine the wider conditions:
People: Who performs, approves and escalates?
Machines: What equipment conditions shape the work?
Processes: What sequence is necessary?
Information: What must be known at each stage?
Interfaces: Where do work and responsibility move?
Control: How is the process monitored and improved?
A software implementation may optimise one application. A systems approach asks whether it fits the factory around it.
11. Understand Before You Automate
The BRIGS approach provides a disciplined sequence:
SEE the actual process, including what happens outside the formal workflow.
CONNECT people, machines, information, responsibilities and systems.
DIAGNOSE gaps in process design, information, ownership, usability or technology.
DESIGN the improved process and decide where technology adds value.
IMPLEMENT the physical, procedural, visual and digital changes.
IMPROVE by checking whether the new process works and whether new problems have appeared.
The intervention may be digital, physical, visual, procedural or combined.
BRIGS Perspective: Technology Has a Place, Not a Starting Position
At BRIGS, technology is one intervention within a larger factory system. Factory UX addresses whether people can understand and use the workflow. Factory OS connects information, permissions and operational controls. Machine and process safety keep digital changes aligned with technical controls, while workplace improvement considers the physical environment.
The starting point is the work, not a software catalogue.
A Practical Next Step With BRIGS
Choose one process your factory is considering digitising. Do not begin with software requirements. Run the Shadow Process Test: map the designed and actual process, then identify workarounds, duplicate entries, unclear decisions, handoffs and manual follow-ups.
Classify each element:
Keep → Simplify → Redesign → Digitise
The aim is not to remove everything human, but to ensure the digital workflow reflects the process the factory intends to operate. A BRIGS site assessment can help examine people, machines, processes, information, interfaces and control.
The right question is not whether a factory can digitise a process. It is whether the process is understood well enough to become digital.
Have a similar challenge on your site?
Tell us what you are trying to improve and we will help you find the practical next step.


