Design
Crafting Meaningful Solution to Support Our User's Goal
Overview
With our design process, we started by identifying the goals and requirements that our solution should follow based on the research we performed. This allowed us to focus on what we wanted our project to accomplish for our users through the creation of our storyboards. We finalized these processes through our information architecture, which detailed the features we wanted NavIndor to contain.
Diverging and Converging Ideas
Design Requirements
Integrating Information
Integrating the key information from our research on user needs and pain points, we created a list of requirements targeting those pain points experienced in the navigating process. Having design requirements allow us to brainstorm our solutions for their pain points and to think about what we can really do based on user needs.
Takeaways
-
Enable users to independently locate a specific room within a building.
-
Allow users one-handed operation of the system so they can still use their cane or guide dog.
-
Provide users with information about their surroundings upon request.
Writing down information we get in the interview and creating the list of design requirments
Writing down information we get in the interview and creating the list of design requirments
Ideating Solutions
With an understanding of our solution’s design requirements, we independently created storyboards to ground potential design solutions in specific contexts. We storyboarded different keypath scenarios with divergent solutions and iterated upon our user’s emotions while using these potential solutions.
Storyboards
Drawing storyboard
Thinking about content in the storyboard
Drawing storyboard
Takeaways
-
Focus less on visual aspects and features of the product in the storyboard and more on user emotions.
-
Use text descriptions sparingly and focus on communicating user reactions and feelings.
Storyboards Examples
Information Architecture
Mapping out Hierarchy
While storyboarding allowed us to identify a direction and focus for our design solution, the information architecture allowed us to envision the detailed functionality of our design. With an understanding of what we wanted to make, we outlined the hierarchy of information between each component of our system. This gave us the basis for our prototype.
Writing down and analyzing our functionalities on the whiteboard
Writing down and analyzing our functionalities on the whiteboard
Takeaways
-
We needed to keep our interactions simple in consideration of our users.
-
Certain functions needed to be accessible in multiple areas of each interface.
Information Architecture Examples
