Find evidenced friction in real customer session replays
Investigate a specific customer journey using recorded sessions and product evidence. Turn verified obstacles into a focused product review queue.
How this works
Use observed customer behavior to investigate a narrow product question, such as where users lose the thread while connecting an account. The deliverable is a set of checkable observations with possible explanations, not a claim to know why every user acted as they did.
Treat replay tools as incomplete instruments. A pause, missing event or dead-click flag may reflect masking, a background tab or instrumentation. The procedure below adds sampling, evidence grading and review contracts so the team can decide what to investigate or change.
Before you start
Research owner
Name the person who can explain the journey and confirm which question matters.
Recording permissions
Use permitted, appropriately masked recordings; exclude staff, tests and bots when identifiable.
Product context
Obtain the relevant release date and a read-only state or event export if available.
Prepare the inputs
- question
- Required
one question and target journey
Identify the expected user action and the event that would count as completion.
- sessions
- Required
recording IDs, time range and access
Retain collection filters and exclusions; state when recordings cannot be watched.
- product_context
- Required
events or state snapshot
Record snapshot time, timezone and join key; do not guess a user identity from a similar name.
Implementation, step by step
Define the sample
- Write the investigation question before selecting examples. Include successful and unsuccessful journeys where possible.
- Record collection window, exclusions and sample size; retain the denominator separately from the number actually watched.
Checkpoint: A reviewer can reproduce the session selection.
Check session identity and completeness
- Determine whether sessions belong to the same permitted pseudonymous user or visit. Keep uncertain joins separate.
- Flag internal traffic, hidden tabs, redacted sections and missing replay intervals. Do not count fragmented sessions as separate customers.
Checkpoint: Every session has an inclusion decision and visibility limits.
Inspect the critical sequence
- Use the timeline to locate moments, then watch the relevant replay or inspect supplied frames. Record timestamps and visible text.
- Describe actions before interpreting intent: repeated clicks, an unchanged state, an error or an unavailable next step.
Checkpoint: Each observation names something visible and its evidence coordinate.
Test alternative explanations
- Compare significant observations with product events, permitted state records and the matching release behavior.
- Check whether a supposed failure was completed elsewhere or later. If corroboration is unavailable, mark the explanation unconfirmed.
Checkpoint: High-priority findings distinguish observation, interpretation and uncertainty.
Prepare a reviewable queue
- Group observations only when they share the same interface state and likely obstacle. List counterexamples.
- Suggest a bounded follow-up, such as verifying label clarity, checking an error path or asking a customer; avoid inventing a conversion gain.
Checkpoint: Each queue item has evidence, a responsible role and a next verification step.
Decisions along the way
Only event timelines are available
Deliver event-based hypotheses and explicitly mark replay verification pending.
Sensitive fields are visible
Mask or omit them from the report and follow the existing recording policy.
What you will produce
friction-review.csv
CSVOne row per evidence-supported finding or clearly labeled hypothesis.
Include: finding_id · journey_step · observation · session_id · timestamp · corroboration · status · next_check
coverage.md
MarkdownA compact account of what was and was not inspected.
Include: window · selection · watched_count · unique_users · exclusions · blind_spots
Check the result
- Replay every critical evidence coordinate before handing off.
- Keep unique users, visits and tool session counts separate.
- Check at least one alternative explanation for each high-priority finding.
When something goes wrong
Replay link expired
Retain the metadata and request an authorized replacement; do not reconstruct unseen behavior.
Product release differs from the recording
Use matching historical context or mark the interpretation unresolved.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: investigate account-connection abandonment.
Inputs
Six recordings cover four users. Two recordings are staff tests. One customer clicks a disabled connection button three times; an adjacent prerequisite is not explained.
Expected result
Exclude staff tests; report the visible disabled state with a timestamp and a hypothesis about missing guidance. Record two other users completing the flow as counterexamples; do not claim a measured conversion loss.
Run a small pilot
Start small
Review one journey across a small mixed sample of completed and incomplete sessions.
Record the baseline
Have a product reviewer assess the same sample and record time and useful findings.
Agree success criteria
Agree the required evidence coverage and maximum unsupported-finding rate before expanding.
Stop or revise
Pause if masking, identity uncertainty or missing recordings prevents responsible interpretation.
Keep the scope clear
- No contact with recorded users or product changes are implied by this review.
- The report describes observed interaction and should not infer personal traits or motives.
Check before using
A product owner verifies important replay moments and proposed interpretations.
Business activities
- Onboard customers, partners, and members
- Plan products and business changes
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Research question · Permitted session recordings · Product event and release context
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow