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
Determine whether activities are related to the same type of case and, if necessary, distinguish new business processes
Establish a case-based mindset
Remove batch-processing and periodic activities from your business process
Order knock-outs by least effort and highest termination probability first.
Delegate and optimize your operations
Consider whether activities may be executed in parallel
Avoid shared responsibilities for tasks by people from different functional units
Offer a green alternative with the same outcome, utilizing different steps, resources, or partners, while retaining the previous existing process
Offer customers the possibility to choose among privacy settings
Workload-based task assignment
Allocate tasks based on individuals' incomplete workload