For product and UX
Friction and confusion, each tied to the step and screenshot where it happened.
Friction, with the screenshot
Findings have five kinds. Friction, question and accessibility are about the experience. Bug and permission are about the code. This one is measured at step 6 of run 2026-10-17-sam-author-006 and confirmed by the reviewer.
Personas have devices and habits
- Role
- Author
- Device
- Phone, 390 by 844
- Goals
- Submit a draft. Reply to review comments
- May
- write draftsreply to reviews
- May not
- approveschedule
The device sets the viewport and the user agent, so the same scenario on a phone and a desktop can produce different findings. Every persona trait needs a source, and the writing guide removes traits without one.
Questions are findings too
| Finding | Kind | Severity | Persona | Runs | Verdict |
|---|---|---|---|---|---|
| A contributor can open the rates table for all writers | permission | major | lin-contributor | 1 | confirmed |
| On a phone the Submit button sits under the keyboard | friction | major | sam-author | 2 | confirmed |
| Scheduling an issue for a past date returns a server error | bug | major | ada-editor | 1 | confirmed |
| The draft title field has no accessible name | accessibility | minor | sam-author | 1 | pending |
| The payment status "settled" is unclear to a contributor | question | info | lin-contributor | 3 | pending |
In run 2026-10-16-lin-contributor-002 the contributor asked what the payment status “settled” means. That is a question finding, tagged inferred because it rests on the persona’s reasoning. Personas are fictional and nothing watches real users.
Sources
The finding kinds and evidence tags are in the run record schema, code. The two runs above are synthetic examples in examples/runs/, measured.