How can we explain the 25% increase in customer support tickets related to Fabric ( Business/Productivity Software)'s document sharing feature over the past quarter?

Introduction

A 25% increase in customer support tickets related to Fabric's document sharing feature over the past quarter is a significant issue that demands immediate attention. This surge in support requests not only impacts user satisfaction but also strains our support resources and potentially signals underlying problems with the feature. I'll approach this analysis systematically, focusing on identifying the root cause, validating hypotheses, and developing both short-term fixes and long-term solutions.

Step 1

Clarifying Questions (3 minutes)

• Given the sudden increase, I'm wondering about recent changes. Have there been any significant updates to the document sharing feature in the last 3-4 months?

Why it matters: Recent changes could directly correlate with the increase in support tickets. Expected answer: Yes, we implemented a new file format support. Impact on approach: If true, I'd focus on the new file format as a potential cause.

• Considering user segments, I'm curious about the distribution. Are these tickets coming from a specific user group or evenly spread across our user base?

Why it matters: Helps identify if the issue is widespread or isolated to certain users. Expected answer: Mostly from enterprise customers. Impact on approach: I'd investigate enterprise-specific integrations or use cases.

• Thinking about the nature of the tickets, what are the top 3 issues users are reporting regarding document sharing?

Why it matters: Pinpoints specific areas of the feature causing problems. Expected answer: Permissions issues, slow loading times, and compatibility problems. Impact on approach: I'd prioritize investigating these specific areas in our analysis.

• Reflecting on our metrics, has there been any change in how we categorize or track support tickets in the last quarter?

Why it matters: Ensures we're comparing apples to apples in our data. Expected answer: No changes in tracking methods. Impact on approach: If changed, we'd need to re-evaluate our baseline metrics.