5. Process
● Competitive Analysis & Lit review around potential problem space
● Interviews with end-users
● Development of problem statement, persona, and requirements
● Braindrawing exercise to generate initial ideas
● Refined designs within defined frameworks
● User testing with clickable prototype
● Iteration on designs
RESEARCH
users and
the domain
MODELING
of users and
use context
REQUIREMENTS
definition of
user, business
and technical
needs
FRAMEWORK
definition of
design structure
and flow
REFINEMENT
of behaviors,
form and
content
SUPPORT
development
needs
7. Competitive Analysis & Lit Review
Competitors:
● Suggest outfits for the user for that day considering the weather forecast.
● Suggest outfits that factor in categorical data like age, location, and gender
coupled with design trends.
● Have the option to save, categorize, and share personalized favorite outfits
with a network of users.
Research indicates:
● Different people’s bodies respond to different environmental conditions. For
instance, the temperature in office buildings are determined based on the
average male, making it uncomfortable for many females and the elderly
(Kingma & van Marken Lichtenbelt, 2015).
8. Interviews with end-users
Insights:
• Looking good and feeling comfortable were equally weighted
• Commuting can make getting dressed really challenging
• People want to choose their outfit quickly and accurately, not
spend endless time making a decision
10. Problem Statement
Commuters spend excess time and effort deciding what to
wear in the morning. They must decide on a comfortable and
appropriate outfit that takes into account the weather, their
commute, work environment and any activities on their
schedule. Additionally, they must consider their own unique
reactions to temperatures and different environments,
making it difficult to rely on existing technology that is not
personalized to their preferences or available clothing
options.
“
15. SUS score: 72.5 (B)
I thought it was really cool.
User Testing
Positive feedback:
• Weather, calendar, activities were all
very useful
• Swiping to see options was intuitive
• Providing feedback was easy to follow
Constructive feedback:
• Labels on buttons were not intuitive
• Navigation through sections and
progress indication could be improved
• Feedback options could be more
appropriate to the type of clothing
• Home screen should be more clear
what outfit you’re looking at (today’s,
not tomorrow’s)
“
16. Iteration on Designs
Final designs iterations focused on user test insights:
• Navigation & progress
• Logical feedback options
• Better home screen
• Pushed some things to V2 (mobile, smart hangers, biometric tracking)
• Removed audio input for voice navigation
17. How IxD helped us solve our problem
Similarity & Match
user’s mental model
Wayfinding & Chunking
Visibility
18. View of calendar, weather, and schedule
Navigation Inputting clothing
Giving feedback on clothing suggestions
Design elements that helped us solve the problem
19. Our Solution
A smart mirror that enables users to make
appropriate outfit decisions by accounting for the
weather, their commute, and daily schedule, while
also collecting feedback on the effectiveness of
those outfit choices to cultivate a personalized
experience.
“
Editor's Notes
Now you have a sneak peek of the solution we developed, but before we dive deeper into the final designs, we want to share our process with you. Considering our problem statement, we took a goal-oriented design approach towards creating a solution.
Talk about above bullet points
For the purposes of this project, we focus on the first 5 steps of the goal-directed design process. If we were putting this product on the market and moving forward with development, we would need to incorporate the 6th step.
Paraphrase what’s on the screen
Each of us interviewed a potential user of the Dress Yo’Self smart mirror:
Interview insights:
Looking good and feeling comfortable were equally weighted
Commuting can make getting dressed really challenging
People want to choose their outfit quickly and accurately, not spend endless time making a decision
P1:
25-29
Product at technology company
Female
Lives with boyfriend
P2:
25-29
UX Designer at healthcare company
Female
Lives with 2 roommates
P3:
35+
Instructional Technology Specialist at a high school
Female
Lives with husband and mother
We used the insights that we gleaned from the interviews and created our persona, Jill. Jill is a twenty-something who commutes to work by way of walking and taking the train. She does want to spend a long time getting dressed in the morning, but finds it challenging to find something comfortable to wear that will also be appropriate for her schedule, her commute, and the weather forecast.
Based on our research, interviews with end users, and the developed the persona, we generated the following problem statement.
Commuters spend excess time and effort deciding what to wear in the morning. They must decide on a comfortable and appropriate outfit that takes into account the weather, their commute, work environment and any activities on their schedule. Additionally, they must consider their own unique reactions to temperatures and different environments, making it difficult to rely on existing technology that is not personalized to their preferences or available clothing options.
From here, we began to think about potential solutions that could help address this problem.
We started out by putting pen to paper. Though there were many workflows that we hypothesized would be useful to address this problem statement, we chose to generate ideas around the outfit selection process - since that seemed to be the most crucial and central workflow. We used a method called braindrawing to rapidly generate as many potential and divergent solutions as possible between the team.
After three rounds of iterating on our sketches from the braindrawing exercise, we had numerous directions we could go in with this workflow. However, a few things were made clear:
Swiping would be the most familiar and efficient way of browsing through the clothing options
Information such as weather, the date, and the user’s schedule should be displayed on the interface
Considering the dimensions of the mirror, it would be a challenge to show the primary outfit, outwear/extras, and clothing for activities in a way that was both cohesive but logically separated
Once we had agreed on a direction based on our ideation process, we established our design frameworks. The first pass at the industrial design framework was a:
Mirror consistent with standard mirror dimensions of 12x36 in
Powered using an electricity, as seen by the plug and wall socket
With a toggle switch on the side enables the user to switch from a regular mirror display to the smart mirror interface
With an audio input at the top to capture voice for dictating navigation
Our interaction framework included a space for the calendar, schedule, and weather at the top of the mirror, navigation below that, and the suggestion outfit taking up the bulk of the screen.
Our first prototype showed how the navigation would work, by clicking on the button labeled Move On after a user was done with swiping through their options for the “Base Layer” - and again after the “Extras” layer
We tested our designs with a representative end user. We learned some valuable things about what was going well and what still needed to be improved. Overall, the SUS score was 72.5, which rates at about a B on a standard scale for usability. The contextual information provided to the user, like the weather, their schedule, and their commute, was seen as incredibly valuable. The ability to swipe between clothing options was a natural experience, and providing feedback on the outfit was an intuitive flow.
However, the “Move on” and “Done” labels on the buttons caused confusion along with navigational elements. The user had trouble knowing where she was and where to go next without just clicking around - this confusion extended to the content home screen, as she wasn’t sure what she was looking at when she was done with the workflow - if we were displaying today’s outfit or tomorrow’s suggestion. She also expressed that the feedback choices were not clear enough and sometimes didn’t accurately represent feedback she would have wanted to give about a particular type of clothing (for instance, shoes being too heavy/too light didn’t match her mental model).
Based on the insights from the user test, we iterated on the following areas:
Navigation and Progress: Changed content of buttons (move on) and labels (base layer, extras) to be more intuitive
Improved how we show progress through the steps of the workflow
Logical Feedback Options: Improved the options you get when providing feedback and make sure they’re specific to the type of clothing you’re giving feedback on
Better Home Screen: Made the home screen more intuitive
Go into balsamiq for clothing selection process - swiping, moving through tabs. Then switch to protocast for feedback/input/turning off the mirror
https://prototypinggroup4.mybalsamiq.com/projects/presentationfinaldeliverable/prototype/5.0?key=b61505117a56fb5aa6f0aeb910b78ba160e87446
Show protocast (3:24 → end)
Many IxD principles served as guiding beacons for us as we were developing solutions. Some of them were:
SIMILARITY (we placed—generally—the articles of clothing in the same spots that you would see them if you looked at yourself in a mirror, thereby easily orienting the user to the layout of the display). IxD also focuses around how technology should work considering human behavior, which is why we didn’t put the shoes on the bottom of the screen. Human behavior indicates that it’s a strain to bend over each time to swipe through the shoes
WAYFINDING (letting the user know where they are, and where they are going)
CHUNKING (how we broke it up into 3 sections instead of throwing everything on 1 screen)
VISIBILITY (guiding the user through the process again, by means of the progress bar as well as our guiding modals)
And we also wanted to share some specific highlights of design elements that specifically addressed the problem.
View of calendar, weather, and schedule - organizing all of this relevant information and making it consistently visible to the user in one spot
Navigation - navigation was something we worked on for quite a bit. Because we were dealing with limited real estate, we had to develop a solution that not only served as the primary navigation for the interface, but also giving the user a sense of progress
Giving feedback on clothing suggestions - this is where the “smart” comes from in our “smart mirror.” Users are able to go to their Dress Yo’Self smart mirror at the end of the day and comment on what worked well and what didn’t, and the reasons behind that feedback. Through that feedback, the mirror gets smarter about the user’s preferences
Inputting clothing - the options will be based on the user’s real clothing, not general terms such as, “sweater” or “jeans.”