Does Your Team Know Which Decisions It Can Make?

When leaders ask employees to take more ownership, they usually want them to recognize problems, consider the options, make sound decisions, and follow through.

But do employees know which decisions they can make?

And do they know whether their manager will support them when someone disagrees?

These questions matter most when a customer challenges a charge, requests an exception, or expects a commitment that affects another department’s work.

A Scenario

Consider a project manager whose customer requests additional work outside the original agreement. The customer considers it a small request and expects the company to absorb the cost without changing the deadline.

The project manager reviews the agreement, estimates the additional labor, and checks the schedule. Completing the extra work by the original deadline could delay another customer’s project.

She brings her director two options:

1. Charge for the additional work and revise the completion date.

2. Reduce the additional work to preserve the original deadline.

She also explains the customer’s dissatisfaction and asks how to proceed.

The director offers to call the customer and handle it.

The director wants to protect an important account. An unresolved disagreement could cost the company future business.

Yet the project manager has done the preparation. Before taking over, the director needs to understand what help she actually needs.

Find Out What Is Holding the Employee Back

An employee who brings you a difficult situation may need information, approval, practice, or your support. Until you ask, you may not know which one.

In my Leadership Architecture™ program, participants practice using three coaching questions:

1. What do you recommend?

2. What options have you considered?

3. What support do you need from me?

The project manager has already answered the first two. The third could reveal her real concern.

She may feel comfortable presenting the options but wonder how far she can negotiate. She may also question whether her director will support her if the customer calls to challenge the answer.

If the director later waives the charge without involving her, she must explain why the answer changed. The next time a similar request comes up, she may send it straight to the director.

Before assuming she lacks confidence, find out whether she understands her authority and trusts that you will support it.

Be Specific About Decision Authority

A general instruction to use good judgment leaves employees to interpret what that means. Explain what they can decide, which requirements they must follow, and which decisions need your approval.

In Leadership Architecture™, I call these Decision Guardrails™.

For this project manager, the director can establish straightforward guardrails.

She can offer the additional work at the quoted price with a revised completion date, or discuss reducing the additional work to preserve the original deadline. She must confirm schedule changes with operations before making a commitment.

She cannot waive the additional charge, authorize overtime, or change another customer’s delivery date without the director’s approval.

The director also needs to share information that could affect the decision. For example, the company may have already granted this customer several concessions, or the agreement may require the customer to approve additional work in writing before the team begins.

Leaders sometimes forget how much information they have that employees do not. Give employees the information they need to make sound decisions.

Before ending the discussion, ask the project manager to briefly explain her planned approach. Together, they can identify and resolve any remaining questions.

Establish Escalation Triggers

Employees also need to recognize when a situation requires someone else’s authority.

Without specific guidance, one employee may call as soon as a customer objects.

Another may continue negotiating beyond their authority because they believe you expect them to handle everything themselves.

Agree on escalation triggers: circumstances that require the employee to involve you before proceeding.

In this situation, those triggers might include:

• The customer requests a concession beyond the project manager’s authority.

• A proposed solution would delay another customer’s project.

• The customer threatens to cancel the contract.

• New information raises safety, legal, or contractual concerns.

• The customer threatens or verbally abuses the employee.

Explain what the employee should do when a trigger occurs. If the customer threatens to cancel, the project manager should pause negotiations, avoid making further concessions, agree on a response time, and contact the director.

Escalation does not automatically transfer the entire situation to the leader.

The project manager can still gather information, recommend a response, and follow up with the customer.

The director addresses the decision that requires additional authority.

Practice the Difficult Part

The project manager may understand the options yet still worry about the customer’s reaction.

Spend a few minutes practicing the part that concerns her. Have her respond to pressure to waive the charge, accusations that the company has treated the customer unfairly, or demands for an immediate answer.

Listen for whether she explains the additional work clearly and concisely, acknowledges the customer’s concerns, and presents the available options without promising something she cannot deliver.

