A role change can make an experienced player feel like a beginner again. Your timing is different, familiar statistics look worse and you suddenly notice tasks someone else used to handle. That discomfort does not automatically mean the change is a mistake. It means the job has changed and your review needs to change with it.
Whether you are moving into support, taking more responsibility for calls or trying a new position, use a learning plan that is small enough to follow during real matches. The exact responsibilities depend on your game and team, so agree on them rather than assuming the role name explains everything.
Define the job before judging the player
Ask your teammates what they need from the role in common situations. What information should you provide? What resources or space do you manage? When should you make a decision independently, and when should you wait? Turn the answers into a short responsibility list.
Avoid a list of impossible expectations. “Win every opening and always be available to help” may describe conflicting demands. Discuss trade-offs openly. A clear priority lets you make a sensible choice when you cannot do everything at once.
Carry one familiar strength across
You are not starting with no useful skills. Perhaps you communicate clearly, read rotations well or stay organised during preparation. Choose one strength that transfers, then identify the unfamiliar action that needs practice. This gives you a stable foundation without pretending the new role is already comfortable.
Keep your equipment and basic settings predictable during this period where possible. A role experiment becomes harder to evaluate if you also change sensitivity, keybinds and input devices at the same time. Adjust a real setup problem when needed, but record what changed.
Use a three-session learning block
- First session: Notice the situations in which the new responsibility appears. Write down two examples afterwards.
- Second session: Practise one response to one of those situations. Tell teammates what you are testing.
- Third session: Review whether that response helped, then keep it, adjust it or choose a different focus.
This is a suggested structure, not a deadline for mastering a role. Some responsibilities take longer to understand. The value is that each session asks a clear question instead of demanding immediate perfection.
A fair comparison
Imagine you move from an aggressive position into a role that often follows a teammate's contact. Your personal highlight count may drop while your timing becomes more useful to the group. Review whether you were available when needed, whether the call was clear and whether your decision matched the plan.
Do not assume that lower numbers prove you are helping, either. Look at actual examples. A quieter role still requires useful decisions. Ask for feedback about the agreed responsibilities rather than asking the team whether you were “good enough.”
Keep feedback manageable
Request one actionable observation after a match. “At that moment, what information were you waiting for from me?” is easier to answer than “What am I doing wrong?” Share your own uncertainty without apologising for existing in the role. Learning works better when mistakes can be discussed calmly.
If a group responds with personal attacks or refuses to explain expectations, the problem may be the environment as well as the role. You can set boundaries, use reporting tools where appropriate or choose a more constructive group.
Make the next decision deliberately
After the learning block, decide whether to continue, adjust the role or return to the previous arrangement. Changing back is information, not a failure. Browse the GGS Playbook for more competition reading and keep the question practical: what does this team need, and what do I want to learn next?





Join the conversation.
Ask a question, share what worked, or add your take.
No comments yet. Bring a useful question or a tip from your own experience.