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
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.
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).
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.
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.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Consider the division of a general activity into two or more alternative activities
Order knock-outs by least effort and highest termination probability first.