The goal is not to push every decision downward. It is to stop moving decisions higher than necessary—and build the conditions for sound judgment close to the work.

Too many decisions may be returning to you

Your people bring you questions all day.

A customer wants an exception. A supplier cannot meet the original schedule. An employee needs to adjust the order of work. Two departments disagree about who should act first.

You answer because you know the business. You can often decide in a few minutes what may take someone else much longer.

The work moves.

Then another question arrives.

At first, this may feel like responsible leadership. You are available. You protect quality. You prevent mistakes.

But look closely at what is happening.

People are learning that uncertainty belongs to you. Your calendar fills with decisions that begin elsewhere. Employees wait because acting without approval feels riskier than asking.

You become the fastest person in the system—and eventually its biggest bottleneck.

The goal is not to push every decision downward. It is to place each decision at the lowest level where it can be made responsibly.

That level is close enough to the work to see what is happening, but prepared enough to understand the boundaries, consequences, and strategic result that must be protected.

The question is not whether people should decide

People are already making decisions.

They decide whether to act or wait. They decide what information to share, which option to recommend, and when to bring a problem upward.

Even refusing to decide is a decision.

So the question is not whether you should allow people to make decisions.

The question is whether the organization has made sound decision-making possible where the work happens.

That distinction matters.

A leader may say, “Use your initiative,” while keeping authority unclear. An employee may be encouraged to act, then blamed when the result is unfavorable.

The next time, the employee waits.

The organization concludes that people lack ownership. But the person has learned a rational lesson: approval is safer than judgment.

Moving decisions requires more than encouragement. It requires clear responsibility, usable boundaries, access to information, and a leader who can separate a reasonable decision from a guaranteed result.

Lowest does not mean least important

The phrase lowest responsible level can sound like a way of pushing work down the hierarchy.

That is not the idea.

The goal is not to give difficult decisions to the least senior person so managers can escape responsibility. Nor is it to expect frontline employees to carry decisions without the authority and support those decisions require.

The lowest responsible level is the point where four conditions meet:

The person is close enough to the situation to understand what is happening.
The person has enough information and judgment to compare the options.
The person has authority to act within clear boundaries.
The person is connected to the consequences and can follow what happens next.

Sometimes that level is the employee serving the customer.

Sometimes it is the supervisor.

Sometimes the decision genuinely belongs to a manager, executive, board, or specialist.

The purpose is not to move decisions as low as possible.

It is to stop moving them higher than necessary.

Your people may be waiting for rules that exist only in your head

You may believe the team already knows which decisions they can make.

After all, you have worked together for months. You have handled similar situations. They have seen how you respond.

But experience does not always create clarity.

People may know what you decided before without understanding the rule behind the decision. They remember that you approved one customer exception and rejected another, but they cannot see which conditions made the difference.

So they ask again.

This is where the previous article on usable direction becomes important. People need more than the result. They need to know where their authority begins, what it must protect, and when it ends.

A rule that remains inside your head cannot guide anyone else’s judgment.

Bring it into the conversation.

A familiar customer question can reveal the whole system

Imagine an employee handling a delayed delivery.

The customer needs part of the order today. The rest can arrive tomorrow. A faster delivery option will cost more but remain within the margin of the order.

The employee calls the supervisor.

“Can we use the faster delivery service?”

The supervisor asks for the customer name, order value, cost, and reason for the delay. After several minutes, the supervisor approves.

The decision is sound.

But who was in the stronger position to make it?

The employee knew the customer’s immediate need. The cost was already visible. The option stayed within a reasonable limit. The employee would continue handling the result.

The decision moved upward because authority was not clear, not because higher judgment was required.

Now imagine the supervisor responds differently:

“For delays affecting customer operations, you may approve recovery costs up to this amount when the order remains profitable and no safety or legal concern is involved. Tell me afterward what you decided and what caused the delay.”

The next similar decision can remain with the employee.

The supervisor has not abandoned responsibility. The supervisor has clarified the boundary, retained visibility, and created a chance to learn from the pattern.

One decision has moved.

More importantly, the system has begun to change.

Begin with the result the decision must protect

Leaders often distribute authority by amount.

Employees may approve up to a certain cost. Supervisors may approve more. Managers may approve the largest amount.

Financial limits are useful, but they do not explain the complete decision.

