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.
Low Fidelity Wireframes
Based on our design requirements, some of our storyboards, and our individual design sketches, our team started to brainstorm what our interfaces should look like. We chose three main pathways that were critical to our design solution. Our focus was mainly on big picture ‘stuff’ such as interactions, information layout, task completion, and the overall flow of our design. Minor details such as color and text were not considered until our hi-fi prototype.
​
Task 1: Scan Flower Species
Scenario: You and your friend are hiking on a trail and your friend notices some pretty flowers off the trail and wants to go pick them. You remember that your smart map mentioned that there were a few endangered wildflower species to look out for.
Task: Scan the flower species around you to learn more about them.
[Completion Criteria]: Successfully scans and retrieves information on the flower species.
Task 2: Learn about Hike
Scenario: You want to find a new hike near you and adequately prepare for it.
Task: Discover a new hiking trail, explore what to bring on that specific hike, and learn about the trail conditions beforehand.
[Completion Criteria]: Successfully retrieve list of items for the hike and look at trail conditions
.png)
Task 3: Report Tree Damage
Scenario: You are walking on the trail/hike and your path is obstructed due to a fallen tree.
Task: Report tree damage around you
[Completion Criteria]: User must click on the report icon and successfully go through the entire process of reporting tree damage
