Responsibility Is Not Authority

A responsibility chart tells people where they fit in the work. It does not tell them who makes the call when the work is contested.

Suppose your leadership team spent a quarter building a responsibility chart. Every core process mapped. Every function placed. Every cell filled in.

Six months later, the pricing exception still lands on the CEO's desk. The delivery commitment still gets argued in three meetings. A decision made in March is back on the agenda in May.

The chart was not wrong. It answered a different question.

Two different questions

A responsibility chart answers: who is involved in this work? Who does the work, who contributes, who is consulted, who is kept informed. That is useful. It reduces confusion about roles.

Decision rights answer a narrower question: when this choice has to be made, who makes it, and makes it stick?

The difference shows up the moment the people involved disagree. A chart built around tasks says little about what happens next. Decision rights are built around the decision itself: one owner, the inputs that owner needs, the condition that sends it up a level, and a visible close.

Involvement is not authority. A leader can be consulted on every cross-functional decision in the business and own none of them. That is not a flaw. It is the point.

Lowest capable level

Naming one owner is half the standard. The other half is where that owner sits.

As a starting principle, decisions should sit at the lowest level capable of making them well. Capable means three things:

• Close to the information. The owner sees the facts first, not secondhand.

• Able to see the enterprise consequence, not just the functional one.

• Living with the result. The owner carries the outcome, not just the recommendation.

The second criterion is where decisions get pulled upward. The person closest to the information cannot see the enterprise trade-off, so the decision goes to someone who can. Repeat that often enough and the CEO becomes the default owner for cross-functional decisions.

The answer is not automatically to move the decision up. First ask what the owner is missing: the enterprise priorities, a clear rule for the trade-off, or both. Decision rights can move down only when the owner can see the enterprise priorities they are deciding against.

What it looks like when it works

Pick a recurring decision. A pricing exception. A hire above plan. A delivery date inside standard lead time.

Ask three leaders, separately, who owns it. If you hear the same name without hesitation, and the last decision stayed closed unless a defined trigger justified reopening it, the discipline is working for that decision.

If you hear three names, or “it depends,” or “we usually work it out,” the decision has no owner. It has participants.

Why letting go is hard

Assigning a decision on paper is the easy part. The harder part is the leader who used to make it.

Reluctance to give up a decision is not a character flaw. It can be understandable when a leader remains accountable for an outcome they are being asked to stop controlling. Telling that leader to trust the team does not address it.

What addresses it is structure the leader can rely on: the inputs they will still provide, the trigger that brings the decision back to them, and visible confirmation of what was decided. Sometimes it also takes direct work with the leader doing the letting go.

This is where the discipline stops being a design exercise and becomes a leadership one. The structure can name the owner. Only the leader can step back.

Where this sits in the system

Decide depends on Focus. An owner needs something to decide against. Without enterprise priorities, decision rights can produce faster decisions that serve functional interests instead of the enterprise.

And Decide is not enough on its own. Decide without Measure produces fast decisions pointed in different directions. Owners are clear and moving quickly, but nobody has a shared view of whether their choices add up. That is the subject of the next article.

Try this now

Pick the three decisions from the past quarter that took the longest or got reopened. For each, a useful starting point is four lines:

• The decision, written as a choice, not a task.

• One owner.

• Who provides input, and what they provide.

• What would send it up a level.

If you cannot name one owner without calling a meeting, you have found where to start.

Thirty days later, check two things: how many of those decisions came back to your desk, and how many were reopened without new information.

A responsibility chart tells people where they fit. Decision rights tell them who decides.