P2 - Understanding Users (Learning Pod)

pdf

School

University of California, Irvine *

*We aren’t endorsed by this school

Course

131

Subject

Information Systems

Date

Dec 6, 2023

Type

pdf

Pages

8

Uploaded by ChancellorRoseTurtle31

Report
P2 - Understanding Users (Learning Pod) Due May 19 by 5:30pm Points 200 Submitting a website url New Attempt Updated 05/17 - finalized rubric; see items highlighted in red below Overview You may find it useful to watch my video introduction ( https://uci.yuja.com/V/Video?v=7724687& node=32844731&a=132076964&autoplay=1 ) to this project, but please read every word of the assignment description so you meet all the requirements :) Project 2 and Project 3 are connected to each other. In Project 2, you will do some basic user research and analysis. In Project 3, you will build on top of your findings and conduct basic design and prototyping. Both projects will be conducted in your Learning Pod and will culminate in a reflective report. Specifically, for Project 2 your Learning Pod will: 1. Choose a web app and subpopulation 2. Do some user research (interviews) 3. Analyze your interview data 4. Develop a persona for your subpopulation 5. Write a reflective report (optionally add a "going the extra 7%") 6. Submit your report Step 0: Coordinate With Your Learning Pod This is a group project comprising the members of your Learning Pod . Please see your learning pod assignment ( https://docs.google.com/spreadsheets /d/1FoXUPiAdNcpA6D42kDHRuza0Ka01g_RL/edit?usp=share_link&ouid=111492439692688686211& rtpof=true&sd=true ) . In your Communication Agreement, you should have assigned high-level roles to each teammate. For this project, it can be useful to have a "recruiter," "interviewer," "scribe," "designer," and "reporter." Some members will have multiple roles, but interviewer and scribe must be two different people (the scribe will take notes during the interview). It's a good idea to get an early start coordinating your schedules and deadlines for the key activities of the project. Consider that when you recruit, you must usually schedule an interview a few days in
advance, and some interviewees may be no-shows. You will need to run interviews in groups of two (interviewer and scribe), so schedule coordination can cause further delays. After interviews conclude, you will need a block of time at least 2 hours long with all group members in attendance to conduct your post-interview analysis together ( when2meet ( http://when2meet.com/ ) is a useful tool for finding shared availability); the scribe should share notes from interviews with the team, so that everyone can come to the meeting prepared to do the analysis. Then, a persona that integrates the findings needs to be designed and refined. The final "report" requires time for reviewing drafts and iterating. Step 1: Choose a Web App and Subpopulation Choose a web app that your team would collectively like to focus on for the rest of the quarter. Note that a web app runs in a browser--whether it be desktop or mobile--as opposed to a native app running on an OS. Then, identify the web app's range of target users. Within that range, identify a subpopulation on which you would like to focus your study. Think strategically about which web app and which target population you choose. Consider: do all learning pod members have (free) access to the web app? how easy is it to identify the target users of the web app? how easy is it to recruit interviewees from your chosen subpopulation? how will your choice help you impress potential employers, instructors, and classmates? how will your choice play to your pod's strengths and help develop your weaknesses? Here is an example ( https://docs.google.com/document /d/1WvSIBWM5wfszb9YtXnvobLmkZdgqr2RATwKkmSjFA3g/edit# ) of a web app and target user selection, which might help you apply these questions to your own situation. Step 2: Conduct Interviews You will conduct interviews with several people who your subpopulation. The number of people you need to interview is the same as the number of people in your Learning Pod (i.e., if your Learning Pod has 5 people, you must interview 5 people ). Here's what each person in your pod should do: All pod members: To help prepare for the interview and learn important interviewing skills, all team members should read Making Words Fly ( https://drive.google.com/file/d /180oPArjG03sZfhBIdkfBP4hsa88buWPI/view?usp=share_link ) . Recruiter : It is the recruiter's job to find members of the subpopulation and schedule interviews (consider how to recruit your target user sub-population, identify a recruiting strategy, figure out where to meet for interviews, coordinate schedules w/ scribe and interviewer, etc.). Interviewer (aka UX Researcher) : It is the interviewer's job to develop an interview question protocol
and to run the interview session (consider which questions to ask, which order, which wording, how to introduce yourself, what follow-up questions to ask, how to audio record, where to store recordings, etc.). Recommend 30-60 minutes each. Scribe : It is the scribe's job to attend all interviews and take detailed notes as well as expand these notes for teammates' easy reading (consider how many notes to take during vs. after the interview, how much detail is needed, whether to include some exact quotes or only paraphrase, whether to add reflective comments in the notes or not, how to format the notes). Step 3: Analyze Interviews You will need to distill the interviews down into a single persona. This will require making sense of the key insights gained from each interview and comparing these across interviews. Hosting a FigJam can help you collaboratively cluster findings around various categories you choose to include in your persona (e.g., demographics, hobbies, general tech. use, thoughts about the web app, etc.). All team members : Prepare for the team meeting by reading all the notes and/or listening to the interview audio recordings. During your meeting, discuss the key findings from your interviews, as well as the types of information that you would like to include in your persona. If people's feedback conflicts, or there are simply too many problems to summarize in one persona, make sure you discuss that and make conscious decisions about what to exclude. Recruiter : be sure to remind the team about any biases that may have arisen from your recruiting strategy (e.g., "all our interviewees were juniors in computer science identifying as cis men") Interviewer (aka UX Researcher) and Scribe : be sure to remind the team about any user statements from interviews that they may be forgetting, and keep conversations grounded in the actual data you collected (e.g., "actually, our first interviewee said that they really liked that feature, so maybe that isn't a universal problem") Designer (aka UX Designer) : be sure to focus the team on how insights can lead to categories and labels and pared down content for your persona (e.g., "are there any compelling quotes that stand out to you about that issue? I want to include a quote in our persona.") Scribe : Take notes of key findings and conclusions. Hand these to the Project Manager. Reporter (aka Project Manager) : After the meeting, write up the results of the meeting into clear implications for the persona (you should provide all the content for the persona) and hand it off to the UX Designer and work with the UX Researcher to fill in any gaps (e.g., the name, the portrait, etc.). Step 4: Design a Persona After making sense of your interview data, and coalescing it into a single archetype, you will create a
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
one-page persona. Make sure your persona demonstrates the important qualities described in your assigned readings and discussed in class (e.g., a fictitious name, portrait, etc.). Designer (aka UX Designer) : draft the 1-page persona and integrate feedback from teammates All team members : review the persona and offer feedback Step 5: Write a Reflective Report Your submission will be in the form of a short executive summary with a long appendix. The executive summary should this template ( https://docs.google.com/document/d/191bCp-- v9dIWZX86YIJ0_R2WtRfosSixEEksUUgt51U/edit?usp=sharing ) . Reporter (aka Project Manager) : draft the report for the team and solicit individual contributions from each member for their sections. Submit the report for the team. All team members : contribute to your section, and read the full draft. Double check that it was submitted on time with all it parts. If you have questions about this assignment, please ask them in #ask-the-instructors on Slack so that everyone can benefit from the questions and answers. Step 6: Submit 1. Give the instructional team <inf-131-instructors@uci.edu> edit access to your Google Doc 2. Submit a URL to your accessible Google Doc (note, we will pay attention to whether changes are made after the deadline) Rubric (this is subject to change) Professional formatting - 20pts consistent look and feel, makes use of font size, lists, other forms of text emphasis, margins, images, etc. Single spaced. Clear communication (thesis statements, precise language, few grammatical issues and/or demonstration of effort) Accessibility - 20pts Overview - 10pts (did they answer the questions?) Recruiting - 10pts (did they answer the questions? Did they give evidence?) Interviewing - 10pts (did they answer the questions? Did they give evidence?) Analysis - 10pts (did they answer the questions? Did they give evidence?) Persona Design - 10pts (did they answer the questions? Did they give evidence?) Conclusion - 10pts (did they answer the questions? Did they give evidence?)
Assignment #2 Appendix - Interviewee data - 10pts ( table with participant names and key demographic data related to how they fit the subpopulation--for example, gender/profession/age/etc. ) Interview protocol - 12pts (ordered list of questions, clearly worded, thoughtfully ordered) Interview notes - 20pts (readable and understandable to someone not in the interview, include key quotes, >=1 page per interview) Analysis - 22pts ( screenshot of your analysis diagram and/or notes from your team analysis meeting; if the screenshot is too small to see, please also post a link to your source document ) Persona - 22pts (your whole persona--must be visually coherent, >=3 key components of a persona) Going the Extra 7% Description - 14pts ( indicate briefly, 100 words or fewer, what you did that was "extra" so your grader can evaluate it )
Criteria Ratings Pts 20 pts 10 pts 10 pts 10 pts 10 pts 10 pts Professional Presentation Is there appropriate formatting, consistent look, and feel, makes use of font size, lists, other forms of text emphasis, margins, images, etc. Single spaced. Clear communication (thesis statements, precise language, few grammatical issues and/or demonstration of effort) 20 pts Full Marks 15 pts Mostly Satisfying 10 pts Partially satisfying 0 pts No marks Overview (150-300wds) Briefly describe your entire project. What web app did you focus on? Who was your subpopulation? How did you recruit? Who did you recruit and interview? What were the key insights of your analysis? What are the key characteristics of the persona you created? What can we expect to find in the rest of the report? 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks Recruiting (100-250wds) What did your team learn about recruiting? What would you do differently next time? Support your reasoning with examples. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially Satisfying . 0 pts No marks Interviewing (250-450wds) What did you learn about interviewing / taking notes? What would you do differently next time? Support your thoughts with examples. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks Analysis What did your team learn about analysis? What would you do differently next time? Support your thoughts with examples. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks Persona Design What did you learn about making a persona? What would you do differently next time? Support your thoughts with examples. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Criteria Ratings Pts 10 pts 10 pts 12 pts 20 pts 22 pts 22 pts 20 pts Conclusion Interviews and personas are two common HCI methods. Based on your experience, what do you think their strengths and weaknesses are? As a team that will now be asked to re-design an interface based on these materials, do you think you learned anything useful from this exercise? If so, what? If not, why not? Support your thoughts with examples. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks Appendix - Interviewee data table with participant names and >=2 key categories of demographic data related to how they fit the subpopulation--for example, gender/profession /age/etc. 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially satisfying 0 pts No marks Appendix - Interview protocol high-resolution and readable copy of the interview protocol. The list of questions is clearly worded and thoughtfully ordered. 12 pts Full Marks 10 pts Mostly satisfying 6 pts Partially satisfying 0 pts No marks Appendix - Interview Notes High-resolution and readable copy of the interview notes (may be typed or hand-written) taken during interviews and cleaned up after interview completion. Notes are readable and understandable to someone not in the interview. Key quotes are included. 20 pts Full Marks 18 pts Mostly satisfying 10 pts Partially satisfying 0 pts No marks Appendix - Analysis Screenshot of your analysis diagram and/or notes from your team analysis meeting. Notes / diagram should list key findings from interviews. Due to difficulties making screenshots accessible, you only have to add minimal (>=140 character) alt text. 22 pts Full Marks 18 pts Mostly satisfying 12 pts Partially satisfying 0 pts No marks Appendix - Persona High-resolution and readable image of the created persona. The persona is visually coherent. It includes at least 3 key components of a persona. Due to difficulties making an accessible persona, you only have to add minimal (>=140 character) alt text. 22 pts Full Marks 18 pts Mostly satisfying 12 pts Partially satisfying 0 pts No marks Accessibility Headings, lists, hyperlinks with names, images alt 20 pts Full 15 pts Mostly 10 pts Partially 0 pts No
Total Points: 200 Criteria Ratings Pts 14 pts text, and paragraphs/line spacing (no blank lines). Note: persona and analysis screenshot should have minimal alt text (<=140 characters) because making these types of complex images fully accessible is outside the scope of our class's learning objectives. Marks Satisfying satisfying marks Going the Extra 7% 14 pts A Lot Extra 7 pts A Good Bit Extra 2 pts A Little Extra 0 pts No marks