Assisted in UX Strategy: Comparative analysis, Survey, Data Synthesis, Feature Tables, JTBD
Design Lead: Wireflow, Lo-fi, Mid-fi, High-fi, Prototype
UX/UI Designer, a UX Researcher, and Developer
Ecomadic A company like Airbnb but for travelers who want to travel with sustainable accommodations and experiences.
16 Weeks
Figma, Whimsical, Zoom, and Survey Monkey
It was only natural that sustainable travel platform Ecomadic would move into the travel curator space with their own itinerary building platform. Travel Curators (much like a travel agent) would be able to build and manage itineraries, create invoices or quotes, message clients, have a client database, and create event modules for easy itinerary building.
To understand what curators want most out of the itinerary building process while also focusing on how we can turn their needs into a superb experience that can potentially drive new customers and increase revenue for Ecomadic.
I wanted to understand the travel industry: its trends, the verbiage used, and the behaviors of customers and businesses. After learning generally about the travel curator and their role in the industry, I wanted to get a basis for who my user is, what is important to them in the itinerary building process, and whether or not something as simple as an integration from an existing product would be a good fit.
I needed more clarity so I interviewed 6 of the travel curators on Ecomadics waitlist.
Since I didn’t have access to our direct competitors' backend itinerary builders, we opted to analyze itinerary builders available to anyone.
While keeping my other research in mind, I analyzed the 4 most popular itinerary builders. I found that almost none of them had this aspect of effective communication. This then became my opportunity for the solution.
At first I spent 1 week trying to play with a couple of directions: communication system synched with your phone, synching with google suite, etc. But after presenting my initial ideas to the dev team, it became clear that those would take too long to implement, especially for the first MVP. So I decided to stick with a simple messaging system within the platform. During the presentation we also noticed that our initial scope was too much for the time allotted. It would have been nice to include everything in the designs (invoices, inquiries, payment system, event modules, etc.), but ultimately decided to focus my energy on creating effective communication through the itinerary builder itself and forget about the bells and whistles.
Based on various feedback from 6 curators, I continually iterated my design over the span of 4 weeks with 2 major improvements: