How can Ticketmaster improve its mobile app interface to reduce ticket purchase abandonment rates?

Introduction

Improving Ticketmaster's mobile app interface to reduce ticket purchase abandonment rates is a critical challenge that directly impacts user satisfaction and revenue. I'll approach this problem by analyzing user segments, identifying pain points, generating solutions, and proposing metrics to measure success. Let's dive in.

Step 1

Clarifying Questions

• Looking at the product context, I'm thinking about the primary use cases for the Ticketmaster app. Could you help me understand what percentage of users are using the app for discovering new events versus purchasing tickets for specific events they already know about?

Why it matters: This will help us prioritize which part of the user journey to focus on for reducing abandonment. Expected answer: 70% of users come to purchase specific tickets, 30% for discovery. Impact on approach: If most users are coming for specific purchases, we'd focus on streamlining the checkout process rather than improving event discovery features.

• Considering user behavior, I'm curious about cross-platform usage patterns. What percentage of users start their purchase on mobile but switch to desktop to complete it?

Why it matters: This could indicate usability issues specific to the mobile interface. Expected answer: About 25% of users switch from mobile to desktop to complete purchases. Impact on approach: A high percentage would suggest focusing on mobile-specific pain points in the purchase flow.

• Regarding product lifecycle and company alignment, where does reducing mobile app abandonment rate rank in terms of overall company priorities? Are there specific targets or benchmarks we're aiming for?

Why it matters: This helps us understand the resources and support available for this initiative. Expected answer: It's a top 3 priority, with a goal to reduce abandonment by 20% in the next quarter. Impact on approach: High priority would allow for more substantial changes and resources allocated to the project.

• Considering external factors, how has the competitive landscape changed recently? Are there any new entrants or features from competitors that might be influencing user expectations?

Why it matters: This helps us understand if we need to catch up to industry standards or innovate beyond them. Expected answer: A new competitor has introduced a virtual queue system that's gaining popularity. Impact on approach: We might need to consider similar features or find innovative ways to address the same user needs.