You design the test. The personas take it.
Build personas from your research, brief the mission like you’d brief a participant, and decide when the run is done. Percio does the walking.
Start testing freeSound familiar
Design reviews end in “I think” versus “I think”
- 01
Your research ends in a deck
Months of interviews, and none of it shows up when the next screen is being decided.
- 02
Testing waits for the next study
The design changes every sprint. The usability test happens once a quarter, if at all.
- 03
The review ends in opinion
You know the flow too well to see it fresh, and nobody else in the room has evidence either.
01 · Your research
A persona built from what you already know.
Describe who you design for in a chat: interviews, notes, segments. Percio compiles it into a persona with a mind of her own — what she notices, what she already knows, what she expects, and how she feels when a screen lets her down.
02 · Your brief
Write the test the way you’d run it
A mission, the scenario she steps into and the condition that ends the run — the same brief you’d give a participant. Improve with AI suggests a sharper wording; you apply it or dismiss it.
03 · The run
Watch it like a moderated session
Every step shows the screen she is on, what she is about to do and why she thinks it will work. You see the hesitation as it happens, not in a summary afterwards.
04 · The evidence
Findings grounded in heuristics, not taste
Each finding names the Nielsen heuristic it breaks, quotes the persona who hit it and points at the step where it happened — ranked by what it did to her, not by how loud it looks.
Under the hood
Every persona thinks before she clicks.
She sorts the screen, notices what stands out, recalls what she knows, decides, and feels the result. Every step leaves a trace you can read.
FAQ
Questions designers ask.
You build them in a chat from what you already know about your users — interviews, notes, segments. There are no built-in personas; each one is yours.