Problem Categories and the Cost of Downtime
Where you are: Module 1 — Introduction to Troubleshooting · Lesson 1.3 · Based on Chapter 1 (§1.3–1.4) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Classify a problem into one of the book's six categories using its symptoms.
- Use the category to choose a sensible starting point, while keeping an open mind.
- Describe the costs of downtime to individuals and organisations, and estimate a simple downtime cost.
Watch: Problem Categories and the Cost of Downtime
The video sorts a fictional Monday-morning help-desk queue into six categories, shows how one symptom can have causes in several categories, and works out what a two-hour card-reader failure costs a small café. Keep these questions in mind:
- What does each category suggest you check first?
- Why is a category a starting point rather than a verdict?
- Which costs of downtime are easy to count, and which are not?
Six categories of problems
Most problems fall into a small number of categories. Recognising the category early helps the troubleshooter decide where to start. The book uses six:
| Category | Typical symptoms | Typical causes |
|---|---|---|
| Hardware | No power, overheating, noises, failed components | Loose connections, failed parts, physical damage |
| Network | No internet, slow connections, dropped calls | Cables, Wi-Fi, IP configuration, DNS, provider outages |
| Software | Crashes, error messages, freezing | Bugs, corrupt files, incompatible updates, settings |
| Account and access | Cannot log in, access denied | Expired passwords, locked accounts, permissions |
| User and process | Task fails or gives the wrong result | Training gaps, unclear procedures, human error |
| Environmental | Intermittent faults, damage | Heat, dust, moisture, power quality |
A few terms in that table, defined:
- IP configuration is the set of network settings (such as the device's address) that lets a device communicate on a network.
- DNS (Domain Name System) translates names such as example.com into the numerical addresses computers use.
- Permissions are the rules that decide which accounts may open, change or delete a file, folder or system.
- Intermittent faults come and go, which makes them hard to catch.
- Power quality refers to how clean and steady the electrical supply is; surges, dips and cuts are poor power quality.
Notice that the user and process category is not about blaming people. If a task keeps failing because nobody was shown the procedure, the fault lies in the training or the procedure, and that is where the fix belongs.
Using the category to choose a starting point
The category tells you which group of causes to check first. Consider this (fictional) help-desk queue:
| Ticket | Category | Start here |
|---|---|---|
| Laptop fan roaring; shuts down at random | Hardware | Heat, vents, fan |
| Cannot log in: "Account locked" | Account and access | Lockout policy; approved reset process |
| Whole second floor has no internet | Network | Shared equipment (switch, router) or the provider, because many devices are affected |
| Spreadsheet app crashes on opening | Software | The exact error message; recent updates |
| A new starter's invoices keep going out late | User and process | The procedure, and whether it was taught |
Account problems. Never ask a user to tell you their password, and never share passwords while troubleshooting. Locked or expired accounts are resolved through the organisation's approved reset process.
A starting point, not a verdict
Categories overlap, and one symptom can have causes in several of them. A laptop that shuts down at random could have a hardware cause (a clogged fan, a worn battery), an environmental cause (a hot room, dust in the vents), a software cause (a faulty driver update) or a user and process cause (being used on a soft bed that blocks the air vents). The category helps you decide where to look first; the evidence decides the answer.
The cost of downtime
Downtime is the time during which a system is unavailable or not working properly. The book is clear that every problem has a cost:
- For an individual: lost time and frustration.
- For an organisation: lost sales, idle staff, missed deadlines and damaged reputation.
- In some sectors: safety or regulatory consequences as well, for example where a failure affects patient care, transport or legal record-keeping.
The faster and more reliably a problem is solved, the lower that cost. This is why troubleshooting is one of the most valued practical skills in any technical role.
Name the category to choose where to start; count the cost to see why speed and reliability matter.
Worked example
(Fictional scenario; all figures are illustrative.) A small café's card reader stops working at 12:00 and is not working again until 14:00, across the lunchtime rush.
| Cost | Working | Amount |
|---|---|---|
| Lost sales | 20 customers leave because they cannot pay by card × £12 average spend | £240 |
| Idle staff time | 3 staff × 2 hours × £15 per hour | £90 |
| Reputation | Some customers do not return | Hard to measure |
| Total (counted) | £330 |
Three lessons follow from this simple calculation:
- Some costs are easy to count (sales, wages); others, such as reputation, are real but hard to measure, so the true cost is higher than the total.
- Cost grows with time. Had the fault been solved in one hour, the countable cost would have been roughly halved.
- Category guides speed. The reader's screen showed "No connection". That points to the network category, so the first checks are the reader's Wi-Fi or cable and the café's router, rather than the reader's hardware. Starting in the right place is one of the fastest ways to cut downtime.
Try it
Write one example problem for each of the six categories (this is the book's own review exercise). Use problems you have met, or invent realistic ones. For each, record:
- the symptom in one sentence,
- the category and your reason,
- where you would start, and
- one cost of the downtime, naming who bears it.
Then pick one of your problems and estimate its downtime cost for a small business using the café table as a model, labelling your figures as illustrative.
You have finished when all six categories have an example with a reason and a starting point, and one example has a costed estimate that separates countable costs from hard-to-measure ones.
Knowledge check
A user sees Access denied when opening a shared folder. Which category should you start with?
Wi-Fi in a meeting room drops several times a day, usually around lunchtime. Which category is a sensible place to look early, alongside the network itself?
Which of these is a cost of downtime to an organisation named in the book?
Why does the lesson call a category a starting point, not a verdict?
A café's card reader is down for two hours. What happens to the countable cost if the fault is solved in one hour instead?
Answers explained
- a — Access denied usually means the account lacks permissions. Nothing in the symptom suggests failed hardware, heat or a network outage.
- c — Intermittent faults with a time pattern often have environmental causes, such as interference from equipment used at certain times. Accounts, procedures and software do not usually follow a lunchtime pattern.
- b — The book lists lost sales, idle staff, missed deadlines and damaged reputation. The other options are not costs at all.
- d — A random shutdown, for example, could be hardware, environmental, software or how the device is used. Categories apply to every kind of problem (A), and evidence, not the user, decides (B).
- a — Lost sales and idle wages both grow with time, so halving the downtime roughly halves the countable cost.
Key takeaways
- Most problems fall into six categories: hardware, network, software, account and access, user and process, and environmental.
- The category suggests where to start; the evidence has the final word, because causes can sit in more than one category.
- Downtime costs individuals time and frustration, and costs organisations sales, staff time, deadlines, reputation and sometimes safety.
- The faster and more reliably a problem is solved, the lower its cost.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §1.3–1.4; glossary definitions (DNS, intermittent fault); security reminder from §10.4
