Choose a question before pressing play
A replay becomes easier to use when you know what you are looking for. “Why did I lose?” invites thirty minutes of commentary about everything. “Why did this recall cost so much farm?” gives you a sequence to inspect. Pick a recent game you remember reasonably well and a problem that has appeared more than once.
Include wins. An opponent can fail to punish a careless push, just as a sensible retreat can still end in a lost game. You are looking for choices you can repeat or change. A representative match usually teaches more about your normal habits than a game dominated by an early disconnect or an unusual matchup you rarely play.
Rewind to the setup and use your team’s vision
Start before the moment that caught your attention. If you died in the river, inspect the wave and the decision to leave lane. If a recall went badly, inspect the push that preceded it. Rewind far enough to find a point where another choice was still available; there is no mandatory number of seconds.
Watch with your team’s fog of war first. Write down what was visible: your resources, wave position, relevant cooldowns, and enemy sightings. Keep assumptions separate. “The jungler appeared top earlier” is an observation. “They must still be top” is an inference. Full vision can later reveal what happened, but it cannot turn hidden information into something you should have known.
Work backward from the extra turret hit
Imagine you win a lane fight and push the surviving wave under the enemy turret. You have little health, an unavailable escape spell, and no recent sighting of the enemy jungler. You stay for more turret damage, get intercepted on the way out, and focus your review on the skillshot that killed you.
The earlier decision deserves attention. Leaving after the crash would have let you recover and spend gold, while staying offered extra pressure at the cost of a more dangerous exit. Neither the exact return wave nor an enemy response was guaranteed. Compare the likely costs with what you knew then: could you see the route out, could the opponent return soon, and was the extra damage worth giving up a clean departure?
You might still identify a mechanical error in the escape. Record it separately. “Dodge better” does not address the choice that repeatedly leaves you escaping through darkness with no resources. The useful correction may be to leave after a completed crash when your health and missing enemies make another turret hit difficult to justify.
Check an alternative you could actually execute
A review is less useful when every alternative assumes perfect mechanics or instant teammate cooperation. Compare your action with something available to you: retreat earlier, wait for an ally, collect a safer wave, or give up a contested minion. Include the cost of that alternative. Backing off may lose gold even when it is the better decision.
Also inspect a sequence that went well. Identify the cue that made aggression reasonable: an important enemy spell was used, an ally could follow, or the likely response was visible elsewhere. This prevents every review from becoming an instruction to play farther back. Good review should help you recognize when to act as well as when to stop.
Turn the finding into a short practice note
Use five fields: timestamp, visible cue, your decision, a feasible alternative, and a next-game rule. For the example above, the rule could be: “After crashing with low health, check missing enemies and my exit before taking another turret hit.” It tells you when to think and what to inspect without prescribing the same answer in every game.
For the next few matches, review whether you noticed that cue and made a deliberate choice. Winning is not proof that you followed the rule, and losing does not invalidate it. Once the habit becomes reliable, choose another question. A short review that changes one recurring decision has done its job.