Support Operations, Troubleshooting, and Service Delivery
Scope
This domain covers how support is delivered: intake, triage, documentation, escalation, and closure. It rewards process discipline over heroic fixes.
Concepts to master
Understand the ticket lifecycle (open → triage → diagnose → resolve → verify → close), priority vs severity, SLA/OLA, knowledge base use and contribution, asset management, change management, and escalation tiers. Know the troubleshooting methodology: identify the problem, establish a theory, test the theory, establish a plan of action, implement, verify full functionality, document. Understand remote support tools and root-cause analysis.
Traps
- Fixing the symptom without documenting the root cause.
- Skipping verification; questions reward confirming with the user after a fix.
- Confusing severity (impact) with priority (order of work, influenced by business context).
- Making unauthorized changes during an incident instead of following change control.
- Closing a ticket without a resolution note.
Rule of thumb - one change at a time
Change one variable, test, record the result. Multiple simultaneous changes make the cause unknowable and the fix unverifiable.
Worked example
A ticket reads "email down for whole floor." Severity is high (many users, core service). Triage: check the mail server status page and the network link for that floor before touching individual mailboxes. If the floor switch is down, escalate to networking with evidence; document the timeline and the resolution.