Assignment 3: Getting the Design Right

3a: Paper Prototype

Due: Wednesday May 8, 3:00pm

The goal of this milestone is to develop an initial paper prototype that will begin to allow testing of your design.

Develop a paper prototype for your design. It should convey critical components of your design, including support for testing your two primary tasks.

  • Include an overview image that shows your entire paper prototype.
  • The prototype should be complete for each task, including enough detail to show how to complete each step in the task. This should include the desired / expected / intended path, but also likely error conditions (e.g., what happens if some participant input is invalid?).
  • The prototype should be at an appropriate level of detail, supporting understanding of critical components of your design and the context of the your primary tasks.
  • The documentation in your report should explain how the components of your prototype are related. This should include detailed images showing each component as you walk through your two primary tasks.

This prototype has been informed by your prior sketching and storyboarding. But it also contains more details than your prior exploratory designs. If necessary or appropriate, revise your tasks or scenarios based on what you learn in prototyping.

We recommend you do these on paper, then capture a high-quality image (e.g., avoid shadows). You may alternatively use an informal drawing tool, but be sure you do not adopt a tool that will start to embed unnecessary assumptions or decisions in your design process.

If you use an informal drawing tool, you will need to have physical copies of your paper prototype throughout upcoming milestones. You will also need the ability to quickly iterate on your paper prototype.

An EXtension Objective, Kinda (1EXP)

What is this?

Not Your Average Piece of Paper

This is not formally an EXtension Objective, but rather a tip that this is a great assignment to put some extra effort into to get an EXP for an "EXceptional Submission"!

Since everyone's paper prototypes will naturally look very different from each other, we can't really specify exactly what features would achieve this "extra mile"; but some features you might bake into your paper prototype to improve its quality include:

    Interactions that go beyond what you can usually do with paper, e.g. incorporating update-able components via transparencies, post-its, etc.

    Clever representations of interactive UI elements, e.g. a working carousel image display or Wheel Picker.

    A supplemental component related to indicating the context of the interaction / representing real-world variables that exist beyond your interface, e.g. depicting the current state of environment through an image backdrop.

Submission Details

If you choose to develop additional components beyond what's strictly required for the assignment, consider including a supplemental PDF document in your submission just highlighting these "Added Features", including details on how you implemented them, what they add to the prototype interaction, etc.

Submission

No more than one page of text in PDF format, to include:

  • An overview image that shows your entire paper prototype.
  • Detailed images showing each component as you walk through your two primary tasks.

Submission Details

No more than one page of text in PDF format, to include.

  • An overview image that shows your entire paper prototype.
  • Detailed images showing each component as you walk through your two primary tasks.

Additional Details

Submit via Canvas here: Canvas - Assignment 3a

In Class

Bring your most up-to-date paper prototype to all future lectures and sections. You will need it to conduct a heuristic evaluation and other activities during class.

Grading

This milestone will be graded on a scale of 10 points:

  1. Overall Completeness and Appropriateness of Paper Prototype: (2 points)

    Include an overview image.

    Include enough detail to support understanding of critical components of your design and the context of your primary tasks.

  2. Completeness, Appropriateness, and Documentation of Each Task: (2 x 3 points)

    Include each step in the task, with enough detail to show how to complete each step.

  3. Clarity and Presentation: (2 points)


3b: Heuristic Evaluation

The goal of this milestone is to conduct heuristic evaluations as part of rapidly iterating on your paper prototype.

You will receive an evaluation in class, and you will supplement this with another evaluation.

In class, pair with another team to conduct heuristic evaluations. One team will conduct a heuristic evaluation of the other’s paper prototype, then the two teams will reverse roles. Each team will therefore conduct and receive one heuristic evaluation.

We will provide a worksheet with Nielsen's heuristics:

3b-nielsen-heuristics.pdf

For each issue identified in evaluation, record:

  • The heuristic that is violated.
  • A description of the usability issue, including an image of the relevant portion of the prototype.
  • A severity rating (ranging from 0 for no problem to 4 for usability catastrophe).

Revise your paper prototype based on what you learn in heuristic evaluation. Your tasks and scenarios are likely stable, but revise them if your evaluation reveals a need.

Outside of class, arrange to receive a second heuristic evaluation (e.g., with another team). You therefore received two heuristic evaluations of your paper prototype. If desired, you may also conduct a heuristic evaluation or cognitive walkthrough of your own paper prototype.

EXtension Objectives

What is this?

More Practice with Heuristics(2EXP)

