Session Recording Triage: What Actually Needs Fixing?
Objective: Given a synthetic batch of 8 session-recording notes from a checkout flow, apply the lesson's dead-click/rage-click/form-abandonment vocabulary to sort real friction from healthy behavior, and propose the first fix.
You're reviewing 8 session-recording notes from Allbirds' checkout flow after Microsoft Clarity flagged an unusual spike in dead clicks on mobile.
Classify each session note as a real friction signal or normal behavior, then propose the single highest-priority fix based on the pattern.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free tier includes session recordings, filterable by page and rage-click flag
Free, simple audit trail for a small batch of sessions
The process
Specimens to review
Classify each of the 8 sessions as a real friction signal (name the type: dead click, rage click, or form abandonment) or normal behavior. Propose the highest-priority fix.
Allbirds mobile checkout, 8 session-recording notes (synthetic, 1-week sample):
A. User taps the greyed-out 'Apply' promo code button 4 times in under 3 seconds, then abandons cart.
B. User fills in shipping address, scrolls to payment, pauses 12 seconds, then completes purchase normally.
C. User taps a static trust badge icon ('Secure Checkout') twice, nothing happens, then continues to payment normally.
D. User types a full email into the newsletter opt-in field, then deletes it and leaves the page immediately.
E. User taps the promo code field label text (not the input box itself) 3 times before finding the actual input.
F. User completes checkout in 40 seconds with zero extra taps, fastest session in the batch.
G. User taps 'Apply' promo code button 5 times rapidly on a cart worth $340, then closes the tab.
H. User scrolls up and down the shipping form twice before completing it normally.Specimen: synthetic, realistic
Final deliverable
A triage table classifying all 8 sessions, with the single highest-priority fix named and justified by the repeated pattern.
See a reference example
TurkNet checkout session triage (8 sessions) Real friction: - 2x rage click on disabled 'gift wrap' checkbox (root cause: checkbox stays greyed out until an unrelated field is filled) - 1x dead click on a non-clickable delivery-date icon Normal behavior: - 3x standard-pace completions - 1x re-read scroll on the address form - 1x form field typed then deleted, single occurrence Priority fix: make the gift-wrap checkbox active by default, or clearly label the dependency that unlocks it.
Success criteria
You're done when you can:
- Correctly identifies the repeated rage-click pattern (sessions A and G) as the top-priority, checkout-blocking issue
- Distinguishes dead clicks, rage clicks, and form abandonment using the lesson's own definitions
- Does not flag the 4 healthy/single-occurrence sessions (B, C, F, H) as priority problems