2 – Beta + User research + UX map

Checkpoint Two

Peer evaluation one 

(two points, graded separately)

  • Click here to complete your peer evaluation
  • If you do not complete peer evaluations for your peers, you will receive a zero (even if you receive outstanding reviews)

Checkpoint Two Assignments (10 points total / 2.5 points each)

Rubric

Each of the four items below will be graded according to the following scale.

  • 2.5 points: 🔥 
  • 2 points: 👏 
  • 1.5 points: 👍 
  • 1 point: 😐 
  • .5 points:🤦‍♂️ / 🤦‍♀️ 
  • 0 points: 👻 
0. Presentation
  • 3-5 minutes long
  • All team members must present
  • Slides are required, and their design will influence your grade
  • While perfection isn’t the goal here, you should be clearly rehearsed, and we’ll begin to more closely evaluate your presentation skills
  • You should update us on how your user research is going, show off your beta in working form, and give us a quick (but not comprehensive) tour of your UX map
1. Beta
  • Your beta will be evaluated during your presentation; no other submission is necessary
  • We’re looking for clear progress from your alpha; therefore, a quick recap of what you had working in your alpha will be helpful
  • We want to see the core functionality of your app / a tech demo of your MVP (minimum viable product) working. After this presentation, we (your instructors) should let out a sigh of relief and think to ourselves, “Okay, they can actually pull this off.”
2. User Research
  • This assignment can take the form of a Google Doc, slides, or a PDF, and it shouldn’t be text alone. Images, videos, charts, pull quotes, etc. should help illustrate your work.
  • We’re looking for a clear summation of your user research strategies, your findings so far, and your future plans (remember, user research / testing should continue up until SLAM).
Interview Guide
  • Research and Gathering Information
    1. Before an interview, research the subject and the topic you are asking about extensively. Google can be your best friend here.
    2. Always ask more open-ended questions to avoid yes/no answers. This way people will give you longer, more expressive answers.
  • Interview Techniques
    1. Come prepared with questions, but be comfortable going off of the script if they have more to say or you think of follow-up questions. 
    2. Have a consent form prepared or recorded verbal consent before starting the interview. 
    3. When beginning the interview, ask them some basic start-up questions to allow them to warm up before answering more in-depth questions. 
    4. Always take notes during the interview. Take notes of your surroundings, your interviewee’s actions, and quotes you believe will be important. 
  • Processing Data
    1. After an interview, relisten to the interview and pull quotes that you believe will be the most important and interesting. 
    2. Figure out the similarities and differences between the people you interviewed. Take note of what works and what doesn’t!
  • Recording Technology
    1. It’s always important to have a record of what your interview subject said, so that you may go back and have a word-for-word account of what they said.
    2. You don’t need to buy any special recording device, your phone will do just fine!
    3. You are welcome to use the built-in voice memos app in your phone, however, it may be a slow process of transcribing your interview. 
    4. It may be beneficial to download Otter.ai to automatically transcribe your audio. However, do not just copy and paste over the transcription to your data as the AI can make mistakes so always proofread!
  • Submit your user research doc in this Google Drive Folder
  • Use the following naming convention: Project Name_Deliverable Name
    • Acceptable Example: Travlr_User Research
    • Unacceptable Example: User Research 9.10
3. UX Map
  • We’re looking for a hybrid of a user story and a wireframe / storyboard. That is, we’re looking for you to communicate both a) who might use your app and in what context and b) the core flows of your app.
  • We couldn’t care less what tool you use as long as you use it effectively. Adobe XD and InVision Studio are leading contenders, but Marvel, Illustrator, Sketch, Keynote, and pen and paper are all viable options, too.
  • Thoughtful attention to detail is key. We want to see every detail considered, and we hope to see insights from your user research present themselves in the designs you share.
  • We also hope to see you adhering to the idioms of your platform.
  • Stay relatively low fidelity here—now’s not the to emphasize pixel-perfect designs, logo work, or color schemes. Focus on structure, not style.
  • Submit your UX map in this Google Drive Folder
  • Use the following naming convention: Project Name_Deliverable Name
‼️ Last Thing ‼️

We need your team name and desired website URL. Simply visit and complete this very brief form by Checkpoint 2 deadline.

Table of Contents