Reassign tasks along the organisational hierarchy
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 Re-organisation class: Resource Rules frameworkAspect: Organizational Structure perspective: organizational/resource
Task delegation belongs to the reorganisation category of the HRAPs (Goel et al., 2023). Delegation happens when the person originally assigned to a task passes it on to someone else based on their position in the organisational hierarchy. Usually a manager hands a work item to a subordinate. The resource attribute is hierarchical position: who reports to whom, and who may act on whose behalf. The allocation rule is applied at runtime by the original assignee. This sets it apart from patterns that decide allocation before the work is offered. The workflow resource patterns know the same mechanism as delegation.
The pattern is the counterpart of Empower resources. Delegation moves the task down the hierarchy, and responsibility often stays with the delegator. Empowerment moves the decision authority itself. Delegation is a short-term way to relieve an overloaded person, and it complements Deploy extra resources when capacity at a senior level is the bottleneck. Every delegation adds a handover, though, and with it a risk of losing information or context.
For employees, delegation can be a deliberate development tool. It gives subordinates stretch tasks and visibility, and senior staff get relief. It turns harmful when it becomes dumping of unwanted work, when the delegate lacks the authority or information to finish the task, or when accountability becomes unclear. A short handover note and clear decision limits address most of these risks.
■ This pattern ■ Baseline
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes with explicit reassignment or “forward” events, or with resource changes between the assignment and execution of a work item. Location: activities that are assigned to senior resources but executed by people at a lower hierarchy level, and queues in front of managers. Attributes: reassignment frequency, hierarchy level from org data, waiting time at senior resources, and rework or error rates after delegation compared with no delegation. Constraints: respect authority limits and segregation of duties, avoid chains of repeated delegation, and don’t delegate decisions that legally have to be taken by the original role holder.
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
If capacity is insufficient, consider increasing the available number of resources