
Welcome: How This Course Works
Where you are: Orientation · Before Module 1 · Based on the Preface, About the Author and Course Structure of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Welcome
Something stops working. A laptop will not start, a network will not connect, an application keeps crashing, or a routine business process keeps producing the wrong result. Most people react by trying things at random until something seems to help. This course teaches a better habit: a small, fixed set of steps that works on almost any problem, in any system, and that you can explain to someone else afterwards.
Troubleshooting Essentials is an introductory, university-level course in systematic problem-solving. You will learn the method once and then practise applying it to computers, networks, operating systems, software, user accounts, printers, mobile devices and peripherals, and finally to non-technical problems such as late deliveries. The technology changes from module to module. The method does not.
Who this course is for
The course is written for:
- introductory university students in computing, information technology and related subjects;
- people starting out in IT support, help desk or technical roles;
- technical trainees and apprentices who need a dependable working method;
- anyone who wants a calm, logical approach to problems instead of guesswork.
No previous technical knowledge is assumed. Every technical term is defined the first time it appears, and the Course Glossary in the Toolkit collects them in one place. If you already work in support, you will find that the course gives names and a clear order to things you may already do by instinct, which makes them easier to repeat, teach and document.
About the author and this edition
The course is adapted, with the author's permission, from Troubleshooting Essentials: A Systematic Method for Diagnosing and Solving Any Problem, University Edition (2026), by Dr. Tahseen Al Doori, Ph.D., FBCS.
Dr. Al Doori is a university lecturer with two decades of experience teaching networking and information technology at university level in the United Arab Emirates. He is a CCNA Cisco Academy Instructor, a WiMAX Forum RF Network Engineer and a Microsoft Certified Professional, and a Fellow of the British Computer Society. He is the author of the Essentials series of university textbooks, which includes Network Essentials, Cyber Security Essentials and IT Forensics Essentials.
The frameworks taught here (the seven-step methodology, the seven principles, the 5W1H questions, the five quick-win checks, the six isolation techniques and the tiered support model) are the author's, and they are presented exactly as he defines them. The online adaptation and production, including the narrated videos, written lessons, exercises, assessments and Toolkit, are by Turning Point Training Institute. Where a lesson adds material that is not in the book, such as a note about how a command behaves on a current operating system, it is clearly marked as Beyond the book (2026 note) and linked to an official source.
How each lesson works
The 42 core lessons all follow the same pattern, so you always know what to expect.
Watch
A short narrated, animated video (about 4 to 8 minutes) introduces the idea and demonstrates it, often with a realistic fault being worked through on screen.
Read
The written lesson teaches the same content in full, with tables, examples and a worked example. It stands on its own if you cannot watch the video.
Practise
A "Try it" activity gives you something practical to do, safely, with clear criteria for knowing when you have finished.
Check
A short knowledge check of 3 to 5 questions, followed by explanations of every answer, tells you whether the lesson has stuck.
Each module ends with a checkpoint: a brief recap, five questions covering every objective of the module, and a lab that puts the module into practice.
The seven-step method at a glance
Every problem in this course is solved with the same seven steps:
- Identify the problem. Find out exactly what is happening, what should happen instead, when it started, who is affected and what changed.
- Establish a theory of probable cause. List the possible causes, simplest and most likely first.
- Test the theory to determine the cause. Use one small, safe test to confirm or reject the theory.
- Establish a plan of action. Decide what will change, what could go wrong and how the change will be undone.
- Implement the solution or escalate. Apply the plan one change at a time, or pass the problem on with full notes.
- Verify full system functionality. Confirm the original problem is gone, that nothing else has broken, and that the user agrees.
- Document findings, actions and outcomes. Record the symptom, cause, actions and result.
Steps 2 and 3 form a loop. If a theory is rejected, you go back to Step 2 and test the next one, until a cause is confirmed or the problem is escalated. No fix is applied until a cause is confirmed. Module 3 teaches the method in full, and every later module uses it.
The course map
The 14 modules follow the four parts of the book, plus this orientation and a Toolkit of printable resources.
| Part | Modules | What you will learn |
|---|---|---|
| Part I: Foundations of Troubleshooting | 1 Introduction to Troubleshooting · 2 The Troubleshooting Mindset · 3 The Universal Seven-Step Methodology | What troubleshooting is, the professional mindset it needs, and the method every later module builds on |
| Part II: Diagnostic Techniques | 4 Identifying and Defining the Problem · 5 Quick-Win Checks · 6 Isolation Techniques · 7 Essential Diagnostic Tools | How to define a problem precisely, rule out the obvious, narrow a fault down and gather evidence with built-in tools |
| Part III: Applying the Method | 8 Computer and Hardware · 9 Network · 10 Operating System, Software and Accounts · 11 Printers, Mobile Devices and Peripherals | The method applied to the faults met most often in practice |
| Part IV: Resolution and Professional Practice | 12 Root Cause Analysis and Prevention · 13 Escalation, Communication and Documentation · 14 Case Studies and Final Assessment | Stopping problems from returning, escalating and communicating professionally, and applying everything to complete cases |
Suggested pace
The book is designed for a one-semester course of fourteen weeks, with one chapter each week. If you are studying with a class, follow your tutor's schedule. If you are studying on your own, the same plan works well:
| Week | Module | Notes |
|---|---|---|
| 1 | 1 Introduction to Troubleshooting | |
| 2 | 2 The Troubleshooting Mindset | |
| 3 | 3 The Universal Seven-Step Methodology | |
| 4 | 4 Identifying and Defining the Problem | |
| 5 | 5 Quick-Win Checks | |
| 6 | 6 Isolation Techniques | |
| 7 | 7 Essential Diagnostic Tools | Midpoint Review |
| 8 | 8 Computer and Hardware Troubleshooting | |
| 9 | 9 Network Troubleshooting | |
| 10 | 10 Operating System, Software and Accounts | |
| 11 | 11 Printers, Mobile Devices and Peripherals | |
| 12 | 12 Root Cause Analysis and Prevention | |
| 13 | 13 Escalation, Communication and Documentation | |
| 14 | 14 Case Studies | Capstones and Final Assessment |
The course is self-paced. As a rough guide, allow about two hours per module for the videos, reading, practice, knowledge checks and lab, and extra time for the two capstones. These are approximate figures: some learners will move faster through familiar material and slower through new material, and that is fine. Steady progress matters more than speed.
How you will be assessed
| Element | Where | Purpose |
|---|---|---|
| Knowledge checks | End of every core lesson | Quick practice with explanations; for your own feedback |
| Module checkpoints and labs | End of every module | Five questions covering every objective, plus a hands-on or simulated lab |
| Midpoint Review | After Module 7 | A revision summary of Modules 1 to 7 and 15 application questions |
| Capstone 1: Technical Incident Investigation | Module 14 | A full seven-step investigation of a multi-symptom incident, marked against a rubric |
| Capstone 2: Root Cause and Professional Handover | Module 14 | Root cause analysis, prevention, escalation and a professional handover, marked against a rubric |
| Final Assessment | Module 14 | 25 questions across all 14 modules, mostly scenario-based; a separate lesson gives the answers and feedback |
For the Final Assessment, aim for at least 70% (18 out of 25). Treat this as a self-assessment guide: if you score lower, the feedback lesson shows exactly which modules to revisit.
Ground rules for safe practice
Troubleshooting is practical, and practical work needs clear limits. These rules apply throughout the course.
Practise safely.
- Use a training machine. Do practical exercises on a disposable or training computer, a virtual machine, or as a paper or simulated exercise. Never practise on the only device you depend on.
- No destructive commands on your own device. Do not run commands that format, wipe or repair disks (for example
format,diskpart clean,rm -rf,chkdsk /f), edit the registry or flash firmware on your primary device or on any device holding your only copy of important data. - Back up first. Before any change that could affect data, make a backup and record the current settings.
- Electricity and opening equipment. Disconnect power before opening any equipment, use anti-static protection, and never open power supplies or monitors: they can hold dangerous charges even when unplugged. Do not open equipment under warranty without authorisation.
- Stop for danger signs. Burning smells, smoke, sparks, swollen batteries, exposed wiring or water near electricity mean stop, switch off at the source only if it is safe to do so, and escalate.
- Failing storage. If a drive may be failing, back up immediately and stop unnecessary use. Every extra operation can make recovery harder.
- Malware and ransomware. Disconnect the device from the network, do not pay or interact with any message, and report it to whoever is responsible for IT security.
- Passwords and permissions. Never share a password, and never ask anyone to tell you theirs. Use approved reset processes. Do not access other people's accounts, servers or network equipment without authorisation.
How to use the Toolkit
The Course Toolkit at the end of the course holds printable, self-contained resources, adapted from the book's appendices and extended for this course:
| Toolkit item | Use it when |
|---|---|
| One-Page Checklist and Seven-Step Reference Chart | You are under pressure and want to follow the method line by line |
| Problem Investigation Worksheet and 5W1H Question Guide | You are gathering information in Step 1 |
| Problem Log Template | You are recording an incident from start to finish |
| Half-Split Isolation Worksheet | You are narrowing a fault along a chain of components |
| Diagnostic Commands Quick Reference | You need the right command on Windows, macOS or Linux |
| Root Cause Analysis Worksheet | You are running the 5 Whys or drawing a fishbone diagram |
| Escalation Handover Template | You are passing a problem to another person or tier |
| Case-Study Exercise Sheets | You want extra practice with fresh scenarios |
| Final Revision Guide | You are preparing for the Final Assessment |
| Course Glossary | You meet a term you are unsure of |
Print the checklist now and keep it beside you as you work through the modules. You will use the problem log template in the labs from Module 3 onwards, and in both capstones.
Before you start: troubleshooting is not a talent some people are born with. It is a habit of working in order. By the end of this course you will have practised that order often enough to rely on it, and to show others how you reached your answer.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Preface, About the Author, Course Structure, Chapter 3, Chapters 7, 8, 10 and 13 (safety guidance)
