Three people shared ownership of the decision. By the time anyone noticed nothing had happened, six weeks had passed.
This is one of the most common failures in organizational architecture, and it almost never gets named correctly. When a decision gets assigned to multiple owners, leaders usually call it collaboration. Cross-functional alignment. Shared accountability. Whatever language the organization prefers, the structure is the same: more than one person is responsible for the call.
What shared ownership actually produces
What the structure actually produces is the opposite of accountability. Each owner assumes one of the others is going to drive it. Each owner has their own priorities competing for attention. Each owner is waiting for some signal from the room that this particular decision is the one to move on right now. The signal never comes, because all three owners are waiting for it.
Six weeks later, in a different meeting, someone asks what happened. Each owner has a slightly different account of who was supposed to do what. The decision gets reassigned, usually upward, and somebody in a more senior seat has to make the call that should have been made six weeks ago by one of the original three.
Shared ownership is structural ambiguity disguised as collaboration. It feels inclusive. It looks like cross-functional alignment. It produces nothing.
The rule, and the discomfort
The architectural rule is brutal in its simplicity: every decision has exactly one owner. Not two. Not three. One. Consulted parties are named separately. Approval requirements are named separately. But the call - the single person who is responsible for making the decision land - is one human being.
The leaders who actually move at speed do something that looks rude to organizations that have lived inside shared-ownership culture. They assign decisions to specific individuals by name. They tolerate the temporary discomfort of the people who used to share the ownership and now do not. They accept that the person assigned will sometimes make calls others would have made differently - because that is what assigning a decision means.
The opposite isn't worse decisions made faster. The opposite is no decisions made at all, dressed in the language of inclusion.
Where is your execution architecture leaking?
The Execution Drift Diagnostic scores your leadership team against the five drift patterns in about four minutes - including how many of your decisions are sitting in shared ownership right now.
Take the Execution Drift Diagnostic