How to Review Your Games Like a Professional
Most players run their games through an engine and call it analysis. Real game review is completely different — and far more useful for improvement.
Running your game through Stockfish and looking at the red arrows is not analysis. It's evaluation. The distinction matters enormously for improvement.
Analyse Without the Engine First
Sit with your completed game and write down your thoughts: where did I feel uncertain? What was my plan on each major decision? Where did the game feel like it slipped away? This reflection, before seeing the engine's verdict, forces you to engage with your own thinking process.
Find the Critical Moments
Most games turn on two or three key moments. Identify them: the move where the evaluation shifted, the moment where the clock pressure started, the decision that committed you to a losing plan. These are the moments that deserve the deepest investigation.
Use the Engine as a Question Generator, Not an Answer Sheet
When the engine shows a better move, the question isn't just "what is the best move?" but "why didn't I see this move?" If you couldn't see it because of a pattern you don't recognise, that's training material. If you couldn't see it because of time pressure, that's a different problem. The engine shows you what; you have to find out why.
Keep an Error Log
Every game analysis should produce at least one item for your error log: a specific tactical pattern you missed, a strategic concept you misapplied, or an endgame technique you don't know. This log is your personalised curriculum.