How can we explain the recent 30% increase in customer support tickets related to M1 (Financial Software)'s portfolio rebalancing functionality?

Introduction

The recent 30% increase in customer support tickets related to M1's portfolio rebalancing functionality 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 feature. To address this effectively, 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 be a recent change in the portfolio rebalancing algorithm. Has there been any update to the rebalancing logic in the past month?

Why it matters: Recent changes often correlate with spikes in support tickets. Expected answer: Yes, there was a minor update to improve efficiency. Impact on approach: If confirmed, we'd focus on the update's impact on user experience.

• Considering user segments, I'm curious about the distribution of these tickets. Are they concentrated among a specific user group, such as new users or those with larger portfolios?

Why it matters: Helps identify if the issue is widespread or localized to a particular segment. Expected answer: The increase is seen across all user segments. Impact on approach: A widespread issue would suggest a systemic problem rather than a segment-specific one.

• Given the nature of financial software, I'm wondering about any recent market volatility. Have there been any significant market events that could have triggered more rebalancing activity?

Why it matters: External factors can sometimes explain sudden changes in user behavior. Expected answer: No major market events in the past month. Impact on approach: If confirmed, we'd focus more on internal factors rather than external triggers.

• Thinking about system performance, has there been any change in the response time or success rate of the rebalancing API calls?

Why it matters: Performance issues often lead to increased support tickets. Expected answer: No significant changes in API performance metrics. Impact on approach: If performance is stable, we'd look more closely at UX or communication issues.