Assign tasks based on resources' roles in the organisation
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 Structure perspective: organizational/resource
Role-based task assignment belongs to the capability category of the HRAPs (Goel et al., 2023). It assigns tasks to roles in the organisation, such as “claims handler”, “purchasing approver” or “nurse”, rather than to named individuals. Any person who holds the role and is available can take the work item. A role bundles the capabilities, responsibilities and authorisations an organisation expects for a group of tasks, so the resource attribute is role membership. The allocation rule maps each task to one or more roles and offers the work to the pool of people who hold them.
In the study, experts named role-based assignment among the most pervasive patterns. Most workflow, ERP and case-management systems allocate work this way by default. It is the coarse first layer on which the other HRAPs build. Expertise-based task assignment refines it with individual skills. Constraint-based task assignment narrows the role pool for specific cases. Workload-based task assignment or Preference-based task assignment choose within the pool. Broad roles also make Flexible assignment possible.
For employees, well-designed roles make responsibilities clear and reduce constant renegotiation of who does what. Roles that are too narrow or outdated, however, hide individual strengths and limit development. Reviewing role definitions together with the people who fill them keeps them aligned with the work that is actually done.
■ This pattern ■ Baseline
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: check how much work is still assigned to named individuals instead of roles or groups. Location: activities where cases wait in personal work lists, especially during absences, and activities performed by only one or two people. Attributes: distinct resources per activity, waiting time compared with the availability of the assigned resource, the user-to-role mapping from org or system data, and how far the users who actually perform an activity match its intended role. Constraints: tasks that need continuity with a customer or case, or highly specialised expertise, may still require named assignment. Role definitions must be current.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Expertise-based task assignment
Match tasks to experts' specialized skills for efficiency