Skip to content

5. Professionalism and Communication

Technical skill solves the problem. Professionalism determines whether the person you're helping actually trusts you, understands what happened, and wants to work with you again.

A few concrete habits

Habit Why it matters
Avoid jargon, or explain it when you use it "Your APIPA address means DHCP failed" means nothing to most users — explain in plain terms
Set realistic expectations "This might take a while" said upfront beats silence followed by a surprise delay
Active listening Let the person finish describing the problem before jumping to a fix — the real issue isn't always the first thing they mention
Maintain confidentiality What you see on someone's device while fixing it isn't yours to share
Stay calm with a frustrated user Their frustration is with the problem, not with you personally — reacting defensively makes it worse, not better

Explaining technical things to non-technical people

Every "Watch along" and "Try it" in this entire course has been an exercise in exactly this — taking something technical (a protocol, a hypervisor, a troubleshooting method) and explaining it in terms someone without the background could actually follow. That skill transfers directly to talking with an actual user.

Try it

Take one concept from any earlier module and explain it in one sentence, with zero jargon, as if to someone who's never touched a computer's internals.

Tip

If you catch yourself about to say an acronym, pause and say what it stands for first — most jargon isn't wrong, it's just unexplained.

Play it

Open the Operational Procedures Lab and use the Professionalism tab.

Next: Basic Scripting →