Behind the desk: root causes, safe changes and known fixes
▶ Start the interactive lesson
The warehouse Wi-Fi has dropped every Monday at 9am for a month. Each time, someone restarts the access point and closes the incident. Each Monday, it happens again. Priya opens a new record: "We keep fixing the symptom. Today we find the cause, and when we fix it properly, we'll change it safely."
Find the cause, not just the symptom
Fixing an incident gets people working. Finding why it happened stops it coming back. That investigation is a problem record.
Workarounds and known errors
While the real fix is being planned, you might find a workaround: "restart the AP at 8:55 on Mondays". It's not a fix, but it reduces the pain.
Changing things safely
Moving the access point is a change. Changes are where outages come from, so they're controlled. Standard changes are low-risk and pre-approved (like a password policy reset). Normal changes are assessed and approved, often by a change advisory board (CAB). Emergency changes go through a fast-track approval when something is broken right now.
The knowledge base
A knowledge base (KB) holds short articles: symptom, cause, fix. Good desks search it before guessing, and write an article whenever they solve something new.
Key points
- Problem = finding the root cause of repeating incidents (try the 5 Whys). A workaround reduces pain until the fix; cause + workaround = known error.
- Changes are standard (pre-approved), normal (assessed, often by a CAB) or emergency (fast-tracked). All need a rollback plan.
- A knowledge base stores fixes; an asset register / CMDB stores what kit you have.
Words you'll learn
Problem management · 5 Whys (root cause analysis) · Workaround · Known error · Standard change · Normal change · Emergency change · CAB (change advisory board) · Rollback / back-out plan · Knowledge base (KB) · Asset register / CMDB