How does "Push recommendations up, not problems" work?

When people bring problems without solutions, they are implicitly delegating up — pushing the cognitive work back to the manager. Requiring a recommendation trains the analytical and decision-making skills that make genuine autonomy possible. It also reveals how the person thinks, enabling better coaching. The practice works because decision-making skill is developed through doing, not through watching — and "bring me a recommendation" is the smallest viable doing.

How does "Clarify what people can decide without asking" work?

Ambiguity about the boundary of autonomous action forces people to check in for approvals they don’t need, wasting time and signaling distrust. When the fence is clear — "you can commit up to $2,000 / approve schedule changes / respond directly to clients within these parameters" — people can act at full speed within it. Clarity about autonomy is itself a motivator: self-determination theory research consistently finds that perceived autonomy predicts intrinsic motivation and job satisfaction.

Delegation Levels, Made Practical

Q: How does "Name the delegation level explicitly at the start of every task" work?

Most delegation failures happen because manager and report carry different implicit assumptions about who decides and when. Naming the level at assignment time converts ambiguity into a contract. The brain finds uncertainty aversive; clarity about authority removes the background anxiety of "will this be overruled?" and frees the person to focus on the work. This is a simple application of expectation-setting and reduces the coordination failures that come from mismatched mental models.

Q: How does "Match the delegation level to the person’s current competence and confidence" work?

Appropriate challenge is the engine of development — the concept of "flow" and related research suggest that growth happens when challenge slightly exceeds current skill, not when it vastly exceeds or falls short. In delegation, giving a novice a Level 5 (full autonomy) task without support produces failure and erodes self-efficacy; giving an expert a Level 1 (wait for instructions) task is infantilizing and reduces intrinsic motivation. The right level is a moving target as the person develops.

Q: How does "Resist reverse delegation (the "monkey back" problem)" work?

William Oncken and Donald Wass described "management time" being captured by reports who escalate responsibility back to the manager. When a manager accepts a task that was delegated, they model that upward escalation works and incentivize it. The manager becomes the bottleneck; the report becomes a supplicant. Resisting this requires a specific conversational move: returning the next action explicitly to the person who brought it.

Q: How does "Debrief after delegated tasks to build for the next level" work?

Delegation without reflection is just task assignment. The debrief is where capability transfer happens: you share what you saw, the person shares what they experienced, and together you identify what would make the next task require less oversight. This works because expertise is tacit — much of what an experienced manager knows is not explicit until someone asks the right question after a real task.

How do you delegate effectively without micromanaging or abdicating?

Delegation levels frameworks (most commonly a 5- or 7-level scale) give managers and their reports a shared vocabulary for how much authority is being handed over on any task — from "wait for my instructions" to "decide and act without telling me." The model is practitioner wisdom rather than formally studied, but the underlying principle — that ambiguity about authority is the root of both micromanagement and abdication — has solid organizational support.

Most delegation problems are not laziness or incompetence — they are ambiguity problems. The manager thought they were empowering; the report thought they were supposed to check back. Delegation levels frameworks (popularized by management writers including Jan Carlzon, L. David Marquet, and various management texts) solve this by naming, explicitly, how much authority is being handed over for each task. Below are the core practices, with honest notes on where the evidence is strong and where it is principled field experience.

Practices

Name the delegation level explicitly at the start of every task

State clearly whether you want a recommendation, a decision with notification, or a decision without notification — before the work begins.

Match the delegation level to the person’s current competence and confidence

Over-delegate to someone who isn’t ready and they fail; under-delegate and they stagnate.

Push recommendations up, not problems

Require reports to bring a recommendation alongside any problem — it’s a delegation practice, not just a time-saver.

Clarify what people can decide without asking

Define the fence: what decisions can anyone on the team make without checking in?

Resist reverse delegation (the "monkey back" problem)

When a report brings you their monkey, don’t take it — send it back with the next step owned.

Debrief after delegated tasks to build for the next level

A delegation debrief is not a performance review — it is a joint analysis of what you both learned.

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Practice this with IX Coach

IX Coach: 7 days free, then $40/month (about $1.30/day).

Delegation Levels, Made Practical

Practices

Name the delegation level explicitly at the start of every task

Match the delegation level to the person’s current competence and confidence

Push recommendations up, not problems

Clarify what people can decide without asking

Resist reverse delegation (the "monkey back" problem)

Debrief after delegated tasks to build for the next level

Practice this with IX Coach

Related