A diagram can be confusing even when it is simple. If arrows, numbers, and colors change meaning from one page to the next, players must decode the drawing before they can discuss the play. Agree on a small set of team conventions and make the legend visible.
Define the legend first
Show how the diagram represents the ball handler, teammates, and defenders. Give passes, dribbles, cuts, and screens distinct line styles or labels. Do not rely on color alone: pair color with shape, line style, or a short word so the drawing remains readable in grayscale and for people with different color perception.
Use only as many marks as the explanation needs. One convention might use a solid arrow for player movement, a dotted arrow for a pass, and a numbered marker when two lines cross. If a reader has to guess what a symbol means, add it to the legend or remove it.
Give each diagram one question
A first page rarely needs every player's route, every defensive response, every branch, and every finish. Start with the alignment and first read. Add a second panel for the next action or alternative. When a play branches, connect an observable cue—such as a defender dropping or switching—to the decision being taught.
Add one sentence under the drawing: what should the player notice before choosing? A diagram is a shared picture of a situation, not a memorization test. Do not call a reasonable read wrong only because it differs from the line on the page.
Keep the team's language consistent
Use the same play names, jersey numbers, court orientation, and symbols in practice, meetings, and handouts. When updating an old drawing, add a date or version so people can tell which page is current. Follow team rules for storing and sharing diagrams that include player names or other identifying information.
Run a quick readability check
Ask a player who did not draw it to look for a short time and explain the opening action and next decision. If explanations differ, clarify the arrow, legend, numbering, or court orientation. This checks whether the diagram can be used, not only whether the author understands it.
These conventions are practical suggestions, not official rules or a required tactical system. Adapt them to the language your team already uses.
Sources
- FIBA / WABC Coaching Clinic Videos — coaching videos for coach education.
Frequently asked questions
How should a team choose its diagram symbols?
This article proposes examples for a team convention. Follow any materials required by your organization or competition, and align the symbols with your team's existing language and instruction.
Is color alone enough to distinguish players or actions?
Use line styles, numbers, or short labels alongside color so the drawing remains readable in print and on different screens.
How should a play with multiple reads be drawn?
Separate the first read from the follow-up options. State the defensive cue that triggers a branch, and avoid putting every route on one crowded page.