Assign a responsible individual for handling each case type
category: Organization, Human Resource Re-organisation class: Allocation Rules frameworkAspect: Organizational Structure perspective: organizational/resource
Reijers and Limam Mansar (2005) describe this heuristic as appointing one person who is responsible for handling each type of case. Goel et al. (2023) keep it among the HRAPs as case manager assignment (reorganisation category), and the experts they interviewed rated it the most useful of the fifteen patterns.
The Case Manager plays a crucial role within the business process, serving as a central point of coordination and oversight for a specific case. This role entails managing the case from initiation to resolution, ensuring that all necessary steps and actions are carried out effectively and efficiently.
The Case Manager serves as the primary contact for the case, facilitating communication and collaboration among various stakeholders involved. They gather relevant information, analyze the case requirements, assign tasks to appropriate resources, and monitor the progress and quality of work items.
While the Case Manager takes responsibility for the case, it is important to note that they may collaborate with and delegate tasks to other resources within the process, such as subject matter experts or specialized teams. This collaborative approach ensures that the case is handled comprehensively, leveraging the expertise of different individuals while maintaining centralized oversight and accountability under the guidance of the Case Manager.
The allocation rule works on two levels. Each new case gets a manager, who can be chosen with Workload-based task assignment so that caseloads stay manageable. The manager then allocates the work items. The resource attribute is accountability, not execution, which distinguishes the pattern from Assign cases. For employees, end-to-end ownership makes work more meaningful, but concentrated accountability calls for caseload limits.
Involves identifying the process to be managed, selecting a suitable resource as the case manager, providing the necessary authority and resources to carry out the responsibilities, and ensuring effective communication and collaboration among the resources involved.
■ This pattern ■ Baseline
The primary objective of this heuristic is to enhance the external quality of a business process. By appointing a case manager as a single point of contact, the process becomes more transparent from the client’s perspective, resulting in improved client satisfaction. Additionally, having someone accountable for rectifying mistakes can positively impact the internal quality of the process. It is important to note that assigning a case manager carries financial implications due to the allocation of resources for this role.
Hence Quality ▲ and Customer-Centricity ▲. Time is neutral: a manager speeds up handovers but becomes a bottleneck with too many cases. Cost is neutral, as the role’s cost is offset by less rework. Flexibility is neutral, because oversight eases re-routing but ties the case to one person.
An organisation assigns a new resource as a recruitment process manager responsible for decision-making related to process flow, resource allocation, data handling, and other relevant decisions.
As a further illustration, a property insurer could appoint a case manager for every large commercial claim. The manager is the policyholder’s only contact, decides which loss adjusters and specialists are involved, and signs off the settlement. The individual assessment tasks are still carried out by other employees.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: long-running, multi-party case types with customer contact, such as claims, onboarding, complaints or recruitment. Check whether a case-owner attribute already exists and is filled consistently. Location: case types and variants with many distinct resources and departments per case, ping-pong handovers, or repeated “status inquiry” activities. Attributes: resources and departments per case, handover count and waiting time between handovers, customer contacts per case, rework loops and complaint rate. Constraints: don’t apply it to short, standardised, high-volume cases where the role only adds overhead. The manager needs real decision authority, and caseload per manager must stay bounded.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
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
Let workers perform as many steps as possible for single cases
If capacity is insufficient, consider increasing the available number of resources
Establish a case-based mindset
Remove batch-processing and periodic activities from your business process
Form cross-department teams for end-to-end case handling.