Name the problem before choosing the grenade
Start with the round objective. You may need to cross a dangerous line, delay an attack, clear a position, or support a teammate's contact. Choose utility because it helps solve that problem, not because you remember a lineup you want to demonstrate.
Write the intended effect in a short sentence. For example, block a sightline while the team takes a route, or help a teammate commit to a specific fight. If you cannot describe who benefits and what happens next, the throw needs more thought before becoming part of a plan.
Learn a small, complete sequence
A useful sequence includes where you start, what information you need, when you throw, and where you move afterward. Practice reaching the setup safely. Include a fallback if you arrive late or cannot access the position.
Avoid collecting many throws without understanding their timing. A smaller set connected to your regular positions is easier to use under pressure. Keep notes or a short recording for the sequences that matter, and recheck them after map or gameplay updates.
Coordinate the moment of use
Tell teammates what the utility is meant to enable. Agree on the action that follows and who signals the commitment. A well-executed throw can still be wasted if the player it supports is checking another angle or waiting for a different cue.
In practice, rehearse the sequence with the actual teammate when possible. Ask what they can see and when they feel ready to move. If a plan relies on several throws, identify which one is essential and what the team should do if it is missing.
Review utility in context
When a round fails, pause before the throw. Consider the information, time, teammates, and resources available. Was the purpose still relevant, or had the situation changed since the original plan?
Then examine the follow-up. Did the team act while the utility supported the intended space? Did someone assume a position was safe without checking it? Was a later problem caused by spending all available resources too early? Keep the lesson tied to an actual decision rather than judging the throw only by its landing point.
Build a practical map notebook
For each regular position, keep a few entries organized by purpose: opening support, pressure response, retake, or post-plant. Describe the trigger, expected teammate action, and fallback. Add the date you last tested the sequence.
Treat community lineups as starting points to verify in your own environment. Do not claim a throw is guaranteed across every update, position, or opponent response. If a coach reviews your utility, ask for priorities connected to your role and a short set of repeatable tasks.
The objective is better decisions with the resources you have. A useful grenade creates an opportunity the team understands; practice should include recognizing that opportunity and acting on it, rather than stopping once the object reaches the expected location.