Grow your business / Operator

How to Run Your First Service Lead One-on-One

Contractor Lane editorial guidance. Reviewed September 21, 2026. Examples are illustrative, not industry benchmarks.

Your first one-on-one as a service lead should leave the technician with one useful next step and confidence about where to get help. Prepare one observation, ask what is getting in the way, agree on support and set a follow-up. It should not become a surprise disciplinary meeting or a lecture about every number the manager wants improved.

A working lead still runs calls. Their additional responsibility is frontline support: helping teammates understand expectations, asking good questions, noticing problems and carrying useful information to the service manager or operations manager. The company must explicitly delegate one-on-ones to the lead. A title does not automatically grant authority to change pay, set targets or promise consequences.

Before the meeting, establish your boundaries

Ask your manager what you own, what you can approve and what must be escalated. Confirm who receives meeting notes and where sensitive concerns belong. When a service manager exists, the lead can conduct assigned team one-on-ones and report themes to that manager. Without one, Operations should name the reporting and backup arrangement.

Use a plain opening: “My role is to support your work and bring issues to the right person. I can help with the process and arrange the support I am authorized to provide. I cannot make decisions about compensation or other matters reserved for management.” Only state authority you actually have. This avoids becoming the coworker who promises things another manager must later undo.

Make the appointment realistic

Choose a private setting and a time that does not compete with an active customer commitment. Ask about practical availability rather than repeatedly canceling at the last minute. A short, protected meeting is more valuable than an ambitious session that never happens. Twenty minutes is one possible format, not a required industry standard.

Tell the technician what the meeting is for and invite one topic in advance. If a call overruns, communicate and reschedule with a specific replacement time. Do not treat a moving field schedule as an excuse to let the meeting disappear. Keep the same respect you expect employees to show customer appointments.

Bring facts, not a verdict

Review the last agreed action and one recent example relevant to the person's work. “Two job records did not include the customer-approved scope” is a usable observation. “You never care about paperwork” is a judgment that makes improvement harder to discuss. Check whether the record is complete before assuming the employee did something wrong.

Leads may see team results and recognize a pattern, but the manager owns target design and broader financial decisions. A lower result should start a question, not determine the explanation. Different assignments, missing tools, incomplete training and insufficient capacity can all require different support.

Use a five-part conversation

1. Check in: “How is the workload feeling, and what is making your day harder than it needs to be?”
2. Recognize: identify one specific thing the person handled well.
3. Explore: ask about one observed problem and listen before recommending.
4. Practice: choose one behavior to demonstrate or rehearse.
5. Agree: record the next action, support owner and review date.

Let the employee finish their account. Summarize what you heard and ask whether you understood. You are not required to solve everything immediately. Sometimes the useful outcome is identifying exactly which question requires the manager's decision and when you will return with it.

A worked example: incomplete customer explanations

Imagine a technician whose recent notes show customers repeatedly asking what happens next. The lead starts: “On these two calls, the office had to explain the next appointment again. Can you walk me through how you closed the conversation?” This avoids assuming the person ignored customers.

The technician explains that parts availability was uncertain and they did not want to give a false date. The actual gap is a missing handoff, not unwillingness to communicate. Together they practice: “The part date is not confirmed yet. Our office owns the update and will contact you at the agreed time. Here is the number to use if your situation changes.” The office must accept that responsibility before this becomes the shop's standard.

The action is to use the approved closeout summary on the next suitable calls and review two records together at the next meeting. The lead asks the office manager to clarify who owns parts updates. Both people now have work to do; the technician is not being asked to fix a broken process alone.

When the conversation becomes difficult

If the technician disagrees, ask which fact or expectation they dispute. You can say, “Let's separate what happened from what the standard should be. I will verify the record with the manager.” Do not force agreement just to finish the meeting. Write the unresolved question and its next owner.

If someone raises a serious safety concern, misconduct allegation, pay issue or another sensitive matter, follow the company's appropriate reporting process promptly. Do not promise secrecy, investigate beyond your assigned role or turn the concern into ordinary performance coaching. A useful response is: “Thank you for telling me. I need to bring this to the person responsible for handling it. I will share the facts through that process.”

If a technician shares a personal difficulty, you can listen without asking for unnecessary private details or trying to diagnose it. Bring requests requiring management decisions to the authorized person. This article is a coaching structure, not guidance for resolving employment or medical matters.

Record a small, usable follow-up

Write the date, observation, employee's relevant explanation, agreed action, support promised and review date. Avoid gossip, labels and speculative diagnoses. Use the company's approved location and access rules, not a personal message thread that disappears when the lead changes phones.

At the next meeting, begin with your own commitment. Did you arrange the demonstration, obtain the policy answer or fix the missing reference? Reliability works both ways. If the same problem remains, ask whether the action was specific, practiced and possible. Bring repeated unresolved issues to the manager without inventing a punishment.

Your first-meeting checklist

Confirm delegated authority, protect a time, bring one verified example, invite the employee's topic, practice one improvement and record one follow-up. Keep teamwide reminders in the team meeting; use the one-on-one for individual support. For adjacent role preparation, review a helper's first-week training plan and the CSR coaching sequence. The job differs, but the principle remains: observable practice is more useful than hoping that reading alone changes behavior.