Part 1: identification. In class, we used and inspection based method to see if your prototypes violated any of Nielsen's heuristics. For this EXP, look at your current prototype and go through each of Nielsen's heuristics. For each heuristic, either 1. describe where your prototype violates the heuristic or 2. explain features of your design that adhere to the heuristic.

Part 2: incorperation. For 3 out of the 10 heuristics, either 1. address the problem that you identified in your current prototype, or 2. alter your design to even better adhere to the heuristic. Submit before and after screenshots of your prototype demonstrating the change along with a text description describing what you changed and how your design now better adheres to the heuristic.

Submission Details

A list of each of the 10 heuristics, and how your prototype violates or adheres to the heuristic. This could be a bulleted list or table, really any readable format.

Screenshots of how you updated your prototype to better adhere to 3 of the 10 heuristics. See part 2 above for full specifications of what details to include.

Submission Details

Records of your inspection-based methods will be submitted as part of later assignments (eg., see Assignment 3c).

Be sure to keep detailed records, including images of relevant portions of the prototype before and after revisions.


3c: Usability Testing Check-in

Due: Thursday May 16, 8:00pm

Note: This assignment is still under construction and updates on EXP will come soon.

The goal of this milestone is to document changes resulting from your inspection-based analyses and to begin usability testing of your revised prototype with participants.

Complete one usability test with your paper prototype, examining your two primary tasks.

Target an appropriate participant based on your design research and resulting design.

Be sure to divide your team into roles when conducting a usability test. There is simply too much required for a single person to effectively conduct a test. As discussed in class, roles include the facilitator, the computer, and one or more observers.

As part of your introduction, have your facilitator show the participant how to interact with your design. Do not show participants how to perform your tasks that you will later test. Instead show them how paper prototyping works, how your system generally works, and give an example of something specific that is sufficiently different from your tasks.

During the test, record a log of critical incidents, including both positive and negative events. For example, a person might comment on something they like or might make a mistake in a task. Record the incident along with a description of the context of the incident.

Consider recording your tests to allow you to see and show exactly what happened. If you do this, obtain permission from the participant and ensure your recording preserves the anonymity of the participant. Frame your shot such that you capture interaction with the prototype without unnecessarily capturing the participant.

Each participant should perform both of your primary tasks. Keep the data separate for each participant and each task. Remember participation must be voluntary, participants should be free to stop at any time, and you should emphasize that your focus is on identifying usability issues in the design.

Revise your paper prototype based on what you learn in usability testing. This can and should include fixing major issues as soon as they are detected, before additional tests. Your tasks and scenarios are likely stable, but revise them if your evaluation reveals a need.

Present your iterative revisions and your plan going forward:

  • Present a table or list of results from your inspection-based methods. We expect you will report at least four identified issues and resulting revisions, which may be small or large. You may report more, but this is the expected minimum. For each identified issue, include:

    • The heuristic that is violated.
    • A description of the usability issue, including an image of the relevant portion of the prototype.
    • A severity rating (ranging from 0 for no problem to 4 for usability catastrophe).
    • An image and explanation of any revision implemented as a result. If you highlight an issue without revising in response to it, provide explanation of that decision.
  • Discuss your first usability test.

    • Provide a description of your testing method and participant (e.g., the participant, the environment where you conducted the test, why you chose this participant and environment, the test protocol, and the roles of each team member who participated in the test).
    • Discuss anything you learned about the testing process itself. This should include at least one part of your method that was especially effective or one revision you decided you need to make to your testing process.
  • Present a table or list of results from your first usability test. We expect you will report at least two identified incidents, which may be small or large. You may report more, but this is the expected minimum. For each critical incident, include:

    • An image of the relevant portion of the prototype.
    • Description of the incident, remembering that these can be either positive or negative.
    • For negative incidents, a severity rating (ranging from 0 for no problem to 4 for usability catastrophe).
    • For negative incidents, an image and explanation of any revision implemented as a result.
    • For positive incidents, describe what was learned from this incident.
  • Submit detailed images of your current paper prototype, as revised in this process. Your design may have changed more or less, so this is intended to fully convey the current state of your design. As before, ensure your prototype is complete, is at an appropriate level of detail, and documents each task. Include both:

    • An overview image that shows your entire paper prototype.
    • Detailed images showing each component as you walk through your two primary tasks.
  • Present your plan for the remainder of your usability tests. Describe what goals you have for the additional tests and any new approaches you will employ. You will conduct one usability test in section, describe your plans for recruiting an additional participant.

