Writing it down: ticket notes and knowledge articles
▶ Start the interactive lesson
You pick up a ticket from yesterday. The only note says: "Looked at it. Still broken." You have no idea what was tried. You call the user, who sighs: "I've already done all this with your colleague." Priya: "Write notes for the person who picks it up at 3am. One day that's you."
Good ticket notes
Write what was reported, what you checked (and the results), what you changed, and the next step. Facts, times, error messages copied exactly.
Knowledge articles
When you solve something new, write a short KB article: a title written as the symptom users describe ("Outlook says 'Cannot start'"), who it affects, the cause, numbered steps, how to check it worked, and the date and owner.
Other documents you'll keep
Runbooks (step-by-step procedures, e.g. "new starter setup"), network diagrams, the asset register, and records of IP addresses (IPAM).
Key points
- Ticket notes: reported, checked + results, changed, next step. Copy errors exactly.
- KB articles: title = symptom, applies to, cause, numbered steps, how to verify, owner and review date.
- Also: runbooks, diagrams, asset register, IPAM. Keep them dated.
Words you'll learn
Work notes / ticket history · Knowledge base (KB) article · Runbook / SOP · IPAM