A person also needs to know what result should guide the choice.

Suppose an employee can approve a delivery recovery cost of up to ₱5,000.

Should the employee approve it every time the customer complains? Should speed always win? What happens when the issue resulted from customer error? What if the faster solution creates a safety risk?

The amount defines one boundary.

The result provides direction.

You might say:

“Our goal is to protect the customer’s operations when we have failed to meet a confirmed commitment. You may approve recovery costs within the limit when the action can restore that result without creating a safety, legal, or reputational risk.”

Now the employee has more than authority.

The employee has a basis for judgment.

Separate three kinds of decisions

A useful way to clarify decision ownership is to separate decisions into three groups.

Decide and act

The person has enough authority, information, and competence to make the decision and carry the result. The leader does not need to approve it beforehand.

Consult, then decide

The person still owns the decision but needs another perspective, technical advice, or information before acting. Consultation improves the choice without transferring ownership.

Escalate

The decision exceeds the person’s authority or changes something consequential beyond the local situation. It may affect policy, safety, legal exposure, major financial risk, or the organization’s strategic promise.

These categories are more useful than saying, “Ask me whenever you are unsure.”

Uncertainty appears in most meaningful decisions. If uncertainty automatically triggers escalation, people will never develop judgment.

Instead, help them identify which kind of uncertainty they can handle and which kind requires another level.

Escalation should carry thinking, not only a problem

Some decisions must move upward.

That is not a failure.

The problem begins when escalation transfers all the thinking to the next person.

An employee says, “The customer wants a discount. What should we do?”

The supervisor starts from the beginning. What happened? How valuable is the account? What has already been promised? What options exist?

The employee had access to much of this information but brought only the question.

Change the expected play.

When escalating, the person should bring:

the result that must be protected;
the relevant facts;
the options considered;
the recommended decision;
the risk or boundary requiring higher authority.

Now the leader is not receiving an abandoned problem.

The leader is receiving a reasoned recommendation that requires a decision at another level.

This builds judgment even when the final authority remains above.

Do not reward escalation more than judgment

People notice which behavior receives a safer response.

Suppose an employee decides within the agreed boundary and the outcome is disappointing. The leader asks, “Why didn’t you check with me first?”

A week later, another employee escalates a routine issue. The leader gives the answer without questioning why the decision moved upward.

What has the team learned?

Escalation is safe. Judgment is risky.

Soon, people bring you more decisions—not because they cannot make them, but because the system has taught them how to avoid blame.

If you want decisions to remain closer to the work, respond carefully when outcomes disappoint.

Ask whether the reasoning was sound.

Did the person use the available information?

Did the decision stay within the boundary?

Was the strategic result clear?

Was the risk reasonable at the time?

A sound decision can produce an unfavorable result. A weak decision can sometimes produce a favorable one.

Judge the quality of the decision, not only the result that followed.

A poor outcome does not always mean the authority was misplaced

This is where leaders often lose confidence.

They delegate a decision. The employee chooses. The result is not what everyone hoped for.

The leader takes the authority back.

The next time, approval is required again.

Sometimes this is necessary. The person may not yet have the required judgment, or the boundary may have been too broad.

But do not move the decision upward before examining what actually failed.

Was the person missing information?

Was the rule unclear?

Did another department withhold something necessary?

Did the situation fall outside the expected pattern?

Did the employee make a careless choice, or a reasonable choice under uncertainty?

The answer determines the next move.

You may need to clarify the boundary, improve access to information, coach the reasoning, or reduce the decision space temporarily.

Taking every decision back may protect the next result.

It can also prevent the organization from building the capability it needs.

Information must travel with authority

You cannot move a decision without moving the information needed to make it.

An employee may be allowed to solve a customer concern but cannot see the customer’s full history.

A supervisor may be expected to adjust staffing but does not know the week’s demand forecast.

A department manager may own a project but cannot see the commitments made by another function.

The organization says, “You own it.”

The system says, “You cannot know enough to act.”

People then return to someone with more access.

Before moving a decision, ask what the person needs to see.

What facts shape the choice?

Where is that information stored?

Is it available in time?

Does the person understand how to interpret it?

Authority without information creates guessing. Information without authority creates frustration.

Responsible decisions require both.

Move the decision, not only the task

A leader may delegate the activity while keeping every meaningful choice.

