Module3 Knowledge Check

Module 3 Knowledge Check & Challenge

Test Your Knowledge of Low-Fidelity Prototypes

Question 1

You demonstrate an early product model’s scrolling and click functionality to stakeholders before it goes to engineering. What are you demonstrating?

A design type
A wireframe
A prototype ✓
A storyboard

Answer: A prototype is an early model that demonstrates functionality like scrolling and clicking.

Question 2

What is the most significant difference between a wireframe and a prototype?

Interactivity ✓
Time
Fidelity
Cost

Answer: Interactivity is the key difference - prototypes allow users to click from one screen to another.

Question 3

What is the goal of creating a low-fidelity prototype?

Make it easier for engineers to value the design
Create a complex and interactive design that’s ready for development
Make designs testable to collect and analyze feedback early on ✓
Create a complex and static design to show stakeholders

Answer: Low-fi prototypes make designs testable for early feedback collection and analysis.

Self-Reflection: Your Own Biases

Reflection Questions

Question 1: Take a moment to reflect on your own implicit biases.

Do you have a positive or negative association with people who live in a particular city?
Do you have positive or negative assumptions about a particular gender role?
How have these biases influenced your own design work, your interactions with everyday products, or the people you talk to everyday?

Example Responses

City Associations: “I realize I have assumptions about people from rural vs urban areas - thinking urban people are more tech-savvy. This could affect how I design interfaces, making them too complex for users who might be less familiar with technology regardless of where they live.”

Gender Role Assumptions: “I tend to assume mothers handle most childcare decisions. This showed up when I designed a family app and defaulted to ‘mom-focused’ language, potentially excluding fathers, grandparents, or other caregivers who use family apps.”

Design Impact Example: “When designing a financial app, I realized I was assuming users had stable housing and regular addresses for mail delivery. This bias could exclude people experiencing housing instability who might benefit most from mobile financial services.”

Product Interaction Example: “I get frustrated with voice assistants that don’t understand accents well, but I never considered this might be a bigger barrier for non-native English speakers or people with speech differences until I learned about inclusive design.”

Social Impact Example: “I tend to avoid talking to people who seem very different from me, but working on user research taught me that diverse perspectives make products better for everyone.”

Module 3 Challenge

Question 1

You tell your client that you are transitioning the wireframes of the app you are creating into a low-fidelity prototype. They ask you what the goal of a low-fidelity prototype is. What might you say?

To make the designs with full color, typography, and interactivity
To gain confirmation from the marketing team that brand guidelines have been followed
To make the designs testable, so that feedback can be collected and analyzed early in the process ✓
To provide the engineering team with the screens, directions, and final code for the app

Answer: Low-fi prototypes make designs testable for early feedback collection and analysis.

Question 2

You have decided to move into the prototyping phase for the app you are designing. You recommend starting with a paper prototype first. Your client asks you to explain the disadvantages of a paper prototype. What might you say? Select all that apply.

A paper prototype can only be tested in person. ✓
A paper prototype makes it difficult to collaborate with a remote team. ✓
A paper prototype requires refined drawing and sketching skills in order for the end product to be understandable.
A paper prototype can be difficult to interpret and requires a lot of imagination to picture what the end product will look like. ✓

Answer: Paper prototypes can only be tested in person, are difficult for remote teams, and require imagination to interpret.

Question 3

You are adding connections to your prototype in Figma. You select the presentation view and only see one frame from your prototype. How can you see all of your prototype frames in the presentation view?

You will need to go back to the design panel and ensure that all of the connections are correct.
You will need to double-check the coding with the engineer team and ensure they have transferred it over to Figma correctly.
You will need to go back to the prototype panel and, in the interaction details, make sure “Add connection to Frame” is selected.
You will need to add connections to all of your frames. Figma only includes frames with connections in the presentation view. ✓

Answer: Figma only shows frames with connections in presentation view, so you need to add connections to all frames.

Question 4

You would like to conduct a usability test on your Figma prototype. Which mode is the best mode to do this in?

Observation mode ✓
Feedback mode
Comment mode
Suggestion mode

Answer: Observation mode allows you to watch users interact with your prototype during testing.

Question 5

You have designed a mapping app for a large city. The app provides travel directions only for walkers. You did not account for automobiles, public transportation, or bicycle transportation. Which type of bias did you exhibit with the creation of this app?

Implicit bias ✓
Expectancy bias
Confirmation bias
Unconscious bias

Answer: Implicit bias - unconsciously assuming walking is the primary transportation method.

Question 6

You are booking travel through a travel website. When you get to the checkout page, you see that your flight and hotel are in the shopping cart as you indicated. But, you also notice that trip insurance is in the shopping cart. You did not add that trip insurance and remove it from the shopping cart. What type of deceptive patterning is this considered?

Forced continuity
Sneak into basket ✓
Proactive sales
Confirmshaming

Answer: Sneak into basket - items added to cart that users must remove if they don’t want them.

Question 7

Your UX design mentor explains and provides examples of deceptive patterning to you. What is the first step to avoid deceptive patterning in your UX design?

Ask stakeholders what you can add to your designs to trick others into engaging with your app.
Notify the marketing team about any indications of deceptive patterning.
Ask a deceptive pattern expert to audit your designs and flag anything that looks suspect.
Recognize what it is and how the patterns are used. ✓

Answer: Recognition is the first step - you need to identify deceptive patterns before you can avoid them.

Question 8

Your UX mentor discusses deceptive patterning with you and asks for examples of how you could avoid forced continuity, or the notion of charging a membership without a warning or reminder. What examples could you provide? Select all that apply.

Decrease the pressure on the user to commit to the membership.
Make it easy for users to cancel their memberships. ✓
Ensure the buttons are clearly labeled. ✓
Notify users before their free membership trial expires. ✓

Answer: Avoid forced continuity by making cancellation easy, using clear labels, and notifying before trial expires.

Question 9

You have created your wireframes in Figma and are ready to move them into a low-fidelity prototype. What tab should you choose to start this transition?

The device tab
The connection tab
The prototype tab ✓
The design tab

Answer: Switch from Design tab to Prototype tab to start adding interactive connections.

Question 10

As you work on the app for your client, you want to ensure you are considering users’ attention economy. What are some UX design best practices you can use to accommodate this? Select all that apply.

Use goals and metrics. ✓
Share your design choices with your colleagues. ✓
Employ soothing colors and imagery.
Avoid deceptive patterns. ✓

Answer: Consider goals/metrics, share good practices with colleagues, and avoid deceptive patterns to respect users’ attention.