Why has client satisfaction with BNY's Eagle Investment Systems data management platform declined by 10 percentage points since the latest software update?

Introduction

The recent 10 percentage point decline in client satisfaction with BNY's Eagle Investment Systems data management platform following the latest software update 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 not only resolve the current satisfaction drop but also to implement measures that will prevent similar issues in the future and potentially improve overall client satisfaction.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking the update might have introduced usability issues. Have we seen an increase in support tickets or specific feature complaints since the update?

Why it matters: This helps pinpoint whether the satisfaction drop is tied to specific features or a broader usability problem. Expected answer: Yes, there's been a 30% increase in support tickets related to data visualization features. Impact on approach: If true, we'd focus on those specific features; if not, we'd look at broader system performance issues.

• Considering user segments, I'm wondering if the satisfaction drop is uniform across all client types. Can you provide a breakdown of satisfaction scores by client size or industry?

Why it matters: This helps identify if the issue is more pronounced for certain user groups, allowing for targeted solutions. Expected answer: Enterprise clients show a 15% drop, while smaller clients only show a 5% drop. Impact on approach: A significant difference would lead us to investigate enterprise-specific features or scaling issues.

• Thinking about the update process, I'm curious about the rollout strategy. Was this a phased rollout or a simultaneous update for all clients?

Why it matters: The rollout strategy can impact user adoption and reveal potential implementation issues. Expected answer: It was a simultaneous rollout to all clients over a weekend. Impact on approach: A simultaneous rollout might indicate insufficient testing or preparation, leading us to examine our update processes.

• Considering the nature of the update, I'm wondering about the scope of changes. Did this update introduce major new features or was it primarily focused on backend improvements?

Why it matters: The scope of changes can help us understand if the issue is related to new functionality or disruption of existing workflows. Expected answer: The update included both a major UI overhaul and significant backend performance enhancements. Impact on approach: If it's a major update, we'd focus on change management and user education; if minor, we'd look more closely at unexpected technical issues.

• Given the importance of data accuracy in financial systems, I'm concerned about potential data integrity issues. Have there been any reported discrepancies in data output or processing since the update?

Why it matters: Data integrity is crucial for financial systems, and any issues could severely impact client trust and satisfaction. Expected answer: No significant data discrepancies have been reported, but there have been delays in data processing. Impact on approach: Data integrity issues would require immediate technical intervention, while processing delays might indicate performance optimization needs.