SPRINT18 PORTFOLIO

PlanAway

PlanAway the details so you can focus on the fun! Say goodbye to the stress of spending long, tiring nights of researching a foreign city to plan the best pathing. PlanAway helps you turn your bucket list into a well optimized, thoughtful itinerary that organizes your vacation activities based on location, so you’re not trekking across the city and back in a single day.

Problem Space 

Problem Statement  

How might we create an optimized itinerary for travelers so that they can plan their key activities stress-free?

Problem Background  

Have you ever been super excited to go on vacation? Your flight is booked, you're excited to see the sights, and you're ready to go. But wait! You have to create an itinerary and decide when to go to each activity. You have no idea where anything is located or when places are open. Now you're stuck spending hours researching and planning routes for a city you've never been to.

If planning a vacation itinerary is something you've procrastinated on before, you're not alone. In survey responses, 91.2% of surveyed users have at least 1-5 activities they plan to go to and 76.5% place high importance on visiting those planned activities. However, 79.4% don’t plan when to visit or in which order. Only 20% actually create a detailed itinerary where they plan each meal, every activity, and how to get to each spot. This suggests that optimization is important for a pleasant vacation experience, but many don’t plan in that much detail. Users currently use several different products to search up activity locations and hours of operation. They then have to note this information on a separate product and manually plot out routes on a different mapping tool. This is one of the longest processes when planning a vacation, and the most tedious. 

Research Insights

User Pain Points

Five 1-on-1 user interviews were conducted with a total of 34 survey respondents. There are five key pain points users currently experience:

  • Users know which activities they want to visit, but don’t plan for when to go to each
  • Users enjoy researching for activities, but don’t enjoy planning out routes
  • Users would like to cut down time spent on researching specific locations and business hours 
  • Users want a well optimized itinerary, but don’t want to create one themselves
  • Users want to plan a well optimized itinerary with a group of friends or family and ensure everyone is on the same page

76.4% of surveyed users place high importance on a well optimized itinerary. But only 20% actually create a detailed itinerary where they plan each meal, every activity, and how to get to each spot. This suggests that optimization is important for a pleasant vacation experience, but many don’t plan in that much detail. In user interviews, although researching for activities was the most time-consuming, it’s a task that users enjoy. Planning day-to-day logistics is the second-longest task of the process, but users don’t experience the same joy and typically do not plan in detail as this task is more tedious. 

Landing on the Solution

Based on pain points, the following features are a priority:

  • Optimizing activities based on location
  • Optimizing activities based on business hours

These features are crucial to addressing the core needs of planning routes and deciding an order of activity.

Explanation of Solution

After completing a basic prototype, 7 users were surveyed again. Users were able to click into the prototype and saw 8 different pages. Users were asked about their thought process while navigating the app, their likes, dislikes, and what functions they would want to perform, but were not included in the prototype. 

Potential future features that users would like to see:

  • Flexibility: Users want to be able to move activities to different time slots and dates
  • Clarity: Users want defined hours for each time slot and a start and end time for each day
  • Information: Users want details on each activity including seeing location points on a map, business hours, and descriptions

Additional feedback is included in the treemap below:

User Flows/Mockups

https://app.visily.ai/projects/2daa129a-cf3e-45af-8c4f-954ea07d5c41/boards/443185/presenter?play-mode=Prototype 

Future Steps

Since users only saw the most basic mockup, there are several additional features that would improve user experience and satisfaction. Possible problems to address include adding more features to help users navigate, organize, and share their itineraries:

  • Adding more information for each specific activity
  • Business hours
  • Location displayed on a map
  • Activity description
  • Adding a map function so users are able to see all their activities and routes plotted out on one map
  • Providing a way for users to be able to share their itineraries and edit others’ itineraries
  • Better UI design for users to clearly understand and easily navigate
  • Incorporating activity recommendations and suggestions 

Learnings

Product Manager Learnings:

Cindy Wang

I learnt to redirect my focus and mindset on identifying the problem and narrowing down what it is that users are missing. Diving deep into thinking about user segmentation, pain points, and really focusing on the problem space was the biggest learning for me. I also learnt a lot about user interviews (both initial and follow-up with a prototype) and deciphering what users were saying to understand their true pain points.

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

&

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning