Delegation for Senior Leaders: What to Hand Off and What to Keep

For a first-time manager, delegation is mostly about tasks: who drafts the report, who runs the meeting. For a senior leader, it is mostly about decisions. The question shifts from "Who will do this?" to "Who gets to decide this, and within what limits?"

Get that right and the organization moves faster, people grow, and the executive has time for work only they can do. Get it wrong and decisions pile up at the top, or authority gets handed down without the context to use it well.

This guide draws on one of the most fully documented public frameworks for delegating authority, U.S. Army mission command doctrine, along with research on empowering leadership.

Why delegation changes at the top

The Army's command and control doctrine (ADP 6-0, July 7, 2026) puts it plainly: "The higher the echelon, the more time commanders devote to future operations and the broader the guidance provided to subordinates." It adds that delegating decision-making authority "reduces the number of decisions made at the higher echelons and the response time at lower echelons."

The civilian translation: the more senior you are, the more your job is setting direction and conditions, and the less it is making every call yourself. An executive who personally approves every exception becomes a bottleneck, however capable they are.

What to keep

Delegation is not abdication. The doctrine is explicit: "While commanders can delegate authority, they cannot delegate responsibility." It also says commanders "identify decisions that are their sole responsibility and cannot be delegated to subordinates."

Every executive should make that list deliberately. It commonly includes:

• Setting direction, priorities and the intent others will work within.
• Decisions that are hard or impossible to reverse.
• The level of risk the organization will accept.
• Selecting and developing the leaders who report directly to you.
• Standards of conduct, and the response when they are breached.

A useful lens for reversibility comes from Jeff Bezos's 2015 letter to Amazon shareowners, filed with the SEC on April 5, 2016. He described some decisions as "one-way doors," consequential and irreversible or nearly so, which "must be made methodically, carefully, slowly, with great deliberation and consultation." Most decisions, he wrote, are reversible "two-way doors," and those "can and should be made quickly by high judgment individuals or small groups." He warned that growing organizations tend to apply heavyweight processes to most decisions, with results including "slowness, unthoughtful risk aversion, failure to experiment sufficiently."

What to hand off

Good candidates for delegation include:

• Reversible decisions, especially recurring ones.
• Decisions where the best information sits closer to customers, operations or the front line.
• Decisions that would stretch a capable leader on your team.
• Anything you hold onto mainly because you used to do it well.

Delegate intent, not instructions

Mission command relies on commander's intent, defined in the doctrine as "a clear and concise expression of the purpose of an operation and the desired objectives and military end state." It covers the purpose, key tasks and the conditions that define success. The doctrine says intent should be easy to remember and, when possible, delivered in person so people can ask questions.

Intent is paired with mission orders, which "emphasize to subordinates the results to be attained, not how they are to achieve them." The right level of detail depends on the situation; orders should be "neither so detailed that they stifle initiative nor so general that they provide insufficient direction."

A simple civilian version for any significant handoff:

1. Purpose: why this matters and how it connects to the larger goal.
2. Success: what good looks like when it is done.
3. Boundaries: budget, risk tolerance, policies and anything non-negotiable.
4. Authority: whether the person decides, decides and informs you, or recommends for your decision.
5. Resources: the information, people and time they will need.
6. Check-ins: when and how you will review progress together.

The doctrine notes that leaders manage the risk they pass down partly by controlling how many tasks they assign and by providing resources, including "information, forces, materiel, and time." Handing off a decision without the information behind it sets people up to fail.

Calibrate to competence and trust

Authority should grow with demonstrated judgment. The doctrine says commanders "delegate greater authority to subordinates who have demonstrated tactical and technical competency and whose judgment they trust," and that the level of control is continuously assessed and adjusted. It also says leaders build initiative by underwriting good-faith mistakes in training, before the stakes are high.

For executives, that suggests a practical sequence: give a new leader authority over lower-stakes, reversible decisions first, review outcomes together, and widen the scope as their track record builds.

What the research says

Research on "empowering leadership," which includes sharing authority and encouraging autonomy, is broadly supportive. A meta-analysis by Lee, Willis and Tian in the Journal of Organizational Behavior, drawing on 105 samples, found positive effects on performance, organizational citizenship behavior and creativity at both the individual and team levels. Trust in the leader and psychological empowerment helped explain those effects.

Self-determination theory, developed by Edward Deci and Richard Ryan, offers one explanation: conditions that support people's experience of autonomy, competence and relatedness are argued to foster the highest-quality forms of motivation.

There are limits. In a 2015 review in Group and Organization Management, Sharma and Kirkman called for more research into the less positive and unintended effects of empowering leadership, including a possible "too-much-of-a-good-thing" effect. In practice, authority without clarity or support can feel more like a burden than a vote of confidence.

Common failure modes

• Reverse delegation. The problem comes back to you as "What should I do?" Ask for a recommendation instead.
• Snapback. You delegate, get anxious and take it back. Agree on check-ins up front so you do not need to hover.
• Dumping. Handing off work without the authority, information or time to do it.
• Silent overrides. Reversing a delegated decision without explanation teaches people not to decide.

For example, imagine the chief operating officer of a 300-person distributor who personally approves every pricing exception. She hands authority for exceptions below a set margin threshold to regional managers, explains the purpose (keep key accounts without eroding margin), asks for a weekly summary and keeps larger exceptions for herself. Approvals speed up, and the summaries show her which managers are ready for more.

Key takeaways

• At senior levels, delegation is mainly about decision rights, not tasks.
• You can delegate authority but not responsibility; decide in advance which calls stay with you.
• Push reversible, recurring and information-heavy decisions down; keep irreversible, high-stakes ones close.
• Hand off intent (purpose, success, boundaries, authority and resources) rather than step-by-step instructions.
• Expand authority as people demonstrate judgment, and agree on check-ins instead of hovering.

Sources

• Headquarters, Department of the Army, ADP 6-0 Command and Control (July 7, 2026)
• Amazon.com, Inc., 2015 Letter to Shareowners, Exhibit 99.1 to Form 8-K (April 5, 2016)
• Lee, Willis and Tian, Empowering Leadership: A Meta-Analytic Examination of Incremental Contribution, Mediation, and Moderation, Journal of Organizational Behavior (2017)
• Sharma and Kirkman, Leveraging Leaders, Group and Organization Management (2015)
• Center for Self-Determination Theory, Theory