Why Do You Keep Taking Back Decisions You Agreed to Delegate?

Which requests actually require your authority?

Start with the last several requests you answered, rather than a general description of your role. For each one, ask what would have happened if a qualified director had made the decision without contacting you. The answer may reveal a contractual restriction, a commitment outside their authority, or a risk the organization intentionally reserves for you. Those requests need a dependable route to your attention.

Others may reveal an unwritten preference. Perhaps you like seeing client communications before they leave. Perhaps a director expects criticism if their wording differs from yours. Perhaps no one remembers why approval was introduced. Treat these as questions to resolve, not evidence that the team lacks judgment.

Keep information requests separate. Being told a client meeting moved does not require approval. Being asked whether to accept a new commercial obligation might. When both arrive in the same channel with the same urgency, you have to perform the sorting yourself. A useful first change is asking the sender to name the decision, its owner, and when an answer is necessary.

Faster preparation can leave the decision problem untouched

A team member can now turn meeting notes into a polished recommendation before lunch. That may be useful. It also makes it easier to propose another initiative, produce several alternatives, or ask a senior person to inspect work that previously stayed with its owner. If every prepared option becomes a request for your judgment, a faster preparation process can feed the same crowded decision queue.

UC Berkeley researchers described expanding work scope and fewer pauses in an eight-month ethnographic study at one technology company. That finding offers a pattern to inspect locally, not a prediction that AI will overwhelm every executive.

Look for the change in your own records. Are more requests arriving? Are they better specified? Do they concern genuinely new obligations, or more versions of the same decision? A short, well-written recommendation can still omit the information needed to choose. Its apparent completeness should not pressure you to decide before the relevant owner has resolved the uncertainty.

Read the approval queue as a record of organizational habits

Take one ordinary day and reconstruct the requests that reached you. Record the sender, the decision requested, and whether you were the only authorized person who could make it. Include the small interruptions you answered in chat. A queue made entirely from formal approval software will miss the director who asks for a quick view and then treats your reply as authorization.

Notice repeated routes. One capable colleague may send every ambiguous situation upward. Another may ask only after you have unexpectedly reversed their previous decisions. Those are different problems. The first may need a clearer account of their authority. The second may need you to stop changing the agreement after the work is complete.

Also inspect your own invitations. When you say to keep you posted, do people understand that as information or permission to proceed? When you request another version, do you explain what remains unresolved? An executive's casual comment can create substantial work. The audit becomes more useful when it includes what your replies teach people to send next time.

Keep accountability with a person who has actually accepted it

Removing your name from an approval field does not transfer responsibility by itself. The receiving owner needs to understand the outcome they may authorize, the limits that apply, and which other obligations remain with someone else. They also need enough time and information to make the decision. A change that merely moves the queue to an already overloaded director has not resolved the problem.

Discuss a specific category together. For example, a managing partner might agree that an engagement director can approve ordinary presentation edits within the signed scope. Changes to contractual commitments follow the existing commercial review. The exact division depends on the firm. Do not borrow a percentage rule and assume it determines which consequences are acceptable.

NIST's voluntary AI Risk Management Framework provides a useful reference for explicit organizational responsibilities. It does not authorize a particular delegation. Your firm's accountable owners still decide what can move and which controls remain necessary. Document their agreement in the place people use to perform the work.

Ask for the smallest brief that makes the decision possible

An approval request should help you understand why a decision is yours. That does not mean every routine request needs a lengthy template. Ask for the choice, the sender's recommendation, the relevant consequence, and the unanswered question. If the sender cannot name what you must decide, a conversation about ownership may be more useful than another rewritten summary.

For a consequential proposal, ask what could make the recommendation wrong. A generated brief may present competing options elegantly while omitting an obligation known to the team. The responsible person should be able to explain the reasoning and point to the permitted underlying records. Avoid turning this into a demand for an exhaustive research pack whenever someone needs your attention.

Watch for briefs that disguise decisions already made. A request arriving after the client has been promised delivery leaves you choosing whether to absorb the consequence. Address that earlier commitment with its owner. Faster reading will not correct a process in which approval is sought only after everyone assumes it has been granted.

What makes you take the work back?

A director sends an acceptable draft. You can improve it in a few minutes, so you do. Next time, they send the draft earlier. Soon you are finishing the work they were meant to own. Each individual intervention seems reasonable, but the accumulated lesson is that important work becomes yours at the end.

Before intervening, name the actual problem. Did the draft violate an agreed standard? Did new information change the risk? Or would you simply have done it differently? Preference can be worth discussing. It does not automatically justify taking ownership away from someone who met the agreement.

You may also be protecting an identity. Being the person who knows the answer can feel more comfortable than allowing a capable colleague to make a visible decision. That is a possibility to investigate, not a diagnosis. Look at a real incident and what you feared would happen if you stayed out. The useful question concerns your behavior, especially when the organizational authority is already clear.

A hypothetical managing partner who approves every client revision

Consider a U.S. professional-services firm where a managing partner reviews every change to a client presentation. Engagement directors know their clients, but a previous complaint led to an informal rule that nothing leaves without the partner seeing it. The rule now applies equally to routine wording changes and statements with material commercial consequences.

The partner and directors review several recent requests together. They discover that some require specialist review, some fall within existing director authority, and some involve a client promise no one has clearly assigned. They retain the specialist route, confirm the routine boundary, and resolve the unassigned promise before allowing it to proceed. They do not remove review simply because a slide was drafted with AI.

