Why Every Coaching Team Needs a Shared Vocabulary
When two coaches use different words for the same thing, players get mixed signals. When they use the same words, the language becomes culture.
You can have two excellent coaches who completely contradict each other — not on philosophy, but on language. One calls it a reset, the other calls it a defensive dink. One says paddle up, the other says ready position. The player who works with both ends up with twice the vocabulary and half the clarity.
This is fixable, and it costs less than you'd think.
Why shared vocabulary matters
When two coaches use different words for the same thing, players get mixed signals. When they use the same words, the language becomes culture — and players start using it themselves: "Let's play 7-11" → "I need to work on my drop" → "That was my intent."
Shared vocabulary is how the system travels through your players, out the door, and onto the world.
How to structure the database
Every term should carry, at minimum:
- Term — the word
- Tier — at what level a player or coach should encounter this (Fundamentals · Intermediate · Advanced · Methodology · Team-Specific)
- Category — the skill bucket (Control, Dink, Positioning, Placement, Gameplay, Reflexes, Power, Angles is one good set)
- Definition — what the term means, in one sentence
- Coaching cue — the line you'd actually say out loud to a player
- Beginner cue — simpler cue-word version for younger or earlier-stage players
- Source — where the term comes from (e.g., a curriculum, a webinar, your team)
- Notes — anything coaches should know about using the term
The format isn't sacred. A Notion database, a Google Sheet, an Airtable, a shared markdown file — any of these work as long as every coach actually opens it.
Useful views
Once the database has thirty or forty terms, views matter more than the data:
- All terms — default table, everything
- By tier — grouped by learner-readiness tier
- By category — grouped by skill category
- Beginner cues — filtered to Fundamentals with kid-friendly cues
- Coaching methodology — diagnosis frameworks and teaching methods
- Team-specific — everything your team has added on top of the source curriculum
The "By tier" view is the one new coaches use most. The "By category" view is the one mid-level coaches use to plan a block.
How the vocabulary grows
The vocabulary is a living document. If a coach realizes:
- We don't have a shared word for this technique
- I use a cue my players love but it's not in here
- This term needs a better beginner version
…they should add it. Tag it as team-added so attribution stays clean. Notes are encouraged. Have one person (typically the director) review new entries monthly to align wording across coaches.
If a coach is unsure whether something belongs — add it anyway. You'd rather clean up occasionally than miss a term your players are already using.
Start with a source, then add your own
The fastest way to spin up a vocabulary database is to import from an established curriculum, then extend it.
The RacketPro Level 1 and Level 2 coach curriculum is a good starting point — their teaching videos span eight skill categories, and Collin Johns' Hierarchy of Assessment webinar is one of the best diagnostic frameworks publicly available.
Use a source like that for the technical and tactical foundation, then extend it with your team's own language — the system-specific terms only your players hear from your coaches.
That layered approach buys you the best of both: every new coach inherits a vetted base, and your team's specific identity shows up in the layer on top.
The cultural payoff
The first week your players start saying "that was my intent" unprompted, you'll know it landed.
The vocabulary stops being a Notion page and becomes how your team thinks.