How to collaborate on cross-department projects: reducing information barriers and buck-passing
Cross-department collaboration becomes concrete at the point where one team’s output becomes another team’s input. Before adding meetings, agree on what will change hands, who will prepare it, who will check it and what makes it ready to use. A department saying that its own task is finished does not establish that the next department can begin. Start with one important handoff in the project. You do not need to redesign every department’s working methods. You need enough shared detail for the two sides to recognise the same delivery and to identify any responsibility that neither side has accepted.
Walk backwards from the receiving team
Consider a fictional project to produce a printed visitor guide. An editorial team prepares the text, designers create the pages and an operations colleague arranges printing. “Send the content on Tuesday” is not yet a workable handoff. Designers may need approved text, image captions and a clear page order, while the writers may think a draft with unresolved comments is sufficient.
Ask the receiving person what they must have before starting the next task. Then ask the sending person whether that input can actually be produced within the agreed time. Write the answer beside the existing task, including the file location and the version to use. This is a two-way agreement, not a list of demands imposed by the receiving team.
Make the dependency visible
For the guide, record that page layout depends on approved text and that printing depends on a checked print file. Identify the contact at each end. Note the effect if an input changes: a late paragraph may require another layout check, not merely another email. Avoid mapping every relationship in the organisation; concentrate on dependencies that affect this delivery.
Atlassian’s Dependency Mapping guidance asks teams to identify upstream and downstream impacts, owners, risks and review arrangements. This supports making the relationship visible, rather than assuming a deadline in one department automatically includes another department’s work. Discuss the map with the affected teams, because a coordinator may not know all the inputs they rely on.
Resolve the work between named roles
The guide may reveal a task that has no clear owner: who checks whether every caption matches the final image? Writing “editorial and design” beside it can hide the same gap. Ask which person will perform the check, who supplies missing information and who confirms that the result is usable. Names should reflect an accepted responsibility and the person’s actual capacity.
Atlassian’s Roles and Responsibilities exercise recommends identifying a primary owner when duties overlap. Unclaimed duties require a person to find the owner and a follow-up date. That does not mean inventing a permanent new role whenever a small task appears. First see whether an existing responsibility can reasonably include it; if no one can take it, make the unresolved capacity or authority question explicit.
Agree what receiving the work means
Choose a small number of observable receiving conditions. For the design handoff, these might be a complete text file, confirmed captions and unresolved questions marked separately. The receiver can then say what is present and what is missing. Opening a shared folder or replying “thanks” should not silently become acceptance of incomplete work.
The Scrum Guide uses a Definition of Done to establish a shared understanding of completed work within Scrum. An ordinary cross-department project need not adopt that entire framework. The useful principle here is to make completion understandable to everyone relying on it. Do not call a draft final simply because the sender has run out of time, and do not add new acceptance demands after delivery without acknowledging the change.
Handle a changed input without passing the whole problem on
If the approved text changes after layout, record which pages are affected and what needs checking again. The writer remains responsible for the corrected text; the designer confirms the layout work required; the coordinator checks whether the printing arrangement is affected. These are separate commitments. One person notifying everyone does not automatically take over all three jobs.
After the first handoff, compare the agreement with what happened. Did the receiver have usable material? Was any work left between roles? Did a correction create an unrecognised dependency? Adjust that specific agreement before expanding the process. Keep each department’s existing tools where they work, and make the connections between them clear enough that the project can move forward.