Everyone Is Accountable. Nobody Owns the Decision.

A group of capable professionals sits down to resolve an operational problem. Sales explains the customer impact. Operations lays out the production constraints. Supply chain describes what is available. Finance raises the cost implications.

There are several reasonable options. People ask good questions and share information the others need.

Then the meeting ends without a decision.

The group agrees to gather more information or consult another stakeholder. A week later, the same people meet again. Eventually, someone takes the issue to a senior executive, who makes a call that could probably have been made days earlier.

Nobody in the room lacked expertise or was necessarily trying to avoid responsibility. But somewhere between involving the right people and deciding what to do, responsibility became difficult to locate.

And here’s something worth considering. Sometimes the problem isn’t that managers won’t make decisions. It’s that the organization has taught them that making decisions without executive approval is risky.

When everyone is involved in a decision, who is actually responsible for making it?

Sometimes a delay is necessary. A decision may carry significant financial consequences, depend on missing information, or require formal approval. The problem isn’t that decisions take time. It’s when an organization cannot distinguish legitimate complexity from uncertainty about who has the authority to act.

Organizations can talk a great deal about accountability while leaving people unsure about who decides, who contributes, and who is responsible for delivering the outcome. People can end up accountable for results they have little authority to influence.

Participation is not decision authority

A decision involving several departments will naturally require different perspectives. Some people provide expertise. Others need to be consulted because the outcome affects their work. Someone must decide what to do, and someone must ensure the decision is carried through.

Those roles can belong to different people, but they need to be understood.

Problems arise when contributing to a decision becomes an assumed right to approve it, or when being responsible for an initiative is confused with having the authority to resolve every issue affecting it.

A department can have legitimate concerns without holding veto authority. A project lead can own delivery without being authorized to approve every cost. An executive can make a decision while someone else remains responsible for implementation.

Collaboration should improve decisions by bringing the right information into the discussion. It shouldn’t make authority harder to identify.

Consultation is not unanimous agreement

Experienced leaders understand the importance of listening to people who will be affected by a decision. Their perspectives help reveal risks, challenge assumptions, and improve execution.

But seeking input and requiring unanimous agreement are not the same thing.

When consensus becomes an informal requirement, another stakeholder gets added, an objection triggers another discussion, and the group waits for every concern to disappear. Eventually, a department’s preference can become an unofficial veto.

Disagreement doesn’t necessarily mean a decision isn’t ready. People can make their case, raise legitimate concerns, and still accept that someone with the appropriate authority must decide.

Of course, some decisions require specific legal, regulatory, contractual, financial, or safety approvals. Those requirements must be respected. The distinction is between mandatory approval and additional consultation that has accumulated because nobody is certain who can make the call.

A leader can listen to everyone without requiring everyone to agree.

Authority should match consequence

Not every decision needs executive approval, and not every decision should be delegated without limits.

A routine operational adjustment within an established budget is different from a major financial commitment or a decision with significant safety, legal, or strategic consequences.

When organizations apply executive-level approvals to routine matters, they create delays and teach managers to wait. When they delegate significant decisions without boundaries, they expose themselves to unnecessary risk.

Leaders can establish three broad categories:

• Decide independently: Routine matters within established authority and risk limits.

• Decide after consultation: Matters within someone’s authority that require input from affected teams or subject-matter experts.

• Escalate or obtain formal approval: Matters outside delegated authority, involving significant risk, or subject to mandatory oversight.

These categories don’t require a complicated policy covering every possible situation. They simply need to be understood well enough that people aren’t renegotiating authority whenever an issue arises.

Clear boundaries don’t remove judgment. They make responsible judgment possible.

Otherwise, telling someone to “use your judgment” can amount to asking them to take responsibility while hoping they correctly guess what their leader would have wanted.

Giving responsibility means giving room to decide

During my time at a high-readiness military headquarters, I had a young Major working for me who regularly came looking for guidance on decisions he was perfectly capable of making himself.

It wasn’t that he lacked authority. He lacked confidence in his own judgment.

I could have answered his questions and sent him on his way. That would have been quicker in the moment, and he would have received the reassurance that his superior agreed with his thinking. But repeatedly doing that wouldn’t have helped him develop as a leader.

At one point, I stopped him and told him, “You know the answer. You know what to do. Just go do what you think is right.”

My responsibility wasn’t to make every decision for him. It was to help him recognize that he already possessed the knowledge, judgment, and authority to make those decisions himself.

Some months later, he deployed on an advisory mission that evolved into an evacuation operation. I watched him take on greater responsibility, and when we eventually debriefed his experience, I could see how much he had grown.

That experience reinforced something I’ve come to believe strongly about leadership. Giving someone authority is only part of the equation. They also need the confidence to exercise it, and sometimes that confidence develops because their leader deliberately resists the temptation to provide every answer.

I’ve said before on the Peak Performance Leadership podcast that empowerment without decision authority is just theatre. But the reverse deserves attention too.

You can clarify every decision right in an organization and still have people looking over their shoulders for approval. Authority establishes what someone is allowed to decide. Confidence influences whether they’re willing to make the call.

When managers continually seek approval, leaders need to understand why. Are the boundaries unclear? Have previous decisions been second-guessed? Or does the individual simply need more confidence in their judgment?

Those situations may look similar, but they require different leadership responses.

A name beside the initiative is not ownership

Organizations often assign someone to coordinate an initiative and assume the work is now owned.

But putting a name beside a project doesn’t automatically give that person the ability to resolve competing priorities, secure necessary contributions, or make decisions.