The partner then faces the difficult part: leaving an authorized edit with its owner. If a director's version meets the agreed standard, the partner lets it leave even when the wording is not their favorite. A later review examines actual errors and justified exceptions. This is an illustration of a possible agreement, not a reported client result or a claim that a firm should use this exact policy.

Make room for consequential decisions without pretending interruptions vanish

Some decisions genuinely need you while you are considering something else. A practical attention policy includes that reality. Give colleagues a defined route for a real exception, with enough context to explain why the decision cannot wait. Keep ordinary requests in an agreed queue that someone actually reviews.

When an interruption must happen, leave yourself a short note about the question you were considering and the next step. Research by Sophie Leroy and Theresa Glomb found that a brief plan for returning to an interrupted task could reduce attention residue under the studied conditions. It does not establish a universal executive routine.

Your local test is simpler: can you return to the actual decision, or do you spend the rest of the block reacting? Keep the note short enough to use. If the same nonurgent category repeatedly consumes the block, repair its route with the owner. Do not treat every broken focus period as a personal failure of concentration.

Review the boundary using consequences, not the quietness of your inbox

A quieter inbox can conceal problems if people stop raising issues they should report. After trying a narrower approval boundary, ask the affected owners what became easier and what became unclear. Examine decisions delayed by missing authority, errors that crossed the agreed standard, and questions that should have reached you sooner.

Include the work required to maintain the change. If a director now spends hours documenting minor choices to defend their authority, the agreement may be creating a different burden. Reduce unnecessary documentation while retaining the records needed for consequential decisions. The aim is a workable relationship between responsibility and attention.

Finally, look for your own reversals. Did you override an authorized choice without new information? Did you answer a routine question directly and then criticize the sender for bypassing the owner? Those moments matter because colleagues adapt to what you actually reward. Use a specific example to repair the agreement. A clear policy will remain fragile if your daily responses teach the opposite behavior.

Bring a repeated behavior to reflection, not an impossible productivity target

You may already understand delegation and still take the work back. In that case, another framework might give you more language without changing the next interruption. Bring a de-identified example: the request, the authority already agreed, what you did, and the consequence you were trying to prevent. That makes the question about something you can inspect.

The SoulSearching Experience is a five-day retreat in Peru's Sacred Valley for 8–15 participants, without plant medicine. For a leader with this recurring pattern, it can be an occasion to investigate their contribution and identify the first actions to test after returning. It does not decide the firm's governance or promise that a crowded calendar will disappear.

Prepare responsible coverage before leaving. The professional work of assigning authority still belongs with the organization. The personal work is noticing why, when that authority is clear, you keep putting yourself back into decisions you intended to leave with someone else.

Bring the practical question back to your own response

What does taking it back give you in that moment?

Choose the most recent moment this happened. Write what was actually said or requested, what you concluded it meant and the next action you took. Keep those parts distinct. You may discover a real practical gap, a response that repeats in several settings, or both. The observation is a starting point, not a diagnosis.

Choose one appropriate decision you have genuinely delegated. Notice your response before reopening it.

Ask what your usual action provides immediately and what it displaces afterward. Being available may give you contact; intervening may restore familiar influence; another explanation may postpone a difficult conversation. These are possibilities to examine against your own experience. They should not be imposed as the reason you act.

Choose a response you can try in an appropriate, ordinary situation. Respect actual company duties, your household’s agreements and other people’s boundaries. If specialist advice or a formal arrangement is needed, obtain it through the right route. Personal insight cannot supply missing authority or decide another person’s obligations.

At the AI and the Andes Retreat, this personal question is the work to bring. Florian facilitates and offers useful guidance while you investigate what fits your circumstances. You participate in finding your answer and choosing an action for home. The group is not a corporate advisory team, and the experience does not guarantee a business, career or relationship outcome.

Write what you will observe after returning: the moment that usually begins the pattern, the action you choose and the consequence. Review whether you tried the response and what it revealed. Support and accountability continue afterward; ask about current details. Progress need not take the form of an impressive announcement.

How do you face the colleague whose decision you took back?

The reversal already happened. The director watched you reopen a decision they owned. They may now be unsure what they are allowed to decide. Begin with that specific event and ask how they experienced it.

Do it soon and do it specifically. Name the actual event: you rewrote the client reply on Tuesday after agreeing that the director sends it. State that the boundary still stands. If your intervention corrected a real breach of the agreement, say which condition was missed and route it properly next time. If the decision met the standard and you simply preferred different wording, say that plainly. Ask whether the colleague understood the agreement in the same way. Acknowledge any extra work your reversal created.

Then ask what the reversal cost. Did they redo work, delay a commitment, or learn to send you drafts earlier as insurance? Their answer is more useful than your self-criticism, because it tells you what to repair.

Notice what you do when a similar decision comes up again. When the following request arrives, let the authorized owner decide, including when the result is not your favorite. If you catch yourself rehearsing reasons to intervene again, that is the material to examine. That gives you a specific instance to examine alongside what you said in the repair conversation.

When the same reversal pattern continues after a formal handover to a successor, read why you still take decisions back after choosing a successor to extend the repair work.

If you also rejoin meetings you agreed to leave, the parallel pattern is examined in why missing an executive meeting feels harder than it should.