For BlackRock's Aladdin platform, should we prioritize adding new features or improving the user interface for existing clients?

Introduction

The trade-off we're examining today is whether to prioritize adding new features or improving the user interface for existing clients on BlackRock's Aladdin platform. This decision is crucial for maintaining Aladdin's market leadership in investment management software while ensuring client satisfaction and retention. I'll approach this analysis by first clarifying key aspects, then diving into the product understanding, metrics, and experimentation before providing a recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking Aladdin might be facing increased competition. Could you share insights on our current market position and any emerging competitors?

Why it matters: Helps prioritize between feature parity and UI improvements Expected answer: Strong position, but new entrants gaining traction Impact on approach: May lean towards new features if competition is feature-rich

• Considering our revenue model, I assume most income comes from long-term enterprise contracts. What's the typical contract length, and are we approaching a renewal cycle for major clients?

Why it matters: Influences urgency of UI improvements for retention Expected answer: 3-5 year contracts, with 30% up for renewal next year Impact on approach: Could prioritize UI if many renewals are imminent

• Looking at user behavior, I'm curious about adoption rates for new features versus engagement with existing ones. Do we have data on feature utilization across our client base?

Why it matters: Indicates whether new features or UI improvements would have more impact Expected answer: Mixed utilization, with some features underused Impact on approach: Might focus on UI to improve adoption of existing features

• Regarding technical feasibility, I'm wondering about the modularity of Aladdin's architecture. How challenging would it be to implement significant UI changes versus adding new features?

Why it matters: Affects resource allocation and timeline considerations Expected answer: Modular architecture, but legacy code in some areas Impact on approach: Could influence phasing of UI improvements vs. new features

• Thinking about our development capacity, what's our current team structure and bandwidth? Are we staffed more heavily in feature development or UX/UI roles?

Why it matters: Determines our ability to execute on either option effectively Expected answer: Balanced team, but recent focus on feature development Impact on approach: Might need to consider team reallocation or hiring