What you'll learn
- Bring one real people-management case into the conversation.
- Review the team lead's reasoning without judging them from one outcome.
- Agree their next action, your support and what you will check together.
What changes when you are managing managers?
Your first team lead still needs a manager. If your meetings only cover deadlines and project updates, you may learn what the team delivered without learning how the lead managed it. Reserve part of the conversation for a recent people-management decision: what they noticed, what they did and where they need help.
This guide is for an ongoing development conversation once the lead has a case to discuss. When the lead first takes the role, agree what they are responsible for, which decisions they can make and what support you will provide. If there is no recent case yet, choose an upcoming ordinary conversation to prepare together, then revisit it after it happens.
A lead who also does specialist work may need both kinds of support. Discuss their own delivery directly, then make room for their management of the team. The individual contributor versus manager comparison helps explain the role difference; here, the person is already managing others.
Ciphr ran this unweighted survey through Pollfish from 26 August to 8 September 2026. It measured preferences, not the effect of support or actual job changes. The sample was not established as a survey of companies with 10 to 50 people. Ask your own lead what support they need; the finding does not prove that this 1:1 approach works.
Bring one case, not a report on every employee
When managing managers for the first time, invite the lead to choose a case they want help with. It might concern something that went well or something they are unsure about: setting an expectation, giving feedback, resolving a disagreement or helping someone learn a task. A successful delivery can hide a poor process, just as a delay can occur despite a sensible decision. One case cannot establish the lead's overall competence.
Ask for enough context to understand the decision: the expectation, what happened, what the lead knew at the time, their response and any follow-up. Use appropriate work records and the lead's account of what happened, checking the employee's account where needed through the appropriate route. Avoid private-message searches or a running dossier on every teammate. Keep sensitive details in the company's appropriate records with suitable access.
A possible invitation is: “Bring one team situation where you had to decide how to respond. I want to understand what you considered, what happened afterwards and what help you need from me.” Leave project reporting in its usual place so this time does not disappear into a task list.
Examine the judgement before giving your answer
- 01
Start with what the lead knew then
Ask: “What had you seen or heard when you made the decision? What were you still unsure about?” Separate the employee's account, a work record and the lead's interpretation. Do not judge an earlier choice using information that only arrived later.
- 02
Explore the choice they made
Ask what other response they considered and why they chose this one. When you see a gap, name it concretely: an expectation that was never checked, an explanation treated as fact, or feedback postponed without a plan. Recognise sound actions too.
- 03
Rehearse the next management action
Have the lead propose what they will say or do next. Help make it specific, and explain your reasoning when you offer advice. Agree who will act and what to revisit; asking questions indefinitely is not useful support.
Consider a hypothetical handover that arrived late. The lead told the employee to manage their time better. In your 1:1, they say they saw the late file but did not ask about the competing work or check what deadline the employee had understood. Your first useful coaching point is the missing conversation, not a faster way to finish the file yourself.
You might say: “Before we decide this is a time-management problem, what do we need to understand? How will you ask about the deadline and the other commitment?” The lead could rehearse an opening: “We expected the handover on Tuesday and received it on Wednesday. What happened, and what did you understand was due?” Those are suggested words for this example, not a script to use regardless of the facts.
Help them listen and then agree a clear expectation. If the conversation confirms a clear, feasible commitment was missed, the lead still needs to address it. Use behaviour-based feedback for that next conversation rather than recreating a full feedback guide in your 1:1.
Separate coaching from something only you can change
Suppose the hypothetical employee explains that you requested another urgent deliverable for the same afternoon. The lead should check that account and the commitments before reaching a conclusion. If confirmed, you need to resolve the competing deadline with the affected people. The lead can still learn to ask before diagnosing the employee and to raise conflicting priorities earlier. Neither action cancels the other.
If the lead asks for a decision you own, give it or state what you must check and when you will answer. If they need to practise a difficult conversation, rehearse it together. If they lack a required skill, arrange suitable instruction or experienced support rather than treating more questions as training. Make your help fit the problem they actually brought.
Where management time repeatedly disappears into work nobody else owns, use the manager overload guide to investigate that role problem. This 1:1 can reveal it; reviewing another case will not create missing capacity or authority.
Return to the case at the next 1:1
For the hypothetical handover, the note might read: “The lead will discuss the deadline and competing commitment with the employee on Thursday, then confirm the next handover expectation. If the competing request is confirmed, I will agree priorities with the lead and affected people before the next handover. At our next 1:1, we will review what the employee understood, the lead's response and the next handover when it is available.” If the handover falls later, keep the meeting and check preparation; do not pretend an outcome has already occurred.
Ask what changed in the lead's understanding and whether the agreed action happened. Review your own support too. A quieter week does not show that their approach improved, and another delay does not automatically show it failed. Check the relevant work and accounts, then decide whether to keep the approach, try a different response or address the unresolved constraint.
When managing managers for the first time, keep a small record of this development work alongside your normal role and goal conversations. Look across several cases over time before drawing broader conclusions. If you need a formal performance review, make its purpose and process explicit rather than using a supposedly supportive meeting as a hidden assessment.
Cooperly's Fundamentals can bring agreed expectations and role context into preparation, alongside working profiles and team context. They can help you prepare questions and keep follow-up visible; they cannot establish the lead's competence or make the management decision for you.