When progress stalls, the organization may describe the problem as a lack of accountability. The more useful question is whether the person was given the authority and support needed to deliver the outcome.

Ownership doesn’t mean personally performing every task. It means managing the outcome, coordinating contributions, monitoring progress, identifying risks, and following through on commitments.

That includes ensuring work moves between departments. One team may believe its responsibilities are complete while another is still waiting for information, approval, or work that meets an agreed standard. Both can be busy while the initiative remains stalled.

For important cross-functional work, ownership means making those handoffs explicit. People should know what must be delivered, who receives it, when it’s needed, and what happens if the commitment cannot be met.

Of course, that doesn’t remove the individual’s responsibility to act. Ownership also means making decisions within your authority rather than sending every difficult choice up the chain.

It also means escalating issues that genuinely exceed the authority provided. When that happens, leadership must either resolve the issue or clarify who can.

“Take ownership” cannot substitute for giving someone the means to do so.

The Decision Ownership Test

Before questioning someone’s willingness to take ownership, make sure the organization has actually defined what they’re expected to own.

For a consequential or recurring decision, five questions can reveal ambiguity before it becomes a stalled initiative.

This isn’t intended to create another approval process. Routine decisions should already be covered by established authority. The test is most useful when responsibilities cross departments, decisions keep resurfacing, or the consequences of confusion are significant.

1. Who decides?

Identify the person or designated authority responsible for making the decision. If collective or formal approval is required, clarify how it will be reached.

2. Who contributes?

Determine whose information, expertise, or perspective is necessary. Distinguish mandatory consultation from optional input. The goal is to involve the right people, not necessarily the most people.

3. Who owns the outcome?

Identify who is responsible for ensuring the decision produces the intended result. The decision-maker and outcome owner may be different people, but their responsibilities and authority must be clear.

4. What are the boundaries?

Establish financial thresholds, risk limits, required approvals, strategic constraints, and escalation triggers. People should understand where their authority ends.

5. What does delivery look like?

Define the expected outcome, timing, handoffs, and follow-up. Determine who receives each deliverable, what standard it must meet, and how progress will be confirmed.

A decision that never becomes action is not an organizational result.

These questions shouldn’t require an elaborate document or another committee. For familiar decisions, the answers may already be understood. For consequential or recurring work, making them explicit can prevent the same uncertainty from resurfacing.

The purpose isn’t to add process. It’s to eliminate ambiguity.

Return to that production meeting

Let’s return to the production meeting from the beginning of this article and apply those five questions.

Sales wants to protect the customer relationship. Operations is concerned about disrupting other work. Supply chain needs to confirm material availability. Finance wants to understand the additional cost.

Every concern is legitimate. But if nobody knows who has final authority to weigh those competing interests, the discussion can continue without resolution.

Applying the Decision Ownership Test gives the organization a path forward.

The authorized decision-maker is identified. Sales, Operations, Supply Chain, and Finance contribute the information needed to understand the trade-offs. Any required approvals, cost limits, or risk thresholds are established.

Once a decision is made, Operations or another designated owner coordinates the necessary changes, confirms what each department must deliver, and tracks progress against the agreed commitment.

The decision might still be to decline the customer’s request. It might involve adjusting the schedule and accepting an additional cost.

The important point is that the organization knows who decides, what information they need, and who is responsible for turning that decision into action.

Activity can hide the lack of a decision

When decision rights are unclear, an organization can appear remarkably busy.

Meetings take place. Emails circulate. Recommendations are revised. Status reports are produced. Yet the underlying issue remains unresolved.

Over time, managers can learn that escalating a decision is safer than making one. Senior executives become the default destination for unresolved questions, and the organization grows increasingly dependent on their availability.

It’s easy to interpret this as a lack of initiative among managers. Sometimes it is. But it can also reflect how leadership has defined authority, responded to previous decisions, or developed people’s confidence.

This is where executives need to examine their own behaviour.

If you routinely override decisions made within someone’s authority, you shouldn’t be surprised when that person starts seeking your approval. If you expect managers to take ownership but haven’t given them the means to influence the outcome, accountability becomes an unreasonable demand.

And if capable people continually seek reassurance, as the young Major once did with me, the answer may not be another approval or more detailed instructions. It may be helping them trust their own judgment.

Clarity doesn’t require centralizing decisions. In fact, it is often what allows decisions to move to the appropriate level.

Executives should retain decisions that genuinely require their authority or perspective. They shouldn’t become the default destination for every unresolved question.

Look at the last decision that stalled

Think about a significant decision that recently circled through your organization.

Was the delay caused by missing information or legitimate risk? Or were people uncertain about who could make the call?

Did consultation become an unofficial requirement for unanimous agreement? Was someone accountable for an outcome without having the authority to influence it? Did the person responsible have the confidence to act?

And once the decision was made, did someone clearly own implementation?

You don’t need to redesign your entire organizational structure to answer those questions. Start with one decision and determine what prevented it from moving forward.

Then ask whether the same thing could happen tomorrow.

The next time a decision lands on your desk that should have been made somewhere else, don’t immediately ask why your people couldn’t make the call.

Ask whether they knew they could, whether they had the authority to do so, and whether your leadership has given them the confidence to exercise it.

Because sometimes the biggest obstacle to decision-making isn’t the people who won’t decide. It’s the leader everyone believes must.

If too many decisions still require your personal involvement, or important initiatives repeatedly stall between departments, a free Leadership Clarity Session can be a useful place to examine how decision rights, ownership, and accountability are affecting your ability to lead and execute.