Should GoTo prioritize adding new features to GoToMeeting to increase user engagement or focus on optimizing the existing interface for better ease of use?

Introduction

The trade-off we're examining today is whether GoTo should prioritize adding new features to GoToMeeting to increase user engagement or focus on optimizing the existing interface for better ease of use. This scenario touches on the classic product management challenge of balancing innovation with usability. I'll analyze this trade-off by considering user needs, business objectives, and technical constraints.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about GoToMeeting's current market position. Could you share how we're performing against our main competitors in terms of market share and user satisfaction?

Why it matters: Helps understand if we're in a defensive or offensive position. Expected answer: We're holding steady but facing increased pressure from newer entrants. Impact on approach: If we're losing ground, it might justify more aggressive feature development.

• Business Context: Based on our revenue model, I assume most of our income comes from business subscriptions. Is this correct, and are there any shifts in our revenue streams we should consider?

Why it matters: Aligns our strategy with our primary revenue drivers. Expected answer: Yes, business subscriptions are our main revenue source. Impact on approach: If true, we'd prioritize features that appeal to business users and IT decision-makers.

• User Impact: I'm curious about our user segments. Are we seeing different engagement patterns between enterprise and SMB users?

Why it matters: Helps tailor our approach to the most valuable or at-risk segments. Expected answer: Enterprise users engage more frequently but SMBs are growing faster. Impact on approach: Might lead to a two-pronged strategy addressing different segment needs.

• Technical: Considering our current architecture, how challenging would it be to implement major new features versus optimizing the existing interface?

Why it matters: Assesses the feasibility and resource requirements of each option. Expected answer: New features would require significant backend work, while UI optimization is more straightforward. Impact on approach: Could lean towards UI optimization if new features are too resource-intensive.

• Timeline: Is there a specific market event or competitor move driving the urgency of this decision?

Why it matters: Helps prioritize short-term tactics versus long-term strategy. Expected answer: A major competitor is launching a revamped product in Q4. Impact on approach: Might necessitate a faster, more targeted response in our approach.