Practice friction log vocabulary: developer friction log sessions, time-on-task measurement, friction point categorization, and sprint-level friction reduction language.
0 / 5 completed
1 / 5
What is a 'developer friction log session'?
A friction log session is a structured UX research method adapted for developer tools: a developer completes a real task while narrating their experience, and an observer logs every point of confusion, delay, or frustration as a 'friction point'.
2 / 5
In a friction log, 'time to complete task X' is used to measure:
Time-on-task is a key friction log metric. Measuring how long it actually takes to complete a common task (e.g., set up a local dev environment) reveals bottlenecks that developers may have normalised.
3 / 5
What does it mean when a friction log says 'the developer was stuck here for 4 minutes'?
In friction log analysis, 4 minutes stuck on a single step is a red flag. Friction logs capture these moments precisely to help platform teams prioritise which pain points to fix first.
4 / 5
'Friction point categorization' means:
Categorising friction points helps platform teams identify systemic issues — e.g., if 70% of friction points are 'documentation' issues, that points to a clear investment area rather than scattered individual fixes.
5 / 5
A team reports 'we removed 3 ___ points this sprint.' What word fits?
'Friction points' is the standard term for specific moments of difficulty in developer workflows. Tracking their removal sprint-by-sprint demonstrates measurable DX improvement.