Why has customer satisfaction for BeyondTrust's Remote Support product declined by 10 points since the latest software update?

Introduction

The recent 10-point decline in customer satisfaction for BeyondTrust's Remote Support product following the latest software update is a critical issue that demands immediate attention. This analysis will systematically investigate potential root causes, validate hypotheses, and propose targeted solutions to address the satisfaction drop while considering both short-term fixes and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking this might be directly related to the software update. Could you provide more details on when exactly the update was rolled out and when the satisfaction decline was first noticed?

Why it matters: Establishing a clear timeline helps correlate the update with the satisfaction drop. Expected answer: The update was released 2-3 weeks ago, and the satisfaction decline was observed shortly after. Impact on approach: A close temporal relationship would strengthen the focus on update-related issues.

• Considering the nature of remote support software, I'm wondering about the scale of the decline across different user segments. Have you noticed any patterns in the satisfaction drop among various customer types or sizes?

Why it matters: Identifying affected segments can pinpoint specific features or use cases causing issues. Expected answer: Enterprise customers show a more significant decline compared to small businesses. Impact on approach: This would guide our investigation towards features more commonly used by larger organizations.

• Given the importance of performance in remote support tools, I'm curious about any changes in system metrics post-update. Have there been any noticeable shifts in key performance indicators like connection speed or latency?

Why it matters: Performance issues could directly impact user satisfaction. Expected answer: Some users have reported increased latency during remote sessions. Impact on approach: This would prioritize technical performance analysis in our root cause investigation.

• Thinking about the update process itself, I'm interested in understanding the rollout strategy. Was this a phased rollout or a simultaneous update for all users?

Why it matters: The rollout strategy can affect the distribution and severity of potential issues. Expected answer: It was a phased rollout over two weeks. Impact on approach: This information would help in analyzing whether later phases showed improved satisfaction, indicating potential fixes or adaptations mid-rollout.