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.

Why it works

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.

How to do it

1. For each task you delegate, choose a level: "Bring me options," "Decide and tell me before you act," "Decide and act then brief me," or "Handle it — I don’t need to know unless something breaks."
2. State the level out loud or in writing when you assign the task — not just in your own head.
3. Ask the person to restate the level back to you to confirm the same contract.
4. Review the level if circumstances change mid-task.

Evidence

Role clarity — knowing what decisions you own — is one of the more consistently supported predictors of individual performance and job satisfaction in organizational research. (observational)

The delegation levels model itself is a practitioner framework; the benefit attributed to it comes from reducing role ambiguity, which is the better-studied construct.

Sources

• Rizzo, House & Lirtzman (1970), Role Conflict and Ambiguity in Complex Organizations, Administrative Science Quarterly

Common mistake

Assuming the level is obvious from context — the manager says "handle it" meaning Level 4 while the report hears Level 1 and waits for further instructions.