For ACV Auctions's mobile app, should we focus on adding advanced bidding tools to increase engagement or simplify the interface to attract more casual users?

Introduction

For ACV Auctions's mobile app, we're facing a critical trade-off between adding advanced bidding tools to increase engagement or simplifying the interface to attract more casual users. This decision will significantly impact our user acquisition, retention, and overall platform growth. I'll analyze this trade-off by examining our product ecosystem, defining key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking our current user base might be skewing towards experienced dealers. Could you share some insights on our current user demographics and their engagement levels?

Why it matters: Helps determine if we need to prioritize retention or acquisition. Expected answer: Majority experienced users, engagement plateauing. Impact on approach: Would lean towards simplification if we need new users.

• Business Context: Based on our revenue model, I assume we earn from successful auctions. Is this correct, and are there any other significant revenue streams we should consider?

Why it matters: Aligns solution with primary revenue drivers. Expected answer: Primarily auction-based revenue, some ancillary services. Impact on approach: Would prioritize features that directly increase auction participation and completion.

• User Impact: I'm curious about our user retention rates. Are we seeing any significant drop-offs at specific points in the user journey?

Why it matters: Identifies pain points in current UX. Expected answer: Some churn after first auction attempt. Impact on approach: Would focus on simplifying critical auction steps if retention is an issue.

• Technical: Regarding our current app architecture, how modular is it? Could we potentially implement both advanced tools and a simplified interface as toggleable options?

Why it matters: Determines feasibility of a hybrid solution. Expected answer: Moderately modular, but significant work for dual interfaces. Impact on approach: Might consider phased implementation if architecture allows.

• Resource: What's our current team capacity for mobile app development? Are we staffed to handle significant UX changes or feature additions?

Why it matters: Ensures recommendation aligns with resource constraints. Expected answer: Limited capacity, focused on maintenance and minor improvements. Impact on approach: Would prioritize high-impact, resource-efficient solutions.