What metrics would you use to evaluate Expedia's vacation package booking service?

Introduction

Evaluating Expedia's vacation package booking service requires a comprehensive approach to product success metrics. To address this challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders. This approach will allow us to gain a holistic view of the service's performance and identify areas for improvement.

Step 1

Product Context

Expedia's vacation package booking service is a core offering within their travel platform, allowing users to bundle flights, hotels, and sometimes car rentals or activities into a single purchase. This service caters to travelers seeking convenience and potential cost savings.

Key stakeholders include:

• Travelers: Looking for convenient, cost-effective vacation planning
• Hotels and airlines: Seeking to fill inventory and increase bookings
• Expedia: Aiming to increase revenue and market share
• Travel agents: Potentially using the platform to book for clients

User flow:

1. Search: Users input destination, dates, and traveler information
2. Results: Users view and filter package options
3. Customization: Users can modify package components
4. Booking: Users complete the purchase and receive confirmation

This service aligns with Expedia's strategy of being a one-stop-shop for travel planning, differentiating itself from competitors like Booking.com or Airbnb by offering comprehensive packages. Compared to competitors like Priceline, Expedia often has a wider range of package options and more flexibility in customization.

Product Lifecycle Stage: Mature - The vacation package concept is well-established, but there's ongoing innovation in personalization and dynamic packaging.

Software-specific context:

• Platform: Web and mobile apps
• Integration points: Multiple APIs for flights, hotels, and other services
• Deployment model: Continuous integration/continuous deployment (CI/CD) for frequent updates