The employee gathers the data, schedules the meeting, prepares the document, and contacts the customer. The leader selects the option, approves the message, and decides the next move.

The task has moved.

The decision has not.

That arrangement may be appropriate while someone is learning. But when it becomes permanent, the person remains an assistant to the leader’s judgment.

Look for one decision that can move with the work.

If the person prepares the proposal, can they decide which client problem deserves emphasis?

If the employee owns the customer concern, can they choose among approved recovery options?

If the team leader runs the meeting, can they decide how to structure the discussion around the required outcome?

This prepares the way for the next article on how to delegate the win. Ownership becomes real when a person carries not only activity but also the decisions necessary to achieve the result.

Use smaller boundaries while judgment is growing

You do not need to choose between complete control and complete freedom.

Decision authority can grow.

A new employee may begin with a narrow category of routine decisions. The person acts within clear limits and reviews the reasoning afterward.

As judgment becomes visible, expand the boundary.

Allow more variation. Increase the financial limit. Include situations with competing priorities. Reduce the frequency of review.

The movement may look like this:

First, the person recommends while you decide.

Next, the person decides after consulting you.

Then, the person decides and informs you.

Eventually, the person decides and follows the result without routine reporting.

This is not a rigid ladder for every situation.

It is a way to see that decision ownership can develop through practice.

The leader does not wait for complete confidence before allowing any judgment. Nor does the leader give unlimited authority before the person is ready.

Responsibility grows with visible proof.

Avoid the approval trap

Approval can feel efficient.

The employee has done most of the work. You review the final choice, say yes or no, and the decision is complete.

But approval carries hidden costs.

The person may design the recommendation around what you are likely to accept rather than what the situation requires. You become responsible for the final choice without being as close to the work. The employee remains dependent on your availability.

Over time, routine approval becomes part of the process even when it no longer improves the decision.

Review your approvals.

Which ones protect meaningful risk?

Which ones exist because the person lacks capability?

Which ones survive only because nobody has changed the old process?

Which ones could become notification rather than permission?

Do not remove approval merely to speed things up.

Remove it when another person can make the decision responsibly and the approval no longer adds enough value to justify the delay.

Seniority does not always improve the decision

The person with the highest rank may have broader authority and greater experience.

That does not mean they always have the strongest view of the situation.

People close to the customer can see details that disappear in reports. Employees performing the process know where the workaround has become normal. Supervisors can recognize patterns before they become visible in monthly measures.

Higher leaders bring context, cross-functional perspective, and authority over larger trade-offs.

Both views matter.

The decision should sit where the necessary information and responsibility meet.

A local customer recovery decision may belong near the customer.

A change in the customer promise belongs higher.

A routine schedule adjustment may belong to the supervisor.

A staffing decision that changes the organization’s cost structure may require a manager.

Respect hierarchy where consequences demand it.

Do not use hierarchy as a substitute for thinking about where the decision belongs.

The leader’s role changes when the decision moves

When you stop making a routine decision, you do not stop leading.

Your work changes.

You clarify the strategic result. You set the boundary. You make information available. You coach judgment. You review patterns and remove barriers that no local decision can solve.

This is often harder than giving an answer.

Giving an answer creates immediate closure. Building judgment requires patience.

You must allow another person to think differently from you. You must tolerate reasonable variation. You must decide when to intervene and when to let experience teach.

The work may feel slower at first.

But repeated answers solve one situation at a time. Stronger judgment improves many future decisions.

That is how leaders move work without keeping themselves at the center of every move.

Look for decisions that repeatedly travel upward

Do not begin with an organization-wide empowerment campaign.

Begin with the evidence already in your day.

Which questions do people ask you repeatedly?

Which approvals fill your inbox?

Which decisions stop when you are unavailable?

Which problems arrive without options or recommendations?

Which situations have become so familiar that you already know the answer before the person finishes explaining?

These are candidates for movement.

Choose one.

Do not move it simply because it annoys you. Examine what responsible ownership would require.

The person may need a clearer rule. The system may need to expose information. A financial or risk boundary may be necessary. The employee may need practice comparing options.

Design the move around those conditions.

Give people a simple decision play

A practical play helps people pause and think before acting or escalating.

For a recurring decision, use four questions:

