Back to all articlesManager routines

Remove the Manager as a Bottleneck for Routine Decisions

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A customer response is waiting, a schedule change is unresolved, and a routine purchase needs your approval. None deserves your full attention, but each stays blocked until you reply. Meanwhile, the coaching conversation and the consequential exception keep slipping.

To stop being a management bottleneck, audit the decisions actually waiting for you, separate required authority from habitual approval, and give named people the right to make bounded choices. Replace permission requests with clear context, exception triggers, and review after the decision where appropriate. Keep decisions with you when their consequences, competing commitments, or formal authority cannot be transferred.

The goal is not fewer questions at any cost. It is a queue in which routine choices move without you and genuinely consequential decisions reach you with enough context to act.

1. Audit the queue, not your impression of it

Start with real requests rather than asking everyone what they think you should delegate. Review a representative stretch of messages, meeting notes, and unfinished work. Include decisions people are holding back because they assume you are too busy to ask.

For each queued item, capture:

  • The actual choice: What must someone decide, rather than merely complete?
  • The current owner: Who understands the work and could make the choice?
  • The reason for approval: Required authority, missing information, conflicting priorities, uncertain judgment, or habit?
  • The waiting cost: What is stalled while the decision remains open?
  • The consequence of error: Can the choice be reversed, and who else would bear the cost?

Keep time spent deciding separate from time spent waiting. A choice that takes you a moment can still hold up another person's work for much longer. Also record repeated clarification: if every request arrives incomplete, delegation alone will not fix the queue.

Ask a useful diagnostic question: If I were unavailable, what exactly would prevent this person from deciding? An answer such as “they do not know the spending allowance” points to missing context. “Only this role can commit the organisation” points to an authority boundary.

2. Distinguish authority from dependence

Approval requests often look alike but need different remedies. Sort each one before deciding what to hand over.

  • Necessary authority: The decision requires a role, mandate, or commitment the employee does not hold. Retain it or route it to the actual authority.
  • Missing context: The employee lacks current priorities, capacity information, agreed terms, or a relevant budget. Supply that context before transferring the choice.
  • Developing judgment: The person understands the facts but needs practice weighing trade-offs. Start with a recommendation and discussion, then widen discretion as their reasoning becomes dependable.
  • Habitual dependence: The employee can decide, but approval has become the safest social option. Explicitly remove the approval step and support reasonable choices afterward.

Do not mistake a manager's preference for necessary authority. Wanting a message phrased your way is different from needing to approve a new customer commitment.

Equally, do not treat every dependency as a confidence problem. Someone who cannot see workload across teams may be right to escalate a scheduling choice. Either provide that visibility or retain the cross-team trade-off. Telling them to “take ownership” without resolving the information gap simply transfers the blame.

3. Use a filled manager-dependency audit

Fictional worked example: The following audit describes an invented service team. All roles, amounts, time periods, and situations are hypothetical, not customer results or recommended universal limits. The manager wants to free attention for coaching and unusual customer commitments.

Queued decision: move a routine customer appointment

  • Current queue and owner: The coordinator is waiting to move tomorrow's appointment to an available slot.
  • Reason for approval: Habit; the manager has historically confirmed every change.
  • Proposed delegation boundary: The coordinator may move an appointment within the customer's agreed service period when the customer accepts, capacity is available, and no other confirmed appointment must move.
  • Required context: Current staffing, confirmed appointments, customer availability, and any promised completion date.
  • Review trigger: Escalate before committing if the change breaks a promise, needs overtime, or displaces another customer. Review routine moves together at the end of the week.

Queued decision: offer a small service-recovery credit

  • Current queue and owner: A support lead is waiting to resolve a documented service failure.
  • Reason for approval: Financial discretion has never been stated clearly.
  • Proposed delegation boundary: The lead may offer up to a hypothetical £50 credit for an established service failure, within an existing authorised allowance. No repeated credits for the same incident and no new future-service commitments.
  • Required context: Incident history, previous remedies, the existing allowance, and the standard recovery options.
  • Review trigger: Escalate requests above the boundary, disputed facts, or repeat incidents. Review the rationale and total credits weekly, not just each individual amount.

Queued decision: purchase a replacement headset

  • Current queue and owner: An operations coordinator needs to replace a failed headset.
  • Reason for approval: An old practice requires approval for every purchase.
  • Proposed delegation boundary: Choose a standard replacement up to a hypothetical £80, within the existing equipment allowance, without adding a subscription or changing supplier terms. This assumes the organisation permits the manager to delegate that choice.
  • Required context: Available stock, standard equipment choices, remaining allowance, and the purchasing process.
  • Review trigger: Escalate a nonstandard requirement, exhausted allowance, or new contractual commitment. Include completed purchases in the regular spending review.

Queued decision: exchange two employees' shifts

  • Current queue and owner: The team lead is waiting to confirm a mutually requested swap.
  • Reason for approval: Concern about service coverage.
  • Proposed delegation boundary: Confirm only where both employees agree, required coverage and skills remain intact, and the change fits established scheduling rules without additional cost.
  • Required context: Coverage needs, relevant skills, existing commitments, and scheduling rules.
  • Review trigger: Escalate any coverage gap, disputed swap, additional cost, or uncertainty about an applicable rule. Check for repeated undesirable coverage patterns during roster review.

