![rw-book-cover](https://substackcdn.com/image/fetch/w_1200,h_600,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff328d195-8aaf-4bc1-9903-054bcbc0b83d_2350x792.png) ## Metadata - Author: [[John cutler|John Cutler]] - Full Title:: TBM 292: Friction, Documentation, and Product Tools - Category:: #🗞️Articles - URL:: https://cutlefish.substack.com/p/tbm-292-friction-documentation-and - Finished date:: [[2024-06-07]] ## Highlights > My Claim: Many teams should use static, low-tech documents and manual repetition instead of specialized work-tracking tools and goal-setting products. ([View Highlight](https://read.readwise.io/read/01hzs4j65ygar9pr5p52ejs6h5)) > One of the cornerstones of bullet journaling is migration. An example of migration is copying incomplete tasks from a daily log to the monthly log for better prioritization in the upcoming month. ([View Highlight](https://read.readwise.io/read/01hzs4jbvqqzm15g5nv6e7j9sp)) > Say/do is meaningless without state history and a mechanism to reflect (migrate). Teams should endeavor to improve their Say→Try→Did—>UNDERSTOOD ([View Highlight](https://read.readwise.io/read/01hzs4gz1ndp69e2qxy07eaf33))