For Cboe's data analytics services, should we invest in developing more sophisticated tools for professional traders or create more user-friendly interfaces to broaden the customer base?

Introduction

The trade-off we're examining today is whether Cboe's data analytics services should invest in developing more sophisticated tools for professional traders or create more user-friendly interfaces to broaden the customer base. This scenario touches on the classic product dilemma of depth versus breadth, specifically in the context of financial data services.

To address this, I'll walk through a structured analysis, starting with clarifying questions, then diving into product understanding, metrics identification, experiment design, and ultimately arriving at a recommendation with next steps.

Step 1

Clarifying Questions (3 minutes)

• Based on Cboe's market position, I'm thinking this decision could significantly impact our competitive edge. Could you share more about our current market share and main competitors in the data analytics space?

Why it matters: Helps assess the strategic importance of each option Expected answer: Strong position with professional traders, emerging competition in broader market Impact on approach: Would influence whether to defend core market or aggressively expand

• Considering our revenue model, I assume professional traders generate higher per-user revenue. Can you confirm our current revenue split between professional and retail users?

Why it matters: Informs the potential financial impact of broadening the user base Expected answer: 80% revenue from professionals, 20% from broader base Impact on approach: Would help quantify the potential upside of expanding vs. deepening

• Looking at user behavior, I'm curious about the engagement levels of our professional tools. What's the average daily active usage for our professional traders compared to our broader user base?

Why it matters: Indicates the value derived from each user segment Expected answer: High engagement from professionals, lower but growing engagement from broader base Impact on approach: Would influence the focus on retention vs. acquisition strategies

• Regarding technical feasibility, I'm wondering about the complexity of developing more sophisticated tools versus creating user-friendly interfaces. How do our engineering resources and capabilities align with these two directions?

Why it matters: Assesses the practical challenges of each option Expected answer: Strong capabilities in both areas, but sophisticated tools require more specialized expertise Impact on approach: Would impact timeline and resource allocation recommendations

• Considering our product roadmap, how urgent is this decision in relation to other strategic initiatives?

Why it matters: Helps prioritize this decision against other company objectives Expected answer: High priority, needs direction within next quarter Impact on approach: Would influence the depth of analysis and speed of implementation recommended