As you assemble this documentation of the iterative improvement of your design, you may find that some changes feel minor relative to the overhead of documenting those changes. Your goals in this documentation are to:

  • Show your work in the iterative design process, giving enough insight to understand your progress.
  • Capture a record to which you can return in preparing your web content and presentation.

You may choose to not fully document minor changes, but be sure to document enough for these two goals.

Submission

No more than three pages of text in PDF format.

Be sure:

  • This is a group submission. Ensure your section and names of all group participants are appropriately clear.

  • Review and follow guidance on Clarity and Presentation.
  • All group members need to submit a Contribution Statement
  • Names of participants should be replaced with pseudonyms in all documents. It is important to protect participant anonymity, even in the case that reporting seems harmless.

Submit via Canvas here: Canvas - Assignment 3c

Be prepared to discuss your iterative revision of your paper prototype.

In Class

Bring both your submission and your paper prototype to section. You will need your paper prototype to conduct a usability test during section.

Grading

This milestone will be graded on a scale of 13 points:

  1. Issues Identified from Inspection, Revisions Made in Response: (4 x 1 points)

    Include the heuristic that is violated, a description and image of the issue, a severity rating, and any revision.

  2. Discussion of Usability Test and Plan: (2 points)

    Describe your participant, environment, your rationale for both, your test protocol, and the roles of each team member.

    Discuss what you learned about your testing process itself.

  3. Issues Identified in Usability Test, Revisions Made in Response: (2 x 1 points)

    Include an image of the relevant portion of the prototype and a description of the incident.

    For negative incidents, include a severity rating and any revision.

    For positive incidents, describe what was learned from this incident.

  4. Updated Images of Paper Prototype: (3 points)

    Include an overview image.

    Include enough detail to support understanding of critical components of your design and the context of your primary tasks.

    Include each step in the task, with enough detail to show how to complete each step.

  5. Clarity and Presentation: (2 points)


3d: Usability Testing Review

Due: Monday May 20, 3:00pm

Note: This assignment is still under construction and updates on EXP will come soon.

The goal of this milestone is to complete usability testing of your prototype with participants.

Complete a total of at least three usability tests and finalize your paper prototype according to what you learn.

Present the results of your usability testing and your final paper prototype:

  • Discuss your three usability tests.

    • Provide a description of your testing method and participant (e.g., the participant, the environment where you conducted the test, why you chose this participant and environment, the test protocol, and the roles of each team member who participated in the test).
    • Briefly discuss anything you learned about the testing process itself. This should include at least one part of your method that was especially effective or one revision you decided to make to your testing process.
  • Present a table or list of results from your three usability tests. We expect you will report at least three identified incidents, which may be small or large. You may report more, but this is the expected minimum. This may include incidents you previously reported from your first usability test, but may also be completely different in order to focus on the most important incidents you want to report. For each critical incident, include:

    • An image of the relevant portion of the prototype.
    • Description of the incident, remembering that these can be either positive or negative.
    • For negative incidents, a severity rating (ranging from 0 for no problem to 4 for usability catastrophe).
    • For negative incidents, an image and explanation of any revision implemented as a result.
    • For positive incidents, describe what was learned from this incident.
  • Submit detailed images of your final paper prototype, as revised in this process. Your design may have changed more or less, so this is intended to fully convey the current state of your design. As before, ensure your prototype is complete, is at an appropriate level of detail, and documents each task. Include both:

    • An overview image that shows your entire paper prototype.
    • Detailed images showing each component as you walk through your two primary tasks.
  • Discuss two to four revisions that you consider to be your most salient and important modifications based on issues identified in inspection, usability testing, or critique. These may already be included in the above list, but discuss them in more detail and argue why detecting and fixing them is important to your design.

  • Discuss at least one revision you made to promote inclusivity in your design. Describe an unintentional assumption you identified in your design, then describe how you revised your design to address this assumption. If you are unable to identify this before this submission is due, you may discuss this more in section and submit a revised assignment adding this.

As you assemble this documentation of the iterative improvement of your design, you may find that some changes feel minor relative to the overhead of documenting those changes. Your goals in this documentation are to:

  • Show your work in the iterative design process, giving enough insight to understand your progress.
  • Capture a record to which you can return in preparing your web content and presentation.

You may choose to not fully document minor changes, but be sure to document enough for these two goals.

Submission

No more than three pages of text in PDF format.

Be sure:

  • This is a group submission. Ensure your section and names of all group participants are appropriately clear.

  • Review and follow guidance on Clarity and Presentation.
  • All group members need to submit a Contribution Statement
  • Names of participants should be replaced with pseudonyms in all documents. It is important to protect participant anonymity, even in the case that reporting seems harmless.

