Usability study desk: sessions, findings and the fix to test first

What goes on the desk

• Page ‘Test plan and findings’ (widget page)
• Table ‘Session log’ (Participant code, Task, Stuck (checkbox), Time on task, Note) (widget table)
• Chart ‘Stuck by task’ (widget chart)
• a Voice note for your own debrief after each session (widget voice note)
• Gallery of screenshots (widget gallery)
• Tasks ‘Fixes to test’ (widget tasks).

Set it up

write the plan first (tasks, participants, success criteria); add the log.

1. Create a desk named for the real outcome, client or deadline.
2. Add the suggested widgets and rename each one for the job it performs.
3. Bring in the existing files or tables before inventing another copy of the information.
4. Set a due date, add the first visible next action, then save the arrangement as a template if you will repeat it.

Open this desk in the interactive demo

Use it day to day

log each session straight after; synthesise at the end of the round.

A useful desk should reduce copying. Keep each changing fact in one widget, and let charts, summaries or views read from that source.

A worked starting point

Fictional example. Create the desk, add three real items that are already in motion, then use one full work cycle before changing the layout. At the end, remove anything you did not consult and add only the object that would have prevented a real interruption.

Where Plexii helps

the Voice note gives a transcript, a summary and suggested next steps (widget voice note); Plexii answers which participants struggled with a step, from the log with sources (ai assistant); the Page’s AI draft writes findings sections you review (widget page).

Related resources

• demo
• action item