What metrics would you use to evaluate Wolt's delivery time estimation feature?

Introduction

Evaluating Wolt's delivery time estimation feature 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 help us assess the feature's performance, identify areas for improvement, and align it with Wolt's broader business goals.

Step 1

Product Context

Wolt's delivery time estimation feature is a critical component of their food delivery platform. It provides users with an estimated time of arrival (ETA) for their orders, enhancing transparency and setting expectations.

Key stakeholders include:

1. Customers: Want accurate ETAs to plan their meals and activities
2. Restaurants: Need to prepare orders in time for pickup
3. Delivery partners: Rely on accurate estimates for efficient route planning
4. Wolt: Aims to improve customer satisfaction and operational efficiency

User flow:

1. Customer places an order
2. System calculates and displays ETA
3. Restaurant prepares the order
4. Delivery partner picks up and delivers the order
5. Customer receives order and compares actual delivery time to ETA

This feature aligns with Wolt's strategy of providing a seamless, transparent delivery experience. Compared to competitors like Uber Eats or Deliveroo, Wolt's accuracy in ETAs could be a key differentiator.

Product Lifecycle Stage: The feature is likely in the growth or maturity stage, as delivery time estimation is a standard feature in food delivery apps. However, there's always room for refinement and improvement.

Software-specific context:

• Platform: Mobile app and web interface
• Integration points: Restaurant management systems, delivery partner apps, mapping services
• Deployment model: Continuous integration/continuous deployment (CI/CD) for frequent updates