Why No One Owns the Problem Between Departments
Who's responsible? Is anyone?
A quality issue surfaced on night shift. Someone caught it, flagged it the way they’d been trained to, and moved on to the next task, confident the information would reach whoever needed it next.
It didn’t. Day shift’s packing team never saw the alert. It had gone out in an email that wasn’t part of anyone’s start-of-shift routine, and by the time someone noticed, the same defect had already made it into product waiting to ship.
Nobody had done anything wrong. Night shift did their job: they caught the issue and reported it, exactly as trained. Day shift did their job: they ran their standard startup checks, exactly as trained. The alert existed. It just existed in a place neither shift ever checked.
We eventually fixed the communication gap, but the fix isn’t what I want to talk about today. The fix is easy once you’ve found the gap. The interesting part is how the failure even happened. We had two teams, two sets of procedures, both followed correctly, and a problem that fell cleanly into the space between them because nobody’s role covered that space.
That space is where most cross-departmental failures live. Not in negligence, but in the way processes and teams are designed.
Nobody Owns the Seams
Every operation I’ve ever worked in has a clear answer to “who owns this” for almost everything that happens inside a department. Pick owns picking. Pack owns packing. Quality owns quality checks. Maintenance owns the equipment. Ask who’s responsible for a problem inside any one of those lanes, and you’ll get an answer fast.
But if you ask who owns the space between pick and pack, or anywhere that a problem in one department’s output becomes the next department’s problem, you’re likely to get either conflicting answers or just silence.
This is the pattern behind a huge share of the operational failures that get chalked up to “poor communication.” I’ve written before about how much operational information dies at shift changes. The pattern between departments is similar but it gets less attention because a shift change happens on a schedule you can build a process around, while a cross-departmental handoff can happen at any moment, in either direction, without warning.
Org charts are very good at defining ownership inside a box. They are rarely designed to define ownership of the line between two boxes. That line doesn’t show up on anyone’s scorecard, doesn’t appear in anyone’s job description, and doesn’t get raised in anyone’s performance review. It only becomes visible when something falls through it. And even when that happens, the conversation is about damage, not design.
Why This Keeps Happening
If ownership gaps between departments were rare, they wouldn’t be worth an entire article. But they’re not rare, and they’re not random. Three things reliably produce them.
The structural reason: ownership gets drawn around departments, never around the connections between them. Your dashboard measures your department, because it was built to. Pick’s metrics show pick. Pack’s metrics show pack. Nobody’s metrics show the health of the handoff between them, which means a problem in that handoff can get worse for weeks without appearing on either scorecard. The same gap shows up in job descriptions. Nobody was hired to own the transition between pick and pack They were hired to run pick or to run pack.
The behavioral reason: raising it feels like overstepping. This is the most common reason that I see. Most managers I’ve trained aren’t ignoring cross-departmental problems out of laziness, they’re just hesitant to say something about another department’s territory because it can come across as criticism, or as reaching outside their lane. As I’ve written about in my collaborative problem-solving framework, one of the clearest signs a problem needs more than one department’s attention is that it crosses a boundary. But recognizing that a problem needs collaboration doesn’t tell you who’s supposed to be the one who starts it. Politeness causes these sort of issues more often than negligence does.
The reactive reason: the fixes we reach for patch the failure, not the pattern. A ripple check. A communication autopsy. A signature requirement at handoff. These are good, necessary responses. I’d recommend all three, and I’ve used all three myself. But each one only closes the specific gap that just caused a specific failure. Your operation has other gaps that nobody’s watching yet. Fixing one issues won’t fix the underlying pattern that’s causing them.
Ownership Is a Stance, Not a Title
You may have heard the observation that nobody takes a rental car to a car wash. This same idea applies here. It’s not that people are careless. It’s just a fact of human nature that ownership changes behavior. When somebody is responsible for something, they take care of it. But when it’s not yours, you treat it differently. Managers can end up treating the space between departments the same way, cared for by no one, because nobody was ever assigned to care for it.
The leaders who close these gaps aren’t the people with more authority, but a certain mindset. They treat a gap as their responsibility from the moment they first notice it, rather than assuming someone else will take care of it or waiting to confirm it’s officially their responsibility first. This is a mindset that can be learned. All it takes is the next time you spot a gap like this, you decide that saying something is worth the minor discomfort of stepping outside your lane.
From Theory to Action
Run a “ghost audit” on one recent miss. Pick a cross-departmental problem from the last few months. Trace backward: who would have had to notice it early, and did their role actually ask them to say something if they did?
Ask the ownership question out loud. In your next cross-functional meeting, ask directly: “If this specific handoff breaks, whose job is it to catch it?”
Build one lightweight check for your highest-risk seam. Not a full system, just one handoff, one checkpoint, or one person accountable for confirming it happened. Start narrow and prove it works before expanding.
Bring one identified gap to a peer manager this week. Decide jointly who owns it going forward. A ten-minute conversation now is cheaper than the reactive fix later.
Document the pattern, not just the incident. One ownership gap is an incident. Three similar gaps across different areas is a pattern worth raising with your own leadership.