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
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.
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.
■ 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.
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.
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.
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
Allocate task based on collaborative experience: handover time, interactions, diversity
Form cross-department teams for end-to-end case handling.