Who Gets to Make the Call?

A team can have the right people and enough information, yet still struggle to make a decision. Clear ownership gives the discussion somewhere to go.

Another meeting ends with a request to gather a little more input. The team has discussed the options, the trade-offs are familiar, and nobody expects the next conversation to produce a major discovery. The unresolved question is who has the authority to choose.

This is worth examining before asking people to become more decisive. A person may be ready to take responsibility while remaining unsure whether their manager, a neighboring team, or a senior stakeholder will reopen the decision afterwards.

Name the decision before assigning the owner

Broad responsibility is easy to announce. A team can own the customer experience, a project, or a product launch without knowing who decides the next concrete issue. Ownership becomes useful when it is attached to an actual choice.

Consider a hypothetical product team preparing a release. Choosing the release date, accepting an unresolved defect, and approving the customer announcement are related decisions, but they may require different owners. Treating them as one general launch decision can leave everyone waiting for everyone else.

Start by writing the choice in a sentence. Then name the person authorized to resolve it, the people whose input they need, and the limits within which they can act. This can fit into the meeting agenda or project brief; it does not require a new committee.

Match the process to the consequence

In Amazon's 2015 shareholder letter, Jeff Bezos distinguished decisions that are difficult to reverse from those that can be changed. He argued that applying the same heavyweight process to both can slow an organization down. The distinction offers a useful management lens, rather than a universal rule about how every company should operate.

For the release team, changing the wording of a routine internal update may sit within a small, reversible boundary. Accepting a defect that affects customer data is a different decision with different expertise and authority involved. Labeling both urgent does little to clarify either.

Ask what would be needed to undo the choice. Include effects on customers, colleagues, commitments, and trust, as well as the effort of changing a setting. A decision that is technically reversible may still leave consequences that matter.

Make consultation useful

An owner needs relevant challenge. Before asking colleagues for input, explain the question and the kind of contribution needed. A security specialist may need to assess a risk; a delivery lead may need to identify a dependency; a customer-facing colleague may know which promise would be affected.

Be clear about whether someone is advising, approving a defined exception, or holding the final decision. If everyone believes they have a veto, a meeting can look collaborative while concealing incompatible expectations.

The owner should also explain how the input affected the choice. A brief note recording the decision, the main reason, and any unresolved concern makes it easier for others to act without reconstructing the discussion.

Support the authority you assign

A manager's response after the decision matters. If a reasonable choice made within agreed boundaries is routinely overturned without explanation, the next owner has a strong reason to seek approval first.

When a decision needs to change, identify what changed: new evidence, a missed constraint, or a boundary that was unclear. That conversation can improve judgment while preserving the value of delegated authority.

Take one recurring decision that keeps returning to a meeting. Write down who makes it and what they need to know before doing so. Clear ownership starts with a choice the team can actually recognize.