Also practice how to pause when a request exceeds her authority. She needs to explain that she must review the request internally and give the customer a realistic response time.

A brief rehearsal can help her stay composed when the pressure increases.

Agree on Your Role Before the Conversation

If the project manager can handle the conversation herself, let her. Agree on an update afterward covering the customer’s response, the commitments she made, and any issues she still needs to resolve.

If she needs the director to join, clarify their roles beforehand. The project manager can explain the additional work and present the options. The director can provide support and address decisions that require approval.

Then give her room to conduct the conversation. A hesitation, an uncomfortable silence, or wording something differently than you would does not necessarily call for intervention.

Sometimes you will need to step in. Explain the reason afterward so the employee understands what to watch for next time.

Support the Authority You Have Given

Suppose the customer bypasses the project manager and calls the director directly.

If the director immediately waives the charge, the customer may learn that going around her produces a different answer. The project manager may also conclude that the director will withdraw her authority whenever a customer challenges her.

The director should explain that they reviewed the options together and include the project manager in any further discussion.

New information may justify a different decision. When it does, involve the project manager and explain what changed. This helps her understand the exception and make better decisions in the future.

Employees need to know that you will support their decisions when they follow the limits you established, including when someone dislikes the answer.

Review the Outcome and the Next Step

Afterward, review what happened. Discuss the customer’s objections, how the project manager responded, whether she stayed within her authority, and whether an escalation trigger occurred.

Identify any information or support she needed but did not have. Then decide what she can handle with less help next time.

Do not evaluate her performance solely by whether she pleased the customer. A customer may continue to object to the additional charge even when she handles the conversation well.

Look at whether she explained the options accurately, listened to concerns, respected the agreed limits, and followed through.

If she handled those responsibilities well, make the next step explicit. For a similar request, she can develop and present the options without reviewing them with the director first, provided she follows the same guardrails and contacts the director when an escalation trigger occurs.

A Leader’s Cheat Sheet

Before taking over a difficult situation, work through these questions:

Could Your Team Handle It Without You?

In Leadership Architecture™, I use the Vacation Test™ to help leaders consider how their teams would perform if they were completely unavailable for two weeks.

For this director, the question is practical: Could the project manager handle the customer’s request, and would the customer recognize her authority?

If the answer is no, identify what she needs.

• More practice?

• Better information?

• Clearer authority limits?

• Does the director need to communicate her authority to the customer?

Choose one situation you regularly take over. Identify what an employee would need to handle more of it, then use the next opportunity to put that preparation into practice.

Before stepping in, ask yourself:

Does this situation require my authority, or does the employee need help using theirs?

Bonita Richter, MBA, is president of Profit Strategies, where she helps organizations develop leaders, strengthen teams, and improve business performance.

Leadership Burnout: Escaping the Indispensability Trap

Many leaders believe burnout is simply the cost of leadership.

The assumption is:

• work harder,

• become more resilient,

• improve time management,

• and eventually things will stabilize.

But in many organizations, burnout is not primarily a stamina problem.

It is a systems design problem.

Over time, capable leaders unintentionally become the center of too many decisions, approvals, escalations, and problem-solving loops. What initially feels like responsibility and leadership effectiveness gradually turns into organizational dependency.

And dependency does not scale well.

How Leaders Accidentally Create Burnout

Most leaders do not become bottlenecks because they are weak leaders.

They become bottlenecks because they are highly capable leaders with good intentions.

• They care deeply.

• They want quality outcomes

• They want visibility.

• They want to help.

So they:

• stay involved,

• approve everything,

• rescue struggling employees,

• refine every deliverable,

• and make themselves available for every escalation.

At first, this behavior is rewarded.

The leader becomes known as:

• responsive,

• reliable,

• knowledgeable,

• and indispensable.

But eventually, the organization begins routing too much through one person.

The result is predictable:

• leader exhaustion,

