Friction Audit

A friction audit is the four question test that every high stakes flow in your product must pass before it ships. You take the proposed interaction, whether it is deleting a database or letting an AI agent edit production code, and you ask in strict order. Is the action reversible. What does the user lose if they tap by accident. Where in the flow is the friction actually landing. And does that friction read as care or as obstruction to the user. The answers dictate the exact shape of the pause from a 200ms delay on low risk taps all the way to forcing the user to type the full workspace name before the delete button activates. The audit forces teams to treat friction as a design material instead of a binary toggle. It surfaces the six contexts where friction earns its keep. Irreversible actions like force pushing to main or emptying the trash. Money flows where real dollars change hands. AI tool calls that touch the file system or send emails. Destructive settings like account deletion. Publishing and sharing moments that cannot be taken back without embarrassment. And changes to sensitive data or account access. The audit makes sure the weight of the friction matches the weight of the possible mistake so the product signals respect instead of indifference.

It is not a general purpose UX review or a fancy name for making things slower. It is not the excuse product teams use to keep every modal they have ever designed. A friction audit has no business in the first three minutes of user onboarding or on flows where the user has not yet decided to commit. It is not a tool for defending dark patterns that trap users in subscriptions with buried cancel buttons or guilt tripping language. The audit does not create friction for its own sake. It identifies the precise moments where the absence of friction would betray the user. Accidental friction like laggy interfaces, confusing copy, or demanding a fax number in 2026 is always bad and the audit does not touch it. Designed friction is different. It is the deliberate pause at the moment a user might make an expensive mistake. The audit separates the two so teams stop using the bad examples to argue against the good ones. Teams that run the audit poorly treat it as a checklist to complete rather than a conversation about user respect. That misses the entire point.

A concrete example is the friction audit the Linear team ran on their workspace deletion flow in 2025. The action failed the reversibility test because once a workspace is gone the data is scheduled for permanent deletion after 30 days. The loss was massive. Months of project history, integrations, and billing information. The proposed friction landed exactly at the delete button rather than earlier in the settings menu. The typed confirmation would force the user to slow down and confront the full name of the workspace they were destroying. The audit approved the shape because it read as care not obstruction. The team implemented a double confirmation sequence. The first modal explained what would disappear. The second required typing the workspace name in plain text. Error rates for mistaken deletions dropped to near zero and user feedback called the flow respectful rather than annoying. The same audit applied to project archiving passed with much lighter friction. Archive is reversible so a single tap sufficed. The gradient between the two flows taught users the stakes through friction weight instead of documentation. Stripe ran a similar audit on their API key revocation the same year. The typed confirmation plus administrator second approval became the standard because the audit flagged the high cost of a compromised key. Cursor integrated the audit into their AI workflow from the beginning. Every time the model wanted to edit a file the diff appeared and the user had to explicitly accept. The audit classified AI tool calls as trust flows equivalent to money movement. Companies that skipped this step in 2024 and 2025 lost weeks of engineering time recovering from rogue agent actions. Apple Pay has run an implicit version of this audit for years. The double press with one second pause between taps exists because the audit equivalent showed that money movement required hardware level commitment. Twitter added the are you sure prompt on heated replies after an audit equivalent showed that publishing to millions could not afford muscle memory. Slack used it for large channel broadcasts warning you are about to message 4200 people. Webflow and Ghost run it on publish flows showing a final summary of what is about to go live. Each of these examples shows the audit turning potential disasters into deliberate choices.

Use a friction audit on any flow that matches the six high stakes categories and on any new feature that could cost a user more than a few seconds of recovery time. Run it in the design phase then again before launch and once more after the first wave of user feedback. It is mandatory for AI products in 2026 because users will abandon any agent that acts without explicit approval faster than they abandon slow ones. The audit also pays off on publishing flows in tools like Webflow or Ghost where the difference between draft and live can mean public embarrassment. Do not use it on low stakes actions like toggling dark mode or marking a task complete. The audit should correctly tell you to remove friction there. Avoid it as justification for front door friction like mandatory email confirmation before the user has seen any value. Never let it defend hostile unsubscribe patterns that require jumping through four screens and typing passwords on products that did not require passwords to sign up. Those are reputation killers not respect signals. If the action has a clean undo window like Gmails unsend or Slacks edit message the audit should recommend light friction paired with a generous reversal period rather than heavy confirmation. The audit fails when it becomes a rubber stamp instead of a real conversation about tradeoffs.

A friction audit turns products that feel like they are rushing you into products that feel like they respect you.