Use case
A usability session that turns into a report
The session with the participant is over and what is left is an hour of recording and your memory. The document comes out with the moments that matter, the screen of each one, and the moderator’s speech kept apart from the participant’s.
Three things for the session report
Five participants, one report. Export each session and merge them all at once: each participant becomes a task in the document, with their own time, and each one’s speech in the right place.
The clip of the moment, not the whole session. Only the 15 seconds around what you marked are kept, and only if you switch it on. The rest of the video is discarded — and what was kept you erase with one click, which is recorded in the document.
Every moment has a type. Friction, gave up, praised or defect. It goes into the spreadsheet, and it is how you tell the story without re-watching three hours of recording.
Record a session now free — and the participant’s recording does not leave your computer
The pain
Five participants, an hour each, and the analysis takes longer than the sessions. Rewatching to find the minute where the person got stuck is the work — and the report has to be out before the next sprint, not after.
And there is a problem research tools do not solve: the recording is personal data. A session with an external participant, a screen with real data, the face and voice of someone identifiable. Uploading that to a vendor’s cloud is a conversation with legal that a lot of research does not survive.
What comes out
A session report where you can find the moment without reopening the video:
- Moderator and participant kept apart in the transcript — the two audio channels come out labelled, and the report knows who asked what
- Mark the moment during the session: the button on the floating window forces a frame and marks it, without interrupting the person
- Participant code instead of name — the field already reads that way, because the default is what teaches anonymisation
- Redaction to anonymise whatever shows up on screen, burned into the exported image
- Clock time on every moment, to cross-check against your paper notes
- A prompt ready for the report: friction, abandonment and praise marked one by one, findings in order of severity
How to do it
- Pick the Usability test use case in step 1.
- Start recording before the participant shares their screen, with your microphone on.
- During the session, use mark screen on the floating window whenever something important happens — that is what you will be looking for afterwards.
- At the end, keep only the marked moments, fill in study and participant code, and produce the document.
What it does not do — better to know up front
It does not keep the whole session as video. The ~15 s clip around each mark does exist, comes out in the .zip and opens inside the document — but only if you switch it on before recording, and an old browser may not record it. The rest of the recording is still discarded, and that is what makes client sessions workable.
It does not record the participant’s webcam. Only the shared screen and the two audio channels.
It does not do cross-session analysis — tags, affinity, comparing five participants. That is another product (Dovetail, Condens) and keeping the content on a server to compare sessions would erase our only advantage. The bridge to those tools is the export in Markdown, CSV and JSON.
It is not a questionnaire. SUS and NPS are forms, not capture — whoever needs them already has them.
Record a session now See the plans
One person on their own fits in Personal; Team starts at three seats, the smallest team that really splits a round — below that, the answer is one Personal each. What decides the session — separating the channels, marking the moment and anonymising — is free.