Preference-based task assignment

Let people do what they love to do

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

Preference-based task assignment rounds out the capability category of the HRAPs (Goel et al., 2023). It assigns a task according to the person’s preference, defined as the set of activities a person is inclined towards. In practice, these are activities the person may have executed more often and more efficiently. You can capture preference explicitly, through stated preferences, bidding or picking work from a shared work list. You can also infer it from behaviour: when people may choose, which tasks do they pick, and where are they faster? The allocation rule gives a task to an eligible person who prefers it, and if several do, combines this with another criterion.

The pattern is closely related to Expertise-based task assignment, because people often prefer what they are good at and get good at what they like. The two are still not the same: someone can be skilled at a task they dislike. The experts in the study saw preference-based assignment as a better fit for knowledge-intensive processes than high-volume, standardised ones, where throughput and deadlines dominate.

Among the HRAPs, this one is most directly about employee well-being. Doing work you enjoy supports hedonic well-being and intrinsic motivation, and it fits the “BPI for employees” objective of the employee-aware BPI navigator. The main risk is that unpopular tasks are left in the queue, so a fair rule for distributing or rotating them is part of the design.

Key Takeaways

  1. Let people do what they like — Assign tasks that people are inclined towards; they tend to be more motivated and efficient at them.
  2. Stated or revealed — Capture preference through bidding or picking, or infer it from what people choose and where they are fast.
  3. Best for knowledge work — Experts see the strongest fit in knowledge-intensive processes rather than high-volume ones.
  4. Plan for unpopular tasks — Rotate or share less popular work so that it isn’t left in the queue.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

All three rated effects are moderately positive. Time ▲: people tend to start preferred tasks sooner and work on them more efficiently. Cost ▲: higher efficiency and motivation lower the effort per case and can reduce the cost of turnover. Quality ▲: motivated people take more care, and preferred tasks often match their strengths. Flexibility is neutral. Preferences add a constraint to allocation, but in a shared pull queue more people are willing to take on work.

Example

For example, an IT operations team could let engineers pick tickets from a shared queue within their skill area, instead of having them pushed by a dispatcher. Over time the team sees who gravitates to which kind of ticket. A weekly rotation covers the least popular ticket types, and a maximum queue age makes sure no ticket waits too long because nobody chose it.

Spotting the opportunity in event data

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

Fitness: knowledge-intensive processes with some choice in allocation, such as a shared work list or pull-based distribution. Location: activities that people pick from a common queue, and task types with long waiting times because they are rarely chosen. Attributes: how often each resource picks each activity type when choice exists, processing-time differences between preferred and assigned tasks, and the age of items left in the queue. Constraints: don’t apply it where strict deadlines or standardised high volume dominate. Make sure all tasks are covered, and collect stated preferences transparently.

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

Expertise-based task assignment

Match tasks to experts' specialized skills for efficiency

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