INTAKE & ORCHESTRATION

No owner for the decision

Indefinite waiting without a contingency plan

When orchestration gets stuck in limbo Every department imposes its own requirements on a request, legal, security, finance, IT. Without structure, this is where workflows stall. Rather than treating these limitations as barriers, they should be integrated into the workflow.“ To keep orchestration workflows from getting stuck in limbo, procurement and supply chain leaders must account for the different requirements imposed by legal, security, finance, IT and other functions, while keeping the requisitioner’ s experience at the centre of their approach,” says Jonathan.“ To achieve this, procurement and supply chain leaders should begin by viewing the process from the requisitioner’ s perspective and asking what information is truly necessary. Any details irrelevant to the user should be removed or deferred.”

Ownership and deadlines solve who’ s responsible. What’ s asked of the employee is a separate issue and the tension is employees wanting something simple, while back-end systems like ERPs need something structured.