How can we explain the unexpected 20% increase in support tickets related to NinjaOne's network discovery tool in the last two weeks?

Introduction

The unexpected 20% increase in support tickets related to NinjaOne's network discovery tool over the past two weeks is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term fixes and long-term strategic implications.

To tackle this problem, I'll follow a structured approach that covers issue identification, hypothesis generation, validation, and solution development. My goal is to uncover the underlying factors contributing to this surge in support tickets and propose actionable steps to resolve the issue.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might have been a recent update or change to the network discovery tool. Has there been any significant update or feature release in the past month?

Why it matters: Recent changes often correlate with spikes in support tickets. Expected answer: Yes, there was a minor update two weeks ago. Impact on approach: If confirmed, we'd focus on the update's impact and potential rollback options.

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

Why it matters: Helps identify if the issue is isolated to a particular segment or widespread. Expected answer: The increase is seen across various user segments, but with a higher concentration among enterprise clients. Impact on approach: If concentrated, we'd tailor our solution to that specific user group; if widespread, we'd look at more systemic issues.

• Thinking about the nature of the tickets, I'm wondering about the specific issues being reported. What are the top 3 most common complaints or problems mentioned in these tickets?

Why it matters: Identifies patterns in the reported issues, guiding our root cause analysis. Expected answer: Slow discovery process, inaccurate results, and integration issues with other tools. Impact on approach: This would help us narrow down whether the problem is performance-related, accuracy-related, or integration-related.

• Considering external factors, has there been any significant change in network environments or technologies that our tool interacts with recently?

Why it matters: External changes could impact our tool's functionality without any internal changes. Expected answer: No major industry-wide changes, but some clients have been upgrading their network infrastructure. Impact on approach: If confirmed, we'd need to investigate compatibility issues with new network technologies.