Minimize numerical involvement

Too many cooks spoil the broth

Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) All sources

category: Organization class: Resource Rules frameworkAspect: Org-.structure perspective: organizational/resource

Description

The more departments, groups and individuals are involved in a case, the more effort goes into coordination: handing over work, explaining the case again, aligning on responsibilities and waiting for the next party to pick it up. The pattern therefore recommends designing processes so that as few organisational units and people as possible are involved in a single case. “Too many cooks spoil the broth” captures the idea: every additional party adds an interface, and every interface is a potential source of delay, miscommunication and diluted accountability.

In practice, you can reduce involvement by giving end-to-end responsibility to fewer units, by giving the workers who already handle a case the authority to complete it (see Empower resources), or by bringing the skills a case needs together in one team (see Work in customer teams). The pattern is closely related to Reduce touchpoints, which applies the same logic to contacts with customers and third parties, and to Split responsibilities, which avoids shared responsibility for individual tasks.

The heuristic is described by Hammer and Champy (1993), Rupp and Russell (1994), and Berg and Pottjewijd (1997).

Original heuristic (source excerpt)

Applying this heuristic should lead to less coordination problems. Less time spent of coordination makes more time available for the processing of cases. Reducing the number of departments may lead to less shared responsibilities, with similar pros and cons as the split responsibilities heuristic. In addition, smaller numbers of specialized units may prohibit the build of expertise (a quality issue) and routine (a cost issue).

Key Takeaways

  1. Count the parties — Track how many departments and people a single case passes through.
  2. Fewer interfaces, clearer accountability — Each removed party removes a handover and a potential source of delay or misunderstanding.
  3. Don’t dissolve needed expertise — Merging specialised units can destroy routine and know-how that the process relies on.
  4. Combine with team-based designs — Empowerment and customer teams are practical ways to reduce involvement without losing skills.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

Employing this approach should mitigate coordination issues. Time saved on coordination can be allocated to case processing. Decreasing department count could reduce shared responsibilities, akin to the split responsibilities approach. Yet, it might hinder expertise development (quality concern) and routine efficiency (cost concern).

Because these effects pull in different directions, the pattern is rated neutral on all four dimensions of the Devil’s Quadrangle. Time usually gains from fewer handovers and less coordination. Cost can fall through lower coordination overhead, but can also rise when specialised units and their routines are dissolved. Quality benefits from clearer accountability but may suffer where specialist expertise is lost. Flexibility depends on whether the remaining units are broad enough to absorb fluctuations.

Example

For example, an employee onboarding process could involve HR, IT, facilities, payroll, security and the hiring manager, each receiving a separate request and often waiting for the previous party. A company could reduce numerical involvement by making HR the single coordinating unit that triggers all provisioning through one request, and by agreeing standard equipment and access packages per role so that individual approvals by the hiring manager are no longer needed. The number of parties a new hire’s case passes through, and the handovers between them, drop considerably.

Spotting the opportunity in event data

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

Fitness: processes with many distinct departments or resources per case relative to the number of activities. Location: segments with frequent handovers between organisational units, ping-pong between two departments, and activities preceded by long waiting times after a handover. Attributes: distinct departments and resources per case, handover count, waiting time per handover, handover-of-work networks between units. Constraints: legally required separation of duties; specialist units whose expertise and routine cannot be replicated elsewhere; units involved only for small, quick contributions that cause little delay.

Sources & references

  1. Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) Summary on this site Publisher page DOI 10.1016/j.omega.2004.04.012

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

Reduce touchpoints

Reduce the number of contacts with customers and third parties

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