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.

Practice

1. What is the main purpose of using a design sprint workflow in Figma?

easy

A. To create complex animations for marketing

B. To solve problems quickly with clear, organized steps

C. To write code for app development

D. To manage financial reports

Solution

1. Step 1: Understand design sprint goals

   Design sprints focus on solving problems fast by following clear steps.

2. Step 2: Identify Figma's role

   Figma helps organize these steps visually and supports collaboration.

3. Final Answer:

   To solve problems quickly with clear, organized steps -> Option B

4. Quick Check:

   Design sprint = fast problem solving [OK]

Hint: Design sprints = fast, clear problem solving [OK]

Common Mistakes:

• Confusing design sprints with coding tasks
• Thinking Figma is for financial data
• Assuming design sprints create animations

2. Which Figma feature is best for organizing each day of a design sprint visually?

easy

A. Components

B. Plugins

C. Frames

D. Prototypes

Solution

1. Step 1: Identify visual organization tools in Figma

   Frames act like containers to organize content visually on the canvas.

2. Step 2: Match frames to sprint days

   Each sprint day can be a separate frame to keep work clear and structured.

3. Final Answer:

   Frames -> Option C

4. Quick Check:

   Frames = organize sprint days [OK]

Hint: Use frames to separate sprint days visually [OK]

Common Mistakes:

• Confusing components with layout containers
• Thinking plugins organize sprint days
• Mixing prototypes with visual organization

3. Given a Figma file with frames named "Day 1", "Day 2", and "Day 3", what is the best way to share the sprint progress with a remote team?

medium

A. Share the Figma file link with view-only access

B. Copy and paste frames into a Word document

C. Print the frames and mail physical copies

D. Export each frame as a PNG and email them separately

Solution

1. Step 1: Consider collaboration features in Figma

   Figma allows sharing a live file link for real-time viewing and commenting.

2. Step 2: Evaluate options for remote teamwork

   Sharing the file link is faster and keeps everyone updated compared to static exports.

3. Final Answer:

   Share the Figma file link with view-only access -> Option A

4. Quick Check:

   Live link sharing = best remote collaboration [OK]

Hint: Share live Figma links for easy team updates [OK]

Common Mistakes:

• Using static images loses live updates
• Physical copies are slow and outdated
• Copy-pasting reduces design quality

4. You created a prototype in Figma but team members report they cannot click through screens. What is the most likely issue?

medium

A. The text layers are locked

B. The file is not saved

C. The prototype is missing colors

D. Frames are not linked with interaction flows

Solution

1. Step 1: Understand prototype interactions

   Clickable prototypes require linking frames with interaction flows in Figma.

2. Step 2: Identify common prototype issues

   If frames are not linked, clicking does nothing, causing navigation failure.

3. Final Answer:

   Frames are not linked with interaction flows -> Option D

4. Quick Check:

   Missing links = no clicks work [OK]

Hint: Check if frames have interaction links [OK]

Common Mistakes:

• Assuming saving fixes interaction issues
• Thinking colors affect clickability
• Believing locked text blocks stop clicks

5. During a design sprint in Figma, you want to gather quick feedback on a prototype from stakeholders who are not familiar with Figma. What is the best approach?

hard

A. Use Figma's share link with comment access and guide them briefly

B. Export the prototype as a PDF and send it by email

C. Ask them to create a Figma account and edit the file

D. Record a video walkthrough and share it privately

Solution

1. Step 1: Consider ease of access for non-Figma users

   Figma's share link with comment access allows feedback without editing or account creation.

2. Step 2: Provide minimal guidance for smooth feedback

   Brief instructions help stakeholders comment directly on the prototype, speeding feedback.

3. Final Answer:

   Use Figma's share link with comment access and guide them briefly -> Option A

4. Quick Check:

   Comment link + guidance = fast feedback [OK]

Hint: Share comment link and guide stakeholders briefly [OK]

Common Mistakes:

• Sending static PDFs loses interactive feedback
• Forcing account creation blocks quick input
• Videos don't allow direct comments