Should KAR Global prioritize expanding its ADESA Simulcast platform's features or focus on improving the user interface for better dealer adoption?

Introduction

The trade-off we're examining today is whether KAR Global should prioritize expanding ADESA Simulcast's features or focus on improving the user interface for better dealer adoption. This decision is crucial for the platform's growth and market position. I'll analyze this trade-off by examining the product context, potential impacts, key metrics, and experimental approaches to inform our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming ADESA Simulcast is a key revenue driver for KAR Global. Could you confirm the platform's current contribution to overall revenue and its growth trajectory over the past year?

Why it matters: Helps prioritize the importance of this decision in the broader business context. Expected answer: Significant revenue contributor with strong growth. Impact on approach: Higher revenue contribution would justify more aggressive investment in either option.

• Business Context: Based on the competitive landscape, I'm thinking dealer adoption might be our primary challenge. How does our dealer adoption rate compare to our main competitors in the online auto auction space?

Why it matters: Identifies whether UI improvements could give us a competitive edge. Expected answer: Lower adoption rate compared to key competitors. Impact on approach: Would lean towards prioritizing UI improvements if significantly behind.

• User Impact: Considering dealer feedback, I'm curious about the main pain points in the current user experience. What are the top 3 complaints we hear from dealers about using ADESA Simulcast?

Why it matters: Helps determine if UI improvements or new features would address user needs more effectively. Expected answer: Complexity of navigation, slow loading times, lack of mobile optimization. Impact on approach: Would influence the specific focus areas for UI improvement or feature development.

• Technical: Given the potential for UI improvements, I'm wondering about our current tech stack's flexibility. How easily can we implement significant UI changes without disrupting the underlying functionality?

Why it matters: Assesses the feasibility and potential timeline for UI improvements. Expected answer: Moderately flexible, but some legacy systems might pose challenges. Impact on approach: Would influence the scope and timeline of potential UI improvements.

• Resource: Considering our current team structure, I'm thinking about our capacity for parallel development. Do we have separate teams that could work on feature expansion and UI improvements simultaneously, or would this be an either/or scenario in terms of resource allocation?

Why it matters: Determines if we can pursue a hybrid approach or must choose one direction. Expected answer: Limited resources, need to focus on one primary initiative. Impact on approach: Would necessitate a more definitive choice between the two options.