Figma Prototype Testing
A prototype proves its value only when real people use it. Testing reveals confusing buttons, missing steps, and unclear wording before any code exists. Fixing a problem in Figma takes minutes, and fixing it after launch takes weeks.
Prepare the Prototype
- Set a flow starting point on the first screen.
- Check that every button on the main path has a connection.
- Choose a device preset that matches your target screen.
- Click the Play button in the top-right corner to run the prototype.
Prototype Settings
---------------------------
Starting frame Home
Device Phone
Background Light gray
Hotspot hints On
Hotspot hints flash clickable areas when a tester taps empty space. Turn them on for first-time testers.
Share the Prototype
Click Share in the prototype view and copy the link. Anyone with access can open it in a browser. Send the link to testers or open it on a phone through the Figma mobile app for a realistic feel.
- Check the link permission before sending.
- Test the link yourself in a private browser window.
- Close the prototype link when testing ends.
Write Tasks, Not Instructions
A task describes a goal. An instruction tells the tester where to click. Goals show whether the design guides people naturally.
Weak Strong
--------------------------- -------------------------------------
Click the cart icon. Buy a loaf of bread for pickup tomorrow.
Open the settings page. Turn off all email reminders.
Press Search. Find a recipe that takes under 20 minutes.
Run a Simple Session
Step 1 Welcome the tester and explain you test the design, not them.
Step 2 Read one task aloud.
Step 3 Ask the tester to think out loud.
Step 4 Watch quietly and avoid giving hints.
Step 5 Note where the tester pauses or backtracks.
Step 6 Thank the tester and ask one open question.
Small groups of around five testers often reveal the most common problems. Recruit people who resemble your real users.
Record Findings
A simple table keeps results organized across testers.
Task Tester 1 Tester 2 Tester 3 Issue Noted
------------------- -------- -------- -------- -------------------
Find a recipe Done Done Done None
Save a recipe Stuck Done Stuck Heart icon unclear
Share a recipe Done Stuck Done Share button hidden
Problems that appear for two or more testers deserve fixes first.
Leave Comments on the Design
Press C to place a comment pin directly on the problem area. Teammates see the note beside the exact element, and the pin stays until someone resolves it.
Improve and Repeat
- Rank issues by how many testers hit them.
- Fix the top three problems.
- Test again with fresh testers.
- Compare results between rounds.
Respect Your Testers
- Ask permission before recording any session.
- Avoid collecting personal details that the test does not need.
- Use sample data instead of real customer data inside prototypes.
Common Mistakes
- Explaining the screen before the tester sees it.
- Testing only with colleagues who already know the product.
- Skipping a second round after major changes.
Practice Task: Test a Three-Screen Prototype
Build a small prototype with a home screen, a list screen, and a detail screen. Write two goal-based tasks for it. Ask two friends to try the tasks while you watch. Record every pause in the findings table. Fix the biggest problem and run the test again with a third person. The exercise takes under an hour and teaches the full testing loop.
Round 1 Two testers Note problems
Fix One change Biggest problem first
Round 2 One tester Confirm the fix worked