Kennisbank

Coordination between departments: what happens beneath the chat window

Coordination between departments is what happens when work doesn't stay within one team, but moves from one department to another. A request that starts at sales and ends at finance. A complaint that begins at support and is resolved at operations. A change that affects HR, but also IT and legal affairs. AI can play a role here: signalling that a step is complete, informing the next department, tracking status across teams, or flagging deviations from the normal pattern before they escalate. That is not a single task, but a connection between tasks that sit with different people and systems.

What actually happens

Beneath the chat window, coordination between departments is usually a combination of three things. First: information that arises at department A must be readable and usable for department B, without anyone having to retype it manually or explain it again. Second: there must be a moment at which it is clear that a step has been completed and the next one can begin, even if no one is actively watching. Third: if something gets stuck between departments, that must become visible to someone who can intervene, rather than disappearing into a queue that no one checks.

This touches on subjects that already demand attention on their own. Reading and summarising documents is often the first step: before department B can take something over, it must be clear exactly what department A has recorded. Recording and following up on conversations plays a role when the handover does not consist of a document, but of a phone call, a meeting or a verbal agreement that needs to be registered somewhere before the next department can proceed with it. And as soon as there is not just one handover, but a series of steps that follow one another across multiple departments, the question arises of what chains in which steps follow one another require from the organisation in order to keep that chain stable.

What this requires before it can work

Coordination between departments runs through three fundamental conditions, and these follow a fixed order because one does not work without the other.

Organisation comes first. Who is responsible for a step that falls between two departments? If a request gets stuck between sales and finance, who resolves that, and within what timeframe is that checked? Without an answer to that question, no system has anything to hold on to, and coordination between departments will exist on paper but in practice keep coming back to people who have to sort it out manually.

IT infrastructure follows next. Departments often work in different systems, with different access rights and different update schedules. Coordination requires those systems to be able to communicate with each other, or at least a shared place where the status of an ongoing process is visible to everyone involved. Without that connection, coordination remains dependent on people manually retyping information from one system into another.

Data management is the third condition. If department A calls a customer "active" and department B calls the same status "in progress", confusion arises as soon as a process moves from one to the other. Coordination between departments requires shared definitions: what does a status mean, who is allowed to change it, and how is it tracked when that happens. Without those agreements, information loses its meaning along the way, and someone on the other side has to work out again exactly what was meant.

These three — organisation, infrastructure, data management — form the foundation on which coordination can rest. Only after that does it become relevant whether AI can signal that something has been completed, or whether a system can automatically inform the next department. That depends on decision support — who assesses whether a handover has gone correctly — and on monitoring and signalling, which determines whether deviations between departments are noticed in time.

Why this often gets stuck

Pilots around coordination between departments often do not get stuck on the technology, but on the question of who is responsible for what as soon as something falls between two departments. A system that automatically signals that a step is complete has little value if no one is clearly designated to respond to that signal. That is an organisational question, not a technical one, and that question must be answered before coordination between departments can rely on AI.

How you measure this

The maturity assessment from hybridresourcing maps out where your organisation stands on the dimensions that make coordination between departments possible: organisation, IT infrastructure and data management, alongside the other dimensions that follow from these. In a plot round, multiple people from the organisation score separately, and the spread between those scores shows where the picture differs — often exactly at the point where coordination between departments gets stuck. The tool is under construction. Anyone who wants to work with this can sign up for the waiting list.

Where this page describes what coordination between departments requires from the organisation in order to be sustained, the work scan from FTE TO AI takes a step further and calculates, per task, what share of the work can actually be taken over by AI. That is a different question from readiness: it is the question of what, once the foundation is in place, actually shifts in the work itself.