Describe the goal in useful terms
A rating target can express motivation, but it does not tell you what to do during the next session. Add a behavior goal that you control. Examples include supporting the first engagement, delivering clearer information, or using utility with a planned follow-up.
Write why the goal matters and where it appears in your matches. Keep the scope small enough that you can recognize the relevant situation without thinking about an entire checklist. A plan becomes usable when it changes a decision, not when it contains many ambitions.
Gather a small baseline
Review a few representative games or sessions. Avoid choosing only your best performance or your most frustrating loss. Record the recurring situation, the information available, and the action you took.
Separate verified observations from impressions. “I felt late on every rotation” is a useful starting question. A timestamp showing when information arrived and when you moved is stronger evidence for a correction. Keep unknown details explicit instead of filling them with a confident explanation.
Choose one priority and one supporting task
Select the problem that appears often and has a realistic correction. Define a trigger and an action. For example, when the first route becomes blocked, communicate the change and regroup before another unsupported push.
Choose a practice task that rehearses that action. A route drill can help with preparation; a partner exercise can help with spacing; a short replay review can help with recognizing information. Do not add an unrelated task just to make the plan look complete.
Apply the correction in matches
Begin each session by reading the priority. Look for suitable opportunities during play, but do not force the action when the situation does not fit. The goal is recognition and judgment as well as execution.
Afterward, save one relevant example. Note whether the trigger occurred, whether you noticed it, and what happened after your decision. Include successful examples so you know what the desired behavior looks like under realistic conditions.
Set a review point
Choose a practical checkpoint based on your schedule, such as after several comparable sessions. Review the collected examples and ask whether the problem is becoming easier to recognize. Decide whether to retain the priority, refine the drill, or move to another issue.
If you use a coach, bring the evidence and ask for a clear explanation of the recommended change. Agree on session scope, deliverables, and follow-up rather than a promised rank. Keep control of your game accounts and avoid services that require credentials or rule violations.
Allow the plan to change when the evidence changes. Preserve earlier notes so you can understand what worked and why. A useful improvement plan is a short feedback loop between observation, practice, and play. It should fit your time, make the next session clearer, and remain honest about what has and has not improved.