← Blog
How to read a ranked friction list
A practical guide to prioritising what the report tells you.
Start at the top
Findings are ordered by the share of simulated users each one affected. The first item is usually worth fixing before anything else, even if it is not the most interesting.
Check the replay
Before you write a ticket, open the session. Seeing the step in context often changes the fix, and gives you the evidence to persuade a sceptical teammate.
Re-run after every fix
The point of a fast test is a tight loop. Fix one thing, run again, and watch the list change.