[vc_custom_heading text=”Summary:” font_container=”tag:h2|text_align:left|color:%23fc3e1b” google_fonts=”font_family:Montserrat%3Aregular%2C700|font_style:400%20regular%3A400%3Anormal”]
In summary, I thought a lot about how I would begin to approach an assignment where the goal was to define a phase that isn’t exactly in the beginning of the UX thought process.
I wanted to truly understand whom this app was for and who currently uses apps like this. I needed to know what questions I would ask to which users, and why. I also, wanted to know what the business goals were in getting an optimized try-on process.
So, I started with some quick online validated research and took some assumptions from my experience as a designer. I was pretty close with my assumptions on who the users were and what they wanted. I sent out a quick survey via Facebook to my closest friends both female and male in this demographic.
This helped me develop a persona that I could then use to map out user needs, wants and opportunities for a better experience.
I took these ideas and mapped them to a user journey that would tell a story of my proposed experience. I even gave a quick map of these features so the business and developers can see how these all fit together into a robust application.
Whew! Now, with all this ammunition in hand, I have a solid case to explain to my business stakeholders and development team my proposed solution based on user research in this scenario.
They can poke holes in it, ask me why, ask me how and I’ll have some solid answers to give for my recommendations. I can speak for and about the users, referencing my survey and app reviews.
They can ask me how it all fits together, and I can show them my feature map & the conceptual model of user experience I hope to give. I can even scale back with the items I identified as needs vs. wants.
And finally I can speak about the opportunities; the golden nuggets of information that will help the business succeed in creating not only a usable app, but also a meaningful one.