Quality-based task assignment

Allocate task based on past feedback or quality metrics

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

Quality-based task assignment is a productivity pattern in the HRAP catalogue (Goel et al., 2023). It assigns a task based on prior feedback from internal or external customers, or on quality metrics. The resource attribute is the quality of a person’s past work, for example customer satisfaction scores, complaint or reopening rates, error rates found in audits, or reviews from internal clients. The allocation rule gives high-stakes or demanding work to the people whose past work was rated best.

Performance-based task assignment uses execution time and success, measured from the process itself. Quality-based assignment uses the judgement of whoever receives the work. Quality data often sits outside the event log, in survey tools, CRM or QA systems, and you need to link it to cases and resources. Like the other productivity patterns, it is best combined with workload or development rules, so that the best-rated people are not overloaded with the hardest cases.

Implementation

For quality-based task assignments, details related to the customer evaluation feedback for resources need to be known. At the time of allocation, people with the best quality feedback will be chosen for the task.

For employees, using feedback for allocation recognises good work and makes it visible. Constantly handling the most difficult complaints is demanding, though, and feedback can be unfair when customers rate the outcome, such as a rejected claim, rather than the person. Offering coaching alongside the rule, and judging quality across a reasonable number of cases, keeps it fair.

Key Takeaways

  1. Feedback as the attribute — Prior internal or external customer feedback and quality metrics determine who gets the task.
  2. Link quality data to the log — Survey, complaint and audit data usually need to be joined to cases and resources.
  3. Differs from performance — Performance looks at speed and success; quality looks at how the recipient rated the work.
  4. Fair and sustainable — Account for rating bias and spread the hardest cases so that top-rated staff don’t burn out.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

This pattern will result in high-quality outcomes. The effect is strongest on quality (▲): the cases where errors or poor service would hurt most go to the people with the best track record, which improves both external quality (customer satisfaction) and internal quality. Time, cost and flexibility are neutral. The pattern redistributes existing work rather than adding or removing steps. Top-rated people are not necessarily faster or cheaper, and they can become a bottleneck if the rule is applied without workload limits.

Example

An organisation evaluates the performance of its customer service representatives based on customer feedback and assigns high-performing representatives to handle complex customer complaints.

Internally, a software team could assign the review of changes to security-critical modules to developers whose past changes have had the lowest post-release defect rates, as measured over the previous releases.

Spotting the opportunity in event data

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

Fitness: processes with measurable quality feedback, such as customer service, claims, complaints or professional services. Location: high-stakes activities: complaint handling, key accounts, critical reviews. Attributes: satisfaction scores, complaint and reopening rates, audit error rates per resource, linked to cases and resources via case IDs, and the variance in quality between resources. Constraints: you need enough feedback per person, adjustment for case mix and rating bias (outcome versus service), and workload limits for top-rated people. Don’t use it where feedback can’t fairly be attributed to individuals.

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

Performance-based task assignment

Allocate tasks based on past performance: execution time and success

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