D Tour: UX Case Study

The Product Identification workshop focused on defining user personas, where we brainstormed potential user's by exploring their characteristics, actions, and behaviors—focusing on who they are and who they are not. 

This process helped us deeply understand our target audience, ensuring that our design decisions later in the project aligned with user needs and expectations.

The empathy map exercise allowed us to gain insights into user behaviors, identify gaps in our research, and achieve a shared, unbiased understanding of our users' feelings, actions, and goals. 

The User Journey Map outlined the user's entire experience and helped in identifying pain points:

Lack of reliable reviews makes decision-making difficult

User find it time-consuming to research places

This understanding allowed us to focus our design efforts on addressing the identified challenges and creating features that directly address the uncovered pain points.

These were defined as features that our users would expect. But, how do we make our product stand out amongst our competitors? How do we target the aspect of educating users on the history of Dallas everything it has to offer in a way that is not boring? How do we keep users coming back to our app? 

This brought us to the next phase: Feature Ideation.

The How Might We exercise helped us narrow down various areas that we wanted our product to target. To make our product stand out from our competitors, we answered our previous questions on making a unique product, where we came up with the idea of incorporating a gamification feature through AR. 

Following this exercise, we further defined the 4 key features and their functionalities through feature definition:

The user flows allowed us to visualize the various pathways users might take when interacting with the product. This helped us identify key content and decisions users would encounter on specific screens, and provided a clear step-by-step breakdown of what users would see and do, such as doing a filter search on a location, reading reviews, etc. 

The feature prioritization activity helped us determine which features were essential for launch by balancing business value and development effort. We identified high-value, low-effort features as top priorities for our Minimum Viable Product (MVP), while less critical, high-effort features were categorized  for future releases.