(1) Summarize the project goals, context, and stakeholders

Please provide a solid introduction to your project and your activities.

(2) Summarize your test results.

• What method(s) did you use to evaluate the results of your usability tests?
• How did you evaluate the results?
• What did you learn from the testing? What are your main takeaways? Please list these takeaways.

(3) Compare your results with the defined problem (problem statement) you wanted to solve.

• To what extent have you been able to meet your goals? Discuss it.
• What would be your next steps? How would you proceed with this project?

(1) Continue to improve your high-fidelity prototype.

(2) Prepare for a summative evaluation

We will conduct usability tests during the time in the lab. There will be guests invited from the Human-Centered Computing (HCC) research group, who will function as usability test participants. Please prepare for this test session accordingly. We will have three test sessions per group. A test session lasts about 25 minutes.

Please recall your experience and takeaways from your first testing session: What are things you would like to do differently this time?

Prepare all documents (script, consent form, …) you will need during the test session:

• What documents do you need?
• This time, you will measure the effectiveness using the task completion rate. Please use the provided template (PDF, see below).
• This time, you will also measure the satisfaction of users, by using a post-task or post-test questionnaire. Please choose independently what suits your project.
• Which standardized questionnaire did you choose and why?
• Document your preparation.

(1) Reflect on the results of the heuristic evaluation you conducted in class.

• Summarize your results of the heuristic evaluation.
• Derive the main areas of improvement and justify your further procedure.

(2) Continue to improve your high-fidelity prototype.

• What is needed to have a proper prototype? Make sure that you focus on the important. Please list the areas, you plan and you do work on.
• What improvement have you brought into your prototype?

(3) Prepare another round of heuristic evaluation  (this time you test the interface of another group)

• Reflect on your task flows, and if needed, define or adopt new ones.
• Prepare and provide all material needed for three HE-evaluators in paper format for the next exercise.

We now start working on the Hifi-Prototypes.

(1) List your various requirements elicited from the user research.

• This step should be earlier in the process, as you know, but it is useful for focusing your work

(2) Decide based on your requirements and the insights from the low-fi prototype-testing what functionality to include in your high-fidelity prototype.

• Consider your problem statement
• What insights did you gain from the testing? What are your main takeaways?
• Decide on an approach to select the most appropriate requirements (whatever appropriate means in your context)

(3) Define the major task flow you want to support.

• Based on your scenario, describe at least two major task flows.
• These descriptions will serve as task descriptions for the evaluators within heuristic evaluation next week.

(4) Start building your prototype. The UI should be clearly developed (consider all interaction, visual, and information design)

• Ideally, you can iterate on your existing prototype in Figma.

By now, you have developed a thorough understanding of your project in terms of users, context, and tasks. You have also developed a good understanding of the problem you are trying to solve and an idea of what your solution might look like. Now we put it all together and enter the design space! You will begin to build your first testable prototype.

(1) Summarize the feedback you received on your storyboard.

During the last lab session, you collected feedback from your peers. Please summarize the feedback and document which feedback you will incorporate into your prototype.

(2) Develop an interactive paper prototype.

You will develop a low-fidelity interactive prototype that represents multiple states or views. Think about your persona who wants to use your product: What are the minimum needs of your persona? What are the must-haves?

Please describe briefly:

• Your prototyping process.
• The use case this prototype addresses.
• How the storyboard is reflected in your prototype.
• A self-assessment of the potential strengths and weaknesses of this first step into your design space.

Please make sure that your prototype is clickable and that other people can access your prototype for testing. Please don’t worry about what your prototype looks like! It is not about how nice things look, but about communicating a general idea and the main functionality.

TOOLS FOR INTERACTIVE PAPER PROTOTYPES

Suggested process: Do just one more round on paper or a pad. Make photos and link your screens using:

• Marvel POP (Prototyping on Paper)
  App for iPhone or Android
  This would be just enough for now and has everything to make your photos/screens interactive.
• Marvel
  Web application
  One free project with max. 6 team members.
• Figma
  Web application
  One free team project!
• Invision (Prototype)
  Web application
  One free project with collaborators,

Other tools to consider: Sketch (Mac only!), AdobeXD, Axure (30 day trial), Balsamiq (only a 30 day trial).

This assignment gives you the chance to deepen your knowledge in conceptual model building focusing on tasks. Furthermore, you will create a first prototype in the form of a storyboard.

(1) Formulate a problem and hypothesis statement and document it.

Please use the template (shown in class) introduced in the lab session:

PROBLEM STATEMENT

[The name of your PRIMARY persona] needs a way to[user’s need] because [insight/goal]. We will know this to be true when we see: this quantitative/qualitative measure.

HYPOTHESIS STATEMENT

We believe that by [doing this / building this feature / creating this experience] for[the name of your primary persona], we will achieve [this quantitative/qualitative outcome].

(2) Create individual sketches.

• Now it is time for solutions and first drawings!
• Step 1: Look at your persona, your scenario and reflect on your problem/hypothesis statement, and focus!
• Step 2: Each person in the team is drawing on paper (drawing on a tablet is also okay!) a solution he/she thinks would solve your problem.
• Justify your first design rationales by documenting them using QOC.

(3) Share your sketches with your team.

• Each person should present his/her first drawing to the other team members.
• Select features and ideas you think should be part of your prototype.
• You can use the dot-voting method again to make faster decisions.

(3) Condense your results from the previous step into a storyboard.

• Check out the examples and hints on storyboards on the web…
• You should not spend too much time with it, and your solution does not need to be perfect. We will continue working on that!
• Synthesize your design rationales and document them using QOC.
• This step aims to explain your idea/solution using the storyboard to your fellow students.

1. Derive a primary persona from your data-gathering insights
   • Use one of the examples from the lecture slides as a template (or get inspired by the tools below).
   • Be visual, a picture is mandatory! (Do not forget to specify the image source.)
2. Create a scenario that describes your vision of how your persona interacts with your
   • Use the example from the lecture as a template.
   • Highlight what and where.
3. If you think you need to do more data gathering – go for it!

TOOLS AND TEMPLATES FOR CREATING PERSONAS

• User persona template: 
  • https://xtensio.com/user-persona-template/
  • https://www.flowmapp.com/features/personas
  • https://www.openlawlab.com/2014/09/19/persona-template-user-centered-design-process/
• Images of people generated by a GAN: https://this-person-does-not-exist.com/en or any image https://huggingface.co/spaces/stabilityai/stable-diffusion