Teaching Judgment, Not Just Procedure

Why this matters

A tech who follows procedure handles the jobs the procedure covers. A tech with judgment handles the job nobody wrote down, the weird call, the customer curveball, the moment the checklist runs out and a decision still has to be made. Procedure is teachable in a week. Judgment takes deliberate effort, and shops that never teach it end up with techs who freeze, call the office for every wrinkle, or make confident bad calls. Judgment is what lets you trust someone alone in a customer's home with a problem you did not anticipate.

Procedure versus judgment

Procedure is the known answer to the known problem: the steps, the sequence, the spec. Judgment is knowing what to do when the situation does not match the steps, and knowing when the procedure itself is wrong for this case.

You need both. Procedure without judgment is a tech who cannot adapt. Judgment without procedure is a tech who improvises the things that should never be improvised, like the safety steps.

Teach the why behind every step

The fastest way to grow judgment is to never let a procedure be a black box. A tech who knows that you bleed the line for a specific reason can reason about what to do when the situation is a little different. A tech who only knows "do this here" is stranded the moment the situation shifts. When you teach a step, teach what it is protecting against and what happens if it is skipped. The why is what transfers to the next, unfamiliar problem.

Make them decide before you answer

The instinct, when a tech asks "what do I do here," is to just tell them. Telling is faster and it feels like helping. It also robs them of the rep that builds judgment. Instead, turn it back: "What are you seeing? What do you think is going on? What are your options and what would you pick?" Let them reason out loud, then guide. They will reach the answer slower than you would have handed it over, and that slower path is exactly how judgment forms. Save the direct answer for safety and for when they are genuinely stuck.

Walk the gray-area calls out loud

Judgment lives in the decisions that have no clean right answer: repair or recommend replace, push the upsell or read the customer and back off, fix it cheap now or flag the bigger problem, condemn the unit or nurse it through the season. These are the calls a checklist cannot make. Teach them by talking through real ones. After a job with a judgment call in it, spend five minutes on it: what did you decide, what were you weighing, what would have changed your mind. Do this enough and the crew internalizes how you think, which is the whole point.

Let them make safe mistakes

Judgment is built partly from being wrong and learning why. A tech who is never allowed to make a recoverable mistake never develops the instinct to avoid the costly one. Within safe bounds (never on safety, never where a mistake endangers someone or wrecks expensive equipment), let people own decisions and own the outcome. When it goes sideways, debrief it as a lesson, not a failure. "Walk me through how you got there" teaches. "Why would you do that" shuts the learning down.

Build a shared sense of the standard

Judgment is not purely individual, it should reflect how your shop does things. What is the line between a repair you will stand behind and one you will not? When does your shop recommend replacement instead of another patch? How hard do you push add-on work, and where is the line into something that does not serve the customer? When the crew shares these standards, their independent decisions stay consistent with each other and with the business, and a customer gets the same judgment whichever tech shows up. Make these explicit instead of assuming everyone absorbed them.

Know when judgment is the wrong tool

Not everything should be a judgment call. Safety steps, code requirements, and the procedures that exist because someone got hurt or sued are not up for improvisation, those are management and standards, full stop. The skill is teaching techs to know the difference: where the procedure is the law and where it is a starting point they are expected to think past. A mature tech follows the non-negotiable steps without question and applies judgment everywhere else. Teaching both, and the line between them, is the real job.

References

• OSHA standards - the non-negotiable procedures that are never subject to field judgment.
• U.S. Department of Labor registered apprenticeship frameworks - structured progression from supervised procedure to independent judgment.
• See related: Mentoring vs Managing: The Difference.
• See related: Building a Training Culture, Not Just Onboarding.