See where people get stuck in your prototype
A prototype is useful when it shows you what to change. Give participants a concrete task, ask them to complete it and record where they get stuck, with optional expert review alongside.
Why this is hard today
Guesswork
Teams test with colleagues who already know the product.
Wrong signal
Feedback is opinions, not tasks.
Slow answers
Problems are found after the sprint, not before.
How Scrutinizr does it
- 01
Add screens or a link
Upload screenshots or link a Figma or live prototype.
- 02
Write tasks
Concrete tasks such as “add a second user”. Ask whether they completed it and what was hard.
- 03
Add people and experts
Use your users, recruited participants, or UX experts for a heuristic review.
- 04
Fix the top blockers
Blockers are ranked by how many people hit them.
The result
- Task success rate per task
- Blockers ranked by frequency
- Self-reported versus observed completion kept separate
- Optional expert score and notes
Example: barcode-only entry
7 of 20 participants could not add an item without scanning its barcode. Two of three UX experts flagged the same screen. A manual entry button fixed it.
Good to know.
Do you record screens?
Not at the moment. Participants report completion and obstacles; experts can review the prototype directly.
Does it work with Figma?
Yes. Paste a prototype link or connect Figma to attach frames.
How many participants?
Five to eight finds most major issues; 20 gives you reliable success rates.
Make your next move with evidence.
Start with a question and bring your websites, documents, data and customer voices into one evidence trail.