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
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).
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).
■ 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.
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.
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
If capacity is insufficient, consider increasing the available number of resources
Reduce the number of contacts with customers and third parties