Escalation Guide
Purpose: Know when and how to escalate issues effectively.
When to Escalate
Escalation Criteria
Escalate When:
- Time Exceeded: Investigation taking longer than expected
- Expertise Needed: Issue requires expertise you don't have
- Business Impact: Issue affecting critical systems or users
- Resources Needed: Need additional resources or access
- Uncertainty: Unsure about next steps or solution
Don't Escalate Too Early
Try First:
- Follow systematic debugging process
- Use diagnostic tools
- Check documentation
- Review similar issues
- Test hypotheses
Don't Escalate Too Late
Escalate Before:
- Business impact increases
- Too much time wasted
- Customer satisfaction affected
- Issue becomes critical
Escalation Process
Step 1: Prepare Escalation
Gather Information:
- Problem description
- Symptoms observed
- Investigation done
- Evidence collected
- Hypotheses tested
- What you've tried
Step 2: Document Issue
Create Issue Report:
- Clear problem statement
- Symptoms and observations
- Investigation steps taken
- Evidence and logs
- Current hypothesis
- What you need help with
Step 3: Choose Escalation Path
Escalation Levels:
- Team Lead: For guidance and direction
- Subject Matter Expert: For specific expertise
- Engineering Manager: For resource allocation
- On-Call Engineer: For urgent issues
Step 4: Communicate Effectively
Communication:
- Be clear and concise
- Provide context
- Include evidence
- Ask specific questions
- Be open to guidance
Escalation Template
Issue Summary
Problem: [Clear, one-sentence description]
Impact: [Who/what is affected, severity]
Current Status: [What's happening now]
Investigation Done
Steps Taken:
- [Step 1]
- [Step 2]
- [Step 3]
Evidence Collected:
- [Logs, events, metrics]
- [Diagnostic output]
- [Configuration checked]
Hypotheses Tested:
- [Hypothesis 1] - [Result]
- [Hypothesis 2] - [Result]
- [Hypothesis 3] - [Result]
Current State
What Works:
- [What's functioning]
What Doesn't Work:
- [What's failing]
Error Messages:
- [Key error messages]
What I Need
Help With:
- [Specific question or guidance needed]
Resources Needed:
- [Access, tools, information]
Timeline:
- [When resolution needed]
Escalation Channels
Internal Escalation
Channels:
- Slack: #engineering-support
- Email: support@example.com
- Ticket System: Create ticket
- Phone: For urgent issues
External Escalation
For Customer Issues:
- Follow customer escalation process
- Notify customer of escalation
- Provide status updates
- Maintain communication
After Escalation
Stay Involved
Responsibilities:
- Provide additional information
- Test solutions
- Document resolution
- Learn from resolution
Document Resolution
Document:
- Root cause
- Resolution steps
- Lessons learned
- Prevention measures
Follow Up
Follow Up:
- Verify resolution
- Update runbooks
- Share knowledge
- Improve process
Escalation Best Practices
1. Be Prepared
Before Escalating:
- Gather all information
- Document investigation
- Prepare clear summary
- Know what you need
2. Be Specific
In Escalation:
- Clear problem statement
- Specific symptoms
- Concrete evidence
- Specific questions
3. Be Respectful
Communication:
- Respect others' time
- Be concise
- Provide context
- Be open to feedback
4. Learn and Improve
After Escalation:
- Understand resolution
- Learn from experience
- Update knowledge
- Improve skills
Common Escalation Scenarios
Scenario 1: Unknown Issue
Situation: Issue you've never seen before
Escalation:
- Document investigation
- Escalate to team lead or SME
- Request guidance
- Learn from resolution
Scenario 2: Complex Issue
Situation: Issue requires deep expertise
Escalation:
- Escalate to subject matter expert
- Provide all context
- Request specific help
- Learn from expert
Scenario 3: Urgent Issue
Situation: Critical business impact
Escalation:
- Escalate immediately
- Use urgent channel
- Provide clear impact
- Request priority
Scenario 4: Resource Constraint
Situation: Need additional resources
Escalation:
- Escalate to manager
- Explain resource need
- Provide business case
- Request allocation
Related Documentation
Remember: Escalation is not failure—it's using resources effectively. Escalate when it's the right thing to do.