1.5Communicating effectively with users
Users judge IT as much on how they were helped as on whether the problem was solved. That makes communication a genuine technical skill, not a nice-to-have. It starts with active listening: let the person describe the problem fully, ask clarifying questions, and confirm you have understood before diving in. Half of « difficult » tickets are really cases where the technician fixed the wrong thing because they did not listen first.
Then comes explaining without jargon. The user does not need to hear about DNS or NTFS permissions; they need to know what happened, what you did, and what — if anything — they should do differently. Adjust your language to the person, stay calm and patient even when they are frustrated, and show a little empathy: a stressed user who feels heard becomes far easier to help. Manage expectations honestly (« I can fix this in an hour » or « this needs to be escalated »), and follow up so people know they were not forgotten. Strong communication turns IT from a feared black box into a trusted service — and it is a skill you can deliberately practise and improve.
Section vocabulary
- Active listening
- Fully hearing the user out, asking clarifying questions, and confirming understanding before acting.
- Jargon
- Technical vocabulary that is precise for you but confusing for the user; avoid it when explaining.
- Empathy
- Acknowledging the user's frustration and situation, which makes them easier to help.
- Managing expectations
- Being honest about what you can do and by when, including when you must escalate.
- Follow-up
- Checking back so users know their issue was not forgotten.
What quality matters as much as technical skill in user support?
In practice — Handle a frustrated user
- Take a scenario where a user is stressed and their description is vague.
- Write two clarifying questions that would pin down the real problem.
- Draft a one-line, jargon-free explanation of what you will do.
- Add an honest expectation (a rough time, or that you must escalate) and a follow-up promise.
Key takeaways
- Users judge support on the relationship as much as the fix — communication is a technical skill.
- Listen actively and confirm understanding before you start fixing.
- Explain without jargon: what happened, what you did, what they should do.
- Show empathy, set honest expectations, and follow up so no one feels forgotten.
Frequently asked questions
How do I stay calm with an angry or rude user?
Remember the anger is almost always about the problem, not about you: something they need is broken and they feel powerless. Let them vent briefly without interrupting, acknowledge the frustration (« I can see this is really disruptive »), and redirect toward action (« let's get it working — can you show me what happens? »). Staying calm and solution-focused usually de-escalates within a minute, because the person feels heard and sees you helping. Keep boundaries if behaviour crosses a line, but most « difficult » users simply want to be taken seriously and updated honestly.
Should I explain the technical detail so the user learns?
Match the explanation to the person and the moment. Most users want their tool working and a plain summary, not a lecture on the underlying technology; drowning them in detail can feel condescending or overwhelming. A good default is one clear sentence about what happened and what, if anything, they should do differently, and an offer to explain more if they are curious. For users who genuinely want to learn, teaching them a small preventive habit is valuable and reduces future tickets — but let their interest, not your enthusiasm, set the depth.