Build a trust-focused improvement for Freight used by merchants

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber Freight connects businesses that need to move goods with carrier capacity, but merchants depend on the product for high-stakes shipments where uncertainty can directly affect revenue, customer promises, inventory availability, and operational planning. For this product design exercise, focus on merchants as the primary users: businesses or logistics teams arranging freight movement, monitoring shipment progress, coordinating with warehouses or stores, and resolving exceptions.

The question is to design a trust-focused improvement for merchants using Freight. “Trust” should be interpreted broadly: confidence that pricing is fair, capacity is real, pickup and delivery commitments will be met, shipment status is accurate, issues will be handled transparently, and the platform will protect the merchant when something goes wrong. The opportunity is not just to add information, but to improve the merchant’s end-to-end workflow so they feel in control before, during, and after a shipment.

You should assume a marketplace environment with multiple participants, including merchants, carriers, drivers, facilities, and Uber’s operations/support teams. The design should account for the fact that freight is operationally complex: delays happen, shipment data can be incomplete, communication is fragmented, and trust may vary by shipment value, urgency, route, carrier history, or merchant sophistication.

The experience should consider:

- The merchant workflow from quote comparison and booking through pickup, in-transit visibility, delivery confirmation, documentation, and issue resolution.

- Specific moments where merchants may lose trust, such as unclear pricing, uncertain carrier reliability, poor ETA accuracy, missed pickups, damaged goods, late updates, or slow support response.

- Differences between merchant types, such as small businesses booking occasional shipments versus larger logistics teams managing recurring freight volume.

- What information merchants need to make confident decisions without overwhelming them with operational noise.

- How the experience should communicate reliability, accountability, and risk before a merchant commits to a shipment.

- How the product should handle exceptions, disputes, claims, delays, or status gaps in a way that preserves confidence.

- Marketplace constraints, including carrier availability, data quality, support capacity, operational cost, and the need to maintain healthy supply-side participation.

- How trust improvements could be measured through merchant behavior, satisfaction, retention, shipment completion quality, and reduced support escalations.

Your goal is to define a clear merchant trust problem within Uber Freight, identify the most important user needs and friction points, and outline a product experience that increases confidence in using the platform for freight movement without prescribing a generic logistics dashboard or support feature.