Delegate task according to experience: execution frequency, case involvement, interactions
Goel, K., Fehrer, T., Röglinger, M., & Wynn, M. T. (2023). Not Here, But There: Human Resource Allocation Patterns. In Lecture Notes in Computer Science (pp. 377–394). All sources
category: Human Resource Productivity class: Resource Rules frameworkAspect: Organizational Population perspective: organizational/resource
Experience-based task assignment is a productivity pattern in the HRAP catalogue (Goel et al., 2023). It assigns a task to the person with the most relevant experience. Experience is measured by three observable quantities: how often the person has executed the work item, how many cases they have been involved in, and how often they have interacted with others. All three can be computed directly from an event log with resource information. That makes experience one of the easiest attributes to operationalise.
Experience is different from Expertise-based task assignment, which relies on specialised skills a person holds (often certified), and from Performance-based task assignment and Quality-based task assignment, which judge outcomes. Someone can be experienced without being the fastest or best-rated person. The pattern also complements Empower resources: in the study, the experts recommended using the two together so that authority goes to people who have the experience to use it.
Experience metrics for people must be available. At the time of execution, the experience required for the task will be matched with existing data and to select an appropriate person.
A strict experience rule has two side effects. Work concentrates on the most experienced people, who become overloaded, and newcomers never build experience, because they are never assigned the task. The experts in the study raised employee well-being and up-skilling as allocation criteria in their own right. A balanced design caps the workload of experienced staff and deliberately routes a share of tasks to less experienced colleagues, with mentoring.
■ This pattern ■ Baseline
This pattern will result in high-quality outcomes in less time.
Whether these gains appear depends on the task and on how the rule is applied, which is why the ratings are neutral across time, cost, quality and flexibility. On familiar, complex tasks, experienced people tend to work faster and make fewer mistakes. If the rule is applied strictly, however, queues build in front of them, senior staff may cost more, and the pool of people who can do the task stays small, which limits flexibility. Combining it with workload limits keeps the benefits.
An organisation assigns a senior manager role in data and analytics to a person with at least 10 project involvements, five project leadership experiences, and team management experience of at least 20 people.
The same logic works at task level. A claims department could route complex liability claims to handlers who have closed a minimum number of similar claims in the past year, and pair newer handlers with them on some cases so that they build experience.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes where resource information is recorded per activity and tasks vary in difficulty. Location: activities with large differences in processing time or rework rate between resources, which suggests a learning curve. Attributes: execution count per resource and activity, distinct cases per resource, degree in the handover network, and the correlation between experience and duration or rework. Constraints: check the workload of the most experienced people before you route more work to them, leave room for development assignments, and don’t treat experience as a proxy for quality without checking it.
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
Delegate tasks according to resource cost
Performance-based task assignment
Allocate tasks based on past performance: execution time and success
Allocate task based on past feedback or quality metrics
Form cross-department teams for end-to-end case handling.