Field Service Coaching Needs Evidence, Not Anecdotes

Most field service coaching is built on fiction. A supervisor sees a closed work order, a duration, a parts list, and perhaps a customer complaint. Then the supervisor invents the missing story and calls the result feedback. The technician hears advice about a job the manager never saw.

That is not coaching. It is an argument between two incomplete memories.

A new Future of Field Service profile explains how Brightstar Lottery built professional-skills training for more than 600 technicians across 26 states. The company already had a rigorous technical competency model. Yet supervisors struggled to explain what separated top performers from average ones. Their honest answer was often some version of “I just know.”

That answer should make every service leader uncomfortable. If a manager cannot name the behavior, the manager cannot teach it. More importantly, if nobody observes the work, even a good competency model turns into guesswork.

Field Service Coaching Has an Observation Problem

Service organizations collect plenty of outcomes. They know arrival times, completion times, repeat visits, parts consumption, and customer scores. However, outcomes do not explain the decisions that produced them.

A first-time fix might reflect excellent diagnosis. It might also reflect luck and a van full of spare parts. A long visit might show poor preparation. Or it might show a technician patiently preventing a larger failure. Meanwhile, a five-star score can hide a dangerous shortcut.

Good field service coaching needs the middle of the story. What did the technician notice first? Which question changed the diagnosis? How did they explain uncertainty? When did they ask for help? What did the customer understand before the work began?

The technician retirement analysis asks what expertise is lost when a support system never captures how experienced people observe the work.

Those moments rarely survive in a work-order summary. Therefore, managers end up coaching the metric instead of the behavior.

Stop Treating Great Technicians as Mysteries

Brightstar spent 18 months interviewing technicians and supervisors. The team compared people with similar technical ability, then identified behaviors that changed by seniority. At entry level, credibility and interpersonal skill mattered. At senior levels, mentoring and early leadership became more important.

That work matters because “great technician” is usually a lazy label. It bundles judgment, communication, adaptability, and calm into one compliment. Then leaders wonder why they cannot reproduce it.

The fix is to make the work discussable. Start with a narrow behavior. For example, ask how a technician confirms the customer’s description before touching the equipment. Next, define what good execution looks like. Then review a real case where that behavior changed the result.

Field service coaching becomes useful when the conversation moves from personality to evidence. “Be more confident” is vague. “Explain your first diagnostic step before opening the panel” is observable. One sounds personal. The other can be practiced on the next call.

Use Visual Escalations as Coaching Moments

Remote visual support is usually sold as a way to resolve cases faster or avoid a dispatch. That is valuable, but it misses another operational benefit. A live visual escalation lets an experienced person see how the problem is being framed.

The expert can watch the sequence of inspection. They can ask why a technician skipped a connection, focused on a sound, or dismissed visible wear. In addition, they can hear how the technician explains the problem to the customer.

The expert-waiting analysis explains why coaching improvements must be paired with a usable escalation path for the case that is blocked today.

This does not require recording every visit or turning managers into surveillance officers. In fact, constant monitoring would destroy trust. Instead, use selected escalations and scheduled case reviews. Make the purpose explicit. The goal is to improve decisions, not catch mistakes.

We have argued before that the fastest way to bring a new field technician up to speed is not a classroom. The same principle applies after onboarding. People improve when guidance is attached to a real machine, a real decision, and a consequence they can see.

That creates a shared reference point. The technician no longer has to defend a written summary. The coach no longer has to imagine the scene. Both can examine the same evidence and decide what should happen next time.

Coach the Decision Before the Score

Managers often begin field service coaching with the scorecard because the scorecard is available. That sequence is backward.

The Viewabo vs CareAR comparison separates customer triage from expert field collaboration before evaluating a visual-support tool.

First, review the diagnostic path. Did the technician test the cheapest plausible cause before replacing a part? Did they confirm the environment around the equipment? Did they know when the evidence no longer supported the original theory?

Second, review the customer handoff. Did the customer understand what failed, what was fixed, and what remained uncertain? Could the customer recognize the warning signs if the problem returned?

Finally, connect those behaviors to the outcome. Now the first-time fix rate, visit length, or satisfaction score has context. As a result, the metric becomes a consequence to study, not a verdict to deliver.

This approach also protects technicians from bad incentives. If managers praise only speed, people rush. If managers praise only first-time fixes, people replace extra parts. Yet when managers review the quality of the decision, technicians can choose the right tradeoff for the case.

Build a Practice Loop, Not a Training Event

Brightstar’s program uses one week of learning followed by four weeks of practice. That structure reflects a truth many service organizations avoid: behavior changes slowly.

A workshop can give technicians a vocabulary. It cannot create a habit. Therefore, every competency needs a practice loop. Pick one behavior. Observe it in a real case. Debrief soon afterward. Agree on one adjustment. Then look for that adjustment in the next relevant case.

Keep the loop small. Field service coaching fails when every review produces six corrections. The technician remembers none of them and the manager cannot follow up. One specific change creates accountability without theater.

Also, let senior technicians coach from evidence. Their value is not that they always know the answer. Their value is that they recognize signals, test assumptions, and recover when a theory fails. Those moves become teachable only when less experienced technicians can see them applied.

Your Work Orders Are Not a Coaching System

Service leaders keep asking for more complete notes. Better documentation helps the next person. Still, documentation cannot recreate the job.

If you want better field service coaching, stop asking managers to reverse-engineer behavior from administrative residue. Give them selected moments of observable work. Give them a clear competency to discuss. Then require a short follow-up on the next case.

The uncomfortable truth is simple. You do not have a technician consistency problem until you can prove what your technicians do differently. Before that, you have an observation problem.

Fix that first.