Delegation: The Handover Protocol (The 5 Steps)

Delegation is never random; it is a structured communication process. If this protocol is not followed, the risk of error increases with every step omitted. If you skip a step, you leave a door open for the “monkey” to jump back onto your shoulder.

Step 1: Context (The “Why”)

Don’t start with instructions. Start with the big picture. The employee must understand how their piece integrates into the company’s main engine.

• Goal: Alignment with company objectives. If they know the context, the person can make correct decisions when unforeseen situations arise, without calling you.
• Wrong: “Make this Q1 sales report for me.”
  • Result: The employee executes mechanically, without checking data quality, because they don’t understand the stakes.
• Correct: “We are preparing next semester’s strategy, and we need a Q1 analysis to see where we lost corporate clients.”
  • Result: Alignment to the objective. The employee knows what to look for but doesn’t feel personal responsibility for the project’s success.

Step 2: Expected Result – DoD (The “What”)

Describe the final product, not the process to get there. The employee must know exactly what success looks like, leaving no room for interpretation. Definition of Done (DoD) borrows the DNA of the SMART concept (Specific, Measurable, Achievable, Relevant, Time-bound).

• Goal: Elimination of ambiguity. When “Done” is clearly defined, it eliminates the manager’s frustration at receiving something else and the employee’s frustration at having their work rejected.
• Wrong: “I want a good analysis about the clients who left.” (What does “good” mean? 2 pages? An Excel sheet? A PPT presentation?)
• Correct: “I want a 2-page document with top 5 reasons for churn and retention proposals, ready by Friday at 2:00 PM.”

Step 3: Resources and Limits – DoA (The “With what?”)

Delegation is not just the transfer of a task, but also the transfer of the right to use company assets: Financial Assets (Cash/Credit: Budget and signing limits), Logistical Assets (Infrastructure: Access to what the company already “owns”), and Authority Assets (Social Capital: The right to use others’ time and priority). You state exactly what “wallet” they have and what visas they need to obtain.

• Goal: Resource protection and avoiding system overload. The employee must know what “tools” they have and how to check their availability without conflicting with other projects.
• Correct: “You have access to database X. If you need additional data from IT that costs money, you have a budget of €500. Above this amount, you come to me.”
• Golden Rule: Never delegate a task without also delegating the necessary Authority over Resources (DoA – Delegation of Authority).

Step 4: Level of Authority – 7 Levels (The “How much freedom?”)

Define the degree of autonomy.

• Goal: Micro-management prevention. Both parties know exactly where one’s thinking ends and the other’s begins.
• Mechanism: For Step 4 to work, the Scale of Authority (1-7) must be understood by everyone. It’s best if the manager provides the necessary clarification: “For this task, you are at Level 5 (Advise). This means, according to our protocol, that you decide and implement, but you inform me before the final action, so I have veto power if I see a major risk you might have missed.”

Step 5: Confirmation and Checkpoint (The “Control”)

• Goal: Alignment verification (Skill & Will). If the rephrasing is correct, delegation has occurred. If not, the correction is made now, before time and money are wasted.
• Mistake: Never ask “Do you understand?”. It is the most useless question in management.
• Correct Technique (Cognitive Mirroring): “Just to make sure I haven’t missed anything important, let’s quickly recap, in your own words, how you see the deliverable and what the first steps are. Then, let’s establish when we’ll meet for a brief progress check.”

Writing takes the sweat, sharing takes a click. Don't tell me you're lazy!