Consider the division of a general activity into two or more alternative activities
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 Operation class: Routing Rules frameworkAspect: Operation view redesignOperation: Compose; Unfold perspective: functional
Triage means splitting a general activity that treats all cases alike into two or more alternative activities, each tailored to a subcategory of cases. A generic Assess claim step, for instance, could become Assess simple claim and Assess complex claim, each with its own procedure, resource profile and depth of scrutiny. The routing decision is taken as early as possible, using case attributes that are available at intake, so that every case follows the variant that fits it.
A special form of the triage heuristic is to divide a task into similar instead of alternative tasks for different subcategories of the case type. For example, a special cash desk may be set up for clients with an expected low processing time.
The triage heuristic is related to the task composition heuristic in the sense that it is concerned with the division and combination of tasks. Note that the heuristic differs from it in the sense that alternative tasks are considered.
It also differs from Distinguish case types, which works on the level of whole processes rather than single activities, and it is the classic mechanism behind Isolate exceptions. Triage only pays off when the case categories can be recognised reliably and cheaply: a misrouted case either receives too little attention or has to be sent back to the other variant.
The triage concept is mentioned by Klein (1995), Berg and Pottjewijd (1997), and Van der Aalst and Van Hee (2002). Zapf and Heinzl (2000) show the positive effects of triage within the setting of a call center.
■ This pattern ■ Baseline
When applying the pattern in its main form, it is possible to design tasks that are better aligned with the capabilities of resources and the characteristics of the case. Both of these improve the quality of the workflow.
Distinguishing alternative tasks also facilitates a better utilization of resources, with obvious cost and time advantages. On the other hand, too much specialization can make processes become less flexible, less efficient, and cause monotonous work with repercussions for quality. This is lifted by the alternative interpretation of the triage heuristic.
In Devil’s Quadrangle terms, quality improves most clearly, followed by time and cost, because each case receives the effort it needs: simple cases are no longer over-processed and complex cases reach experienced staff. Flexibility is rated neutral to slightly negative, as more variants mean smaller resource pools and less room to shift work when the case mix changes.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: one activity serves a heterogeneous case mix, visible as a wide spread of processing times for the same activity. Location: activities whose duration distribution is bi- or multimodal, or whose downstream path differs strongly by case attribute. Attributes: processing time per activity segmented by amount, product, customer segment or channel; share of one-pass cases without rework; resources per segment. Constraints: the routing attribute must be known when the split happens; segments must be large enough for their own resource pool; don’t split when both variants need the same scarce specialists. In aBPR, triage was an elevated-automation recommendation (AL3): the tool proposes the location and asks the user to confirm that cases can be differentiated.
Foundational free Patterns
Elevate physical constraints by applying new technology
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
Combine small activities into composite activities
Determine whether activities are related to the same type of case and, if necessary, distinguish new business processes
Start implementing actions that can offset or counterbalance the environmental effects generated by business processes that cannot be changed.
Design business processes for typical cases and isolate exceptional cases from the normal flow
Consider to deepen or broaden the skills of resources