Investigating like a pro: narrowing a problem down
▶ Start the interactive lesson
"The CRM is broken!" Five people message you in two minutes. One says it's slow, one says it won't log in, one says it's fine for them. Panic would be: restart things and hope. Sam pulls up a notepad instead: "We're going to shrink this problem until there's only one place left for it to hide."
1. Define it precisely
Turn "it's broken" into facts: who is affected, what exactly fails (error message?), where (site, VLAN, Wi-Fi or wired), when it started, and what changed around then.
2. Scope it: what works and what doesn't
Compare a working case with a failing one: same app from another site? Another app from the same site? Same user on another PC?
3. Divide and conquer
Work through the layers or along the path. Bottom-up: link lights and errors → IP and gateway → DNS → port open? → app response.
4. Prove it, fix it, write it down
Make one change at a time, and test after each. If it didn't help, undo it.
Key points
- Define it: who, what, where, when, and what changed.
- Scope it by comparing working and failing cases. The pattern points to the place.
- Divide and conquer: test bottom-up or split the path in halves; capture at the edges.
- Prove with evidence, change one thing at a time, and write it up.
Words you'll learn
Problem definition · Baseline / known-good comparison · Divide and conquer / half-split · Bottom-up troubleshooting · Root cause · Post-incident review / PIR