Three people think they own the decision. Nobody actually does.
Key decisions aren't being made, or they're being made three times by three different people. The result is the same: paralysis, rework, and a project that drifts.
Why this really happens
- A reorg reshuffled responsibilities without updating decision rights
- Multiple stakeholders believe the decision falls in their domain
- The project was started under one organizational structure and now lives in another
- Nobody explicitly defined who decides what at the project's start
There’s a particular kind of meeting that happens in every organization with unclear decision rights. Six people sit in a room. Someone presents options A, B, and C. Everyone discusses. Everyone has opinions. Nobody decides. The meeting ends with “let’s think about it and reconvene.” Two weeks later, the same meeting happens.
Meanwhile, the developers have nothing to build. Or worse — they’re building something based on what they think the decision will be, and another team is building something different based on a different assumption.
Why decisions go unowned
Reorgs break ownership chains. Before the reorg, Sarah owned the technical architecture. After the reorg, Sarah moved to a different group. Her old team assumed the new group lead picked up her decisions. The new group lead assumed those decisions stayed with the old team. Result: nobody owns them.
Growth outpaces governance. When a company is small, everyone knows who decides what because everyone is in the same room. At 50 people, you need explicit structures. At 200, you need written frameworks. Most companies skip this step because it feels bureaucratic — until the cost of not having it becomes unbearable.
Consensus culture masks indecision. “We decide together” sounds collaborative. In practice, it means nobody has the authority to make a call that someone else disagrees with. So nothing gets decided until everyone agrees, which is never.
The real cost
Every unowned decision is a blocker. Some are small — which color should the button be? Those resolve themselves. But the big ones — which vendor to use, what architecture to follow, which market to target first — those can stall a project for weeks or months.
And the cost isn’t just the delay. It’s the rework. When a team builds without a clear decision, they build based on assumptions. When the decision finally gets made, those assumptions are often wrong. So the work gets thrown away, and the team’s trust in the project erodes.
How to diagnose it
The three-person test. Pick a decision that feels stuck. Ask three people independently: “Who owns this decision?” If all three name the same person, the decision is owned. If they don’t, you’ve found the problem.
The decision audit. List every significant decision the project needs in the next four weeks. For each, write down who owns it. Wherever the answer is “I don’t know” or “we all do” — that’s an unowned decision. Our decision ownership mapper walks you through this exercise.
The meeting test. If a topic comes up in the same meeting more than twice without resolution, it’s because nobody has the authority to resolve it.
How to fix it
Assign owners, not committees. For every unowned decision, name one person. Not a group. One human being. That person consults whoever they need to, but they make the final call. This feels uncomfortable in consensus cultures. It works anyway.
Write it down. Once you’ve assigned decision owners, publish the list. A shared document that says “Architecture decisions: Alex. Vendor selection: Maria. Feature prioritization: James.” This document will save more time than any process improvement.
Give owners permission to be wrong. The reason people avoid owning decisions is that ownership means accountability. If the decision turns out badly, the owner gets blamed. Make it explicit: a fast wrong decision that gets corrected in two weeks is better than no decision for three months. Wrong is fixable. Stuck is not.
Revisit after reorgs. Every reorg should include a “decision rights review.” Who owned what before? Who owns it now? Where are the gaps? Thirty minutes of this exercise prevents months of drift.
Common questions
- How do I figure out which decisions are unowned?
- Ask three people independently: who decides X? If you get three different answers, that decision is unowned. Our decision ownership mapper at /tools/decision-mapper automates this exercise.
- Should every decision have exactly one owner?
- For speed, yes. That doesn't mean one person decides alone — they can consult anyone. But one person must have the final call. RACI matrices exist for a reason, even if nobody likes filling them out.
- What if the ownership problem is between my team and another team?
- Then you need someone above both teams to assign it. If that person doesn't exist or won't decide, the ownership gap is a symptom of a larger organizational problem.
Symptoms you might recognize
Sound familiar?
I help unstick software projects like this. No slide decks — just a conversation about what's actually wrong.
Tell me what's stuck