For those of you who are interested in getting a job or an internship in UX
http://vitamintalent.com/vitabites/get-your-next-ux-job-create-a-killer-sample-deck
This is another article that offers clarification on the use of personas.
The persona method has developed from being a method for IT system development to being used in many other contexts, including development of products, marketing, planning of communication, and service design. Despite the fact that the method has existed since the late 1990s, there is still no clear definition of what the method encompasses. Common understanding is that the persona is a description of a fictitious person, but whether this description is based on assumptions or data is not clear, and opinions also differ on what the persona description should cover. Furthermore, there is no agreement on the benefits of the method in the design process; the benefits are seen as ranging from increasing the focus on users and their needs, to being an effective communication tool, to having direct design influence, such as leading to better design decisions and defining the product’s feature set (Cooper, 1999; Cooper et al, 2007; Grudin & Pruitt, 2002; Long, 2009; Ma & LeRouge, 2007; Miaskiewicz & Kozar, 2011; Pruitt & Adlin, 2006).
UX work happens in many different contexts, from very lean startups that employ Agile methodologies and embrace little documentation, to consulting engagements for third-party clients, all the way to large corporate or government environments with strict process and documentation requirements. What unites these very different work environments is the need for UX professionals to communicate design ideas, research findings, and the context of projects to a range of audiences. Though we often communicate our work in conversation with others, deliverables help us document work for discussion, presentation, implementation, and later reference.
http://www.nngroup.com/articles/common-ux-deliverables/
Create two (2) Personas and two (2) Scenarios (this would be one scenario for each persona).
Create two (2) Personas and two (2) Scenarios (this would be one scenario for each persona).
These are examples of some of the decks created in last semester’s UX/UI Design class.
A scenario is a “day in the life of” one of your personas. It should include both the persona’s daily working tasks as well as how your app or website fits into their lives.
Writing a scenario is as simple as taking your research and extrapolating from it to document the tasks that your persona’s perform when using your product.
http://www.uxforthemasses.com/scenario-mapping/
https://uxthink.wordpress.com/2010/11/30/using_scenarios/
http://www.usability.gov/how-to-and-tools/methods/scenarios.html
http://www.uiaccess.com/accessucd/scenarios_eg.html
A persona is a fictitious identity used to represent one of the user groups for who you are designing. They are created by taking both qualitative and quantitative data from; analytics, surveys, interviews user testing and other research techniques that the UX designer uses to craft a sketch of an ideal user.
A good persona needs a name, photo, realistic and research based motivations and goals, and a backstory rooted in reality.
http://www.usability.gov/how-to-and-tools/methods/personas.html
http://www.sitepoint.com/create-data-backed-personas/
http://uxmastery.com/create-ux-personas/
http://www.ux-lady.com/introduction-to-user-personas/
http://www.uiaccess.com/accessucd/personas_eg.html
Homework—Group Project
https://www.interaction-design.org/literature/article/5-simple-usability-tips
The OpenLab is an open-source, digital platform designed to support teaching and learning at City Tech (New York City College of Technology), and to promote student and faculty engagement in the intellectual and social life of the college community.
