The gaps between departments are the problem
Within a department, work moves reasonably well. Between departments it queues: sales to operations, operations to finance, finance back to sales. Each handover adds days and each is nobody's responsibility.
Measuring a cross-departmental process almost always reveals that most of the elapsed time is spent in the gaps rather than in the work.
Appoint an owner first
You cannot automate a process nobody owns. Somebody has to be able to decide what the rules are when two departments disagree, and that decision cannot be made by the automation.
This is an organisational step rather than a technical one, and skipping it is the commonest reason cross-departmental automation projects stall.
Map the handovers, not the tasks
- List every point where responsibility passes from one team to another
- Measure how long each handover takes, in elapsed time
- Identify what triggers the receiving team to act
- Ask what information is missing at each handover, causing a request back
Missing information at handover is the usual cause of delay, and it is usually fixable by capturing it earlier rather than by chasing later.
Automate the trigger and the context
Most handover delay is that the receiving team does not know there is something to do, or does not have what they need to do it.
Automating the notification with full context — the record, the history, what is needed — removes both. That alone frequently halves elapsed time without changing anything else.
Give everyone the same view
A shared status view showing where each item is, and how long it has been there, changes behaviour without any enforcement. Queues become visible, and visible queues get attention.
It also ends the conversation about which department is causing the delay, because the answer is in front of everyone.
Expect the political part to be harder
Cross-departmental automation surfaces disagreements about definitions, priorities and standards that have been avoided for years. That is uncomfortable and it is the actual work.
Budget time for it, and expect the technical build to be the straightforward half of the project.