Queued decision: promise an accelerated customer deadline

  • Current queue and owner: An account lead wants to promise an earlier completion date.
  • Reason for approval: The promise would consume another team's capacity and could displace existing commitments.
  • Proposed delegation boundary: Retain the commitment decision with the manager or designated cross-team authority. Delegate preparation of feasible options, not the promise itself.
  • Required context: Capacity estimates, affected commitments, customer need, and the cost of each option.
  • Review trigger: Seek a decision before making any external commitment. Reconsider delegation only if a genuine capacity allowance and appropriate authority are established.

Queued decision: resolve a formal performance issue

  • Current queue and owner: A team lead asks what action to take following a recurring performance concern.
  • Reason for approval: The next step may require designated managerial authority and an established organisational process.
  • Proposed delegation boundary: Retain the formal decision with the appropriate manager. The lead may assemble factual observations and continue ordinary support within their role, without promising an outcome.
  • Required context: Prior expectations, documented observations, support already offered, and the organisation's relevant process.
  • Review trigger: Route the issue promptly to the responsible manager; do not fold it into a routine delegated-decision sample.

4. Turn each boundary into a usable decision agreement

An audit identifies opportunities. A decision agreement makes them usable. For each delegated category, state the owner, permitted choice, constraints, information needed, escalation conditions, and review point. Name one accountable decision-maker even when several people contribute.

In the fictional appointment example, the agreement could read:

You own routine appointment moves. You may confirm a move when the customer accepts, the agreed service period is preserved, and the slot has capacity without displacing another appointment. Record the reason and the new commitment. If any condition is unclear or unmet, bring the options to me before promising a change. We will review completed moves at the end of the week; you do not need advance approval for moves inside these boundaries.

Specify whether consultation is advice or consent. “Check with the team lead” is ambiguous: does the lead supply capacity information, offer a view, or have to agree? Ambiguity can create a replacement bottleneck.

Also define what happens when the manager is unavailable. Name an appropriate alternate for exceptions and a safe interim action, such as holding the current commitment while gathering options. Silence must not become implied approval.

5. Keep consequential decisions where the authority belongs

Some work should stay with the manager even when the queue is inconvenient. Retain or route decisions that exceed the team's mandate, create substantial commitments, resolve competing priorities across teams, or carry consequences the proposed owner cannot reasonably assess or contain.

Ask three questions before transferring a decision:

  1. Can I delegate this authority? Being asked for approval does not prove you have the right to pass that approval onward.
  2. Can the owner see the consequences? A locally sensible choice may move cost or disruption onto another team.
  3. Can the downside be contained? Consider reversibility, cumulative effects, and the effort required to repair a mistake.

Retention need not mean doing all the work yourself. Ask the employee to prepare the decision: explain the issue, recommend an option, identify affected commitments, and state when an answer is needed. The manager keeps the consequential judgment without becoming the researcher, coordinator, and messenger for every case.

6. Review judgment without rebuilding the approval queue

Review after action is what makes bounded delegation different from unrestricted discretion. But reviewing every choice before it takes effect simply renames approval.

Use the risk of the decision to choose the review method. Routine, reversible choices can be sampled afterward. Developing judgment may justify a temporary recommendation-first approach. Decisions outside the boundary still need advance escalation.

During review, ask what the person knew, which constraint mattered, what alternatives they considered, and what happened. Separate an undesirable result from a poor decision. A reasonable choice can produce a disappointing result; a weak choice can succeed by luck.

Watch cumulative effects too. Individually acceptable credits, schedule changes, or purchases can collectively strain an allowance or create unfairness. Include aggregate patterns in review rather than relying only on per-decision limits.

When a choice was within the agreement, do not override it merely because you prefer another style. Explain useful alternatives as coaching, not as a hidden new approval requirement.

7. Repair failures without taking everything back

If a delegated decision goes wrong, contain the immediate consequence first. Then diagnose the failure before changing the arrangement.

  • Missing context: Make the necessary information available and clarify who keeps it current.
  • Unclear boundary: Rewrite the specific condition that allowed conflicting interpretations.
  • Judgment gap: Temporarily narrow that category and practise comparing options together.
  • Boundary ignored: Address the conduct directly rather than adding approval steps for everyone.
  • Unexpected consequence: Add a relevant trigger or aggregate review if the original design missed a real risk.

A pause may be appropriate, but make it specific. State which decision category is paused, who owns it meanwhile, and what evidence will support restoring discretion. Taking back all decisions after one mistake teaches the team that ownership is temporary and asking permission is safer.

Check manager behaviour as well. If you repeatedly reopen sound decisions, reward unnecessary checking, or respond faster to permission requests than to thoughtful recommendations, dependence may be a rational response to your signals.

8. Run a bounded pilot and measure the queue

Start with a small set of frequent, reversible decisions rather than a department-wide announcement. A suggested pilot is to audit one working week, agree boundaries for selected categories, and review the arrangement after the following fortnight. Adjust the timing to the volume and consequences of the work.

Compare the pilot with the starting queue using a few observable measures:

  • Waiting: How long do routine choices sit unresolved?
  • Dependence: How many within-boundary decisions still reach the manager for permission?
  • Decision quality: Which choices require correction, and why?
  • Escalation quality: Do genuine exceptions arrive before commitments are made, with usable options?
  • Manager attention: Does time actually move toward coaching and consequential work?

Fewer requests alone is not success: people may have stopped raising important issues. Look for shorter routine waits alongside timely exceptions and manageable correction work.

Your next action is to take the oldest routine approval in your queue and complete the audit fields for it. If authority can move, write the boundary and name the owner. If it cannot, remove avoidable preparation work from your part of the decision and set a response point. Either way, replace an unexplained wait with a clear decision path.

DelegationManager routinesDecision rightsTeam operations

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications