FIELD NOTE |
July 22, 2025
Who Owns the Middle?
Organizations divide work into functions. Customers, information, money, risk, and consequences keep moving between them.
I've been told to stay in my lane. More than once.
I've also been trusted precisely because I didn't.
That contradiction has stayed with me.
Which has made me wonder what a lane actually is.
Organizations need boundaries. People need clear ownership. Not everybody inserting themselves into everything is systems thinking. Sometimes it's just interference.
But the work itself doesn't respect the lines on an org chart.
A customer moves across them.
Money moves across them.
Information moves across them.
Risk moves across them.
Consequences definitely move across them.
A salesperson makes a promise. That promise may become a product commitment, a contract term, a billing requirement, an implementation plan, a support expectation, a revenue forecast, and eventually an accounting entry.
From the customer's perspective, it is still one promise.
Internally, we may have divided responsibility for keeping it across seven teams.
That division can be useful. Specialization is useful.
It can also make the relationship between the pieces strangely difficult to see.
This may be one reason "stay in your lane" has always been hard for me. What another person experiences as crossing a boundary can feel, from inside my cognition, like following the information.
I see the dependency.
If something happening in Product changes what Sales can promise, which changes what Finance forecasts, which changes what Operations has to support, those aren't four unrelated subjects to me.
They're one system.
That doesn't mean my interpretation is always right.
Pattern recognition has its own seductions. Once you see connections everywhere, it becomes very easy to assume every connection matters, or that your view of the whole is more complete than it actually is.
Ownership without blindness
Other people possess information I don't.
Boundaries can protect focus and preserve expertise. They can keep someone like me from turning every interesting dependency into everyone else's emergency.
So I don't think the lesson is that lanes are bad. Some boundaries help people do their jobs. Others prevent anyone from seeing the thing they're collectively building. The difficulty is knowing which kind you're looking at.
A boundary can clarify ownership without pretending the things on either side of it are unrelated.
A lot of organizational dysfunction gets described as a communication problem. Sometimes it is. But sometimes everyone is communicating perfectly well inside structures that make the larger relationship invisible.
A failed handoff doesn't only delay the work. It can change the relationship between the people involved.
The next time those teams have to work together, they may require more documentation, more checking, more escalation, or more assurances before they're willing to proceed.
Some of that caution may be justified. But it also means the original failure continues to consume capacity long after the immediate problem has been resolved.
Trust changes how much coordination a system requires. And repairing trust can be as consequential to future execution as repairing the process that failed.
The problem is in the middle.
Who is responsible for the space between them?
Who sees the customer promise all the way through?
Who notices when optimizing one function moves the cost somewhere else?
Who owns something that only exists in the relationship between two things someone else owns?
I don't think crossing boundaries is inherently virtuous.
Boundaries are useful. They create focus, clarify ownership, and protect expertise.
They don't make the things on either side of them unrelated.
So why do we design organizations with lanes and then act surprised when the most consequential problems occur in the space between them?