Move activities to more appropriate places
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: Routing Rules frameworkAspect: Behavioral view redesignOperation: Sequentialize; Add Task; Remove Task perspective: control-flow
Activities are often ordered the way they have always been performed, or the way a form or system screen dictates, rather than according to their actual dependencies. Resequencing asks you to move each activity to the position in the process where it is most effective.
The current sequencing of tasks in existing workflows may not fully reflect the logical constraints that need to be observed between tasks. As a result, it can occasionally be advantageous to delay a task, particularly if it is not necessary for tasks that immediately follow. By doing this, there’s a chance that the task may turn out to be unnecessary, leading to cost savings. Moreover, positioning a task closer to another task of a similar nature can potentially reduce setup times. Examples of these resequencing strategies include the knock-out heuristic, control relocation, and the parallelism heuristic.
Moving an activity later, closer to where its result is needed, avoids wasted effort on cases that are cancelled or rejected in between (Delay Execution develops this idea further). Moving an activity earlier helps when its result informs routing or reveals problems sooner, as in Fail Early and Control relocation. Placing an activity next to a similar one reduces set-up time, much like Combine activities. The diagram below sketches the idea: activity 3 is moved ahead of activities 1 and 2.
flowchart LR start(start)-->3-->1-->2-->fin(end)
The resequencing heuristic is mentioned as such by Klein (1995).
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes with notable cancellation or rejection rates, or with activities whose results are often discarded. Location: activities performed before a decision point that frequently ends the case; activities executed long before their output is used. Attributes: share of executions whose result is never used because the case ends, time between an activity and the first activity consuming its output, variance in the observed order (an order that already varies without harm is not a hard dependency). Constraints: genuine data or legal dependencies; activities with long lead times that must start early so they do not delay the case.
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
Order knock-outs by least effort and highest termination probability first.
Consider whether activities may be executed in parallel