Remove batch-processing and periodic activities from your business process
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: Integral Workflow Rules frameworkAspect: Operation view perspective: Control flow
This pattern recognizes that practical business processes often deviate from the ideal case-based and make-to-order concepts. It acknowledges the presence of constraints like work item batching and periodic activities that rely on specific computer system availability. These constraints can hinder the efficient handling of cases and impede process performance.
By applying this pattern, organizations can strive to remove these constraints and align their business processes more closely with the case-based approach. This entails eliminating the piling up of work items in batches and finding alternatives to periodic activities that rely on specific system availability. The ultimate goal is to create a more streamlined and efficient process where cases can be handled promptly and without unnecessary delays.
The pattern is the conceptual opposite of Consolidate Work; which way to go depends on whether responsiveness or economies of scale matter more for your process.
To understand how this pattern can be enacted in an example process, let’s consider a customer support system in an e-commerce company. Currently, the support team receives customer queries in batches and processes them in bulk, leading to delays in response times and potential customer dissatisfaction. The periodic activities, such as generating automated reports or system updates, are performed at fixed times, causing further delays in case resolution.
By introducing the case-based work pattern, the company can transition to a more efficient and responsive process. They can implement an automated ticketing system that assigns individual cases to support agents as soon as they arrive. This eliminates the need for batch processing and ensures timely attention to each customer inquiry.
Additionally, the company can leverage technology to remove constraints related to periodic activities. For example, instead of relying on specific system availability for generating reports, they can implement real-time reporting dashboards that are accessible to agents at any time. This enables them to access up-to-date information and resolve cases promptly, without being dependent on specific processing windows.
Through the adoption of the pattern, the customer support process becomes more streamlined, cases are handled promptly, and customer satisfaction improves. The removal of constraints allows for more agility and responsiveness, resulting in a more efficient and effective support system.
This heuristic rule results from [@Reijers.2003].
Although workflows are essentially case-based and make-to-order, several features may be present in practical workflows that are on bad-terms with these concepts. The most notable examples are (a) the piling up of work items in batches and (b) periodic activities, depending on computer systems which are only available for processing at specific times. Getting rid of these constraints may significantly speed up the handling of cases. On the other hand, efficiencies ocf scale can be reached by batch processing. The cost of making information systems permanently available may be costly also.
■ This pattern ■ Baseline
Switching to case-based work can have significant performance implications on the overall process. By eliminating work item batching, cases can be handled more swiftly, reducing delays and improving customer satisfaction. Removing reliance on specific system availability for periodic activities ensures that tasks can be performed consistently, avoiding bottlenecks caused by limited processing windows.
However, it’s important to consider the trade-off between efficiency and cost. While streamlining the process and removing constraints can enhance case handling, it may require investments in infrastructure, technology, and system availability. Organizations need to assess the potential financial implications and weigh them against the benefits gained in terms of improved efficiency, customer experience, and overall process performance
In line with this trade-off, the pattern is rated neutral on all four dimensions of the Devil’s Quadrangle. Time typically gains most, since cases no longer wait for a batch run or a processing window. Cost can move either way: permanent availability costs money and economies of scale from batching are lost, while lower work-in-progress saves some. Quality and flexibility depend on the setup.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes in which waiting, rather than processing, makes up most of the throughput time. Location: activities whose timestamps cluster at fixed times (e.g. all at 02:00 or every Friday), and the waiting time that builds up before them. Attributes: timestamp distribution per activity (hour, weekday), executing user (batch or system user), number of cases completed with an identical timestamp, waiting time before the activity compared with its processing time. Constraints: genuine economies of scale such as bundled payment runs or consolidated transport; legal or system processing windows; the cost of permanent availability.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Determine whether activities are related to the same type of case and, if necessary, distinguish new business processes