Delegating with Context

Delegation is not just "giving orders." It's about empowering your team to make decisions. To do this, you must provide Context.

The Why-What-How Framework

1. The Why (Context): "We need to reduce our server costs because we are over budget for Q3."
2. The What (Goal): "I'd like you to identify the top 3 most expensive queries in our database."
3. The How (Autonomy): "I'll leave it to you to decide which tools to use for the analysis."

Setting Success Criteria

Don't just say "Do a good job." Say what "Good" looks like:

• "Success for this project looks like a 10% reduction in latency."
• "I'll consider this done when the documentation is merged and the team has been notified."

Checking In (Not Checking Up)

• Micromanagement: "Did you finish line 42 of the code yet? Send me a screenshot."
• Supportive Management: "How's the query analysis going? Do you need any extra resources from the DevOps team?"

Alex's Tip: Use the phrase "I'm delegating the outcome, not the task." This signals to the employee that you trust their expertise to find the best way to get the result.

Notice own the outcome. This signals that the person is accountable for the result, not just the activity.

Confirming understanding

After delegating, always confirm understanding, but in a way that invites real questions:

• What questions do you have about this?
• What support do you need?
• Let's recap: you'll... by...

Avoid Does that make sense? It pressures the person to say yes, even if they are confused. What questions do you have? assumes there may be questions and makes asking them normal.

Giving ownership, not tasks

The mindset shift: delegate outcomes, not tasks.

• Task delegation: Write three emails, post on LinkedIn, update the sheet. (tells them exactly what to do)
• Outcome delegation: Grow our waitlist to 500 signups by the end of the month. You decide the best approach; I'm here to help. (tells them the goal)

Outcome delegation develops the person because they must think strategically. Task delegation turns them into an order-taker.

Setting checkpoints

For larger delegations, set checkpoints so you can course-correct without micromanaging:

• Let's check in on Wednesday to see how it's going.
• Ping me if you hit a blocker.

Checkpoints let you stay informed without controlling every step.

Common mistakes

1. No context or outcome. Handle the report leaves the person guessing.
2. No deadline. Without a date, the task drifts.
3. Micromanaging after delegating. If you delegate, let them own it; check in, do not control.

Practice

Rewrite this vague delegation using the four-part framework:

Can you sort out the launch?

A clear version:

We're launching the mobile app on the 15th (context). Could you own the launch checklist and comms (task) so that all stakeholders know their part and the app goes live with zero critical bugs (outcome), with a final review on the 14th (deadline)?

In the next lesson, you will learn the language of performance reviews and career conversations.