The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
The story boards were created to visually communicate how our product would be used in the context of hiking. They augmented our user journey map by narrowing the focus on one fragment of the user journey and assisted our team with the lo- fi prototypes by visualizing how users can interact with the digital map and what features should be included in the prototype. We individually designed each of the storyboards with a user pain point and a pathway to address the needs of the user. These were mainly focused on getting the scenario and general approach correctly and had not delved too deep into the specific solution features. These solution ideas in our storyboard developed into more specifically constructed features in our low-fidelity prototype.
Personas
recognizing our user group
Meet Alex & Lily!
After synthesizing research findings, we constructed two personas as a reflection of our core users. With this archetype, we aimed to gather user research data in a way that constantly reminded us of who we were designing for. The majority of the characteristics, pain points, desires, goals, and demographic information of Alex and Lily were derived from interview response recordings.
Based on the critique feedback, we decided to brainstorm solutions catered more to Alex’s persona instead of Lily. One aspect of Lily’s persona revolved around scheduling and coordinating hiking plans. We found this area was heavily explored through other already existing digital products and we felt that incorporating a scheduling element into our problem statement and any potential solutions would not reach the full potential of our project. The scheduling aspect was abandoned after consulting with our professors and peers, and we decided to primarily focus on learning about hiking and easy access to information for Lily’s persona. Our team felt that Alex’s diverse persona was more valuable in terms of containing data ripe for solution space exploration. The personas we devised served as a guide for our users desires and needs.
​
