Miventy: Designing the Adaptive Provider Catalog

Research & Discovery: Provider Pain Points

My research focused heavily on the provider-side experience—interviewing small business owners and freelancers in the event industry about their current processes for listing and managing their services.

Key Provider Pain Points

• Data Entry Fatigue: Existing platforms often force providers to fill out irrelevant fields (e.g., a Magician being asked for "kitchen access requirements"). This leads to frustration and incomplete listings.

• Inconsistent Data: Without strict form structure, providers often miss critical information, forcing customers to send follow-up messages, slowing down conversion.

• Booking Mismatch: Unclear listing rules result in customers trying to book services that are physically or logistically impossible (e.g., booking a service outside the provider's travel radius).

The Solution Goal

To design an Adaptive Catalog Form that uses conditional logic to simplify data entry for the provider while standardizing the data presented to the customer.

The Solution: The Adaptive Catalog System

The final design centered on creating an intelligent, step-by-step upload process for service providers.

1. The Adaptive Provider Upload Form

The core of the UX solution was a progressive, segmented form utilizing conditional logic.

• Step 1: Category Selection: The provider first selects their primary service category (e.g., "Catering"). This choice immediately triggers the tailored workflow.

• Step 2: Dynamic Fields: All subsequent form fields are dynamically loaded based only on the selected category.

  • Example: Catering: Fields for Minimum Order Value, Menu Packages, and Allergen Disclosures appear.

  • Example: Face Painter: Fields for Hourly Rate, and Required Setup Time appear.

• Real-Time Validation: Input fields included specific constraints (e.g., number-only, min/max characters) and tooltips to guide providers, ensuring the data captured was accurate and usable.

An integral part of the listing creation process was the catalog section. Users are able to create a digital catalog for their services, and this has to encompass all the services provided while adapting to each service. For this I came up with a single catalog flow which can be adapted for all the services. Before arriving at the final design, 3 iterations were made in succession to each other. The first iteration prioritized physical service providers like caterers and bakers, this left lot of un needed fields for other services to fill up. This was later corrected in the final catalog design.