Why has FactSet's Portfolio Analysis tool seen a 15% drop in daily active users over the past month?

Introduction

The recent 15% drop in daily active users for FactSet's Portfolio Analysis tool is a concerning trend that requires immediate attention. As we delve into this issue, we'll employ a systematic approach to identify, validate, and address 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 wondering if there have been any recent updates to the Portfolio Analysis tool. Have there been any significant feature changes or UI/UX modifications in the past 1-2 months?

Why it matters: Recent changes could directly impact user behavior and engagement. Expected answer: Yes, there was a major UI overhaul last month. Impact on approach: If confirmed, we'd focus on user experience and adoption issues.

• Considering user segments, I'm curious about the distribution of the drop. Is the 15% decrease uniform across all user types, or are certain segments more affected?

Why it matters: Helps identify if the issue is global or specific to certain user groups. Expected answer: The drop is more pronounced among less frequent users. Impact on approach: We'd investigate factors affecting casual users' engagement.

• Thinking about external factors, has there been any significant market volatility or economic events that might influence portfolio analysis needs?

Why it matters: External events could explain changes in user behavior. Expected answer: No major market events in the past month. Impact on approach: We'd focus more on internal factors if external influences are minimal.

• Regarding system performance, have there been any reported issues with tool speed, accuracy, or availability in the past month?

Why it matters: Technical issues could directly impact daily active usage. Expected answer: Some intermittent slowdowns reported in peak hours. Impact on approach: We'd prioritize investigating and resolving performance bottlenecks.