Cheat Sheet For Developers

  Sample 1: Initial Alert (Sent Immediately When an Incident is Detected) Subject:  URGENT: Service Disruption - Customer Login System Dear [Stakeholder Name(s)], We are currently experiencing a major service disruption affecting our customer login system. Customers are unable to access their accounts, and this is impacting our ability to process transactions. Our engineering team is actively investigating the issue and working to restore service. We will provide an update within the next 30 minutes. We understand the severity of this issue, and we are working hard to fix it. Regards, [Your Name] [Your Title] Sample 2: Ongoing Incident Update (Sent During a Prolonged Outage) Subject:  UPDATE: Customer Login System Disruption - Investigation Ongoing Dear [Stakeholder Name(s)], This email provides an update on the ongoing disruption to our customer login system. Current Status:  The issue persists. Customers are still unable to access their accounts. Timeline: 10:00 AM...

  I. Meeting Header: Meeting Title:  Clear and concise (e.g., "Project X Status Update," "Q3 Planning Meeting"). Date and Time:  Record the date and time the meeting took place. Location/Platform:  Indicate where the meeting was held (e.g., Conference Room A, Zoom). Attendees:  List the names and roles of everyone who attended. Absent:  List the names of key individuals who were invited but did not attend. Meeting Owner : Who was in charge of the meeting ? Document owner : Who is in charge of the documentation ? II. Key Discussion Points (Concise Summary): Purpose:  Briefly summarize the main topics discussed. Format:  Use bullet points for brevity. Content: Decision Points:  Clearly state any decisions that were made. Key Information:  Summarize any crucial information shared. Key Questions : Summarize the key questions that were raised. Open Issues:  Note any issues that remain unresolved. Stakeholder Focus:  Frame the summar...

  Phase 1: Connect (Build Relationships) Goal:  Establish personal connections with each team member and key stakeholders. Actions: One-on-Ones:  Schedule individual meetings with each team member. Purpose:  Get to know them, understand their background, career goals, and perspectives. Questions:  What are they working on? What are they excited about? What challenges are they facing? What are their strengths? Stakeholder Meetings:  Meet with key stakeholders (managers, product owners, other tech leads). Purpose:  Understand their expectations and priorities. Questions:  What are their key goals? How does the team's work impact their objectives? What are their concerns? Team Introductions:  Introduce yourself to the team as a group. Purpose:  Share your background, leadership style, and vision. Ask them : Ask them to share their expectations. Active Listening:  Pay attention to what people are saying (and not saying). Be Authentic: ...

  Phase 1: Assess (Understand the Situation) Identify:  What is the issue? What is happening? Scope:  How widespread is the issue? Is it affecting a small group of users, or is it a major outage? Impact:  What is the impact on users, the business, or the system? Is it critical, high, medium, or low? Severity : How severe is the issue ? Gather Information : What are the key details about the issue. Resources:  What resources (people, tools, systems) are available to address the issue? Prioritize:  Is this the most important thing you and your team should be working on right now? Phase 2: Act (Take Action to Resolve the Issue) Contain:  Take immediate action to contain the issue and minimize its impact. This could involve: Rolling back a recent change. Restarting a service. Taking a system offline temporarily. Diagnose:  Identify the root cause of the issue. Resolve:  Implement a solution to fix the problem. Test:  Ensure the fix works and...