The Exception Became Routine.
Search Info
Primary topic: Recurring exceptions, workarounds and the divergence between formal processes and actual workflows
Central question: What happens when organisations continue to treat recurring deviations as exceptions even though everyday work increasingly depends on them?
Key concepts: workarounds, process exceptions, workflow design, standard operating procedures, process drift, organisational routines, shadow processes
Core insight: A recurring exception eventually stops being evidence that people are deviating from the process and starts becoming evidence that the formal process no longer describes the work.
The Case That Was Always Slightly Different
Many processes of the 2020s contained an apparently reassuring distinction. There was the normal procedure, and then there were exceptions.
The normal procedure could be documented, standardised, digitised and measured. Exceptions were the cases that did not quite fit. They required an additional telephone call, a manual correction, an alternative approval, a spreadsheet beside the official system, an email to a particular colleague or a slightly different sequence known to experienced employees.
None of this was necessarily problematic. Real work contains variation, and processes that allow no deviation at all can become less robust rather than more reliable. Employees need discretion when unusual circumstances arise.
The structural problem began elsewhere: when the unusual circumstance stopped being unusual. The workaround remained labelled an exception even as people encountered it every day. At that point, the organisation faced a condition that its formal process description could no longer represent accurately.
Why Exceptions Were Necessary
Standardisation depends on simplification. A process defines a repeatable sequence for situations sufficiently similar to be handled in the same way. That reduces coordination effort, supports consistency and makes responsibilities easier to establish.
But no formal workflow can encode every possible condition. Customers differ. Cases arrive incomplete. Software behaves unexpectedly. Priorities change. External partners introduce variations. Decisions create combinations that designers of the original process did not anticipate.
Exceptions therefore provide useful flexibility. Structurally, an exception says: the standard remains valid, but this particular case requires temporary deviation. That definition contains an important assumption. The deviation is temporary because the underlying condition is exceptional. Once the condition begins to recur, the logic changes.
When the Workaround Acquired a Routine
Imagine a process in which missing information occasionally prevents the next step. An employee contacts another department, obtains the information and continues. The deviation is minor, and redesigning the entire workflow would make little sense.
Then the missing information appears more frequently. Employees become familiar with the problem. They learn whom to contact. A standard email template develops. Experienced colleagues warn newcomers about the issue. Someone creates a small checklist. Perhaps a shared spreadsheet begins to track affected cases. Operationally, something important has happened. The organisation has created a process for dealing with the failure of the process. Yet because this second process emerged informally, the original workflow can continue to appear unchanged. The official procedure still shows the intended sequence. The actual procedure now contains an additional route understood primarily by the people performing the work. The exception has acquired structure. It simply has not acquired formal recognition.
Exception Normalisation
This condition can be described as exception normalisation: the gradual incorporation of recurring deviations into ordinary work while those deviations continue to be classified as exceptional.
The concept is related to established discussions of workarounds, shadow processes and process drift, but it draws attention to a specific contradiction. The organisation continues to describe one process while routinely operating another.
This difference matters because formal and operational reality now produce different pictures of the same work. According to the documented workflow, a task contains five steps. According to the employee performing it, there are seven.
The additional two may not appear in process documentation, workload calculations, software design or performance expectations. Yet without them, the work may not be completed reliably. The invisible steps become part of the real cost of the process.
Why Successful Workarounds Could Hide Structural Change
A recurring workaround can be remarkably effective. Experienced employees know exactly what to do, and the deviation may add only a few minutes to each case. Problems are resolved before customers notice them. Deadlines are maintained. Performance indicators may remain acceptable.
The workaround therefore appears to demonstrate adaptability. And it does. But adaptability can also conceal structural change.
When employees compensate successfully for a recurring process mismatch, the organisation continues to receive the expected output. Because the result remains stable, there may be little pressure to reconsider the process that produced it.
This creates a familiar Struction pattern: successful compensation reduces the visibility of the condition requiring compensation. The better the workaround functions, the easier it becomes to continue calling the underlying situation an exception.
The Difference Between Variation and Drift
Not every recurring deviation means that a process is defective. Some work genuinely contains irreducible variation. Professional judgement, unusual customer situations or rare technical conditions may always require flexible treatment.
The more revealing question is whether the pattern of deviation itself has become predictable. If different exceptional situations arise unpredictably, the organisation may simply be dealing with legitimate variation. If the same deviation repeatedly requires the same correction, another phenomenon is present.
The process has begun to drift away from its formal representation. Process drift occurs when actual practice gradually diverges from the procedure originally designed or documented. Exception normalisation is one mechanism through which that divergence can remain unnoticed: each individual departure continues to be explained locally even though the departures collectively describe a new operational pattern. The individual case still looks exceptional. The series of cases no longer does.
When Shadow Processes Appeared
The divergence became particularly visible when employees created additional tools around official systems.
A spreadsheet compensated for information the central software did not display. A messaging group accelerated coordination that the formal workflow made cumbersome. Personal notes recorded cases that otherwise disappeared from view. An experienced employee maintained a list because everybody knew that the official status field could not be trusted completely.
Such arrangements are often described as shadow processes or shadow systems. They are easily interpreted as evidence that employees are resisting standardisation or failing to use existing tools correctly.
Sometimes that interpretation is justified. But the R2049 reconstruction introduced another possibility. A shadow process could also be evidence that the official structure had ceased to contain something operationally necessary. The unofficial tool survived because it performed a function. Understanding that function was therefore more informative than merely noticing that the tool should not officially exist.
The Cost That Formal Processes Could Not See
Once work divided into official and unofficial sequences, measurement became more difficult.
A formal process might appear efficient because its documented steps required little time. The actual workload could be considerably higher because recurring exceptions introduced additional communication, checking, correction and follow-up.
This produced what can be described as hidden process load: recurring work necessary for reliable completion but absent from the formal representation of the workflow.
Hidden process load is easily attributed to employees because it appears in their working time rather than in the process model. People seem slower than expected. Teams appear overloaded despite manageable case numbers. Additional staffing seems necessary even though the formal workflow contains no obvious explanation for the workload.
The missing explanation may lie in the gap between the process being measured and the process actually being performed. The organisation calculates one sequence. Employees execute another.
When Experience Became Knowledge of the Exceptions
Exception normalisation also changed the meaning of experience. Experienced employees often appeared faster because they knew the process better. In some environments, however, their advantage lay partly in knowing where the formal process could not be followed literally.
They knew which field was frequently incomplete, which approval required an informal reminder, which cases needed an additional check and which official sequence had to be altered under familiar circumstances. Their expertise therefore contained a map of recurring structural deviations. This knowledge was highly valuable but difficult to transfer because much of it did not exist in formal documentation. New employees had to acquire it through observation, correction and repeated exposure to situations officially regarded as exceptions. The organisation then became dependent on knowledge it had never formally acknowledged as part of the process.
What the Organisations of the 2020s Had Misread
From the perspective of 2049, the central error was not that organisations allowed exceptions. A system incapable of accommodating exceptions would have been structurally brittle.
The misreading occurred when the category exception was allowed to explain recurrence. Calling something exceptional describes its relationship to a standard. It does not explain why it keeps happening. Once the same deviation repeatedly requires the same workaround, recurrence itself becomes information. It indicates that the formal structure and operational reality may no longer coincide.
This changes the diagnostic question. The relevant issue is no longer simply: Why was the process not followed? It becomes: What does the repeated deviation tell us about the process that is supposed to be followed? That shift is small, but structurally consequential. It moves attention away from individual compliance and towards the adequacy of the workflow itself.
Closing Reconstruction
From 2049, many apparently well-established processes of the 2020s looked less stable than their documentation suggested. Alongside the official sequence existed a second layer of corrections, shortcuts, additional checks and informal routes through which experienced employees kept work functioning.
These deviations were often called exceptions because they did not belong to the process as designed. But repetition had already given them another status. They belonged to the process as lived.
The exception stopped being exceptional long before the organisation stopped calling it one.
Summary
Organisations need exceptions because no standard process can anticipate every situation. Yet from the perspective of 2049, a different pattern became structurally significant: the same exceptions recurred until employees incorporated them into everyday routines while the formal workflow remained unchanged. The result was a growing separation between documented process and operational reality. This article reconstructs that condition as exception normalisation — the point at which a workaround is still classified as deviation even though the organisation has begun to depend on it.
Transparency
This article was developed within the framework of the concept The Second Thinking Space with the support of generative artificial intelligence. AI is used to explore questions, broaden perspectives, generate alternative formulations, identify patterns and facilitate the critical examination of ideas and assumptions. The article has been substantively reviewed, editorially revised and approved by the author. All editorial decisions, evaluations, interpretations and conclusions are the sole responsibility of the author.
