Should HireRight prioritize faster turnaround times for background checks or more comprehensive data sources to improve accuracy?

Introduction

The trade-off between faster turnaround times and more comprehensive data sources for background checks is a critical decision for HireRight. This scenario involves balancing speed and accuracy, two fundamental aspects of background check services. I'll analyze this trade-off by examining its impact on various stakeholders, evaluating key metrics, and proposing an experimental approach to inform our decision.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking speed might be a key differentiator. Could you share how our turnaround times compare to our main competitors?

Why it matters: Helps assess our competitive position and urgency of improvement Expected answer: We're slightly behind industry average Impact on approach: Would prioritize speed improvements if significantly behind

• Considering our business model, I assume accuracy directly impacts client satisfaction and retention. What's our current client retention rate, and how does it correlate with check accuracy?

Why it matters: Establishes the business impact of accuracy Expected answer: Strong correlation between accuracy and retention Impact on approach: Would emphasize maintaining or improving accuracy if retention is at risk

• Looking at user behavior, I'm curious about the impact of turnaround time on candidate experience. Do we have data on candidate drop-off rates during the background check process?

Why it matters: Helps quantify the user impact of slow turnaround times Expected answer: Significant drop-off after X days Impact on approach: Would focus on reducing turnaround time to below the drop-off threshold

• From a technical perspective, I'm wondering about the scalability of our current data sources. What's our current capacity for processing checks, and how would expanding data sources affect this?

Why it matters: Assesses feasibility and potential bottlenecks Expected answer: Current system near capacity, expansion would require significant upgrades Impact on approach: Would need to factor in technical debt and infrastructure costs

• Considering resource allocation, I'm curious about our current team structure. How are our teams currently split between speed optimization and data source expansion efforts?

Why it matters: Helps understand current priorities and potential for reallocation Expected answer: 70% on speed, 30% on data sources Impact on approach: Would inform resource reallocation strategies based on chosen priority