How can we explain the unexpected 40% increase in customer support tickets related to MBI's Visual Report Builder in the last two weeks?

Introduction

The unexpected 40% increase in customer support tickets related to MBI's Visual Report Builder over the past two weeks is a critical issue that demands immediate attention. This surge in support requests not only impacts customer satisfaction but also strains our support resources and potentially signals underlying problems with the product. To address this challenge, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term fixes and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Given the sudden spike, I'm wondering about recent changes. Have there been any updates to the Visual Report Builder in the last month?

Why it matters: Recent changes often correlate with support ticket increases. Expected answer: Yes, a minor update was released three weeks ago. Impact on approach: If confirmed, I'd focus on that update as a potential cause.

• Considering user segments, are we seeing this increase across all user types or is it concentrated in a specific group?

Why it matters: Helps narrow down if it's a universal issue or specific to certain users. Expected answer: The increase is primarily from new users. Impact on approach: If true, I'd investigate onboarding processes and new user experience.

• Looking at the nature of these tickets, are they clustered around specific functionalities within the Visual Report Builder?

Why it matters: Identifies if there's a particular feature causing issues. Expected answer: Many tickets relate to data integration and visualization options. Impact on approach: Would focus on these specific areas for immediate investigation.

• Regarding system performance, have there been any notable changes in server load or response times coinciding with this increase?

Why it matters: Performance issues often lead to increased support tickets. Expected answer: Some intermittent slowdowns have been reported. Impact on approach: Would prioritize backend performance analysis if confirmed.