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
Buffer external information and subscribe to updates
Establish a case-based mindset
Remove batch-processing and periodic activities from your business process
Design business processes for typical cases and isolate exceptional cases from the normal flow
Let customers interact with your organization whenever they want to.
First-contact problem resolution
Establish a one-contact resolution for customer issues
Preference-based task assignment
Let people do what they love to do
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Performance-based task assignment
Allocate tasks based on past performance: execution time and success
Allocate task based on past feedback or quality metrics