The Friction Logging Protocol
by David Singleton • Chief Technology Officer at Stripe
Responsible for guiding Stripe's engineering and design teams for over five years. Previously spent over a decade at Google as VP of Engineering. Known for operationalizing high-craft engineering cultures at scale.
🎙️ Episode Context
David Singleton dissects Stripe's unique engineering culture, explaining how they maintained a product-minded engineering team that delayed the need for Product Managers for years. He details specific internal rituals like 'Friction Logging' and 'Engineerications' that operationalize their core value of being meticulous, while sharing how they balance 99.999% reliability with deploying changes 16 times a day.
Problem It Solves
Prevents 'blindness' to user pain points as a product scales and leadership gets further from the actual usage experience.
Framework Overview
A disciplined practice where a team member (often a PM or Leader) simulates a specific user persona to complete a core task, recording every moment of hesitation, confusion, or delight.
🧠 Framework Structure
Select a specific Persona: Do not jus...
Stream of Consciousness: Write down t...
Full Stack Audit: Don't stop at the U...
Praise the Good: Explicitly call out ...
Instant Remediation: Prioritize the '...
When to Use
On a recurring cadence (e.g., monthly) for existing products, or during the pre-launch phase of new features.
Common Mistakes
Treating it as QA/Bug bashing rather than an empathetic review of the user's flow and feelings.
Real World Example
David onboards as a new Stripe user once a month, writing logs that led to error messages being rewritten to include direct links to the relevant documentation.
You need to put yourself in a particular user's shoes. It's actually important to have a very clear idea of who is the person I am kind of modeling the friction for right now.
— David Singleton