I coach League of Legends players who mostly sit between Gold and low Diamond, and most of my sessions are built around recorded solo queue games rather than polished highlight clips. I have spent years watching players lose matches they were mechanically capable of winning because one poor recall, one rushed roam, or one unnecessary fight changed the next five minutes. My job is rarely to teach someone what their champion’s abilities do. I focus on helping players recognize the decisions they keep making on autopilot.
I Start With the Mistakes That Actually Cost Games
One of the first things I learned as a coach was that correcting every mistake is almost useless. A player can make 30 small errors in one match, but perhaps three of them create most of the damage. I usually watch the first 15 minutes closely because early decisions expose habits before a chaotic late game hides them. That gives me a much clearer picture of what needs attention.
A top laner I worked with last winter thought his biggest weakness was trading. His mechanics were fine, and he could explain most matchups well enough, but he repeatedly stayed for one extra wave with no vision and the enemy jungler missing. In one review, that habit caused two deaths before 12 minutes and destroyed a lane that had started evenly. That was the real problem.
I prefer fixing that sort of repeatable decision before touching smaller mechanical details. One correction can affect dozens of future games because the player starts asking a better question before the same situation appears again. Sometimes the lesson is surprisingly short. Stop taking that wave.
Structured Feedback Beats Random Advice
I have seen plenty of players consume hours of educational videos and still struggle to apply any of it during ranked games. The information itself may be solid, but broad advice becomes difficult to use when someone is trying to track a wave, watch the minimap, manage cooldowns, and predict the enemy jungler at the same time. Coaching works better for me when I reduce the lesson to one or two priorities. The player needs something usable during the next queue, not another page of theory.
For players who want structured one-on-one feedback, I sometimes point them toward LoL Сoaching as an example of a resource centered on deliberate improvement rather than random tips. I still tell players to judge any coaching service by the quality of the feedback they receive and by how clearly that feedback connects to their own games. A useful session should leave a player with specific decisions to practice. It should not feel like someone simply narrated a replay.
During my own reviews, I often pause immediately before a mistake rather than after it. I might stop a replay at 8:40 and ask the player what information is currently visible, which enemies are missing, and what they expect to happen during the next 20 seconds. Their answer tells me much more than asking why they died afterward. The goal is to rebuild the thought process that existed before the mistake.
Champion Mastery Is Often More About Repetition Than Mechanics
I regularly coach players who switch champions whenever they have two frustrating games. That makes improvement harder because every new pick introduces different damage limits, matchup patterns, wave interactions, and teamfight responsibilities. I usually recommend keeping a ranked pool to roughly two or three serious champions for a while. Smaller pools make repeated situations easier to recognize.
One mid laner I coached last spring had played more than a dozen champions during a short ranked stretch. He understood each one at a basic level, but he was constantly hesitating during trades because he had no strong sense of his limits. We reduced his pool to three champions and reviewed the same common lane situations repeatedly. Within several sessions, our conversations became much more detailed because we no longer spent half the review explaining champion-specific basics.
Mechanics still matter. I simply find that players often improve mechanically through familiar situations rather than endless isolated drills. If someone has played the same matchup 10 times, they start noticing exactly when an opponent steps too far forward or wastes an important cooldown. That recognition creates faster reactions without the player consciously thinking through every possible response.
Wave Management Changes More Than the Lane
Wave management is one of the areas where I see players know the vocabulary but misunderstand the purpose. They can tell me what freezing, slow pushing, or crashing means, yet they sometimes perform those actions without asking what they are trying to achieve. I treat the wave as a tool for creating another advantage. The wave itself is rarely the final objective.
For example, I reviewed a bot lane game where my student forced a large wave under the enemy turret around minute 7, then stayed in lane doing almost nothing while the opponents collected it. That crash could have created a recall, vision window, river movement, or temporary numbers advantage somewhere else. Instead, the player stood near the turret waiting for another wave. The technique was correct, but the follow-up was missing.
I often ask players to connect each wave decision with the next 30 to 60 seconds of the game. If the jungler wants to contest an objective, the wave plan should support that timing. If a player has enough gold for a meaningful purchase, forcing one more risky wave may accomplish very little. Small timing choices eventually become map control.
Replay Review Needs a Question
Watching a replay from beginning to end is rarely how I spend a coaching session. I prefer entering the review with a question such as why the player keeps losing leads, why their farm drops after lane, or why they reach objective fights late. A 30-minute game becomes much easier to analyze once we know what pattern we are searching for. Otherwise, replay review turns into passive viewing.
I also avoid stopping at every missed ability. Players usually know when they missed an obvious skillshot, and spending five minutes discussing it adds little value unless positioning or decision-making caused the miss. I care more about why the player entered that situation. If they were fighting with no reason to fight, landing the ability would not make the decision good.
One support player came to me convinced that his ward placement was the reason he kept losing control around objectives. After reviewing three games, I noticed that he was usually arriving in the river about 40 seconds too late, which forced him to ward dangerous areas after the enemy had already established control. His ward locations were mostly sensible. His timing was the larger issue.
I Give Players One Practice Goal at a Time
The worst homework I could give a student would be a list of 15 things to remember during every ranked game. League already demands attention from too many directions, so adding a huge mental checklist usually makes performance worse. I normally choose one major habit for the next five to ten games. Once that behavior begins to feel natural, we can layer another habit on top.
A jungler I worked with had a habit of starting fights immediately after reaching an objective area. Instead of giving him several lessons at once, I asked him to spend his next six games checking teammate positions before committing to any major engage. That single rule slowed his decision-making just enough for him to notice situations he had previously ignored. His mechanics did not change during those games, but his fights became much easier to understand afterward.
I also ask players to write down one sentence after each match. It does not need to describe every mistake or turn the game into homework. Something like “I recalled too late before dragon” is enough if that is the habit we are tracking. Five clear observations are more useful to me than pages of vague notes.
I have never seen useful League coaching as someone handing a player secret information. Most improvement comes from identifying a repeated decision, practicing a better response, and seeing the same situation enough times that the correction becomes automatic. I would rather have a student remember one useful adjustment in their next 20 games than leave a session impressed by how much theory we discussed. That is the standard I use whenever I review a match.