Should RingCentral prioritize adding new features to its video conferencing tool or focus on improving the reliability of existing core calling functions?

Introduction

The trade-off we're examining today is whether RingCentral should prioritize adding new features to its video conferencing tool or focus on improving the reliability of existing core calling functions. This scenario touches on the classic product management challenge of balancing innovation with stability. I'll approach this analysis by first clarifying the context, then diving into the product understanding, identifying key metrics, designing an experiment, and finally providing a recommendation with next steps.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking video conferencing has become a critical feature for unified communications platforms. Could you share how RingCentral's video conferencing tool is currently performing compared to core calling functions in terms of user adoption and revenue generation?

Why it matters: Helps prioritize resources based on product performance and market demand. Expected answer: Video conferencing growing faster but calling still generates more revenue. Impact on approach: Would influence whether to focus on expanding the growing segment or protecting the core business.

• Considering our user base, I'm assuming we have a mix of small businesses and enterprise clients. Can you provide a breakdown of our customer segments and their respective needs regarding video conferencing vs. core calling?

Why it matters: Different segments may have varying priorities, affecting our decision. Expected answer: Enterprise clients prioritize reliability, SMBs more interested in new features. Impact on approach: Would tailor our strategy to cater to the needs of our most valuable segments.

• From a technical standpoint, I'm curious about the current state of our infrastructure. What's the current uptime for our core calling functions, and how does it compare to industry standards?

Why it matters: Helps assess the urgency of reliability improvements. Expected answer: Slightly below industry average, causing some customer complaints. Impact on approach: If significantly below standards, would lean towards prioritizing reliability.

• Regarding our development resources, I'm wondering about our team's capacity and expertise. Do we have separate teams for video conferencing and core calling, or would this decision require reallocating resources?

Why it matters: Influences the feasibility and timeline of potential improvements. Expected answer: Shared resources with some specialization. Impact on approach: Would consider team structure in planning and execution of chosen strategy.