When Two People Own It, Nobody Does - The SPRIITE Series/Article 2 of 9

A company I advised had a delivery problem that three separate leaders were working on. Operations had a plan. Sales had a plan. The general manager had asked a project lead to fix it. All three plans were reasonable, all three were underway, and the delivery numbers had not moved in nine months.

When I asked who owned on-time delivery, I got three answers in the same meeting, and each person named themselves in a slightly different way. Operations owned the execution of it. Sales owned the commitment of it. The project lead owned the improvement of it. Nobody owned the number.

We put one name beside on-time delivery. Not a new person and not a reorganization, just one name, in public, with the other two explicitly supporting. The number started moving inside a quarter, and that was the only deliberate change we made.

What structure actually means

Structure is the first of the seven conditions, and it answers four questions. Who owns what. Who decides what. Where one person's accountability ends and another's begins. And whether the teams inside the company are pointed at the same goals.

A reporting chart answers a different question, who reports to whom, and most of them stop there. That is why a company can have a current, accurate org chart and still fail the structure test badly. I have sat in front of beautiful charts in companies where no one in the room could tell me who had the authority to approve a price exception.

A note on how this fits with what I have written before. The accountability chart is the artifact, and I covered building one in Who Owns What.

Structure is the condition that artifact serves. You can have the chart and still fail the condition, which is the more common situation. Communication between teams matters as much as either, and I score that under Information rather than here, so the two do not both quietly drop it.

Structure scores low when capable people spend their energy negotiating territory instead of producing. You can hear it in the language. When a leadership team starts sentences with "well, technically that would be" or "I would have to check with," you are listening to a structure problem in real time.

The cost of shared ownership

Shared accountability is the most polite way a company has of guaranteeing that nothing gets owned. It usually arrives with good intentions. Two capable leaders both care about an outcome, neither wants to take it from the other, so the outcome gets assigned to both and everyone feels collaborative.

What follows is predictable. Each of them works the part of it that sits closest to their own department. The parts that sit between them get worked by neither. When the number misses, both can point to real effort, and both are telling the truth. The company gets two partial solutions and no result, and it pays two salaries' worth of attention for it.

The fix is one name on the outcome and everyone else explicitly in support. Collaboration survives that fine. What makes it a harder conversation than it sounds is that it means telling a capable person that something they care about now belongs to a peer. Owners avoid that conversation for months at a time, and it costs more than the awkwardness would have.

Decision rights are the part nobody writes down

Most companies have some version of who owns what. Very few have written down who decides what, and that is where structure quietly fails in growing businesses.

In a company of fifteen people, decision rights live in the owner's head and that works fine, because the owner is in every room. At fifty people the owner is no longer in every room, but the decisions still route to them, so they arrive late, in batches, stripped of context, and the whole company waits. At that point the owner is not a bottleneck because of any flaw in judgment. They are a bottleneck because nobody ever moved the authority.

The exercise that surfaces this is short. List the ten decisions your company makes most often that carry real consequence. Pricing exceptions, hiring approvals, capital spend above a threshold, whether a late order ships partial, whatever they are for your business. Beside each one, write who decides it today and who should decide it. In most companies I have run this with, the two columns disagree on at least half the list, and the owner's name appears in the first column far more often than anyone expected.

Scoring structure honestly

On a one to five scale, structure at a two looks like this. More than one person believes they own the same important outcome. Nobody can state the approval threshold for a common decision without checking. New hires learn who really decides things by making a mistake.

A four looks like this. Every outcome that appears on the scorecard has exactly one name beside it, and everyone can say the name. Decision rights for the ten common decisions are written down and current. When something falls between two departments, there is a known way to resolve it that does not require the owner.

Nobody scores a five, and I would be suspicious of a company that did. What separates the twos from the fours is not sophistication. It is whether anyone has ever sat down and done the work of naming things out loud.

I have watched capable people fail inside unclear structures and get blamed for it, in companies I ran and in companies that brought me in afterward. If your team is working hard on the same problem from three directions and the number is not moving, look at the structure around the number before you look at the people. And if an outside voice would help you have that conversation, my door is open.