Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

SEI Investments

What factors are contributing to the 20% increase in support tickets for SEI Investments's Global Wealth Services in the last month?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem Solving Strategic Thinking Financial Services Wealth Management FinTech Product Strategy Data Analysis Root Cause Analysis Customer Support Financial Services
Product Management Root Cause Analysis Question: Investigating support ticket increase for wealth management platform

Introduction

The recent 20% increase in support tickets for SEI Investments's Global Wealth Services is a critical issue that demands immediate attention. This surge could indicate underlying problems affecting user satisfaction and potentially impacting the company's reputation and bottom line. 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.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking there might be a recent product update. Has there been any significant change to the Global Wealth Services platform in the last 1-2 months?

Why it matters: Recent changes often correlate with support ticket increases. Expected answer: Yes, a major update was released. Impact on approach: If yes, we'll focus on the update's features and potential issues.

  • Considering user segments, I'm curious about the distribution of these tickets. Are we seeing an increase across all user types, or is it concentrated in specific segments?

Why it matters: Helps identify if the issue is widespread or segment-specific. Expected answer: The increase is primarily from institutional clients. Impact on approach: If segment-specific, we'll tailor our investigation to that user group.

  • Given the nature of wealth services, I'm wondering about any recent market volatility. Have there been any significant market events that might have triggered increased user activity or concerns?

Why it matters: External factors can drive support ticket volume. Expected answer: Some market volatility, but nothing extraordinary. Impact on approach: If significant events occurred, we'd consider their impact on user behavior.

  • Thinking about system performance, I'm curious about any recent changes in our infrastructure. Have there been any updates to our backend systems or data providers in the last month?

Why it matters: Backend changes can sometimes cause unexpected issues for users. Expected answer: No major infrastructure changes. Impact on approach: If changes occurred, we'd investigate potential system-level issues.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025