Design sprint workflow in Figma - Dashboard Guide

Dashboard Mode - Design sprint workflow in Figma

Goal

Understand the step-by-step design sprint workflow visualized in Figma to track progress and collaboration.

Sample Data

Task	Owner	Status	Day	Time Spent (hrs)
Understand Problem	Alice	Complete	Day 1	3
Sketch Solutions	Bob	Complete	Day 2	4
Decide on Solution	Carol	In Progress	Day 3	2
Prototype	Dave	Pending	Day 4	0
Test with Users	Eve	Pending	Day 5	0

Dashboard Components

• KPI Card: Total Hours Spent
  Formula: SUM of 'Time Spent (hrs)' column = 3 + 4 + 2 + 0 + 0 = 9 hours
• KPI Card: Tasks Completed
  Formula: COUNT of rows where Status = 'Complete' = 2
• Bar Chart: Hours Spent per Day
  X-axis: Day (Day 1 to Day 5)
  Y-axis: Time Spent (hrs)
  Bars: 3, 4, 2, 0, 0 hours respectively
• Status Table: Shows Task, Owner, and Status columns for quick status overview

Dashboard Layout

+----------------------+----------------------+
|  KPI: Total Hours    |  KPI: Tasks Completed |
|       9 hrs          |          2           |
+----------------------+----------------------+
|                      Bar Chart: Hours Spent per Day                      |
| Day 1 | Day 2 | Day 3 | Day 4 | Day 5                                   |
|  3    |  4    |  2    |  0    |  0                                     |
+-------------------------------------------------------------------------+
|                            Status Table                                 |
| Task            | Owner | Status                                         |
| Understand Problem | Alice | Complete                                       |
| Sketch Solutions  | Bob   | Complete                                       |
| Decide on Solution | Carol | In Progress                                    |
| Prototype        | Dave  | Pending                                        |
| Test with Users  | Eve   | Pending                                        |
+-------------------------------------------------------------------------+

Interactivity

Filter by Status: Selecting a status (e.g., 'Complete') updates the Status Table to show only tasks with that status. The KPI cards update to reflect totals for filtered tasks. The Bar Chart updates to show hours spent only for filtered tasks.

Filter by Day: Selecting a specific day filters the Status Table and KPIs to tasks scheduled on that day. The Bar Chart highlights the selected day's bar.

Self Check

If you add a filter for Status = 'Complete', which components update?

• Status Table shows only 'Understand Problem' and 'Sketch Solutions' tasks.
• KPI Cards update: Total Hours Spent = 7 (3 + 4), Tasks Completed = 2.
• Bar Chart shows hours only for Day 1 and Day 2 bars (3 and 4 hours), other days show zero or are hidden.

Key Result

A Figma-based dashboard visualizing design sprint tasks, hours spent, and status with interactive filters.

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