Should Cockroach Labs prioritize improving CockroachDB's scalability features or focus on enhancing its SQL compatibility to attract more enterprise customers?

Introduction

The trade-off between improving CockroachDB's scalability features and enhancing its SQL compatibility presents a critical decision point for Cockroach Labs. This scenario encapsulates the classic product management challenge of balancing technical excellence with market demands. I'll analyze this trade-off by examining the product context, potential impacts, key metrics, and experimental approaches to inform a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on our current market position, I'm thinking enterprise customers might be our primary growth driver. Could you share more about our current customer segmentation and which segments are showing the most growth potential?

Why it matters: Helps prioritize features based on target customer needs Expected answer: Enterprise segment growing fastest, but mid-market showing potential Impact on approach: Would influence whether to focus on advanced scalability or broader SQL compatibility

• Considering our product roadmap, I'm assuming we have ongoing initiatives for both scalability and SQL compatibility. Can you provide context on the current state of these features and any specific pain points we're addressing?

Why it matters: Identifies existing momentum and technical debt Expected answer: Scalability is strong but SQL compatibility lags behind competitors Impact on approach: Might suggest prioritizing SQL compatibility to close the gap

• Looking at our competitive landscape, I'm thinking our unique selling proposition might be influencing this decision. How do we currently differentiate from other distributed SQL databases in the market?

Why it matters: Helps align decision with overall product strategy Expected answer: Strong in scalability, but losing deals due to SQL compatibility issues Impact on approach: Could justify focusing on SQL compatibility to remove adoption barriers

• Considering resource allocation, I'm curious about our engineering team's expertise. How is our team currently structured in terms of scalability vs. SQL compatibility expertise?

Why it matters: Assesses feasibility and potential trade-offs in development capacity Expected answer: Stronger expertise in scalability, would need to ramp up SQL compatibility team Impact on approach: Might influence timeline and resource allocation for chosen priority

• Given the potential impact on our product positioning, I'm wondering about our sales team's feedback. What are the most common objections or requests they're hearing from enterprise prospects?

Why it matters: Provides direct market feedback to inform prioritization Expected answer: SQL compatibility is a frequent objection, but scalability is a key selling point Impact on approach: Could help balance short-term sales needs with long-term product vision