Where Work Falls Through the Cracks: A Swimlane Checklist for Cleaning Up Handoffs
In Lean Six Sigma, the swimlane (or cross-functional) diagram is the map you reach for when a process crosses people, departments, or systems. Each lane is an actor — a role, a team, an application — and the work flows left to right while the responsibility moves up and down between lanes. Every time an arrow crosses a lane boundary, that is a handoff: a place where work waits, context is lost, and accountability gets fuzzy. Delays and defects love those boundaries.
This was hard to ignore in early 2021. With teams split between home and office and suppliers running behind, the smooth handoffs people used to manage with a hallway conversation broke down. The work itself had not changed; the seams between people had simply become visible. A swimlane is the cheapest way to see them on purpose instead of by accident.
Drawing the map this week
Bound the process. Write down the trigger that starts it and the outcome that ends it. "From request received to permit issued" is a process you can map; "permitting" is a topic you cannot.
List the actors, one lane each. Keep it to the roles and systems that actually touch the work. If a lane never does anything, drop it; if two roles always act together, consider merging them.
Map what really happens, not the policy. Walk the process with the people who do it. Draw the current state, including the workarounds and the rework loops — that is where the savings hide.
Mark every lane crossing. Highlight each handoff. For each one, note how the work is passed (email, system, paper) and what waits at that point.
Add time, not just steps. Capture rough touch time versus wait time at each stage. In most office processes the wait between steps dwarfs the actual work.
Reading the map for waste
Once it is on the wall, look for the patterns that map to classic Lean waste. The diagram turns vague frustration into specific, fixable problems:
Handoffs that bounce back and forth across the same two lanes — a sign of unclear ownership or missing information at the source.
Queues where work sits in an inbox between lanes, the single biggest source of wait time in most processes.
Rework loops where an item returns to an earlier lane for correction, signalling a quality problem upstream.
Duplicate checks where two lanes inspect the same thing because neither trusts the other.
A lane that touches the work many times — possible overprocessing, or a bottleneck role doing too much.
The goal is not a prettier diagram; it is fewer crossings and shorter waits. Each handoff you can remove, or make cleaner with a clear trigger and a complete-information rule ("this lane never passes work without these three fields"), takes friction out of the process permanently. A good target is to reduce the number of lane crossings and to convert silent email queues into a visible, pulled flow.
A few cautions
Map the current state honestly before you design the future one — teams that jump straight to the ideal diagram fix problems that do not exist and miss the ones that do. Validate the map with the people in each lane; a process owner's mental model is often a Sprint behind reality. And resist adding detail for its own sake: a swimlane that needs a magnifying glass has stopped being a tool and become a wall decoration.
When handoffs between agencies, contractors, and internal teams are where your projects lose time, XNM's strategic advisory can help you map the seams and redesign them for good.