Consider whether activities may be executed in parallel
Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4)
The heuristic is mentioned by Rupp and Russell (1994), Berg and Pottjewijd (1997), and Van der Aalst and Van Hee (2002). Van der Aalst (2000b) provides quantitative support for this heuristic.
The obvious effect of applying this heuristic is that the throughput time may be considerably reduced. The applicability of the heuristic in workflow redesign is large. In practical experiences we have had with analyzing existing workflows, tasks were mostly ordered sequentially without the existence of hard logical restrictions prescribing such an order.
A drawback of introducing more parallelism in a workflow that incorporates possibilities of knock-outs is that the cost of workflow execution may increase. The management of workflows with concurrent behavior can become more complex also, which may introduce errors (quality) or restrict run-time adaptations (flexibility).
Foundational free Patterns
Let workers perform as many steps as possible for single cases
Assign a responsible individual for handling each case type
Reduce the number of contacts with customers and third parties
Form cross-department teams for end-to-end case handling.
Automate for environmental impact
Implement automation in a sustainable way
Let customers interact with the company wherever they want to
Preference-based task assignment
Let people do what they love to do
Workload-based task assignment
Allocate tasks based on individuals' incomplete workload
Constraint-based task assignment
Allocate tasks considering business process execution constraints