How do you map a process that crosses several departments?

One useful option is a swimlane map: rows or columns for participants, with the actual flow of work between them. Establish who performs each step and what is handed over rather than arrange department names alone.

What is a swimlane map?

It is a flowchart with parallel lanes for departments, teams or roles. An action sits with its actual performer; connections show sequence, branches and handoffs. Lanes can run horizontally or vertically. Netcall covers the possibilities and limits of swimlanes.

Lucid proposes a sequence that can serve as a starting point:

List participants and process boundaries.
Place steps in the lanes of their actual performers.
Check actions, order and exceptions with the participants.
Agree which version records current work and how future changes are approved.
Track changes and keep the description current.

A validated current-state map does not mean the present sequence is automatically approved as a future standard. Mapping itself does not include changing systems. Separate describing the work from deciding what to change.

Which problems can it help examine?

Lanes draw attention to dependencies worth checking:

Task or information handoffs: is there waiting, missing data or repeated entry?
Feedback: who expects a response, from whom and under which condition?
Quality and responsibility: who checks the result and who handles a problem spanning several teams?

These are possible questions, not three inevitable defects in every process. Arrow length or the number of lanes crossed does not measure waiting. Connect particular handoffs to examples, records and time before identifying them as a cause of delay.

What do published examples look like?

Miro shows a software-development example with frontend, backend, infrastructure and quality-assurance teams. Planning, design review, development, testing, deployment and monitoring connect through their responsibilities. This is a provider’s diagram example, not our measured client case.

Venngage shows an employment-contract preparation diagram crossing several departments. It illustrates responsibility and handoffs; it is not legal guidance on drafting a contract. Neither example alone establishes where your request waits longest.

For your own map, take a particular request and trace what passes between participants: a reference number, file, email or decision. Separate active work from waiting and show returns caused by incomplete data. Where paths differ, record the conditions selecting them.

When should you define the lanes?

Identify participants when setting the scope. Venngage recommends noting cross-department processes early. That helps invite the right people; it does not guarantee no new participant or exception will emerge during checking.

Choose detail that keeps the diagram readable without losing responsibilities. A participant with a rare but important step must not disappear or have their action assigned to another department for a tidier drawing. A separate view or clearly identified subprocess can retain a traceable connection.

Questions

Does it differ from a plain flowchart?

Lanes add visible grouping by performer to the flow. A plain flowchart can also label roles or owners. Choose the format that shows the needed connections clearly rather than treat lanes as the only correct method.

Does every department need its own lane?

Not necessarily in every overview. But the actual performer and handoff must remain clear, even for rare involvement. When simplifying, use a label or linked detailed diagram rather than change ownership for layout reasons.

How does it differ from a RACI matrix?

Lanes show flow and performers. According to Netcall, RACI distinguishes who does the work, who is ultimately accountable, who is consulted and who is informed. The matrix can complement the map. If a combined view is crowded, link separate descriptions.

Sources

Check what happens at departmental handoffs.

The Expert Review maps the agreed processes and connections between them. It records which number, file or email passes from whom to whom and how, alongside steps inside departments. The scope is agreed and signed; the map does not promise a review of every connection across the entire business.

Ask about the Expert Review

or write to contact@ergostrat.com