Delegation and Mentoring: Growing Others as a New Lead
Soft SkillsLesson 4 of 45 min read
What you'll learn
- Decide which work to delegate and which to keep
- Write a delegation brief with outcome, constraints and a deadline
- Set up check-ins that support people without micromanaging them
- Run a first 1:1 using a ready-to-use agenda
On this page
The hardest part of becoming a lead is that the skill that got you promoted, doing excellent work yourself, stops being the main job. Your output is now what your team produces, and that depends on how well you hand work over and help people grow.
Why delegation and mentoring matter
New leads often fall into one of two traps. One is doing everything themselves because it is faster and they know it will be done right. The other is dropping work on people with a one-line message and hoping. The first burns you out and stops others growing; the second produces rework and frustration. Good delegation sits in between: clear about the result, flexible about the method.
What to delegate, and what to keep
A useful starting point is to delegate work that someone else can do at 80 percent of your quality if it helps them grow and frees you for work only you can do. Keep work that needs your authority or is genuinely sensitive.
| Good to delegate | Usually keep |
|---|---|
| Well-defined tasks a teammate can learn from, such as a feature slice or a report refresh | Performance conversations and hiring decisions |
| Recurring work you do out of habit | Decisions that need your authority or a stakeholder relationship |
| Stretch tasks slightly above someone's current level, with support | Genuine emergencies where speed matters more than learning |
| Work that someone else is closer to, like the person who knows the customer | Confidential matters |
Write a clear brief
Most delegation failures are brief failures. A good brief makes the outcome, the constraints and the deadline explicit, and leaves the how to the person. It should take five minutes to write and save hours of misunderstanding.
Task: [one line]
Outcome: What does done look like? How will we know it worked?
Why it matters: Who uses it and what depends on it?
Constraints: Must / must not (budget, tools, security, existing conventions)
Decision rights: What you can decide yourself; what to check with me first
Deadline: Final date, plus an earlier checkpoint
Resources: Links, people to ask, examples of good work
Check-in: When we'll look at it together"Aisha, I'd like you to own the weekly churn report from now on. The outcome is that the sales leads get one page every Monday by 10am that shows churn by plan, with a note on anything unusual. Constraints: use the existing warehouse query, and don't change the definition of churn without asking me. You can decide the layout. Let's look at a first draft together on Thursday so you can ask questions early. I'm happy to help with the query logic, and Rohan built the original, so ask him if you get stuck."Check-ins without micromanaging
The right amount of supervision depends on the person's experience with that particular task, not their seniority. Someone new to a task needs more frequent check-ins; someone who has done it five times needs very few. Agree on the rhythm up front so a check-in is a planned conversation instead of surveillance.
- Set one early checkpoint, when 20 to 30 percent of the work is done, to catch misunderstandings while they are cheap to fix.
- Ask open questions: 'What's the part you're least sure about?' rather than 'Is it done?'
- When you see a problem, ask a question first. 'How are you thinking about the edge case when the file is empty?' often works better than telling.
- Let people do it differently from you, if the outcome and constraints are met.
- When something goes wrong, focus on what to change in the brief or the process, not on the person.
Mentoring: coaching versus telling
Mentoring is helping someone develop their own judgment. Sometimes the right move is to tell them the answer, especially when they are stuck on something trivial or the clock is ticking. Often it is better to ask. A useful pattern is to ask what they have tried, ask what they think the options are, and then share your view as one input, not the verdict.
"What have you tried so far?"
"What do you think the options are?"
"What would you do if I weren't here?"
"What's the trade-off between those two?"
"What did you learn from that, and what would you do differently?"Your first 1:1 agenda
A 1:1 is a regular private meeting (weekly or every two weeks, 30 minutes) that belongs to the other person. Your first one sets the tone. Do not use it to review a task list; use it to learn about them and agree how you will work together.
1. Check-in (3 min)
"How are you doing, outside of work too, if you want to share?"
2. Your background and goals (7 min)
"What do you want to be doing in a year?"
"What kind of work gives you energy, and what drains you?"
3. How you like to work (5 min)
"How do you prefer to get feedback: in the moment or in writing?"
"How often would you like check-ins on your tasks?"
4. How I work (5 min)
Share your preferences and how to reach you.
5. Current work and blockers (5 min)
"Is anything blocking you? Is anything unclear about priorities?"
6. Feedback and next steps (5 min)
"What's one thing I could do to make your work easier?"
Agree the next 1:1 time and the agenda doc you'll both add to.Common mistakes
- Delegating a task but not the authority to make decisions about it, so the person keeps coming back to you.
- Vague briefs like 'Can you look into this?' with no outcome or deadline.
- Taking work back at the first sign of trouble, which teaches people not to try.
- Checking in so often it feels like surveillance, or so rarely that problems arrive on the deadline.
- Cancelling 1:1s whenever you are busy. It signals that the person is low priority.
- Giving feedback only when something is wrong. Name specific good work too.
How this shows up in interviews and on the job
Interviewers for lead and senior roles ask: 'How do you delegate?', 'How have you helped a struggling teammate?' and 'Tell me about a time you mentored someone.' They are looking for specifics: how you set expectations, how you supported without taking over, and what happened to the person. Frame stories with the STAR method from Behavioral Interview Questions and the STAR Method. If you have not led formally, mentoring an intern, onboarding a new joiner, or leading a college project all count.
On the job, the test is simple: can your team do good work, and keep doing it, when you are away for a week? If the answer is no, you are the bottleneck, and the fix is clearer briefs and more deliberate delegation. Habits from Leadership Without Authority, like writing things down, make this much easier.
How to practice
Pick one task you currently do that someone else could do with support. Write the brief using the template, hand it over, and schedule the early checkpoint. If you are not a lead yet, practice by mentoring a junior classmate or newer colleague with the same question list.
Try it yourself
Choose one recurring or upcoming task and write a delegation brief for it using the template, including a checkpoint date. Then draft your first 1:1 agenda for a real or imagined teammate, adapting the template to your situation.
Show a hint
If you cannot write the 'Outcome' line as something observable, you are not ready to delegate the task yet; clarify what success looks like first.
Key takeaways
- Delegate work that helps others grow and frees you for work only you can do; keep sensitive and authority-based decisions.
- A good brief states the outcome, constraints, decision rights and deadline, and leaves the method to the person.
- Match check-in frequency to the person's experience with the task and agree it in advance.
- Ask questions before giving answers when coaching, but tell directly when time is short.
- Your first 1:1 should be about the person: goals, working style, blockers and feedback.
Test yourself
A trick from this lesson's ride: Hand over what teaches them. Keep what needs your badge. Four more tricks like it wait along the route, each followed by a question.
Frequently asked questions
What should a new team lead delegate?
Delegate well-defined tasks that help a teammate learn, recurring work you do out of habit, and work where someone else is closer to the details. Keep performance conversations, hiring decisions and anything that needs your formal authority or is confidential.
How do you write a good delegation brief?
State the outcome and how you will know it is done, why it matters, the constraints, what decisions the person can make alone, the deadline and an early checkpoint. Leave the method to them. A short brief like this prevents most rework.
What should I talk about in a first 1:1 with a new direct report?
Focus on the person: their background and goals, how they like to work and get feedback, any blockers or unclear priorities, and what you can do to help. Share your own working style too, and agree on a regular time and a shared agenda document.