One-on-One With a Technician

Why this matters

A regular one-on-one is the single best tool for keeping a good tech and catching a problem before it becomes a resignation. Most techs do not quit over money first. They quit because they felt unheard, stuck, or jerked around, and nobody asked until it was too late. A short, recurring, private conversation gives you a standing channel to hear what the huddle never surfaces: frustrations, ambitions, and the small things that quietly pile up. It is also where coaching actually lands, because it is private and unhurried.

Step 1: Make it regular and protected

A one-on-one only works if it happens whether or not anything is on fire.

  • Set a cadence and hold it. Every two weeks or monthly is plenty for most shops. Twenty to thirty minutes.
  • Protect it. Canceling because the day got busy tells the tech they are last in line. Reschedule, do not skip.
  • Make it private. In the truck, in your office with the door shut, on a walk. Never within earshot of the crew.
  • Keep it off the schedule pressure. Do not sandwich it between two callouts where you are both watching the clock.

Step 2: Remember whose meeting this is

A one-on-one is the tech's meeting, not yours. Your status updates and assignments belong in the huddle. This time is for what is on their mind. The fastest way to ruin a one-on-one is to turn it into you reading a task list. Talk less than half the time. The signal you are doing it right is that they bring the topics.

Step 3: Ask open questions and then be quiet

Open questions get real answers. Closed ones get "fine." Have a few in your pocket and let silence do its work, because people fill a pause with the truth.

  • "How is the work going for you lately?"
  • "What is slowing you down or driving you nuts?"
  • "Is there anything you want to be doing more of, or learning?"
  • "Anything I am doing, or not doing, that makes your job harder?"
  • "What would make next month better than this one?"

When they answer, do not jump to defend or fix. Let them finish. The temptation to explain why the schedule is the way it is will shut down the next three things they would have told you.

Step 4: Separate coaching from venting

Two different things happen in a one-on-one, and you handle them differently.

  • Venting needs to be heard, not solved. Sometimes the whole fix is "that sounds frustrating, tell me more." Trying to solve a vent makes the person feel dismissed.
  • Coaching is forward-looking and specific. If you saw a skill gap or a customer-handling slip, name the behavior, not the character. "On the Patel job the customer felt rushed" lands. "You have a bad attitude" does not. Then ask how they would handle it next time so the answer is theirs.

Step 5: Close the loop on what you promised

A one-on-one where the tech raises something and nothing happens is worse than no one-on-one, because now they know talking changes nothing. Every meeting:

  • Write down anything you committed to. A tool they need, a training they want, a scheduling fix.
  • Do at least one of those things before the next meeting, even a small one.
  • Open the next session by closing the last one: "Last time you mentioned the bad ladder, it is replaced." That single habit is what makes techs believe the meeting is real.

Step 6: Watch for the quiet signals

The value of recurring one-on-ones is the trend, not any single meeting. Watch for drift:

  • A normally talkative tech goes flat and short.
  • Repeated mentions of the same frustration you keep not fixing.
  • Talk that shifts from "we" to "you guys."
  • A growing tech who stops asking about growth.

Any of these is an early warning. Catching it here, in private, with time to act, is the entire reason this meeting exists.

Common mistakes

  • Turning it into a performance review. Reviews are scheduled and formal. One-on-ones are frequent and loose. Mixing them makes the tech guard up every time.
  • Only holding them when there is a problem. If a one-on-one always means trouble, people dread it. Hold them when things are fine, so they are not loaded.
  • Doing all the talking. If you walk out having said most of the words, you ran a briefing, not a one-on-one.

References

  • See related: Accountability Without Micromanaging
  • See related: Meeting vs Message vs Walk-Over Decision Tree
  • Trade-standard practice for field-service team retention and coaching