Introduction
Planet Labs' recent spike in customer support tickets related to data delivery delays for its Basemap product requires immediate attention. This issue not only impacts customer satisfaction but also threatens the core value proposition of timely earth observation data. I'll approach this problem systematically, focusing on identifying the root cause, validating hypotheses, and developing both short-term fixes and long-term solutions.
This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.
Step 1
Clarifying Questions (3 minutes)
Why it matters: Recent changes often correlate with performance issues. Expected answer: Yes, a new algorithm was deployed last week. Impact on approach: If confirmed, we'd focus on the new algorithm's performance and rollback options.
Why it matters: Data acquisition is the first step in our pipeline and could be a bottleneck. Expected answer: No significant issues reported with the satellite constellation. Impact on approach: If confirmed, we'd shift focus to downstream processes in the data pipeline.
Why it matters: Helps determine if the issue is related to specific ground stations or global infrastructure. Expected answer: The delays are primarily affecting customers in the Asia-Pacific region. Impact on approach: If regional, we'd investigate region-specific factors like ground station capacity or local network issues.
Why it matters: Could indicate issues with our tiered service infrastructure or SLA management. Expected answer: Enterprise customers are reporting fewer delays than standard tier customers. Impact on approach: If tiered, we'd investigate our service prioritization mechanisms and capacity allocation.
Practice similar questions
Subscribe to access the full answer