You give direction during a job or breakdown and an experienced technician says, in front of everyone, that your plan is wrong.
Do not make authority the first problem
The fastest way to lose the value of the moment is to respond as if public disagreement is automatically insubordination. The first question is whether the technician sees something you do not.
A confident leader can tolerate a technical challenge long enough to understand it. That does not surrender authority. It protects the decision from ego.
Establish the technical facts
Ask what they are seeing, what failure mode or constraint they believe matters, and what evidence supports their concern. If the job is time-critical, keep this brief and specific.
If the challenge exposes a real risk or missing fact, change the plan. If it does not, explain the decision and move forward.
Address delivery separately if needed
If the technician was disrespectful, belittling, or disruptive, handle that after the immediate technical question is settled. Do not use a legitimate behavior concern to ignore good technical information.
Likewise, do not allow technical competence to become permission to undermine the team.
Avoid these traps
- Trying to win the room instead of solving the problem.
- Shutting the technician down before hearing the concern.
- Changing the plan only to avoid conflict.
- Correcting tone publicly when a private conversation will do.
- Allowing repeated disrespect because the technician is technically strong.
Useful language
What good looks like
The crew sees that technical truth can challenge hierarchy, that the leader still makes decisions, and that behavioral standards remain real.