Friction logging 101
summary
Friction logs capture end-to-end developer journeys across multiple products using a simple template—tester/date/use case, products, environment, exact steps and links—and a color-coded emotional trail (green/yellow/red) so teams see where people pause, hunt online or give up. Example: deploying a Rails app to App Engine hit a missing resdb migrate step that required web searches (orange), producing a concrete suggestion. New hires write logs, outputs include file bugs and write docs, create tutorials or helper libraries, and the process stays manual because the emotional context cannot be automated.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:36DevRel is a two-way communication
- 2:23DevRel is an Internal Outsider
- 5:35A friction log should include
- 7:14Example (clean environment)
- 9:52New Members Write Better Friction Logs
- 11:16Friction Log vs Bug
- 13:30Focus on Experience
- 14:19When to write friction logs
- 15:36After writing a log
- 16:35Summary
related talks
38mLogging as a Painkiller
28mFind friction in your developer experience by user testing with developers
31mObservability for Developers: How to Get There
05mLightning Talks from Robson Port
35mDev Experience in Technical Writing: 15 Tips to Boost Developer Satisfaction
27mHow's Your Log Life?
44mTesting Documentation: Why So Technical?
19mA Frictionless Inner Source Journey