How can we explain the unexpected 20% increase in customer support tickets related to PandaDoc's template library functionality in the last two weeks?

Introduction

The unexpected 20% increase in customer support tickets related to PandaDoc's template library functionality in the last 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 our 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)

• Looking at the timing, I'm thinking there might have been a recent update. Has there been any change to the template library functionality in the past month?

Why it matters: Recent changes often correlate with sudden metric shifts. Expected answer: Yes, a minor update was released three weeks ago. Impact on approach: If confirmed, we'd focus on the update's specifics and rollout process.

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

Why it matters: Helps identify if the issue is localized or widespread. Expected answer: The increase is primarily from new users. Impact on approach: If true, we'd examine onboarding processes and new user experiences.

• Thinking about the nature of the tickets, I'm wondering about the content. What are the most common issues reported in these support tickets?

Why it matters: Reveals specific pain points within the template library functionality. Expected answer: Users are reporting difficulty in customizing templates. Impact on approach: This would guide us to focus on the template customization feature.

• Considering potential system issues, I'm curious about our monitoring. Have there been any detected anomalies in system performance or uptime related to the template library?

Why it matters: Rules out or confirms technical issues as a root cause. Expected answer: No significant anomalies detected. Impact on approach: If true, we'd shift focus from technical issues to user experience and functionality.