Repeated review comments are a system problem

Every coach knows the feeling.

You open review on Tuesday and say the same thing you said on Thursday:

• We are too slow to reset after a failed contest.
• Our second wave setup in bot lane is inconsistent.
• We are talking about draft goals, then forgetting them by minute eight.

At some point, the issue is no longer whether the point is correct. The issue is whether the team has a reliable way to retain it.

Why live review is not enough

Live review is strong for urgency, clarification, and shared context. It is weak for memory.

Players leave with a good conversation in their head, but by the next block they are juggling:

• Solo queue goals
• School or work obligations
• New patch adjustments
• Different lane-specific asks from staff

Without written follow-through, even good review points become disposable.

Shared notes reduce friction between sessions

The most useful coaching notes are not giant reports. They are short, specific reminders that connect directly to future sessions.

A useful shared note usually includes:

• The pattern that keeps repeating
• The condition that triggers it
• The behavior the player should look for next time

For example:

Weak note

"Needs better map awareness."

Strong note

"When top wave is crashing and jungle is pathing bot, communicate whether you can hold teleport for dragon setup instead of defaulting to lane catch."

The second version gives the player something to look for in practice.

Notes should survive staff handoffs

This matters more than most teams expect.

If the coach is absent and an analyst runs review, or if a manager helps organize the week, the staff still need one place to see what themes are active.

Shared notes help answer:

• What is this player currently working on?
• Which habits are improving?
• Which issues have been repeated too often to ignore?

That prevents review from starting at zero every time the room changes.

What to record after a session

After a scrim block, staff do not need to write everything down. They need to preserve the things that should affect the next block.

Good categories include:

• Decision-making patterns
• Lane communication triggers
• Objective setup habits
• Draft understanding gaps
• Confidence or hesitation around specific champion identities

A note should point forward

The best notes are not only descriptive. They should help plan the next rep.

If a support player is struggling with engage timing, that may affect tomorrow's draft goals. If a jungler is over-forcing early windows, that may affect the review clips you choose and the scrim emphasis for the next evening.

The note becomes operational, not archival.

Why players engage with shared notes

Players are more likely to revisit written feedback when it feels personal and current.

That means:

• Keep the language concrete
• Avoid writing for staff ego
• Link the note to situations the player will actually meet this week

The goal is not to produce a beautiful knowledge base. The goal is to reduce repeat mistakes between Tuesday and Friday.

When a note can be archived

Not every issue needs to stay visible forever.

Once a theme has clearly improved, move on. Shared notes work best when they reflect the team's current reality, not a permanent record of every flaw a player has ever shown.

That keeps the system credible and makes it easier for the team to trust what is still being tracked.