How do you like this site? We would love to hear from you! Take a short survey or

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.

Split task responsibilities
Split task responsibilities

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

Establish a case-based mindset

Remove batch-processing and periodic activities from your business process

Deploy extra resources

If capacity is insufficient, consider increasing the available number of resources

Apply Integral technology

Elevate physical constraints by applying new technology

Establish standardized interfaces

Consider a standardized interface with customers and partners

Minimize numerical involvement

Too many cooks spoil the broth

Tailored privacy settings

Offer customers the possibility to choose among privacy settings

Experience-based task assignment

Delegate task according to experience: execution frequency, case involvement, interactions

Cost-based task assignment

Delegate tasks according to resource cost

What's Happening?