Submit via Canvas here: Canvas - Assignment 3d

In Class

Bring both your submission and your paper prototype to section. You will need your paper prototype for final critique.

Grading

This milestone will be graded on a scale of 16 points:

  1. Discussion of Usability Tests: (2 points)

    Describe your participant, environment, your rationale for both, your test protocol, and the roles of each team member.

    Discuss what you learned about your testing process itself.

  2. Issues Identified in Usability Tests, Revisions Made in Response: (3 x 1 points)

    Include an image of the relevant portion of the prototype and a description of the incident.

    For negative incidents, include a severity rating and any revision.

    For positive incidents, describe what was learned from this incident.

  3. Updated Images of Paper Prototype: (3 points)

    Include an overview image.

    Include enough detail to support understanding of critical components of your design and the context of your primary tasks.

    Include each step in the task, with enough detail to show how to complete each step.

  4. Discussion of Key Revisions in Design Process: (2 x 2 points or 4 x 1 points)

    Convey your most important modifications and why detecting and fixing them has been important.

    If you discuss fewer examples, provide justification and explanation of that focus.

  5. Discussion of Revisions to Promote Inclusivity: (4 points)

    Include an identified assumption, the revision, and how it addresses the assumption.

  6. Clarity and Presentation: (2 points)


3e: Digital Mockup

Due: Thursday May 23, 3:00pm

The goal of this milestone is to transition your prototype into a digital mockup of your design.

Create your digital mockup based on your final paper prototype. Do not begin working in digital prototyping until you finish revising your paper prototype. It is much easier to iterate on your design in the paper prototyping phase.

As you transition into digital prototyping, you will need to consider other aspects of the design. This can include detail you may not have previously considered (e.g., visual design, layout, color, typography), but can also include constraints or mismatches introduced by the technology itself. Note decisions or changes you need to make as you transition from paper to a digital representation.

The mockup should effectively communicate your design in a manner appropriate for your web content, presentation, and poster. Implement your digital mockup to include key frames that illustrate your design. It should convey all critical aspects of your design, including walkthroughs for your two primary tasks.

We have no strong preference regarding what digital tools you use to create your mockup. But it must be digital (e.g., you may not use pictures of a hand-drawn sketch). Some tools support creation of interactive mockups (e.g., allow clicking active regions to move between screens). You are welcome to use such a tool, and such interactivity may be helpful. But interactive mockups are neither expected nor required.

Figma is a widely-used web-based collaborative tool:

Other commonly-used tools include:

Present your digital mockup together with discussion of the decisions and changes you made:

  • Submit detailed images of your digital mockup. Include both:

    • Overview images that show your digital mockup.
    • Detailed images showing each component as you walk through your two primary tasks.
  • Discuss decisions and changes you made in implementing the digital mockup.

    • We expect you will report at least three decisions or changes you made, which may be small or large. You may report more, but this is the expected minimum.
    • Describe each decision or change in a few sentences, including why the change was necessary or desired. Include images to be sure it is easy to understand the decision or change.

As you assemble this documentation of the iterative improvement of your design, you may find that some changes feel minor relative to the overhead of documenting those changes. Your goals in this documentation are to:

  • Show your work in the iterative design process, giving enough insight to understand your progress.
  • Capture a record to which you can return in preparing your web content and presentation.

You may choose to not fully document minor changes, but be sure to document enough for these two goals.

Submission

No more than one page of text in PDF format.

Be sure:

  • This is a group submission. Ensure your section and names of all group participants are appropriately clear.

  • Review and follow guidance on Clarity and Presentation.
  • All group members need to submit a Contribution Statement
  • Names of participants should be replaced with pseudonyms in all documents. It is important to protect participant anonymity, even in the case that reporting seems harmless.

Submit via Canvas here: Canvas - Assignment 3e

Be prepared to discuss your digital mockup and revisions that occurred in its creation.

Grading

This milestone will be graded on a scale of 14 points:

  1. Overall Completeness and Appropriateness of Digital Mockup: (3 points)

    Include an overview image.

    Include enough detail to support understanding of critical components of your design and the context of your primary tasks.

  2. Completeness, Appropriateness, and Documentation of Each Task: (2 x 3 points)

    Include each step in the task, with enough detail to show how to complete each step.

  3. Discussion of Decisions and Changes in Implementation: (3 x 1 points)

    Describe each decision or change and why is was necessary or desired.

    Include images to convey each decision or change.

  4. Clarity and Presentation: (2 points)