How to Collect Useful Feedback on a Figma Prototype
A lightweight workflow for getting focused feedback on an interactive prototype without confusing preference with usability.
Set one task or decision
Prototype feedback works best when participants understand what they are reviewing.
- Share a working prototype link and confirm its permissions before inviting participants.
- State the scenario, such as ‘Find where to change your notification settings,’ without revealing the answer.
- Choose whether you need comprehension, expectations, or preference feedback. These are different questions.
Keep questions neutral
Prompt participants to describe what they saw and expected.
- Ask ‘What would you do next?’ rather than ‘Was this easy to use?’
- Ask what they thought a button or screen would do before explaining it.
- Include an open question for anything unexpected or missing.
Interpret feedback carefully
Self-reported reactions do not prove that someone completed a task successfully.
- For critical usability questions, observe actual task attempts or use a moderated test.
- Separate reported confusion from a verified interaction failure.
- Record the prototype version so later feedback can be interpreted against the correct design.
Make a concrete revision decision
Use recurring issues to choose the next iteration.
- Group feedback by issue, not just by positive or negative sentiment.
- Prioritize issues that block understanding or a critical task.
- Test the revised prototype with fresh participants when possible.
Related workflows
Use these resources to put the guidance into practice.
Turn a question into a validation
Create a focused validation, share it with relevant participants, and review their responses.