Look at your last strategy doc and find the word "own."
You'll see sentences like "the GTM team owns pipeline generation." "Marketing and Sales share responsibility for the handoff." "RevOps owns reporting and enablement." It reads like accountability. It photographs like accountability. It is, in fact, the precise opposite of accountability, because not one of those sentences contains a name.
If ownership lives in a slide instead of a person, it doesn't exist. "The GTM team owns it" means no human wakes up on Monday feeling the weight of it. "Marketing and Sales share it" means each side is quietly, reasonably assuming the other has it. Shared ownership isn't ownership divided. It's ownership deleted. When everyone owns a thing, no one does, and the thing sits there unattended until someone trips over it a quarter later and asks why it was never handled.
And the cost of that doesn't sit still. It compounds, which is the part the strategy doc never accounts for.
An unowned outcome doesn't just fail to get done. It rots, and the rot spreads outward. The gap it leaves gets papered over by someone's heroics, which hides it for another quarter. The people around it start building workarounds, so now there's process bolted on top of the gap, and fixing the original problem means unpicking everything that got built to survive it. Meanwhile every decision the unowned thing touches needs a meeting, because no single person has the authority to just call it, so your org's speed degrades one committee at a time. And when it finally misses, nobody owns the post-mortem either, because nobody owned the outcome, so the same failure files itself neatly away to happen again next quarter.
Shared ownership isn't ownership divided. It's ownership deleted.
That's the compounding cost. Not the thing that didn't get done. The tax that thing levies on everything around it, every week, growing, while everyone points at a slide that says the team owns it.
Unclear ownership is comfortable in ways clear ownership isn't. Shared ownership feels collaborative. Naming a single person feels like you're setting them up, isolating them, maybe even blaming them in advance. So the kinder-seeming move is to spread it around, everyone nods, and nobody notices that "kind" just quietly became "nobody's responsible."
There's a quieter reason too, and it's less flattering. Ambiguity keeps everyone's options open, including the leader's. If no one owns it, no one can be blamed when it misses, and that includes you. Unclear ownership is a way of never having to have the hard conversation, because there's no single person to have it with. It feels like collaboration. It's often just conflict avoidance wearing a nicer outfit.
And then RACI made it worse, not better. It let you assign five people to one outcome across five neat categories and call the result clarity, when what you actually built was five people who can each point at one of the other four. A chart that needs a legend is not accountability. It's a diagram of who to blame later.
So here's the test. For any outcome that actually matters, run it through three questions.
Can you name the one person accountable, without using a team name and without a slash? One human. If the honest answer is "the GTM team" or "Sarah and Tom," it's unowned. A slash is just two people agreeing to blame each other.
Can that person make the call the outcome requires, without convening a meeting to do it? Ownership without authority is just being the designated person to feel bad when it fails. If they can't decide, they don't own it. You do.
Are they on the hook for the outcome, not just the activity? "Ran the campaign" is activity. "Moved the number the campaign existed to move" is ownership. If someone can succeed at all the tasks while the result fails and still feel like they did their job, you've assigned the wrong thing.
Named, empowered, accountable for the result. Fail any one and the outcome is unowned, and it's costing you more every week you leave it that way.
Here's the one thing to ship this week. Take your top five revenue outcomes for the quarter. Next to each one, write a single name. Not a team. Not two names with a slash. One person. Where you can do it instantly, good, that outcome has a chance. Where you hesitate, or catch yourself writing a function instead of a human, you've just found exactly where your org is quietly stalling. That blank space next to the outcome is the compounding cost, made visible.
Then do the uncomfortable part. Go to that person, out loud, and tell them they own it. Not the activity, the result. Make sure they can make the calls it needs without asking permission. And make sure everyone else knows it's theirs, so the next time it comes up in a meeting there's a name in the room, not a slide on the wall.
Accountability was never a box on an org chart. It's a person who loses sleep when the number's at risk. Give every outcome that matters one of those, by name, and watch how fast the stalling stops.