Review a question, not an entire game
“Find everything I did wrong” is too broad. You will either create an exhausting list or judge decisions only by whether they worked. Begin with one question: why did my lane lose control, why was I late to objectives, or what happened before each avoidable death?
Start before the visible mistake
The death is often the final event in a longer chain. Rewind far enough to find the first decision that narrowed your options: a poor reset, a missed wave read, an unnecessary cooldown, a path taken without information, or attention placed in the wrong area.
At each important moment, record four things
- Information: What could you reasonably know?
- Options: Which actions were available?
- Priority: What mattered most in the game state?
- Cue: What should help you recognize this situation next time?
Separate decision quality from outcome
A low-probability play can work. A strong decision can fail. Ask whether the choice used the available information and served the correct priority—not only whether the screen later said victory or defeat.
Do not use hindsight to pretend you knew information that was hidden when the decision was made.
Look for repetition
One missed skillshot may not deserve a training plan. Three late rotations caused by staying for one more wave probably do. Patterns are valuable because one correction can improve many future situations.
End with one or two priorities
A review is only useful if it changes play. Convert the pattern into something observable: check the wave before following a roam, identify the next objective before recalling, or move the camera before committing to a path.
Need a second set of eyes?
A one-on-one VOD review can reveal patterns that have become too familiar for you to notice.