Isolate exceptions

Design business processes for typical cases and isolate exceptional cases from the normal flow

Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) All sources

category: Business Process Behavior class: Integral Workflow Rules frameworkAspect: Behavioral view perspective: functional

Description

The pattern focuses on the recognition that exceptions in a workflow can disrupt normal operations and cause inefficiencies. To address this, the pattern suggests separating exceptions from the regular flow of work to improve overall process performance.

What counts as an exception is best defined by data rather than intuition: cases that leave the standard path, need unusual expertise or consume disproportionate effort. A front-end Apply triage step then separates them from the regular flow as early as possible.

By isolating exceptions, organizations can assign dedicated workers or teams who specialize in handling these unique cases. This enables the development of specialized expertise and knowledge, leading to more effective and efficient resolution of exceptions. Additionally, by filtering out exceptions, organizations can streamline their processes, potentially implementing Straight-Through-Processing where applicable, reducing manual intervention, and increasing operational efficiency.

However, it’s important to consider the trade-off between the benefits and the associated costs and complexities. Isolating exceptions can add complexity to the workflow, potentially decreasing its flexibility. It may require additional resources to train and develop specialized knowledge among workers. Without investing in specialized expertise, the desired improvements in handling exceptions may not be realized.

Original heuristic (source excerpt)

Exceptions may seriously disturb normal operations. An exception will require workers to get acquainted with a case although they may not be able to handle it. Setup times are then wasted. Isolating exceptions, for example by a triage, will make the handling of normal cases more efficient. Isolating exceptions may possibly increase the overall performance as specific expertise can be build up by workers working on the exceptions. By filtering out all exceptions, it may be possible to offer Straight-Through-Processing (MacSweeney, 2001). The price paid in isolating exceptions is that the workflow will become more complex, possibly decreasing its flexibility. Also, if no special knowledge is developed to handle the exceptions (which is costly) no major improvements are likely to occur.

The heuristic is mentioned by Poyssick and Hannaford (1996).

Key Takeaways

  1. Specialized Exception Handling — By assigning specific workers or teams to handle exceptions, expertise can be developed, leading to more effective resolution.
  2. Straight-Through-Processing — Filtering out exceptions may enable the implementation of streamlined, automated processes, reducing manual intervention.
  3. Consider Complexity and Cost — Isolating exceptions adds complexity to the workflow and requires investment in developing specialized knowledge.
  4. Define exceptions with data — Identify exceptions by the deviations, effort and expertise they cause, and recognise them as early as possible.

Performance considerations

By separating exceptions, normal case handling becomes more efficient as workers can focus on regular cases without being disrupted by unfamiliar or complex situations. This reduces setup times wasted on dealing with exceptions that workers may not be adequately equipped to handle.

The specialization of workers or teams in handling exceptions leads to the development of expertise, resulting in more effective and timely resolution of these unique cases. This can lead to improved customer satisfaction, streamlined processes, and reduced operational costs. Additionally, by filtering out exceptions and implementing Straight-Through-Processing, organizations can automate routine tasks, reducing manual effort and increasing process efficiency.

However, it’s crucial to carefully manage the added complexity that comes with isolating exceptions. The workflow may become more intricate, requiring proper coordination and communication between teams. Furthermore, organizations need to consider the investment required in developing specialized knowledge among workers handling exceptions, as it may involve training, resources, and ongoing support.

In Devil’s Quadrangle terms: time and cost gain in the regular flow, quality gains for expert-handled exceptions, and flexibility tends to drop as the process grows more complex.

Example

An illustrative example of this pattern can be found in a healthcare setting. In a hospital, the triage process serves as a practical application of isolating exceptions. Patients arriving at the emergency department are initially assessed by triage nurses who quickly identify urgent cases that require immediate attention, such as critical injuries or life-threatening conditions. These cases are isolated and given priority, ensuring they receive specialized care promptly. Meanwhile, the regular flow of patients is handled separately, improving the overall efficiency of patient care delivery in the hospital.

Spotting the opportunity in event data

Framed along the FLAC rule types — fitness, location, attribute, constraint.

Fitness: processes in which a small share of cases accounts for a disproportionate share of throughput time, rework or variants. Location: variants outside the happy path, escalation activities, loops and manual interventions in otherwise automated paths. Attributes: case attributes that predict deviation (product, value, country, customer type), processing time and number of resources for deviating versus standard cases, and the share of cases that could run straight through if the exceptions were removed. Constraints: exceptions that cannot be recognised early; exception volumes too small or too diverse for a dedicated team.

Sources & references

  1. Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) Summary on this site Publisher page DOI 10.1016/j.omega.2004.04.012

Share this pattern

Enjoy these

Foundational free Patterns

Apply Integral technology

Elevate physical constraints by applying new technology

Apply triage

Consider the division of a general activity into two or more alternative activities

Appoint case managers

Assign a responsible individual for handling each case type

Assign cases

Let workers perform as many steps as possible for single cases

Automate activities

Consider automating activities

Automate for environmental impact

Implement automation in a sustainable way

Buffer information

Buffer external information and subscribe to updates

Combine activities

Combine small activities into composite activities

Consolidate Work

Collect similar work items and work in batches

Constraint-based task assignment

Allocate tasks considering business process execution constraints

← Back

Connected to

Apply triage

Consider the division of a general activity into two or more alternative activities

Fail Early

Order knock-outs by least effort and highest termination probability first.

What's Happening?

Dec 2023
New Pattern

Consolidate Work

Nov 2023
Oct 2023
Oct 2023
New Cheat sheet

Redesign Essentials

Sep 2023
Sep 2023
Aug 2023
New Pattern

Task delegation

Aug 2023
Aug 2023
New Pattern

Green Feature

Aug 2023