Expertise-based task assignment

Match tasks to experts' specialized skills for efficiency

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 Capability class: Allocation Rules frameworkAspect: Organizational Population perspective: organizational/resource

Description

Expertise-based task assignment belongs to the capability category of the HRAPs (Goel et al., 2023), together with Role-based task assignment and Preference-based task assignment. It assigns a task according to the unique skills of the people involved, where expertise means the specialised skills a resource has. The allocation rule matches the skill a task needs with the skill profiles of the available people, and routes the task to someone with the right specialisation. Skill information usually comes from qualifications, certifications, skill matrices or HR systems. A task’s need for a specialist often only becomes clear after the case has been classified, so the pattern frequently follows Apply triage or Distinguish case types.

In the study, experts rated it among the most useful and the most pervasive patterns. It is the HRAP form of the specialist side of Specialist-generalist. It is in direct tension with Cost-based task assignment: experts deliver faster and better results on complex work, but their time is expensive and scarce. Using it only for cases that really need specialist knowledge is the usual compromise.

For employees, being deployed for one’s own skills is motivating and gives a sense of competence. Experts who are the only ones able to do a task, however, become bottlenecks and risk overload, and their knowledge stays in silos. Spreading expertise through pairing or training lowers both the burden and the dependency.

Key Takeaways

  1. Match skill to need — Route each task to someone whose specialised skills match what the task requires.
  2. Classify first — Triage or case-type distinction shows which cases really need an expert.
  3. Experts are scarce and costly — Use experts for complex cases and accept higher cost there, or balance with cost-based rules.
  4. Avoid single points of failure — Spread expertise so that specialists are not overloaded and knowledge is not stuck with one person.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

Time ▲: specialists solve complex cases faster and with fewer escalations, reassignments and search effort. Quality ▲: matching skill to task increases first-time-right and the quality of the result. Cost ▼: specialists are paid more and are scarce, and building and maintaining skill profiles takes effort. Flexibility is neutral. Precise matching makes the process responsive to complex cases, but it ties certain tasks to a small group of people.

Example

For example, an IT service desk could tag incoming tickets by technical area and route database incidents directly to the database specialists, instead of having first-level agents try and then forward them. Generalists would keep the standard password and access requests. The desk would track how many tickets still need reassignment, to check whether the skill tags and the routing are accurate.

Spotting the opportunity in event data

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

Fitness: knowledge-intensive processes in which cases vary in complexity. Location: activities followed by “forward”, “escalate” or “reassign” steps, and loops in which cases return after a failed first attempt. Attributes: number of reassignments per case, match between case category and the executing resource’s skill (skill data joined to the log), first-time-right rate and processing time per resource group. Constraints: check the available capacity of the specialists, factor in their higher cost, and keep enough people with each skill so that you don’t create single points of failure.

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

Preference-based task assignment

Let people do what they love to do

Role-based task assignment

Assign tasks based on resources' roles in the organisation

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