Most players assume a coach watches their replay the way a friend watches over their shoulder — reacting to the flashy mistakes, the missed skillshots, the death that lost the fight. That impression is understandable, but it misses what a real diagnosis is. A coach isn’t hunting for the moment you played badly. They’re looking for the pattern that produced that moment, and the pattern usually shows up long before the death that made you close the client in frustration.
The signals a coach pulls from a single replay
A single game holds far more information than the scoreline suggests. When a coach loads your VOD, they aren’t watching it front to back like a movie. They scrub. They pause at fixed checkpoints — the first three minutes, each wave crash, every objective spawn — and note what you were doing at each one relative to what the map was asking for.
The useful signals are rarely mechanical. Where your camera sits, how often you check the minimap, whether your cursor hovers over the shop while a fight is brewing, how long you stand still after a recall — these are behavioral tells. They repeat. A single fumbled combo is noise; a habit of walking to lane with no ward and no plan is signal. The coach’s first job is filtering one from the other.
Turning minimap movement and gold curves into evidence
Footage tells you what happened. The data tells you when and by how much. This is where the diagnosis becomes measurable instead of impressionistic.
Gold and experience curves are the backbone. A coach lays your numbers against the enemy laner’s and looks for the exact minute the lines diverge. If you were even at eight minutes and down eight hundred gold by twelve, the window between those timestamps is where the game was decided — and that’s the footage worth rewatching frame by frame. Minimap movement adds the spatial layer: recall timing, roam paths, the recurring habit of pushing into a warded bush without vision. Cross-referenced, these turn a vague feeling of “I fell behind” into a specific, timestamped claim about a decision you made and can change.
Separating symptoms from the root cause
Here is where amateur review and professional diagnosis split apart. It’s easy to list everything that went wrong. It’s hard to figure out which mistake caused the others.
Consider a game where you died three times to ganks. The symptom is “I get camped.” The tempting fix is “ward more.” But when the coach traces the sequence backward, the ganks all follow the same setup: you shoved the wave without a vision advantage, giving the jungler a slow, predictable target. The warding was never the root — the wave state was. Fix the pushing habit and the deaths disappear on their own, along with a handful of unrelated problems that shared the same cause. A good diagnosis collapses a long complaint list into two or three underlying levers, because pulling one lever moves several symptoms at once.
Building the prioritized fix list that ends up in tailored solo mentoring
A list of ten equally-weighted corrections is useless; a player can only rebuild one habit at a time. So the final step is ranking. The coach orders the root causes by how much they cost per game and how quickly they can be changed. A wave-management flaw that bleeds gold in every single lane phase outranks a positioning quirk that only matters in the rare five-on-five. High cost, low effort goes to the top.
That ranked list is the actual product of the analysis, and it’s what shapes the sessions that follow. In a structured program of tailored solo mentoring — the kind offered by organizations working with players across the Washington, D.C. area and remotely — each session tends to focus on the top one or two items, then re-checks the next batch of replays to confirm the fix held before moving down the list. The prioritization is what keeps a player from drowning in feedback they can’t act on.
None of this is a one-time verdict. Habits drift, patches shift the value of objectives, and a fix that held for a month can quietly slip once you stop watching for it. Treat the diagnosis as something to run again periodically, not a document you file away — the pipeline only pays off if you keep feeding it fresh games.
