How can PagerDuty improve its mobile app to streamline incident response on-the-go?

Introduction

To improve PagerDuty's mobile app for streamlined incident response on-the-go, we need to focus on enhancing user experience, optimizing key features, and leveraging mobile-specific capabilities. I'll outline a strategic approach to address this challenge, starting with clarifying questions, then moving through user segmentation, pain point analysis, solution generation, and finally, evaluation and measurement.

Step 1

Clarifying Questions

• Looking at PagerDuty's position in the incident management space, I'm curious about the current user base composition. Could you provide insights into the breakdown between enterprise and SMB customers using the mobile app?

Why it matters: This helps tailor our improvements to the most impactful user segment. Expected answer: 70% enterprise, 30% SMB Impact on approach: Focus on enterprise-grade features and scalability if heavily enterprise-skewed.

• Considering the critical nature of incident response, I'm wondering about the current usage patterns of the mobile app. What percentage of incidents are currently being managed primarily through the mobile interface versus desktop?

Why it matters: Determines the importance and potential impact of mobile app improvements. Expected answer: 40% mobile, 60% desktop Impact on approach: Higher mobile usage would prioritize more comprehensive mobile features.

• Given the evolving landscape of DevOps and IT operations, I'm interested in understanding the key competitors in the mobile incident response space. Who are our main competitors, and what unique features are they offering in their mobile apps?

Why it matters: Helps identify gaps in our offering and potential areas for differentiation. Expected answer: Competitors like OpsGenie and VictorOps offering features like voice commands or AR incident visualization. Impact on approach: Would focus on innovative features to maintain competitive edge.

• Thinking about the product lifecycle, I'm curious about the current state of the mobile app. How long has the current version been in the market, and what are the primary metrics driving this improvement initiative?

Why it matters: Informs whether we need a major overhaul or incremental improvements. Expected answer: Current version is 2 years old, with declining engagement rates and increased time-to-resolution as key metrics. Impact on approach: Would focus on user re-engagement and core functionality optimization.