Journal · March 2026

Reading session replay without inventing motive

Team looking at screens in a meeting room

Replay is a film of motion. It is not a confession. In User Path Mapping Studio we ask students to mark three things before they write a sentence about the person: a pause longer than the surrounding rhythm, a system dialog, and any moment where the cursor or thumb retraces.

Motive language (“they were lost”, “they hated the paywall”) arrives too early in most product meetings. It feels collaborative and it is usually unearned. Path Analysis for App Users can survive without it. You can still recommend an event, a copy change, or the removal of a prompt.

A practical sequence: watch once without speaking. Watch again with a notepad that only accepts timestamps and UI objects. Only then write one hypothesis, labelled as such. If the hypothesis cannot point at a timestamp, it does not enter the tracing brief.

This is slower than a highlight reel. It is also the only way we have found to stop a room from projecting last quarter’s persona work onto a single session from Tuesday night.

Back to the journal