For Reltio's Identity Resolution capabilities, should we emphasize real-time processing speed or invest in more comprehensive entity matching across a wider range of data types?

Introduction

The trade-off we're examining for Reltio's Identity Resolution capabilities is between emphasizing real-time processing speed and investing in more comprehensive entity matching across a wider range of data types. This decision is crucial for Reltio's product strategy and will significantly impact our ability to serve customers effectively in the rapidly evolving data management landscape.

In my analysis, I'll explore the implications of this trade-off, considering technical feasibility, user impact, business alignment, and long-term strategic consequences. I'll structure my response using a comprehensive framework that covers clarifying questions, product understanding, hypothesis formulation, metrics identification, experiment design, data analysis, and decision-making.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Reltio is facing increasing demands for both speed and accuracy in identity resolution. Could you provide more context on what's driving this trade-off consideration? Are we seeing specific customer requests or competitive pressures?

Why it matters: Helps understand the urgency and external factors influencing the decision. Expected answer: Mix of customer demands for faster processing and competitors offering more comprehensive matching. Impact on approach: Would help prioritize which aspect to focus on first.

• Business Context: Based on Reltio's current revenue model, I'm thinking this decision could significantly impact our pricing strategy. How does our current pricing structure align with these two capabilities?

Why it matters: Determines if we need to consider pricing changes alongside product changes. Expected answer: Current pricing favors comprehensive matching, but there's interest in speed-based tiers. Impact on approach: Might lead to a hybrid solution or tiered offering.

• User Impact: I'm considering the different user segments we serve. Can you share which customer segments are most vocal about real-time processing versus comprehensive matching?

Why it matters: Helps tailor the solution to meet the needs of our most valuable or strategic customers. Expected answer: Enterprise clients prioritize comprehensiveness, while mid-market favors speed. Impact on approach: Could lead to a segmented product strategy.

• Technical Feasibility: Given our current architecture, I'm wondering about the technical challenges in improving both aspects simultaneously. What are our main technical constraints?

Why it matters: Determines the feasibility and timeline of potential solutions. Expected answer: Significant refactoring required for real-time processing, less so for expanding data types. Impact on approach: Might influence phasing of improvements or need for architectural changes.

• Resource Allocation: Considering our current team structure, I'm curious about our capacity to pursue both improvements. Do we have the necessary expertise and bandwidth in-house?

Why it matters: Helps determine if we need to hire, train, or outsource for this initiative. Expected answer: Strong team for comprehensive matching, need to bolster real-time processing skills. Impact on approach: Could influence timeline and resource allocation strategy.