Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
How would you respond if I asked you,
do you know how long it'll take me to get to the bank?
You'd probably ask, where are you, where's the bank?
Are you walking, driving, biking?
But if you just guessed the details of
my situation to direct me to the bank,
your response would be a day late and $1 short.
It seems such a natural thing to ask
questions and gather information to solve a problem.
But it's usually one of those most
overlooked steps and troubleshooting.
Troubleshooting is the ability to
diagnose and resolve a problem.
One of the most difficult skills to acquire in
an IT role isn't
technical knowledge, but effective troubleshooting.
Rather that's helping someone face-to-face or remotely.
It's not specific to the IT world either.
We use troubleshooting skills everyday.
My car is broken,
the light bulb went out. I feel sick.
Imagine if you went to your doctor and said,
I feel sick and without any other information,
he gives you a prescription for allergy medicine,
time to find a new doctor.
Well, this might seem far-fetched.
This can happen pretty often in the IT world.
We're so in the habit of fixing things that sometimes we
try to fix something without diagnosing it first.
We're going to give you the tools you need
to develop good troubleshooting habits.
No matter how big or small the problem is,
the first thing to do in troubleshooting
is, ask questions.
There are a lot of factors that can cause a problem.
You want to make sure you gather
all your data before you start to tinker with it.
Over the next several videos,
we're going to demonstrate real-world
in-person and remote troubleshooting scenarios.
For the in-person scenarios,
you'll meet Gail and Marty.
And yes, we have another Marty joining us.
But he spelled his name with a y and I
still mine with an i, confusing. I know.
Please keep in mind these are not professional actors.
We want to give you the opportunity to see how
these different scenarios would
play out in real-world settings.
Let's look at a quick scenario of
a not so awesome troubleshooting
interaction and an awesome one.
My computer's broken.
This looks bad. I think
you're going to need a new computer.
It's going to be about a 1,000 bucks.
My computer's broken.
Can you tell me a little bit more about how it's broken?
Does it turn on at all?
Has there been any damage to it lately that you know of?
Well, when I hit the power button,
I hear a Ding, but nothing comes up on screen.
Oh, okay. Can I take a look?
Sure.
Let me just see what's going on here.
You know what, the brightness was turned down.
These brightness buttons are a little bit fiddly and it's
easy to hit them by accident. There you are.
Great. Thank you.
You're welcome.
If we didn't ask follow-up questions,
we wouldn't have realized the issue is
something as small as screen being dim,
but it's important that you're able to gather
enough information to start troubleshooting an issue,
whether it's big or small.
With a little digging,
we're able to understand
the situation and effectively troubleshoot the issue.
What's also really important to call out
from the scenario is the tact
and make the user feel silly for not
realizing the screens brightness was down.
Can you think about a time someone made you
feel silly or even dumb?
It's a pretty terrible feeling.
Don't be that person that does it to someone else.
Remember, IT support is
about working in the service of others.
Always try to create a positive experience for the user,
will deep dive into customer service later on.
In the meantime, I'll see you back in
the next video on isolating the problem.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.