ROLE:
SOLE UX/UI DESIGNER
TOOLS:
FIGMA, ZOOM
TIMELINE:
16 WEEKS
PROJECT TYPE:
UX/UI CASE STUDY
Planit
about.
problem.
constraints.
research.
This research is to assess the current space of digital tourism, explore the intrinsic behavior of users in the travel space, and determine ways to centralize and expedite trip planning.
In the digital tourism space, there is no widely-used application focused solely on trip planning. Instead, the current solution is to rely on a variety of apps to effectively plan their trips.
interviews.
I conducted a screener survey and interviewed 6 users with trip planning experience, synthesizing over 350 data points using affinity diagramming and empathy maps. Two key insights emerged:
Too Many Resources, Too Few Tools: Users shared a common workflow for trip planning, but one interviewee summed it up: "I forget I’m supposed to enjoy it." The fragmented process is taxing and often discouraging, highlighting the need for better planning tools.
Group Travel Needs Collaboration: I anticipated tension around planning methods, but interviews revealed that collaboration and communication within group travel are key to satisfaction and excitement—an often overlooked issue.
ideation.
solutions.
testing.
I conducted two rounds of moderated usability testing with 10 sessions, uncovering key UX and UI issues. The most impactful revision was renaming the "Time Block" to "Suggestion Block" due to user confusion.
Originally, "Time Block" was intended for reserving time for activities without a set location (e.g., “lunch from 12-1”), but users misunderstood it as an unchangeable period.
After testing alternatives like Event, Brainstorm, and Activity, I chose "Suggestion Block" for clarity. Post-revision, 80% of users confirmed this terminology aligned better with their expectations and reduced cognitive load.
conclusion.
This project allowed me to simplify the fragmented trip planning process by centralizing everything into one platform. Planit addresses key pain points like information overload, collaboration, and trust with features such as the Trip Dashboard, Pre-Trip Survey, Suggestion Block, and in-app navigation, making planning more efficient and enjoyable. After discussing the concept with 12 users, all expressed a strong desire for a solution like this, emphasizing its potential to improve their trip-planning experiences.
reflection.
This project has taught me valuable lessons about the complexities of designing for the travel space. In hindsight, I would have:
Defined information architecture earlier
Focused on an MVP and refined key features
Created a cheat sheet for easy reference
Despite challenges, executing this long-held idea has been the most rewarding part. With more time, I’d conduct further testing on terminology and voting features, enable task management for better collaboration, and explore version control for activity tracking and revisions.
