Split responsibilities
Avoid shared responsibilities for tasks by people from different functional units
Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4)
Description
The idea behind this redesign pattern is that tasks for which different departments share responsibility are more likely to be a source of neglect and conflict.
Performance considerations
Reducing the overlap in responsibilities should lead to a better quality of task execution. A higher responsiveness to available work items may be developed also, so that clients are served quicker. On the other hand, reducing the effective number of resources that is available for a work item may have a negative effect on its throughput time, as more queuing may occur.
Share this pattern
Enjoy these
Foundational free Patterns
Let workers perform as many steps as possible for single cases
Determine whether activities are related to the same type of case and, if necessary, distinguish new business processes
Reduce the number of contacts with customers and third parties
Elevate physical constraints by applying new technology
Minimize numerical involvement
Too many cooks spoil the broth
Consider whether activities may be executed in parallel
Offer customers the possibility to choose among privacy settings
Assign tasks based on resources' roles in the organisation
Performance-based task assignment
Allocate tasks based on past performance: execution time and success