Travel has changed in the world but our need for in-person connection hasn’t. How might we make travel more accessible for older adults in a post-pandemic world especially if they are immunocompromised?
I worked on this project with two other team members, leading the initial stages of design and then transitioning more into a documentation role, synthesizing details to make iterations to our high fidelity prototype.
In 10 weeks, our team of three utilized a mix of secondary research and user testing to design a mobile app that provided trip recommendations, budgeting options, and trip focused accessibility information to make traveling easier for older adults.
Technology moves fast, and as much as we try to make things simplified older generations have struggled to maintain the same connectivity that they once had. With the pandemic shutting down in-person events, returning back prioritized work places and schools’ which left older adults in a limbo on how to meet again.
We were tasked with creating a solution for older adults traveling in a post pandemic world that would create a meaningful experience. So what type of things would we need to consider?
With their living situations impacting their ability to see others on a regular basis, our team decided to see what other barriers could be hindering their ability to meet with others and travel.
Due to our rather quick timeline, we focused on generating findings through secondary research and found three core factors to consider:
While we often talk about intersectionality in conversations around systemically oppressed identities, its key idea of compounding barriers to entry apply here as well.
If our users aim to connect with one another through a trip and one of them is limited financially while the other physically, their ability to travel together becomes significantly harder.
These features would prioritize generating affordable search results for our users with the ability to share and receive the accessibility information they need prior to booking a trip.
In our 10 weeks, we built 3 prototypes: paper, midfidelity, and high fidelity. Our class collectively aimed to complete this project in 9 weeks, staggering our prototype fidelity with one every 2 and half weeks, with the last week reserved for final presentations on our respective solutions.
After completing our paper prototype we tested with our peers, ages 19–24, understanding where our large pain points lie. Our main finding was not enough connectivity to a home section. We re-iterated in our mid fidelity and high fidelity, testing each of these with four adults ages 53 and up.
Even though users were able to navigate through the app with the trip selection process, their largest concern revolved around splitting the cost.
Some were unsure how to book a trip if they wanted to invite their immediate family but wanted to pay in full. While others holistically did not understand what the feature aimed to communicate.
We took a step back and aimed to focus our efforts on the copy to maintain the integrity of the design, yet in the high fidelity testing, we still received similar feedback.
With one week left we were stuck. While we consulted our professor for help, we also realized that this issue would require a lot more time to brainstorm and design before a usable solution was ready.
We decided to maintain the design and include the issue in our final presentation to receive feedback. While this felt very defeating as a team, we understood that facing roadblocks on deliverables is a consistent aspect of UX and after we presented I reflected on the experience as a whole.
This was one of my first projects when I decided to start UX Design in 2022, and diving deep into the workflow and sprint culture was something familia but different to me. Coming from an animation background, the culture of systemized workflow is so integral and I aimed to bring that to UX with our short and long term goal setting each week.
Implementing a split cost feature was a helpful idea in theory but we did not spend enough time to extrapolate how we would be able to make this a full fledged feature with customization. We could’ve used more outside research on competitors that successfully implemented it for other industries to foresee this issue prior to user testing.
Products aren’t finished. They are merely useable and each time you successfully reiterate, they become more so. Even at the end of this project, there were pain points that needed more brainstorming to fix based on our classes feedback and our user testing. Keeping these in mind allowed me to prioritize specific types of features going forward, and understand how I could apply these learnings to a future project.