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

Appoint case managers

Assign a responsible individual for handling each case type

Work in customer teams

Form cross-department teams for end-to-end case handling.

Parallelize activities

Consider whether activities may be executed in parallel

Consolidate Work

Collect similar work items and work in batches

Green Compensation

Start implementing actions that can offset or counterbalance the environmental effects generated by business processes that cannot be changed.

Tailored privacy settings

Offer customers the possibility to choose among privacy settings

First-contact problem resolution

Establish a one-contact resolution for customer issues

Preference-based task assignment

Let people do what they love to do

Performance-based task assignment

Allocate tasks based on past performance: execution time and success

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?