2022-09-10 Sat 14:46 PM ![[DALL·E 2022-11-14 23.24.06 - the parts of the system form a coherent whole, digital art.png]] From a few minutes ago ([[2022-09-10 Sat]]): >daaaammmiititttt >I made a huge stupid blunder in one of my chess games. Blundered my queen away when I had a huge lead in late mid-game. So I reflected on what happened. What in my thinking process led me to make this mistake. How might my process have been different such that I would not have made the mistake. My mistake, I think, was that I had seen earlier that the enemy's knight move threatened my queen, but I didn't finish making my move in that sitting. I put the app away and came back later. And when I finally made the move, I was blind to the threat because it was obvious and I had already seen it, and I was treating the situation as if I had integrated all previous analysis. But in reality I had forgotten previous analysis. So I blundered. So one lesson is to systematize important decisions. A good example of a way to do this is to use the [[z.Templates/Decision template]]. But systematiztion can be accomplished in many ways. The important thing is to create a structure that secures benefits like these: 1. Causes the products of thought-work **accrete** and **persist** 2. Allows prior knowledge come to bear 3. Allows others give input 4. Ensures that all important information is integrated at decision time ([[Integrate your learnings]]) In the case of the chess move, the written decision template would work well, but it's overkill. The steps I have actually implemented are: 1. I more clearly (mentally) label "lines" that I have considered and their status 2. If I have evaluated lines in a previous session and not in this one, before executing a move I am required to revisit those previously-visited lines in this sessiona nd understand why I am not choosing those moves