Should New Relic prioritize expanding APM features or improving the user interface of New Relic One to increase customer adoption?

Introduction

The trade-off we're examining today is whether New Relic should prioritize expanding APM features or improving the user interface of New Relic One to increase customer adoption. This scenario involves balancing technical depth with user experience enhancements, both aimed at driving customer adoption. I'll approach this analysis by first asking clarifying questions, 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 APM might be facing increased competition. Could you share insights on our current market position and how it's evolving?

Why it matters: Helps prioritize features vs. UI based on competitive landscape Expected answer: Increased competition in APM space Impact on approach: May lean towards UI improvement if APM features are at parity

• Considering our revenue model, I assume expanding APM features could directly impact our pricing tiers. How does our current pricing structure align with potential new APM capabilities?

Why it matters: Determines if feature expansion can drive revenue growth Expected answer: Tiered pricing based on feature set and data volume Impact on approach: Could prioritize APM if it allows for higher-tier upsells

• Looking at user behavior, I'm curious about the adoption rates of our current APM features versus overall platform usage. Do we have data on feature utilization across different customer segments?

Why it matters: Identifies if low adoption is due to discoverability or feature gaps Expected answer: Varied adoption rates across segments, potential UI friction Impact on approach: May favor UI improvements if feature adoption is lagging

• Regarding technical feasibility, how integrated is our current APM offering with the rest of New Relic One? Are there any architectural constraints to consider?

Why it matters: Assesses complexity of expanding APM vs. improving overall UI Expected answer: Some integration challenges, but manageable Impact on approach: Could influence timeline and resource allocation

• Considering our development capacity, how are our teams currently structured between APM and UI/UX? Is there flexibility to reallocate resources?

Why it matters: Determines feasibility of executing either option effectively Expected answer: Separate teams with some shared resources Impact on approach: Might favor option aligning with current team structure