• slower decision-making,

• reduced team ownership,

• and organizations that struggle to operate independently.

Burnout Often Happens When Responsibility Expands Faster Than Ownership

One of the clearest warning signs of unsustainable leadership is when responsibility grows, but ownership distribution does not.

As organizations become more complex:

• more decisions emerge,

• more coordination is required,

• and more issues need attention.

But instead of distributing ownership, many organizations continue escalating upward.

The leader absorbs:

• more approvals,

• more meetings,

• more visibility requirements,

• more interruptions,

• and more operational involvement.

Eventually, exhaustion becomes inevitable.

Many leaders quietly interpret exhaustion as proof of commitment.

Sometimes it is actually proof the system no longer scales.

The Three Leadership Traps That Create Dependency

Over the years, I’ve observed three common leadership patterns that unintentionally create burnout and organizational dependence.

1. The Tollbooth

This leader becomes the approval gate.

Everything flows through them:

• emails,

• meetings,

• sign-offs,

• decisions,

• and escalations.

The leader believes they are staying informed.

The organization experiences slowed movement and reduced autonomy.

When leaders insist on visibility into everything, teams stop developing judgment.

There is an important distinction between:

• being informed,
  and

• being involved in every transaction.

Healthy leadership systems create structured visibility without constant interruption.

2. The Lifeguard

This leader rescues too quickly.

They solve problems immediately.
They absorb responsibility from others.
They avoid letting people struggle.

Usually, this comes from positive intentions:

• protecting relationships,

• preventing mistakes,

• or helping the team succeed.

But over time, rescuing weakens accountability and reduces independent problem-solving.

Every unnecessary rescue trains future dependency.

One of the simplest coaching questions a leader can ask is:

“What do you recommend?”

That small shift changes ownership dramatically.

3. The Tinkerer

This leader constantly adds value.

• They refine every idea.

• Improve every deliverable

• Insert expertise into every discussion.

Many high-performing leaders unconsciously confuse contribution with leadership.

But leadership at scale eventually shifts from precision to capacity-building.

If leaders always improve everyone else’s work, teams stop fully owning excellence.

Sometimes:

“85% done by your team is better than 100% done by you.”

Because sustainable organizations require distributed capability — not centralized brilliance.

Your Calendar Reveals Your Leadership Model

One of the fastest ways to diagnose leadership sustainability is to examine a calendar.

Does it reflect:

• strategic leadership,
  or

• reactive survival?

Many leaders operate in a constant context-switching:

• excessive meetings,

• endless approvals,

• constant interruptions,

• and “CC culture.”

CC culture develops when organizations rely on leaders for visibility, reassurance, or approval.

Eventually, leaders become information-processing hubs instead of strategic thinkers.

A scalable organization creates visibility through:

• dashboards,

• KPIs,

• escalation thresholds,

• and structured communication rhythms.

Not constant interruption.

As I often tell leaders:

“My goal isn’t less visibility. My goal is higher-quality visibility.”

Sustainable Leadership Requires Redesign

Leadership burnout rarely improves through personal efficiency alone.

At some point, leaders must redesign:

• decision ownership,

• approval structures,

• communication flow,

• meeting culture,

• and escalation habits.

This requires difficult but important reflection:

• What am I still carrying that my team should own?

• What approvals exist simply because “that’s how we’ve always done it”?

• What work continues to depend on me unnecessarily?

The systems that exhaust leaders can also be redesigned by leaders.

The Real Goal of Leadership

The ultimate goal of leadership is not to become indispensable.

It is to build:

• capable teams,

• scalable systems,

• independent thinkers,

• and sustainable organizations.

Strong leadership should increase organizational capability, not dependence.

A powerful reflection question for leaders is this:

“If I stepped away for two weeks, what would stop?”

The answer often reveals whether the organization has built true capability, or simply become dependent on one person.

And perhaps the most important question of all:

Are you building dependence… or capability?