Language, Pace and Who You Are Helping

Technical competence is assumed. How a session is spoken determines whether the person understands what happened, and whether they will ask for help again.

The practical lesson in “Language, Pace and Who You Are Helping” is to make responsibility visible without confusing visibility with certainty. A team reviewing read the full overview for cognitive offloading can add structured time and project context, provided the purpose is disclosed and the interpretation is checked with the people affected.

Pace

Most support is conducted faster than the person can follow, because the helper has done it a hundred times.

For an independent reference related to “Language, Pace and Who You Are Helping”, consult the Google Safety Center; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.

Slowing by a third costs a minute and changes comprehension entirely.

And pauses matter: say something, then stop, so they can ask.

Jargon

Not avoiding it entirely — some terms are the accurate words.

Explaining it once in passing: "the cache, which is the saved copy it keeps to be faster".

Six words, and they can follow the rest.

What not to do

Talking down. People detect it immediately and it is the fastest way to make somebody stop asking for help.

Over-explaining to somebody technical, which wastes their time and signals you have not listened.

And assuming the level from their age or their voice, which is wrong often enough to be worth dropping entirely.

Finding the level

Ask early: "how familiar are you with this?"

Then adjust, and adjust again if the first answer was modest.

People understate their competence, particularly older people, and they overstate it occasionally too.

When English is not their first language

Slower, simpler sentences, not louder.

Avoid idiom, which is what actually causes incomprehension rather than vocabulary.

Confirm understanding by asking them to say back, not by asking "does that make sense", which everybody answers yes to.

When somebody is distressed

A lost document, a frightening message, work due in an hour.

Acknowledge it before diagnosing: "that is a horrible thing to happen, let me look".

Then be calm and specific, because calm is what they need from you more than speed.

The person who has been defrauded

They will be ashamed and may not say what happened.

Ask gently and without implication.

And do not react, because the reaction is what determines whether they tell anybody about the next one.

Saying you do not know

"I am not sure what that is, let me find out" is better than confident wrongness.

It also models something useful: that not knowing is normal around computers, which is the belief most worth leaving somebody with.

What to check

Do you ask how familiar somebody is before starting?

Do you pause, or talk through?

Could the last person you helped repeat what happened?

And how do your technicians sound when somebody is upset?