Task delegation

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

Description

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.

Key Takeaways

  1. Runtime reassignment — The original assignee passes the work item to another person, usually down the hierarchy.
  2. Task, not authority — Unlike empowerment, delegation moves the task while responsibility often stays with the delegator.
  3. Relief at senior bottlenecks — Delegation can quickly relieve an overloaded manager, which reduces waiting time.
  4. Hand over context — Pass on information and decision limits with the task to avoid errors and rework.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

Time ▲: work no longer waits in the queue of a busy senior person, and lower-level staff can often start it sooner. Quality ▼: each delegation adds a handover in which context can be lost, and the delegate may have less experience or authority, which raises the risk of errors and rework. Cost is neutral. Moving work to lower-paid staff can save money, but this is offset by the extra coordination and occasional corrections. Flexibility is neutral: delegation gives managers a way to react to load, but it doesn’t change the process structure.

Example

For example, a department head who receives every purchase-request approval could delegate routine requests below a set amount to a team lead during peak periods or absences, and keep strategic or unusual purchases. The workflow system would record the delegation, so that later audits show who decided and on whose behalf.

Spotting the opportunity in event data

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.

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

Deploy extra resources

If capacity is insufficient, consider increasing the available number of resources

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