Friction atlas

A shared vocabulary for the moments interfaces slow people down. Use it to brief stakeholders—or start a detection audit with language everyone already understands.

Quiet workspace with soft morning light

Hesitation pauses

Unusually long dwell before a primary action—often unclear labels, competing CTAs, or missing reassurance. We separate careful reading from stuck moments using intent signals.

Rage and mistaps

Rapid repeated taps or clicks on non-responsive or overlapping targets. We require absolute counts beside rates so thin samples do not drive redesigns.

Dead ends

Flows that strand people without a clear next step—empty states, blocked permissions, or forms that fail silently. We map exits against intended recovery paths.

Error loops

Validation or system messages that send people back into the same failing step. We track retry depth and which fields or states keep regenerating friction.

  1. 1. Name the signals

    We lock definitions for hesitation, rage interaction, dead ends, and error loops so product, design, and analytics share one taxonomy.

  2. 2. Scan agreed journeys

    Signal rates arrive with absolute counts, sample-size notes, and device slices only when the data can support them.

  3. 3. Rank by impact and confidence

    Not every noisy screen is a defect. We weigh reach, severity, and confidence before recommending design or engineering work.

  4. 4. Hand off experiments

    You leave with prioritized hypotheses, measurement plans, and clear owners—not a slide deck that dies in email.

Ready to scan a journey?

Browse engagements or tell us which flows feel sticky—we will suggest a workshop, audit, or retainer that fits.