Teach annotated games: a practical guide — Like a pro
A sustainable approach to Teach Annotated Games beats an intense one every time. Here is how to build the sustainable version.
What you need
- A notebook or notes app
- One hour of setup time
- A weekly review reminder
Step by step
Tips
- Label things; future-you has worse memory than present-you.
- Photograph complex assemblies before disassembly.
- When stuck, explain the problem out loud — half the time the answer appears.
Common mistakes
- Working on the real thing before practicing on a throwaway copy.
- Confusing activity with progress — track outputs, not hours.
- Quitting during the inevitable plateau instead of scheduling through it.
FAQ
Do I need special equipment?
No. The lists above stick to essentials. Upgrade only after the basic version works and you know which limitation actually bothers you.
How do I maintain the result?
Add the final maintenance step to a calendar. Ten minutes monthly prevents most regressions.
What if I get stuck?
Return to the last verified checkpoint and redo the failing step slowly. If it still fails, search for the exact error or symptom rather than the general task.
Related guides
[[how-to-learn-endgames]] [[how-to-learn-time-management]] [[how-to-learn-pawn-structures]] [[how-to-learn-a-study-plan]]
That is the whole loop: prepare, change one thing, verify, repeat. Mastery is just reps with feedback.