Turn “it’s broken” into a testable symptom.
Capture the task, exact error, timing, scope and safety implications before guessing at a cause.
A practical guide for IT support staff who need to turn a vague report into a safe next action—without fixing somebody’s theory, losing evidence or creating the next incident.
Leanpub edition: PDF and EPUB · DRM-free · free updates · from US$9.99

Useful default: What do we know, how do we know it, and what is the smallest safe test that could prove us wrong?
New support staff, service-desk analysts and junior systems engineers do not need another commands list. They need a reliable way to clarify impact, find the useful boundary, test safely and hand over an honest record when the next step needs more authority.
Capture the task, exact error, timing, scope and safety implications before guessing at a cause.
Prefer a narrow, reversible comparison over a restart that restores service and destroys the useful evidence.
Escalation is not failure. It is the right move when the next safe step needs access, authority or a second set of eyes.
The method does not slow urgent work down. It helps distinguish the useful kind of fast from random activity with elevated privileges.
The complete guide uses three contrasting scenarios to show how the same decision habits change pace and response:
Includes worked scenarios, decision drills, an evidence and test-selection worksheet, a handover record and a one-page desk reference.