✳flâneur — a map of the web's best reading

sbensu: How to: friction logs

blog.sbensu.com · 1,437 words · saved by 2 readers

Most software is bad. I neither know why, nor how to solve the problem. Instead, the best I have to offer is a technique to keep the badness away for a while: friction logs. Friction logs are what they sound: a detailed log of everything that caused friction when using a product. This post teaches you how to make one. I recommend you to make one if: Here are a couple of the friction logs that I made this past year for products I was curious about: You can find a lot more here. They are only interesting to the team that is working on the product. I only link them so that you have examples to base yours from. Open a new document. You can structure this however you like. I usually write what I find and take screenshots of it as I go along. Alternatively, here is Mike Fix’s more structured template with a two column table with screenshot on the left and notes on the right: I use Notion or Dropbox Paper because they simplify text formatting and make it easy to lay out several images in col

sbensu: How to: friction logs How to: friction logs December 2023 Most software is bad. I neither know why, nor how to solve the problem. Instead, the best I have to offer is a technique to keep the badness away for a while: friction logs. Friction logs are what they sound: a detailed log of everything that caused friction when using a product. This post teaches you how to make one. I recommend you to make one if: You are working on a software product You are very curious about a company and their product You are trying to get better at product management and design Here are a couple of the fr

Explore this link on the map →

saved by

related reading