Department-based assignment

Distribute tasks by interdepartmental interactions to enable or restrict involvement

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 Collaboration class: Allocation Rules, Resource Rules frameworkAspect: Organizational Structure perspective: organizational/resource

Description

Department-based assignment is one of the two collaboration patterns among the HRAPs (Goel et al., 2023). It allocates tasks according to the department a person belongs to and how that department interacts with others. The pattern can be used in two directions. You can deliberately involve several departments when a task requires shared responsibility or several perspectives. Or you can restrict a task to fewer departments to remove handovers that add waiting time but no value. In the second direction it implements Minimize numerical involvement at the level of organisational units.

The resource attribute is department membership, combined with the observed interaction between departments: how often work passes between them, how long those handovers take, and whether they lead to rework. Teamwork-based assignment looks at the same collaboration question for individual people. Work in customer teams is the structural solution, because it makes a cross-department team permanent instead of assembling it for each task.

Implementation

For department-based assignments, prior information related to different departments, people in those departments, their skills, and the time involved in handovers may be required. Based on this information and the objective of the process, the appropriate resources would be allocated to the tasks of the process.

For employees, cross-department assignments broaden their view of the end-to-end process and help mutual understanding. This matches the “BPI with employees” objective of employee-aware BPI. They also add coordination effort and can blur who is accountable, so shared tasks need a clear lead and a clear decision rule.

Key Takeaways

  1. Two directions — Involve several departments where shared responsibility adds value, and limit involvement where handovers only add waiting time.
  2. Unit-level collaboration — The pattern works at the level of organisational units; Teamwork-based assignment applies the same idea to individual people.
  3. Handover data matters — Department skills, people and handover times are the basis for deciding whom to involve.
  4. Clarify the lead — Shared tasks need one accountable lead to avoid diffuse responsibility.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

This pattern will result in a high-quality outcome in less time and cost.

Quality ▲ is the strongest effect. When the right departments are involved from the start, requirements are considered jointly and late objections and rework become less likely. Time ▲ and cost ▲ come mainly from limiting involvement: each department that is no longer needed removes a handover, its queue and the coordination effort that goes with it. Flexibility is neutral. A broader set of departments gives more options, but fixed department rules can make allocation harder to change.

Example

The review loan application task has been assigned to a resource from the finance and human resources departments, as they have shared responsibility.

The pattern also works in the other direction. A company could restrict a standard address-change request to the customer-service department, removing a handover to the back office that added waiting time but no value.

Spotting the opportunity in event data

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

Fitness: cross-functional processes in which cases pass through several organisational units. Location: activities at department boundaries, and tasks where a department joins late and triggers rework. Attributes: departments per case (resource-to-department mapping from org data), handover frequency and waiting time between department pairs, ping-pong between departments, and the rework rate after late involvement. Constraints: don’t remove a department that performs a mandatory control or holds legal responsibility. Involving more departments only pays off if their contribution changes the outcome.

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

Teamwork-based assignment

Allocate task based on collaborative experience: handover time, interactions, diversity

Work in customer teams

Form cross-department teams for end-to-end case handling.

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