Accountability Starts With Decision Rights, Not Follow-Up Meetings

Some managers repeat one question constantly: “Why didn’t you follow this up?” It is not a bad question, but it is often asked too late. By the time work has reached repeated check-ins, reminder messages, and explanation meetings, the problem is usually not just one person’s lack of effort or attention. There is a good chance that decision rights were unclear from the beginning.

We give someone an outcome and say they own it. They may need to finalize a customer order, recover a delayed project, resolve a quality issue, or respond to an important request. Yet at the same time, we keep the key decisions for ourselves. We must approve the discount, set the priority, sign off on any schedule change, and hear about every small risk.

On the surface, responsibility has been delegated. In reality, only the work has been delegated. The person is expected to produce the outcome but is not allowed to make the decisions required to produce it. Then we expect speed, initiative, and accountability. This contradiction is one of the roots of exhaustion in teams.

Accountability is not created by saying, “This is yours.” It takes shape when a person knows which decisions are genuinely theirs, how far they can go, and at what point they should stop and bring the issue upward. Without that trio, delegation looks more like passing off a problem than creating ownership.

In this situation, follow-up meetings usually become a painkiller. The manager asks what happened; the person explains they were waiting for approval; the manager asks why they were not told earlier; and everyone agrees that next time the issue should be raised sooner. The meeting ends, but the decision rule remains vague. A few days later, the same performance returns with a different subject.

The problem is that many organizations substitute follow-up for design. Rather than clarifying who decides what, they fill calendars with meetings. Rather than defining risk boundaries, they ask people to use “good judgment.” Rather than making escalation paths clear, they look for someone to blame after an error.

Judgment matters, but judgment does not work in a vacuum. Even an experienced person, if they do not know what is acceptable, what is a red line, and which consequence matters most to the business, will either act more cautiously than necessary or take the wrong kind of risk. The first kills speed; the second damages trust.

For recurring work, the answer does not need to be complicated. A short decision-rights sheet can remove much of the ambiguity. Not a heavy document for filing away, and not a collection of bureaucratic sentences nobody reads. Just a simple page that creates a conversation about recurring decisions before delegation or at the start of a working relationship.

The first part of this sheet should name the delegated decision, not merely the job title. “Handling orders” is not a decision. “Confirming delivery dates for standard orders within stated capacity” is more specific. “Managing the project” is vague too; “prioritizing the week’s work based on customer commitments and team capacity” is clearer and actionable.

The second part is the expected outcome. There is no need to suffocate everything with countless metrics and heavy reporting. It is enough to make clear what a good decision is meant to protect or improve: customer satisfaction, cash flow, quality, delivery time, safety, profit margin, or team coordination. When the outcome is unclear, people make decisions based on personal preference or fear of the manager’s reaction.

The third part is the boundary of authority. How far can the person act without seeking approval? Can they reorder work? Can they reach an agreement with another department to solve an issue? Are they allowed to propose an alternative solution to retain a customer? Authority boundaries need practical language, not phrases such as “as needed” or “at your discretion.” Under pressure, those phrases offer almost no help.

Then state the non-decisions explicitly. Some managers fear this section because they think a list of limits destroys authority. The opposite is true: clear limits give authority meaning. If changes involving financial commitment, legal risk, critical quality, safety, or a sensitive customer relationship sit outside the person’s authority, it is better to say so before a problem happens, not afterward.

The next part is notification points. Informing is different from asking permission. Someone may have the right to decide, while the manager or team still needs to know about that decision; for example, when a major priority shifts or a key customer is affected. If that distinction is unclear, people wait for approval every time they need to inform someone, and the manager assumes they are kept in the loop while decisions are delayed.

The most important part is escalation triggers. Escalation should not depend on a vague feeling that the person should raise an issue “if necessary.” It should be as specific as possible: crossing a risk boundary, conflict between two important priorities, insufficient data to choose, a decision that commits another department, or a situation where an exception could become a precedent.

These rules are not meant to predict every possible scenario. Trying to do that usually buries an organization in procedures. The goal is not to eliminate judgment; it is to give judgment firmer ground to stand on. People should be able to act independently in normal situations and escalate unusual ones properly, without fear or political games.

One useful sign of ambiguity is this: if someone repeatedly asks, “Am I allowed to do this?” before acting, the issue may not be a lack of confidence. The organization may simply have failed to tell them what is truly within their authority. Another sign is a manager complaining at the end of every week about their workload while most decisions reaching their desk are repetitive, predictable, and close to daily operations.

Of course, decision rights without capability, data, and feedback are risky too. Giving authority does not mean abandoning the person. The manager still needs to explain business context, teach the criteria for good decisions, make necessary data available, and offer feedback on decisions made. But that is fundamentally different from making someone wait for approval on every small move.

Do not try to begin with every decision in the organization. Choose one recurring bottleneck: a place where people are constantly followed up with, decisions keep moving upward, or people are trapped between speed and caution. Write a decision-rights sheet for that situation, review it with the person who will decide, and after a few weeks review not only the outcome, but the boundaries themselves.

In that review, you may discover that authority was too limited or, conversely, that risks were underestimated. That is not failure; it is part of the design. A mature organization is not one that has a ready answer for every situation. It is one that can pull recurring decisions out of the manager’s head, clarify their boundaries, and improve those boundaries through learning.

If every important outcome requires a follow-up meeting, your team may not need more motivation. It may need clearer decision rights. Managers who want to see real accountability should ask themselves a harder question before asking, “Why wasn’t this done?”: “Did I make it clear from the start what decision this person had the right to make?” The answer usually determines the quality of many meetings that follow.

Follow-up is necessary, but it should not be the main pillar of managing work. Good follow-up is for learning, removing obstacles, and noticing change; not for compensating for ambiguity created by the manager. When decision rights, authority boundaries, and escalation rules are clear, follow-up becomes lighter and accountability becomes a natural part of daily work rather than a management slogan.

In a world where work is more complex and decisions move faster, keeping every decision at one point is not a sign of control; it is a sign of limited capacity. Building real accountability starts here: delegate the decision along with the work, while making its boundaries clear.

You do not need to create a formal form to begin. In your next delegation conversation, clarify just six questions: What decision is yours? What outcome is desired? How far does your authority go? What is not yours to decide? When do you simply inform others? And when do you need to escalate? That short conversation is worth more than many follow-up meetings later.

Real accountability means a person can say, “I made this decision, based on this reasoning, within this boundary, and with awareness of its consequences.” If that sentence cannot be said in your team, you probably have not delegated responsibility yet; you have only pushed the expectation for results downward.