Practice
Where session replay stops being insight
Session replay is a microscope. Most Friday packs treat it like a documentary: three clipped videos, a gasp about a rage click, and no named audience. That genre entertains the product room. It rarely changes the next build.
Replay after the cut, not before
If you have not named the audience, replay will invent one. You will watch a single late-night user fail KYC and declare a national problem. Watch replay only after the cohort exists: first-order PromptPay, bilingual KYC, returning household in Chiang Mai. Then the video is evidence, not theatre.
What you should not keep
Form fields, chat contents, precise location crumbs, anything a support agent would hesitate to read aloud in a mixed room — mask them or do not record. Privacy-Aware Analytics Practice spends a full session on this, because “we use a reputable vendor” is not a policy. Thailand’s PDPA expectations still apply when the vendor’s HQ is elsewhere.
If counsel has not seen your replay settings this year, do not put replay clips in an external memo. Internal critique lab at Proxy Flowcore uses anonymised, masked samples provided by the participant. We do not ask you to upload raw sessions to us.
A useful clip is boring
The useful clip shows the same friction the funnel already named. It lasts under forty seconds. The caption states which audience and which rail. If the room laughs, you probably chose entertainment over evidence. Save the laugh for after the memo is filed.
Insight reporting can mention replay once, as confirmation. It should not become the report. Numbers still carry the argument; video occasionally proves you are not imagining the button.