What caused the sudden 30% decrease in API call volume for Bazaarvoice's Product Information Management (PIM) system last week?

Introduction

The sudden 30% decrease in API call volume for Bazaarvoice's Product Information Management (PIM) system last week is a critical issue that demands immediate attention and thorough analysis. As we delve into this problem, we'll follow a systematic approach to identify, validate, and address the root cause while considering both short-term fixes and long-term implications for the product.

Our analysis will cover issue identification, hypothesis generation, validation, and solution development. We'll start by clarifying the context, then rule out external factors before diving deep into the product's user journey, metric breakdown, and potential internal causes. Finally, we'll propose a structured plan for resolution and prevention.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking this could be related to a recent system update. Has there been any significant change to the PIM system or related infrastructure in the past two weeks?

Why it matters: Recent changes often correlate with sudden performance shifts. Expected answer: Yes, there was a minor update to the API gateway. Impact on approach: If confirmed, we'd focus on the update's impact on API calls.

• Considering the scale of the decrease, I'm wondering about potential data anomalies. Can you confirm that the 30% decrease is consistent across all data sources and measurement tools?

Why it matters: Ensures we're addressing a real issue, not a measurement error. Expected answer: The decrease is consistent across multiple monitoring systems. Impact on approach: If inconsistent, we'd investigate data collection methods first.

• Given the nature of PIM systems, I'm curious about seasonal patterns. Is this 30% decrease unusual compared to historical data for this time of year?

Why it matters: Helps distinguish between normal fluctuations and anomalies. Expected answer: This decrease is significantly larger than typical seasonal variations. Impact on approach: If seasonal, we'd focus on why this year's pattern is more pronounced.

• Considering potential user-driven changes, have there been any significant shifts in client behavior or onboarding of new major clients recently?

Why it matters: Large clients can significantly impact overall API usage. Expected answer: No major client changes in the past month. Impact on approach: If client-related, we'd analyze specific client usage patterns.

• Thinking about system dependencies, has there been any change in the performance or availability of systems that the PIM integrates with?

Why it matters: API call volume could be affected by issues in connected systems. Expected answer: No reported issues with integrated systems. Impact on approach: If confirmed, we'd investigate potential integration problems.