When Everything Is Shared, Nobody Owns It

Most of the organizations I've worked with haven't lacked competence. They haven't lacked good intentions either. Many have had clear strategies, strong teams of skilled people, and individuals who genuinely want to succeed. And yet some of them have still struggled to prioritize, make decisions, and create momentum.

At first, I thought this was mainly about strategy. When an organization can't move fast enough, it's natural to assume the direction is unclear. Later, I thought it was about governance. Maybe the decision-making processes were too weak, or maybe accountability wasn't clearly enough defined. But over time, I started noticing a different pattern. Whether the discussion was about products, capabilities, organization, priorities, or larger transformations, the same question kept coming up, again and again.

Who owns this?

What was interesting wasn't that the question got asked. What was interesting was how often the answer turned out to be unclear.

Involvement Can Replace Ownership

Many of the most complex challenges show up in areas that a lot of people care about. Once an area becomes important enough, interest around it grows. More stakeholders want influence. More teams get involved. More perspectives need to be taken into account. On its own, that's both natural and desirable. Collaboration is rarely the problem. The problem starts when involvement gradually begins to replace ownership.

"We Own This Together"

I've heard the phrase "we own this together" many times. It sounds positive. It signals collaboration, maturity, and shared accountability. And yet, over time, I've become skeptical whenever I hear it. Not because collaboration is wrong, but because the phrase often hides an important ambiguity. When everyone owns something together, it often becomes hard to tell who actually owns the outcome.

How It Happens Gradually

This rarely happens as a deliberate decision. It happens gradually. A product picks up more stakeholders. A capability becomes relevant to more parts of the business. An initiative grows in importance. Eventually, the area becomes significant enough that more and more people need to be involved. None of these steps look problematic on their own. If anything, each one seems reasonable. But together, they can move the organization into a situation where a lot of people feel responsible, while fewer and fewer experience clear ownership.

When the Friction Becomes Visible

This is usually the point where friction starts to show. Decisions take longer than expected. Priorities feel unclear. Roadmaps change more often. The organization spends more and more energy on coordination. More meetings get scheduled. More governance forums get established. More documents get written. A feeling emerges that more structure is needed to create progress.

More Coordination Instead of Clear Ownership

What's striking is that organizations rarely respond by clarifying ownership. Instead, they often try to compensate for the lack of ownership with more coordination. They build mechanisms around the problem instead of addressing it directly. In the short term, this can create a sense of control. In the longer term, it usually increases complexity. And sooner or later, the question comes back.

Who owns this?

Responsibility Can Be Shared. Ownership Can't.

The more I've observed this pattern, the clearer the difference between responsibility and ownership has become. Responsibility can be shared. Large, complex work genuinely requires many people to contribute. Ownership works differently. Many people can contribute to an outcome, but someone still has to own the whole. Someone has to own the priorities. Someone has to own the trade-offs. Someone has to own the result. Without that, it becomes difficult to create long-term direction, because no one has the mandate to carry the consequences of the decisions being made.

Who Owns the Outcome?

That's probably why I've started asking a different question when discussions start going in circles. Not whether the strategy is right. Not whether the governance model is good enough. Not whether the organization needs more meetings or more governance forums.

Instead, I ask:

Who owns the outcome?

Because sometimes the problem isn't the strategy. Sometimes the problem isn't the people. Sometimes the problem isn't governance.

Sometimes the problem is much simpler.

Everyone feels responsible.

No one owns the result.