Determine whether activities are related to the same type of case and, if necessary, distinguish new business processes
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: Operation class: Integral Workflow Rules frameworkAspect: Operation view perspective: functional
Over time, processes accumulate activities and sub-processes that serve very different kinds of cases. A single customer-request process might handle complaints, address changes and quotation requests with one generic flow, or an invoicing sub-process might be embedded, with slight variations, in several primary processes. This pattern asks you to check whether all activities really relate to the same type of case and, where they do not, to distinguish separate processes or extract common sub-processes that can be managed in their own right.
One should be cautious of parts of business processes that are not specific for the business process they are part of. Ignoring this phenomenon may result in a less effective management of such a sub-process and a lower efficiency. Applying this heuristic may result in faster processing times and less cost.
Especially Berg and Pottjewijd (1997) convincingly warn for parts of business processes that are not specific for the business process they are part of. Ignoring this phenomenon may result in a less effective management of this “subflow” and a lower efficiency.
Note that this heuristic is in some sense similar to the triage concept. The main interpretation of the triage concept can be seen as a translation of the case type pattern on a activity level.
Where triage creates alternative variants of one activity, distinguishing case types creates separate process flows, each with its own design, performance targets and possibly its own owner.
This heuristics has been mentioned in one form or another by Hammer and Champy (1993), Rupp and Russell (1994), Peppard and Rowland (1995), and Berg and Pottjewijd (1997).
■ This pattern ■ Baseline
Applying this best practice may yield faster processing times and less cost. Also, distinguishing common subflows of many different flows may yield effciency gains. Yet, it may also result in more coordination problems between the business process (quality) and less possibilities for rearranging the business process as a whole (flexibility).
This matches the profile in the Devil’s Quadrangle. Time and cost improve because each process can be streamlined for its case type, with fewer decision points and less generic handling, and shared sub-processes can be run efficiently by a dedicated unit. Quality is rated as slightly worsening, since the interfaces between the separated processes need coordination and a customer may now meet several processes instead of one. Flexibility worsens because the separated processes are harder to rearrange as a whole and resources become tied to one process.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes with very many variants and low conformance to any single model. Location: groups of variants that share few activities; sub-processes that recur almost identically in several processes. Attributes: case attributes (request type, product, channel) that explain which activities occur; clustering or decision-tree splits that separate cases into groups with distinct paths and throughput times, as in a case group analysis. Constraints: groups too small to justify a separate process; strong dependencies between case types (e.g. the same customer order); coordination effort that would outweigh the gains.
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
Let workers perform as many steps as possible for single cases
Establish a case-based mindset
Remove batch-processing and periodic activities from your business process