Design sprint workflow in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the Purpose of a Design Sprint Workflow

What is the main goal of using a design sprint workflow in Figma for a product team?

A To quickly prototype and test ideas to reduce risk before full development

B To create detailed final designs without user feedback

C To replace all user research with automated tools

D To finalize the product launch plan without design iterations

💡 Hint

Think about why teams use sprints to save time and effort.

The design sprint workflow helps teams prototype and test ideas fast, reducing risks before investing in full development.

❓ visualization

intermediate

Identifying Key Stages in a Design Sprint Workflow

Which of the following sequences correctly represents the typical stages of a design sprint workflow in Figma?

A Prototype & Test & Sketch & Decide & Understand & Map

B Decide & Understand & Map & Sketch & Test & Prototype

C Understand & Map & Sketch & Decide & Prototype & Test

D Test & Prototype & Decide & Sketch & Map & Understand

💡 Hint

Remember the logical order from problem understanding to testing.

The design sprint typically starts with understanding the problem, mapping it, sketching solutions, deciding on the best, prototyping, and finally testing.

❓ data_modeling

advanced

Organizing Figma Components for a Design Sprint

In Figma, how should you organize components to best support collaboration during a design sprint?

A Duplicate components for each team member to avoid conflicts

B Create a shared library with clearly named components and use pages for each sprint stage

C Keep all components in one page without naming conventions

D Use raster images instead of components to speed up loading

💡 Hint

Think about how to keep designs consistent and easy to update.

Using a shared library with clear naming and organizing pages by sprint stages helps teams collaborate efficiently and maintain consistency.

🎯 Scenario

advanced

Handling Feedback During the Test Stage in Figma

During the test stage of your design sprint in Figma, you receive conflicting feedback from users. What is the best way to document and manage this feedback within Figma?

A Export the prototype as images and collect feedback outside Figma only

B Ignore conflicting feedback and proceed with your original design

C Delete prototype screens that received negative feedback

D Use Figma comments pinned to relevant prototype screens and organize feedback in a dedicated page

💡 Hint

Consider how to keep feedback connected to design elements for easy reference.

Pinning comments to prototype screens and organizing feedback in a dedicated page helps track issues clearly and supports iteration.

🔧 Formula Fix

expert

Fixing Prototype Interaction Issues in Figma Design Sprint

You created a prototype in Figma for your design sprint, but clicking a button does not navigate to the intended screen. Which option correctly fixes this issue?

Figma

Prototype interaction setup:
Button on Frame A -> Navigate to Frame B

Observed behavior: Clicking button does nothing.

A Ensure the button is set as a clickable hotspot and the interaction is linked to Frame B in prototype mode.

B Disable prototype mode and use presentation mode instead.

C Delete Frame B and recreate it with the same name.

D Convert the button to a raster image to fix interaction.

💡 Hint

Check how interactions are assigned in Figma prototypes.

Interactions must be assigned to clickable elements and linked properly to target frames in prototype mode for navigation to work.