Friction Log

A friction log is a stream-of-consciousness written record of a product experience, kept from the perspective of a specific user persona. Used to identify the highest-impact places to invest in product quality.

Primary source: David Singleton on Stripe (David Singleton, Stripe CTO). Public template available at stripe.dev.

Purpose

The friction log answers: where should we be meticulous? Meticulousness applied universally is impractical; applied selectively to the highest-friction points, it compounds into measurable outcomes.

Stripe’s evidence: accumulated small checkout improvements measured at a 10.5% increase in user revenue — large by an industry where individual optimisations typically deliver basis-point uplifts.

How to run a friction log

1. Define a specific user persona. Not ‘a developer’ but ‘an engineer at Atlassian who is actively integrating Stripe Billing for the first time.’ Specificity enables accurate friction detection.
2. Go through the full product flow end-to-end from the realistic entry point: dashboard, documentation, code writing, integration, error handling.
3. Keep a stream-of-consciousness log of everything encountered. Friction and excellence. Praise the good explicitly.
4. Tag the right people for each friction point who can take action.
5. Share broadly inside the company — friction logs are a form of quality communication, not private notes.

Cadence

• Product teams: PM or engineering manager runs a friction log on their product end-to-end on a regular cadence (typically monthly).
• Senior leaders: recursively, for their whole scope. David Singleton personally onboards as a new Stripe user once a month.
• All-hands version: Walk the Store — David runs a product walkthrough with the whole company at Stripe’s Friday Fireside, building shared language and quality bar.
• Internal tooling: engineering managers and CTOs use the same technique for internal developer experience via engineer-cation.

Why it works

Thousands of engineers working in parallel will drift the user experience in many small ways. No individual engineer sees the whole. The friction log provides a regular top-down view of the full product experience — a synthetic cohesion check that complements distributed execution.

It also creates a shared quality vocabulary: specific friction points, shared across the company, become reference points in prioritisation discussions.

At Stripe: design leadership application (Katie Dill)

Katie Dill (Head of Design at Stripe) describes friction logging as the measurement component of Stripe’s 15 Critical Journeys programme. Her team identified 15 of the most important user journeys, assigned engineering, product, and design leaders to each, and required those owners to ‘walk the store’ — going through the journey as a user would — on a regular cadence. Leaders file friction logs (screenshots, commentary, severity tags) and submit a summary colour score (red/yellow/green) based on a rubric across usability, utility, desirability, and delight.

The scores feed a quarterly calibration (called a Product Quality Review, or PQR) where leaders compare scores and debate interpretation — similar to how performance-review calibration sessions align managers on a shared standard. This operationalises the friction log from an individual diagnostic into an organisational quality programme.

Source: Katie Dill on Design Quality, the ROI of Design, and Operationalising Excellence

Relationship to adjacent concepts