Eliminate activities

Eliminate unnecessary activities

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: Operation class: Task Rules frameworkAspect: Operation view perspective: functional

Description

Every activity in a process should contribute to an outcome that the customer or the organisation actually needs. Activities that fail this test still consume time and capacity, create waiting time and handovers, and add complexity without adding value. This pattern asks you to identify such activities and remove them.

A common way of regarding a activity as unnecessary is when it adds no value from a client’s point of view. Typically, control activity in a workflow do not do this; they are incorporated in the model to fix problems created or not elevated in earlier steps. Control activities can often be found back as iterations and reconciliation tasks.

Beyond controls, typical candidates are duplicate data entry, approvals added after a long-past incident, reports nobody reads, and steps that only exist because of a technical or organisational limitation that has since disappeared. Before you remove a control, ask why it was introduced. If it catches defects created upstream, the better redesign is to prevent those defects at the source, for example through Control relocation or Establish standardized interfaces, and only then remove the check. Removing a control without addressing its cause simply pushes errors downstream, which is why this pattern is the counterpart to Activity addition.

The heuristic is widespread in literature, for example see Peppard and Rowland (1995), Berg and Pottjewijd (1997), and Van der Aalst and Van Hee (2002). Buzacott (1996) illustrates the quantitative effects of eliminating iterations with a simple model.

Key Takeaways

  1. Ask whose value it adds — An activity that adds no value from the customer’s point of view is a candidate for elimination.
  2. Treat causes, not checks — Controls and reconciliations often compensate for upstream problems; fix the source before removing the check.
  3. Loops are a signal — Iterations and repeated activities frequently point to control work that could be avoided.
  4. Mind the quality risk — Removing a control that still catches errors trades speed and cost for quality.

Performance considerations

The aims of this heuristic are to increase the speed of processing and to reduce the cost of handling a case. An important drawback may be that the quality of the service deteriorates.

Removing an activity shortens the path of every case that passed through it: its processing time and the waiting time in front of it disappear, and the capacity of the resources performing it is freed. Cost drops accordingly. Quality is the critical dimension of the Devil’s Quadrangle here. If the eliminated activity still caught errors, those errors now reach the customer. Flexibility is generally unaffected or slightly improved, since a leaner process has fewer dependencies. Assessing the actual value of each control is therefore the decisive step.

Example

For example, a purchasing department could require a second approval for all purchase orders above a modest threshold, introduced years ago after a single incident. If the event log shows that the second approver hardly ever rejects or changes an order, while the step adds several days of waiting time, the department could remove it or raise the threshold so that it applies only to high-value or unusual orders. The decision should be documented together with the residual risk that is accepted.

Spotting the opportunity in event data

Framed along the FLAC rule types — fitness, location, attribute, constraint.

Fitness: processes with high rework rates or many control and reconciliation activities relative to value-adding ones. Location: approval, check, verification and reconciliation activities; loops and activities repeated within a case. Attributes: effect rate of a control (share of executions leading to rejection or change), waiting time before the activity, rework triggered after it, cost per execution. Constraints: legal, regulatory or audit requirements such as separation of duties; controls that rarely fire but prevent high-impact failures; activities whose value lies outside the observed process, such as data needed by other processes.

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

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