Should Ancestry prioritize expanding its DNA matching features or focus on improving the accuracy of existing family tree suggestions to enhance user engagement?

Introduction

The trade-off between expanding Ancestry's DNA matching features and improving the accuracy of existing family tree suggestions presents a critical decision point for enhancing user engagement. This scenario involves balancing innovation with refinement, each path offering distinct benefits and challenges. I'll analyze this trade-off by examining product understanding, metrics, experimentation, and decision frameworks to arrive at a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking DNA feature expansion might be a competitive differentiator. Could you share insights on how our DNA matching features currently compare to competitors?

Why it matters: Helps assess the urgency of feature expansion vs. improvement Expected answer: We're on par with major competitors but not leading Impact on approach: Would influence whether to prioritize innovation or refinement

• Considering user behavior, I'm assuming family tree accuracy directly impacts user trust and engagement. Do we have data on user churn or engagement drop-offs related to inaccurate suggestions?

Why it matters: Quantifies the impact of inaccuracies on user retention Expected answer: Yes, there's a correlation between inaccuracies and decreased engagement Impact on approach: High correlation would prioritize accuracy improvements

• From a technical standpoint, I'm thinking expanding DNA features might require significant infrastructure changes. What's our current technical capacity for handling increased DNA data processing?

Why it matters: Assesses feasibility and resource requirements for expansion Expected answer: Current infrastructure can handle 20% increase without major upgrades Impact on approach: Limited capacity might delay DNA feature expansion

• Regarding resources, I'm assuming we have dedicated teams for both DNA and family tree features. How are our engineering and product resources currently allocated between these areas?

Why it matters: Determines the feasibility of pursuing both options simultaneously Expected answer: 60% on family trees, 40% on DNA features Impact on approach: Uneven allocation might influence which option to prioritize

• Considering timeline, I'm thinking this decision might align with our annual product roadmap. Is there a specific launch window or milestone we're targeting for either of these initiatives?

Why it matters: Helps prioritize based on strategic timing and market opportunities Expected answer: Aiming for a major feature release in Q4 Impact on approach: Would influence the scope and timeline of the chosen initiative