Why has Jobber's online booking feature seen a 15% drop in usage over the past month?

Introduction

Jobber's online booking feature has experienced a 15% drop in usage over the past month, signaling a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for the product.

I'll approach this problem by first clarifying key details, ruling out external factors, and then diving deep into the product ecosystem, user journey, and relevant metrics. From there, I'll generate data-driven hypotheses, conduct root cause analysis, and propose a comprehensive plan for validation and resolution.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might be a seasonal component. Has this 15% drop been compared to the same period last year?

Why it matters: Seasonal fluctuations could explain the change without indicating a deeper problem. Expected answer: No significant seasonal pattern observed in previous years. Impact on approach: If seasonal, we'd focus on optimizing for known patterns rather than troubleshooting.

• Considering user segments, I'm curious about the distribution of this drop. Is the 15% decrease uniform across all user types, or is it concentrated in specific segments?

Why it matters: Identifying affected segments helps narrow down potential causes and tailor solutions. Expected answer: The drop is more pronounced among small business users. Impact on approach: We'd prioritize investigating factors specific to small business needs and usage patterns.

• Thinking about recent changes, have there been any updates to the booking feature or related systems in the past 1-2 months?

Why it matters: Recent changes often correlate with sudden metric shifts. Expected answer: A minor UI update was rolled out 6 weeks ago. Impact on approach: We'd scrutinize the UI changes and their potential impact on user behavior.

• Regarding data integrity, has there been any change in how we track or define "usage" for the online booking feature?

Why it matters: Ensures we're comparing apples to apples and not chasing a non-existent problem. Expected answer: No changes to tracking or definitions. Impact on approach: Confirms the issue is real and not a data anomaly, focusing our efforts on actual usage patterns.