For GetYourGuide's mobile app, should we focus on simplifying the booking process or adding more detailed information about each tour option?

Introduction

The trade-off we're examining for GetYourGuide's mobile app is whether to focus on simplifying the booking process or adding more detailed information about each tour option. This decision is crucial for enhancing user experience and potentially impacting conversion rates. I'll analyze this trade-off by considering user needs, business goals, and technical feasibility.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming GetYourGuide is facing challenges with mobile app conversion rates. Could you confirm if this is the case, and if there are any specific user segments we're particularly concerned about?

Why it matters: Helps focus our solution on the most critical user segments and pain points. Expected answer: Yes, conversion rates are lower for first-time users on mobile. Impact on approach: Would prioritize simplifying the booking process for new users.

• Business Context: Based on the company's current strategy, I'm thinking this might be tied to increasing mobile bookings. How does this align with our overall growth targets for the year?

Why it matters: Ensures our solution supports broader business objectives. Expected answer: Mobile bookings are a key growth driver, targeting 40% increase YoY. Impact on approach: Would justify more resources allocated to this initiative.

• User Impact: Considering user behavior, I'm hypothesizing that detailed information might be more critical for high-value tours. Do we have data on how information needs vary across different price points or tour types?

Why it matters: Helps tailor the solution to different user needs and tour categories. Expected answer: Yes, users spend more time researching expensive or longer duration tours. Impact on approach: Might lead to a hybrid solution, simplifying for some tours while adding details for others.

• Technical Feasibility: Given our current app architecture, I'm wondering about the complexity of implementing dynamic content loading. How flexible is our current system for adding more detailed tour information without impacting app performance?

Why it matters: Determines the feasibility and timeline for implementing more detailed tour information. Expected answer: Our current architecture can support it, but it would require significant development effort. Impact on approach: Might favor a phased approach, starting with simplification and gradually adding details.

• Resource Allocation: Considering our product roadmap, I'm curious about the resources available for this project. Do we have a dedicated mobile team that can focus on this, or would it require pulling resources from other initiatives?

Why it matters: Helps determine the scope and timeline of the project. Expected answer: We have a small mobile team, but could potentially reallocate resources from other projects. Impact on approach: Might lead to a more focused, iterative approach to implementation.