Teamwork-based assignment

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

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 frameworkAspect: Organizational Population perspective: organizational/resource

Description

Teamwork-based assignment is one of the two collaboration patterns in the HRAP catalogue (Goel et al., 2023). It assigns a task to a person based on their experience of working with others. That experience is measured by three things: the time taken for handovers between them and others, the number of interactions, and the diversity of the people they have worked with. All three can be derived from an event log. Handover-of-work and working-together networks are standard techniques of organisational process mining. The allocation rule is applied mainly to tasks that need more than one person, or that depend on smooth handovers. It selects people or pairs whose past collaboration was fast and effective.

Department-based assignment addresses the same question for organisational units, and Work in customer teams makes good collaboration permanent through a fixed team structure. The diversity measure works as a counterweight: always assigning the same well-practised pairs makes them efficient, but it creates cliques and keeps knowledge from spreading.

Implementation

For a teamwork-based assignment, a prior understanding of the interaction of a resource with other resources needs to be known. Based on that understanding, appropriate resources will be allocated

For employees, working with colleagues they trust supports psychological safety and job satisfaction. Pairing new and experienced people on purpose helps onboarding and learning. Teams should not be locked in permanently, though, and when the task is a four-eyes check, a close working relationship may undermine the independence the control relies on.

Key Takeaways

  1. Collaboration history as attribute — Handover time, number of interactions and diversity of collaboration partners determine the assignment.
  2. Measured with social network mining — Handover and working-together networks from the event log reveal who works well together.
  3. Balance familiarity and diversity — Use proven pairs for critical joint tasks, but vary teams so that knowledge spreads.
  4. Mind independence — For four-eyes controls, close collaborators may not provide an independent check.

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: people who work well together communicate better, understand each other’s input and make fewer handover errors. Time ▲ and cost ▲ come from shorter handover times and less coordination and rework. Flexibility is neutral. The rule adds a matching criterion, but a broad and diverse collaboration network actually makes more combinations of people workable.

Example

The review risk task in a loan application process requires two resources to work together. The task is hence allocated to resources A and B as they have evidenced working well together in the past. Impact: This pattern will result in a high-quality outcome in less time and cost.

The diversity attribute can also be used in the other direction. A team lead could deliberately pair a new employee with an experienced colleague who has a broad network, to speed up the newcomer’s onboarding.

Spotting the opportunity in event data

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

Fitness: processes with joint tasks or frequent handovers between individuals. Location: activities that need two or more resources, and handover points with long transfer times. Attributes: the handover-of-work network, handover time per resource pair, the number of joint cases per pair, the diversity of each person’s collaboration partners, and the rework rate per pair. Constraints: you need enough shared history for each pair. Avoid fixing teams permanently, respect segregation of duties for control tasks, and be transparent about analysing individual collaboration data.

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

Department-based assignment

Distribute tasks by interdepartmental interactions to enable or restrict involvement

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