Performance-based task assignment

Allocate tasks based on past performance: execution time and success

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

Description

Performance-based task assignment is a productivity pattern in the HRAP catalogue (Goel et al., 2023). It assigns tasks according to how a person has performed in the past. Performance is measured by two quantities: execution time and successful outcomes. Both can be derived from event data. Execution time is the time between the start and completion of a person’s work items. Success is a defined outcome, such as a case closed without rework, an approval granted, or a claim settled without being reopened. The allocation rule ranks eligible people by these measures and gives the task, often a critical or time-sensitive one, to the strongest performer.

Performance is different from Experience-based task assignment, which counts how often someone has done the work, and from Quality-based task assignment, which relies on feedback or quality metrics rather than time and success. The experts in the study named the main risk: allocating by performance alone overloads the best people and creates an imbalance in the team. It should therefore be paired with Workload-based task assignment or another balancing rule.

The employee angle matters a lot here. Allocation based on individual performance data can feel like surveillance, and it can lock slower learners out of the work they need in order to improve. Transparent criteria, metrics adjusted for case complexity, and early involvement of employees and their representatives make the pattern acceptable. In Germany, for example, technical systems that are able to monitor employee performance are subject to works council co-determination.

Key Takeaways

  1. Time and success — Past execution time and successful outcomes, both derivable from event data, define performance.
  2. Balance against overload — Combine with workload limits so that top performers are not swamped.
  3. Normalise for case mix — Compare people on similar cases, otherwise the metric rewards those who get easy work.
  4. Transparency and consent — Performance-based allocation needs transparent criteria and the involvement of employees and their representatives.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

Quality ▲: routing critical tasks to people with a track record of successful outcomes increases the share of cases that are done right the first time. Time is neutral. Strong performers finish individual tasks faster, but if too much work goes to them, queues build and the gain disappears. Cost is neutral because the pattern redistributes existing work and does not change staffing. Flexibility is also neutral, since the pattern doesn’t change the structure of the process, although depending heavily on a few top performers makes the process more fragile.

Example

For example, a mortgage lender could route applications with tight closing deadlines to processors whose files have historically closed on time with the fewest condition loops. At the same time, it would cap each processor’s open files and compare performance only within the same loan type, so that the rule does not simply favour those who usually get simpler cases.

Spotting the opportunity in event data

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

Fitness: processes with recorded start and complete timestamps per resource and a clear success criterion. Location: activities with large performance differences between resources, and time-critical or high-value case segments. Attributes: processing time per resource and activity, success rate (no rework, no reopening, approval), variance between resources, and case-complexity attributes for normalisation. Constraints: sample sizes per person must be sufficient, results need to be adjusted for case mix, the workload of top performers must stay bounded, and legal or co-determination rules on performance monitoring apply.

Sources & references

  1. 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). Summary on this site Publisher page DOI 10.1007/978-3-031-41620-0_22

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

Cost-based task assignment

Delegate tasks according to resource cost

Experience-based task assignment

Delegate task according to experience: execution frequency, case involvement, interactions

Quality-based task assignment

Allocate task based on past feedback or quality metrics

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