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) All sources

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

Description

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).

Key Takeaways

  1. Order follows dependencies — Sequence activities by what they actually need, not by habit or screen layout.
  2. Postpone what may become unnecessary — Delaying an activity until its result is needed avoids effort for cases that drop out.
  3. Bring discriminating steps forward — Early checks and routing decisions save effort downstream.
  4. Respect data dependencies — An activity moved ahead of its inputs creates rework instead of savings.

Performance considerations

Resequencing has no fixed performance profile; its effect depends on the direction of the move. Postponing an activity until it is needed lowers cost, since it is no longer performed for cases that drop out earlier, and throughput time is usually unaffected unless the activity moves onto the critical path. Bringing checks forward or placing similar activities together can reduce both time and cost through earlier rejection and fewer set-ups. Quality may benefit from detecting problems earlier, but suffers if an activity is moved ahead of the information it needs. Flexibility is largely neutral across the Devil’s Quadrangle, although a fixed, deliberate order leaves less room to vary the sequence at run time.

Example

For example, a telecom provider could schedule the technician visit for a new broadband connection right after the order is entered, before the address and line-availability check. Every order that later fails the check wastes an appointment that has to be cancelled. Moving the availability check ahead of scheduling, and booking technicians only for orders that passed, removes the cancellation work and frees technician slots for orders that will go ahead.

Spotting the opportunity in event data

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.

Sources & references

  1. Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) Summary on this site Publisher page DOI 10.1016/j.omega.2004.04.012

Share this pattern

Enjoy these

Foundational free Patterns

Apply Integral technology

Elevate physical constraints by applying new technology

Apply triage

Consider the division of a general activity into two or more alternative activities

Appoint case managers

Assign a responsible individual for handling each case type

Assign cases

Let workers perform as many steps as possible for single cases

Automate activities

Consider automating activities

Automate for environmental impact

Implement automation in a sustainable way

Buffer information

Buffer external information and subscribe to updates

Combine activities

Combine small activities into composite activities

Consolidate Work

Collect similar work items and work in batches

Constraint-based task assignment

Allocate tasks considering business process execution constraints

← Back

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?

Dec 2023
New Pattern

Consolidate Work

Nov 2023
Oct 2023
Oct 2023
New Cheat sheet

Redesign Essentials

Sep 2023
Sep 2023
Aug 2023
New Pattern

Task delegation

Aug 2023
Aug 2023
New Pattern

Green Feature

Aug 2023