Creative agency glossaryProject Management and Workflow

Cross-Department Collaboration

Cross-department collaboration is the practice of getting teams with different jobs, from strategy to production to finance, working on the same problem at the same time instead of handing it down a line.

What is cross-department collaboration?

Cross-department collaboration is what happens when the walls between functions come down for the length of a project. In a conventional organization, work travels: marketing writes a brief, hands it to creative, who hand it to production, who hand it to finance for approval, and each hand-off loses something. Collaboration across departments puts those people in one conversation from the start, so the strategist hears the producer's constraint before the idea is set, and finance understands why the budget looks the way it does before the invoice arrives.

In agencies the phrase usually describes the relationship between strategy, creative, production and account teams. On the client side it describes brand, product, sales, legal and the channel owners who all have a stake in a campaign. In either case the goal is the same: fewer surprises, faster decisions and work that reflects what the whole organization knows rather than what one department thought.

Why it matters

Why cross-department collaboration matters

Most bad work is not made by bad people. It is made by good people who found out too late. The idea that cannot be shot for the budget, the film that legal cannot clear, the campaign the sales team has no stock for: each is a conversation that should have happened in week one and instead happened in week nine, when changing course costs ten times more. Collaboration moves those conversations forward.

It also makes the work better, not just safer. A producer in the ideation meeting sees a way to make the ambitious idea affordable. A designer in the strategy session notices that the positioning has a visual problem. The departments that are usually downstream carry knowledge the upstream ones lack, and the only way to use it is to invite them in before the decisions are made.

In practice

How cross-department collaboration works in practice

  1. 01

    It needs structure, because goodwill alone does not survive a deadline. The project kicks off with everyone who will touch it in the room, including the people who would normally be briefed later, and the brief is agreed there rather than circulated afterward. One shared source of truth holds the schedule, the budget and the decisions, so no department is working from a stale version. Regular check-ins are short and cross-functional, and they end with decisions assigned to names.

  2. 02

    The harder part is culture. Departments have their own language, their own measures of success and sometimes their own grievances, and collaboration asks them to care about each other's outcomes. That usually takes a leader who holds the whole project, not one function, and who makes it clear that the goal is the finished work rather than any department's comfort. Shared credit helps. So does shared blame.

At RIOT

Cross-department collaboration at RIOT

We are a creative agency and production studio built so that there are no departments to cross. Strategy, creative, design and production sit in one room, and the person who wrote the brief is the person in the edit. The idea that wins the pitch reaches the screen without a hand-off, which is the whole reason we work the way we do. Krova, our production software, grew out of the same conviction: a production runs best when the client, the creative team and the crew are looking at the same plan at the same time.

See the work →

Watch out

What people get wrong about cross-department collaboration

Mistaking meetings for collaboration. Inviting every department to every call produces exhausted people and no decisions; collaboration is about the right people being in the right conversation early, not about everyone being in every conversation always. The other mistake is treating it as a culture program rather than a way of running projects. Posters about teamwork change nothing. A kick-off with the producer in the room changes everything.

A third mistake is leaving it to the departments to sort out. Collaboration across functions needs someone whose job is the whole project, because every department will, reasonably, protect its own.

Questions

People also ask

What is the difference between cross-department and cross-functional collaboration?

In practice they describe the same thing: people from different disciplines working on one project together. Cross-functional is the more common term in product and software teams; cross-department is more common in agencies and corporate marketing. Both mean the hand-offs have been replaced with a shared table.

Why does cross-department collaboration fail?

Usually because nobody owns the whole project, so each department optimizes for itself. It also fails when the collaboration is bolted on as extra meetings rather than built into how the work is planned. Start with one shared brief, one schedule and one decision-maker, and most of the friction disappears.

Who is responsible for cross-department collaboration on a campaign?

A project lead who holds the entire outcome, whether that is a producer, a project manager or, in a small agency, the creative director. Their job is to bring the right people in early and keep every department working from the same version of the plan.

Next to it in the glossary

  1. Cross FunctionCross function is collaboration across the departments of a business, where people from different disciplines work on the same problem at the same time rather than in sequence.
  2. Cross Functional Team ManagementCross-functional team management is the work of leading a team drawn from several disciplines, such as strategy, creative, production and development, toward one outcome on one schedule.
  3. Cross FunctionalityCross functionality is the ability of a team or a person to work across different disciplines, so that collaboration between roles happens naturally rather than by handoff.
  4. Daily Productivity TrackerA daily productivity tracker is a tool or habit for recording what was done each day, so a person or a team can see where their time and output actually went.
  5. Daily Time TrackerA daily time tracker is a tool for logging the hours of a working day against tasks and projects as they happen, instead of reconstructing them at the end of the week.
  6. DeadlineA deadline is the date by which a deliverable has to exist, and in client work it is the one date everything else in the project is planned backward from.

Every Project Management and Workflow term →

In the work

Where it shows up

All our creations →

From the journal

Read around it

The journal →

Talking the talk is one thing

We make the work.

RIOT is a creative agency and production studio in New York. Strategy, brand, film, photography, design and the campaigns that carry them, made by one team. A few lines is enough to start: we read every brief the same day.

    Footage