Overview
In the design phase, we brainstormed how the Senior Saver device would be used by our customer base. We identified design requirements that would help our customers achieve the easiest-to-use experience that would meet the needs we identified in our user research, personas, and user journey maps. We created design requirements, storyboards, interface design sketches, and information architecture to develop ideas and begin working on our prototype design for the Senior Saver device.
Design Requirements
Using findings from preliminary research, we identified our user’s pain-points, desires, and goals which helped us fine-tune our design requirements. Our design goals focus on characteristics, not functions, or features. They specify the goals that users will be able to accomplish by using the product.
Click to see our design proposal
Key Takeaways
-
Simplicity in design and use was key
-
Family members need peace of mind that the user is safe
-
Design must help with day-to-day tasks
Key Design Requirements
-
Remind user to take medications
-
Voice assistance for all functions
-
Allow family members to monitor usage and events
Storyboards & Interface Design
Through brainstorming user stories, we broke large stories up into smaller ones. This helped us with designing and conveying a user experience based on scenarios our personas might have with our design. We focused on current issues or experiences that our users may have and how our design could improve their experiences. After we had an idea for what to build we went back to the drawing board to demonstrate the major aspects of our design and their strengths and weaknesses.
Key Takeaways:
-
Storyboards revealed the gap between our ability as designers and our users’ abilities
-
Storyboards reinforced the need for an easy-to-use design
Information Architecture
We mapped where and how content (not features) would be organized in our design. Specifically, "locations" that users might find themselves at in our design rather than the function of those locations. The visual organization of the high-level hierarchy of our design helped us to design the various navigation paths for the user.
Key Takeaways:
-
Longer pathways indicated a non-simplistic design
-
Voice assistance could be used to reduce the length of many paths