V4.02.1Assignment versus self-selectiondesignresearch

Assignment and claiming create ownership differently and suit different conditions

Aliases: task assignment · self-selection · work allocation

What it is

Assignment versus self-selection distinguishes two ways a task acquires an owner. A coordinator assigns work using priorities, capabilities, and load; a member claims work using local knowledge of their own situation. Assignment favors coverage and deadlines, while claiming can exploit distributed expertise and autonomy. They are not merely two paths to the same assignee field.

Why it happens

Assignment centralizes allocation with someone who may understand dependencies but not each person's hidden load, interests, or skills. Self-selection incorporates that local information, yet attractive work may be claimed first while risky or invisible work remains untouched. Uncertainty, urgency, scarce expertise, and power relations determine which allocation cost dominates.

Studying it

Compare assigned, self-selected, and hybrid task pools on time to coverage, match quality, lateness, reassignment, and concentration of burden. Interview coordinators and members separately about their decision criteria. Task difficulty and attractiveness must be controlled or coded; claim speed alone cannot establish a better allocation mechanism.

Where it stops holding

Emergency response, statutory responsibility, and tightly coupled critical paths often require assignment. Exploratory, modular work with distributed expertise is more compatible with claiming. Self-selection may still reflect reputation competition or peer pressure rather than free choice. Hybrids create both delay and overreach if switching rules are unclear.

Applying it

  • Declare a default allocation mode and transition rule for each task class, such as assigning work left unclaimed near a deadline.
  • Show capability and actual load before assignment; show dependencies, risks, and completion criteria before claiming.
  • Represent nomination, assignment, claim, and acceptance as distinct states.
  • Validate the mode using coverage time, rework, and burden distribution by task type.

Related

  • Same group: V4.02.2 Information needed for claiming · V4.02.3 Fallback assignment · V4.02.4 Acceptance as commitment · V4.02.5 Responsibility chains in reassignment
  • Adjacent: V1.07 Effects of Group Size · V4.05 Handoffs and Context Transfer
  • Search terms: task allocation · self-selection · work assignment

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/V4.02.1