Home / Companies / PagerDuty / Blog / November 2011

November 2011 Summaries

3 posts from PagerDuty

Filter
Month: Year:
Post Summaries Back to Blog
PagerDuty's team is actively participating in Movember, showcasing a strong sense of camaraderie and enthusiasm, even as they navigate the challenges of remote work. Ian, despite being based in Toronto, is effectively coordinating the team's efforts, with Simon initially leading and Lukasz impressively surpassing everyone. While James is noted for having the best mustache, Ali and John provide stiff competition, and Liz and Ana join to ensure the author doesn't rank last in facial hair growth. Baskar's contribution is humorously noted as being ample enough for the entire founding team, illustrating the playful peer pressure and team spirit surrounding the event. Donations to support their Movember efforts are encouraged through the provided links.
Nov 24, 2011 144 words in the original blog post.
PagerDuty is enhancing user support by integrating context-sensitive help throughout its product, leveraging its support team's efforts on the knowledge base. This ongoing initiative aims to identify and prioritize pages where users most frequently seek assistance, with the goal of continually expanding documentation. Users are encouraged to provide feedback via email to support the prioritization process.
Nov 21, 2011 92 words in the original blog post.
The third post in a series on enhancing service or system availability focuses on reducing the mean time to recovery (MTTR) by implementing a Standard Operating Procedure (SOP) for severe issues. This SOP acts as a generic, adaptable guide for addressing major failures, distinct from specific documented failure modes. Key elements include initiating a conference call with a designated Incident Commander to coordinate efforts, establishing a prepared communication channel like a dedicated phone line or platform such as Skype, and setting up a chat system for sharing data. Additionally, it is crucial to have diagnostic procedures ready and to designate a representative to liaise with business stakeholders, keeping them informed without disrupting the technical resolution process. This approach aims to streamline communication, reduce stress, and ensure a consistent and rapid response during critical incidents.
Nov 08, 2011 596 words in the original blog post.