Friction Logging and UX Reviews

Friction logging is the practice of systematically identifying every hurdle, point of confusion, and "broken edge" in a user flow. By adopting a specific user's mental model and recording a stream-of-consciousness log of the experience, teams move beyond abstract metrics to granular, actionable improvements that compound into a superior product.

The Solo Friction Log Process

Perform this audit individually on a recurring basis (e.g., once a month) or when a new feature is ready for its first end-to-end test.

1. Define the Persona: Choose a specific user profile to mental-model. Do not just "test the product"—be "an engineer at a large SaaS company integrating a billing API for the first time."
2. State the Goal: Define exactly what the user is trying to achieve (e.g., "Set up a subscription with a 30-day trial").
3. Start the Stream of Consciousness: Open a blank document. Record every thought, frustration, and moment of delight as you move through the flow.
4. Note the Details:
   • Context switching: "I had to leave the dashboard to find a secret key in the docs."
   • Error handling: "The error message was generic; it didn't tell me what field was missing."
   • Latency: "This page took 3 seconds to load, making me wonder if it crashed."
5. Include Praise: Explicitly mark things that work well. This reinforces high-quality patterns across the team.
6. Tag and Distribute: Share the log with the relevant PMs and Engineering Managers. Tag specific owners for "paper cuts" (minor issues) and "blockers."

Group Review: "Walking the Store"