Buy-in is a coaching problem
Athletes do not resist velocity because they doubt the physics. They resist it because a new number on a screen feels like a new way to be judged, and because "the sheet said 82.5 kg" was comfortable.
So do not introduce it as measurement. Introduce it as the thing that stops them wasting a session. Every athlete has had the day where the programmed load was too heavy and the session broke, and the day it was too light and they left something on the table. Velocity is the answer to both, and that is the entire pitch.
The two numbers, and only two
Give each athlete two numbers to own. Not five. Not a dashboard.
- Their target velocity for the set. "This set lives at 0.60 m/s or faster." Simple, actionable, and it makes intent the job.
- Their reference number — velocity at the fixed warm-up load. "Yours is 0.78. If you're near it, you're normal. Well under, tell me."
Everything else — profiles, estimated maxes, velocity loss, trends — is yours to read, not theirs to carry. Athletes who are handed the full analytics screen stop training and start auditing themselves.
The 90-second introduction
Say roughly this, once, to the whole group, on day one:
"We are timing every rep now. The sensor tells us how fast the bar moved. Here is why that matters: your max is not the same on a Tuesday after a night shift as it is on a fresh Saturday, but the number on the sheet never knew that. Now it does. Some days you'll lift more than planned. Some days less. Both of those are correct. Your job does not change: move it as fast as you can, every single rep. If you do that honestly, the number takes care of the rest."
Then let them see their own first set. Athletes convert when they watch their own bar speed drop across a set they thought felt identical the whole way through.
Objections, and what actually answers them
| What they say | What they mean | Answer |
|---|---|---|
| "I don't want to lift lighter than the plan." | Ego and identity. | "Nobody is capping you. On a good day this makes you go heavier than the plan. It only pulls you back on the days the plan was going to cost you a week." |
| "Isn't this just RPE with extra steps?" | Fair scepticism. | "RPE is you guessing at how heavy it felt. This is the bar telling you how fast it actually moved. They usually agree — and the day they disagree is the day it saves you." |
| "Now everything I do is being tracked." | Trust. | Be direct: what you look at, what you do not, and what you will never use it for. Then be consistent about that. |
| "My numbers are worse than his." | Comparison. | "They are not comparable. Limb length and technique set your velocity. You compete against your own line, and nothing else." |
| "It slows the session down." | Usually true in week one. | Mount once, keep sensors with the bars, and stop after two weeks: it costs about thirty seconds per warm-up once the habit lands. |
The first week on the floor
- Call one velocity out loud per set, for the whole group. Public and normal beats private and clinical.
- Praise the fast light set. Whatever you praise is what they will chase, and intent on submaximal loads is the behaviour that makes all of the data usable.
- Show one athlete their own trend at the end of week one. One person seeing their line convinces the room faster than any explanation.
- Never use velocity as punishment. The first time a slow number costs someone extra conditioning, honest intent dies and your data goes with it.
- Put the app on their phone. Ownership beats surveillance: athletes who see their own history start coaching themselves.
Selling it upward
If you need a director, athletic department or club board to approve it, do not lead with bar speed. Lead with the three things they buy:
- Fewer maximal tests. Estimated maxes any week, without a max-out day and its injury exposure.
- Objective load management. A record of every session, every athlete, and the reason each adjustment was made.
- Continuity. The roster's history survives a staff change, because it lives in the portal and not in a coach's spreadsheet.
Ask for a pilot: one group, one block, one reference lift. A single testing day and eight weeks of data makes the case better than any pitch, and it is exactly the rollout in the 30-day playbook.
Run a pilot with one group.
One block, one reference lift, real data to take to your director. Tell us the group size and we will scope the pilot with you.