Troubleshooting: The Most-Needed Skill Not Taught in Schools
Udemy
Course Summary
Learn exactly how to master the art of troubleshooting from a master troubleshooter, and land the IT job of your choice!
-
+
Course Description
Computers and the systems they run are known to break. People who use computers are known to open support tickets for problems they are encountering. At some point someone has to fix broken computers...but first it is important to know if something truly is broken. Troubleshooting begins when the problem is reported, and contrary to popular belief, the first step is not to jump in and fix something. The skill of troubleshooting is not taught in schools, mainly because of two different reasons: 1) it's not the easiest to teach (but it is easy to learn), and 2) troubleshooting is an art more than it is a science. Have you ever wanted to...
- Land a job in the IT field, being an excellent troubleshooter is a valuable skill that sets you apart
- Become better at troubleshooting so that it doesn't take you nearly as long to figure something out and implement a fix
- Not get frustrated with computer problems or clients
- Fix your own computer without hiring some expensive person or company to do it for you
- The mindset behind troubleshooting that I always keep as my focus, which helps to uncover the right questions to ask that lead to the solution
- Why you should never blindly trust your client's statement
- Why you should take more time up front to understand the problem, and exactly how to do that
- How to use the acronym S.O.A.P. to powerfully uncover data and lead to a fix
- Keys to gathering data that many IT professionals overlook
- How exactly to leverage data gathered from questions to lead you to a solution
- 14 key questions I ask almost every time + 6 more on reproducing the problem
- What binary tree thinking is, and how to use it to go down the right path to a solution
- How to craft a hypothesis and why doing so is critical
- 2 ways to go about implementing fixes and key considerations for each
- 2 key points for testing that absolutely make a difference
- Rules you must follow when making changes to a broken system...that is, if you don't want to make more work for yourself
- 3 real-life examples where I go through the process, demonstrating how it works
- 3 more examples YOU can troubleshoot by messaging me - examples that I literally had to troubleshoot, and as such I have solutions for them you can uncover
- Access to our existing lectures
- Free access to our new lectures
- Ability to get your questions answered in our discussion section or one-on-one via private message
- The secrets that set you apart from other IT folks
- An unconditional 30-day money-back guarantee - if you don't become a better troubleshooter, I'll buy back this course no questions asked!
-
+
Course Syllabus
- Introduction
- Introduction
- Why Learn This Skill, and Why I'm Teaching It
- An Important Point
- The Troubleshooting Process
- Troubleshooting Process: High Level
- The Client's Problem May Not Be the REAL Problem
- S.O.A.P. Plus One Other Method
- Mindset Behind Discovering the Problem
- It's All About the Data
- Keys to Gathering Data Many IT Professionals Overlook
- Reproducing the Problem
- Great Data Gathering Questions for Just About Every Problem
- Potential Root Causes
- Using Binary Tree Thinking
- Assessing the Data
- Crafting the Hypothesis
- Fixing the Problem
- Two Reasons to Test Fixes
- Key Point for Testing #1: Not ___________ the Outcome
- Key Point for Testing #2: _______ Things Out
- Rules for Changes While Testing Fixes
- SOAP Examples
- Examples Introduction
- SOAP Example #1: Cannot Connect to Company's Application
- SOAP Example #2: App on Phone Opens but Does Nothing
- SOAP Example #3: The Internet Is Down
- Your Turn! 3 Real-Life Examples YOU Can Troubleshoot!