Delegating a task
Hand over work with context, outcome, deadline and check-ins, or turn a vague task into a clear one.
Case study: "Just look into it"
Rahul, a team lead in Hyderabad, told a developer, "Can you look into the slow dashboard?" A week later the developer had rewritten three database queries and was planning a cache layer. Rahul had only wanted a short note on the cause, for a Manchester client call on Monday. Both were frustrated. The next time, Rahul tried a different script: "The client says the dashboard takes ten seconds. I need a one page summary of the top two causes by Friday, so I can talk to them Monday. Don't fix anything yet. Let's check in on Wednesday." The work came back on Thursday, exactly right.
Takeaway: Clear delegation names the why, the what, the when and the check-in. Clear receiving asks for them.
Many of us accept vague tasks without questions so we don't seem slow, and many leads give short instructions assuming people will figure it out. Global teams prefer explicit expectations and welcome clarifying questions up front.
Delegating clearly
Goal: Hand over the task so they know why it matters, what done looks like, when it's due and when you'll check in.
Step by step
- Context. Why this matters and who it's for.
- Outcome. What done looks like, and what's out of scope.
- Deadline. A specific day and time.
- Check-in. One midpoint conversation and an open door.
Say this, not that
| The client says the dashboard takes ten seconds to load, and I'm meeting them on Monday. | Just look into it. | Context helps people make good decisions without you. |
| What I need is a one page summary of the top two causes. Please don't fix anything yet. | Saying what's out of scope prevents wasted work. | |
| Could you have it to me by Friday at noon? | Whenever you get time. | Without a date, the task drifts behind everything else. |
| Let's do a quick check-in on Wednesday. If you get stuck before that, just ping me. | ||
| Can you play it back to me in your own words, so I know I explained it well? | Understood, no? | Most people say yes to 'understood?' even when they're not sure. |
Model conversation
- You
- Nikhil, I've got a task for you. The client says the dashboard takes ten seconds to load, and I'm meeting them on Monday.
- Nikhil
- Okay. Should I start optimizing the queries?
- You
- Not yet. What I need is a one page summary of the top two causes. Please don't fix anything this week.
- Nikhil
- Got it. When do you need it?
- You
- Friday at noon. Let's check in on Wednesday. Can you play it back to me in your own words?
- Nikhil
- Sure. Find the top two causes of the slow dashboard, write a one page summary, no fixes, by Friday noon. Check-in Wednesday.
- You
- Perfect. And if you get stuck before Wednesday, just ping me.
- Nikhil
- Will do. Thanks for the clarity.
Clarifying a vague task
Goal: Turn a vague ask into a clear outcome, deadline and format before you start work.
Step by step
- Say yes to the goal. Show you're willing before you ask questions.
- Ask the why. Who is it for, and what decision does it support?
- Define done. Format, depth, and what's out of scope.
- Confirm in writing. Send a two line summary of what you agreed.
Say this, not that
| Happy to take it. Can I ask a few quick questions so I get it right? | Okay, will do. | Saying yes without questions often means doing the wrong thing well. |
| Who is this for, and what will they decide based on it? | ||
| What does good look like? A one pager, a slide, or a working prototype? | Format questions save days of rework. | |
| When do you need it, and is there a version you'd want to see earlier? | I will try to finish soon. | An early draft catches wrong turns cheaply. |
| Let me send you a quick summary of what we agreed, just to be sure. |
Model conversation
- Emma
- Hey, could you look into what it would take to add offline mode to the app?
- You
- Happy to take it, Emma. Can I ask a few quick questions so I get it right?
- Emma
- Of course.
- You
- Who is this for, and what will they decide based on it?
- Emma
- It's for the leadership review. They'll decide whether to fund it next quarter.
- You
- Got it. So you need an estimate and the main risks, not a prototype? And when's the review?
- Emma
- Exactly. Two pages max. The review is on the twentieth, so the eighteenth would be ideal.
- You
- Great. I'll send you a draft outline on Monday, and the final by the eighteenth. I'll put that in an email now.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.