Giving constructive criticism is crucial for team growth, but it can be challenging. This guide provides a structured approach and script to deliver feedback effectively while maintaining a positive working relationship.

Difficult Feedback Site Reliability Engineers

As an SRE, you’re responsible for ensuring system reliability and performance. This often involves identifying and addressing issues, which includes providing feedback to your team. Giving difficult feedback to a direct report is a critical, yet often avoided, skill. This guide will equip you with the tools and strategies to handle these conversations professionally and constructively.

Understanding the Core Issue: The discomfort often stems from a fear of damaging the relationship, causing defensiveness, or simply not knowing how to deliver the message effectively. However, avoiding the conversation only allows the problem to fester and impacts team performance and morale.

1. Preparation is Paramount:

• Specificity is Key: Don’t be vague. Instead of saying “Your incident response wasn’t good,” say “During the recent database outage, the lack of immediate escalation to on-call engineers prolonged the resolution time by 30 minutes.” Document specific instances.

• Focus on Behavior, Not Personality: Frame feedback around actions and their impact, not character traits. Instead of “You’re disorganized,” try “I’ve noticed several Missed Deadlines on the automation project, which has impacted our velocity.”

• Consider Intent: While the impact is what matters, try to understand why the behavior occurred. Is it a lack of training, unclear expectations, or a systemic issue?

• Choose the Right Setting: A private, one-on-one meeting is essential. Avoid public criticism at all costs.

• Anticipate Reactions: Prepare for defensiveness, denial, or even anger. Have responses ready that acknowledge their feelings while reiterating the importance of the feedback.

2. High-Pressure Negotiation Script:

This script assumes the issue is related to performance – specifically, a lack of proactive monitoring and a reactive approach to incidents. Adjust it to fit the specific situation.

You (SRE Lead): “Hi [Direct Report’s Name], thanks for meeting with me. I wanted to discuss your recent performance, specifically regarding incident response and proactive system monitoring. I appreciate your hard work and dedication to the team.”

Direct Report: (Likely response: “Okay, what’s this about?” or similar)

You (SRE Lead): “I’ve observed a pattern where we’re often reacting to incidents rather than preventing them. For example, during the [Specific Incident Date] outage, the initial response involved [Specific Action/Omission]. This resulted in [Specific Negative Impact, e.g., increased downtime, customer impact]. My concern is that a more proactive approach to monitoring and alerting could have mitigated this.”

Direct Report: (Potential responses: “I was following the established procedures,” “I didn’t think it was that serious,” “I was overloaded with other tasks.”) Pause and actively listen. Acknowledge their perspective.

You (SRE Lead): “I understand you were following procedures, and I appreciate you managing a heavy workload. However, the current procedures aren’t always sufficient, and we need to be willing to adapt and escalate when necessary. The impact of the outage extended beyond just the immediate issue; it affected [Specific Stakeholders/Systems]. My expectation is that you’ll actively review alerts, investigate anomalies, and escalate concerns promptly, even if you’re unsure.”

Direct Report: (Potential response: “What do you want me to do differently?”)

You (SRE Lead): “Moving forward, I’d like you to focus on [Specific Actionable Steps, e.g., reviewing alert thresholds, participating in blameless postmortems, proposing improvements to monitoring dashboards]. I’m happy to provide training and support to help you with this. Let’s schedule a follow-up in [Timeframe, e.g., two weeks] to discuss your progress. I’m confident you can improve in this area, and I’m here to help you succeed.”

Direct Report: (Potential response: Agreement, further questions, or continued resistance.)

You (SRE Lead): (Regardless of response, reiterate your commitment to their success and the importance of the changes. Document the conversation and agreed-upon actions.)

3. Technical Vocabulary:

• SLO (Service Level Objective): A target level of service reliability.

• SLI (Service Level Indicator): A metric used to measure SLOs.

• Postmortem (Blameless Postmortem): A structured analysis of incidents to identify root causes and prevent recurrence.

• Alert Fatigue: A state of desensitization to alerts, often leading to missed critical issues.

• Runbook: A documented procedure for responding to specific incidents.

• Observability: The ability to understand the internal state of a system based on its external outputs.

• Telemetry: Data collected from systems to monitor their health and performance.

• On-Call Rotation: A schedule for engineers to respond to incidents outside of regular working hours.

• Incident Commander: The person responsible for coordinating incident response efforts.

• MTTR (Mean Time To Resolution): The average time it takes to resolve an incident.

4. Cultural & Executive Nuance:

• Empathy is Crucial: Remember that receiving feedback can be difficult. Acknowledge their feelings and show that you understand their perspective.

• Focus on Growth: Frame the feedback as an opportunity for development and improvement. Connect it to their career goals.

• Executive Alignment: Ensure your feedback aligns with company values and performance expectations. If the issue is significant, consider involving HR or your manager.

• Documentation is Key: Document the feedback, agreed-upon actions, and follow-up dates. This provides a clear record and protects both you and the employee.

• Follow-Up is Essential: Regularly check in on progress and provide ongoing support. This demonstrates your commitment to their success and reinforces the importance of the feedback.

5. Common Pitfalls to Avoid:

• Public Shaming: Never criticize an employee in front of others.

• Personal Attacks: Focus on behavior, not personality.

• Vagueness: Be specific and provide concrete examples.

• Ignoring Emotions: Acknowledge and validate the employee’s feelings.

• Lack of Follow-Up: Ensure the feedback leads to tangible changes and improvements.”

},

“meta_description”: “A comprehensive guide for Site Reliability Engineers (SREs) on how to effectively deliver difficult feedback to direct reports, including a script, technical vocabulary, and cultural considerations.