What result are we protecting?
What options are available?
What do I recommend, and why?
Is this decision within my boundary?

When the answer to the fourth question is yes, the person acts and follows the result.

When the answer is unclear, the person consults.

When the decision clearly exceeds the boundary, the person escalates with a recommendation.

This play is simple, but it changes the quality of the conversation.

Instead of beginning with, “What should I do?” the employee begins with the result, options, and reasoning.

The leader can then coach how the decision is being made rather than automatically becoming the decision-maker.

Follow the pattern, not only the individual decision

One decision tells you what happened once.

A pattern tells you what the system is producing.

If several employees escalate the same type of issue, the boundary may be unclear.

If only one employee escalates, that person may need additional practice or confidence.

If decisions remain close to the work until an urgent customer calls, pressure may be triggering the old pattern.

If supervisors take decisions back when senior leaders are watching, the culture may still reward visible control.

Follow what repeats.

The purpose of daily execution is not to produce one successful example. It is to make the new response usable, repeatable, and supported by the system around it.

Ask what must change for sound local decisions to become normal rather than exceptional.

Some decisions should remain high

Not every decision belongs near the frontline.

Some choices affect many people, create large or irreversible commitments, or change the organization’s direction.

Keep decisions higher when they involve matters such as:

enterprise strategy and major resource allocation;
legal, safety, or ethical risks beyond the local boundary;
commitments that change the customer promise;
policies affecting several teams or functions;
consequences that the local decision-maker cannot reasonably see or carry.

Even here, information should travel upward from the people close to the work.

Higher authority should not mean lower curiosity.

The executive may make the final decision, but the people who understand the situation should help frame the problem, surface options, and explain likely consequences.

The decision remains high.

The thinking remains connected to reality.

Explain why you are keeping a decision

When you take a decision upward, tell the person why.

Do not simply say, “Leave this with me.”

Explain the boundary:

“This affects the service promise we make to all customers, not only this case. You have handled the local part well, but changing the promise requires a decision at the executive level.”

Or:

“This option creates a legal exposure beyond your authority. Bring me your recommendation and the facts. I will involve legal and make the final call.”

The explanation teaches the person how to recognize the boundary next time.

It also shows that escalation is not a loss of ownership.

The employee can continue gathering information, serving the customer, and carrying the next steps within their role.

Only the decision that requires higher authority moves.

Review decisions without taking them back

A review should strengthen future judgment.

Ask the person to reconstruct the choice.

What was the situation?

What result mattered?

Which options were considered?

What assumption shaped the recommendation?

What happened afterward?

What would the person keep or change?

Resist the temptation to explain immediately what you would have done.

Listen first.

You may discover that the person noticed something you missed. You may also see exactly where the reasoning became weak.

A useful review does not end with, “Next time, ask me first.”

It ends with a clearer principle the person can use when the situation returns.

This is part of Strategic Learning: choose, act, follow what becomes visible, and improve the next move.

The decision has already happened.

Make it teach the organization something.

Move one decision this week

Choose one decision that returns to you regularly.

Write down who handles the situation now, who makes the final choice, and why the decision travels upward.

Then ask:

What result must the decision protect?
What information does the person need?
What boundary would make action responsible?
Which risks still require consultation or escalation?
How will you review the first few decisions without taking ownership back?

Explain the new arrangement to the person.

Do not say only, “You can decide this from now on.”

Describe the rule, the limits, and the proof.

Then let the decision move.

The first attempt may reveal gaps. That is useful. Improve the boundary, information, or practice.

You are not trying to prove that the person should have been deciding all along.

You are building the conditions under which the decision can remain where it belongs.

Build a team that brings judgment, not only questions

You do not need people to stop asking for help.

You need them to know what help is required.

Sometimes they need information. Sometimes they need another perspective. Sometimes they need authority only you possess.

And sometimes they already have enough to decide.

A leader who moves decisions does not make people guess. The leader gives them a clear result, a visible boundary, access to information, and room to practise judgment.

Over time, the questions change.

Instead of “What should I do?” you begin hearing:

“Here is what we are protecting. These are the options. This is my recommendation. I need your decision only on this risk.”

That is movement.

The next article, Delegate the Win, will show how to transfer ownership of a meaningful result together with the decisions, support, and proof needed to carry it.

Make Decisions at the Lowest Responsible Level