How do you like this site? We would love to hear from you! Take a short survey or

Resequence activities

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)

category: Business Process Behavior
class: Routing Rules
frameworkAspect: Behavioral view
redesignOperation: Sequentialize; Add Task; Remove Task
perspective: control-flow

Description

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.


  flowchart LR
	start(start)-->3-->1-->2-->fin(end)

Performance considerations

Share this pattern

Enjoy these

Foundational free Patterns

Combine activities

Combine small activities into composite activities

Eliminate activities

Eliminate unnecessary activities

Assign cases

Let workers perform as many steps as possible for single cases

Parallelize activities

Consider whether activities may be executed in parallel

Tailored privacy settings

Offer customers the possibility to choose among privacy settings

First-contact problem resolution

Establish a one-contact resolution for customer issues

Role-based task assignment

Assign tasks based on resources' roles in the organisation

Workload-based task assignment

Allocate tasks based on individuals' incomplete workload

Constraint-based task assignment

Allocate tasks considering business process execution constraints

Back

Share this

Connected to

Fail Early

Order knock-outs by least effort and highest termination probability first.

Parallelize activities

Consider whether activities may be executed in parallel

What's Happening?