We Taught It. That Doesn't Mean They Learned It.

For eleven weeks this summer, we worked on what players do between points.

Not forehands. Not backhands. Not serve patterns. The few seconds after one point ends and before the next one begins.

We built a court around it. We taught a routine, the 16-Second Cure. We repeated it. We reminded players. By the end of the summer, nobody doubted whether they could do it.

Then something encouraging happened. I was at an L6 at Courtyard Tennis Club watching our players. Jack Newman was watching other Austin Tennis Academy players at another L6 at Westwood. We weren't together and hadn't compared notes ahead of time, but we came home saying the same thing.

The between-point work looked good. Players were resetting. They were doing what we'd spent the summer asking them to do. That mattered, because the real question hanging over any training exercise is whether it survives contact with competition. Something can look great when a coach is standing ten feet away and disappear as soon as a score gets attached to it.

This time, it had traveled.

Then Jack went to New York. He was at a USTA coach-education event, and one assignment was to watch what players do between points. His assignment was Grigor Dimitrov, playing a qualifying match, and he came back talking about how consistent Dimitrov looked. You couldn't tell from his between-point routine whether he'd won the last point or lost it. The process looked the same either way.

We had just spent eleven weeks working on exactly that. There was some satisfaction in hearing it. What we'd emphasized all summer wasn't some strange academy exercise. Coaches at the highest level were being told to pay attention to the same part of the game.

Then Jack came home and saw something more useful.

He logs into the academy cameras on weekends sometimes, when the facility isn't programmed and he wants to see who's out getting extra work. This time he pulled up one of our players in a practice match.

The between-point routine was gone.

Not a little worse. Essentially gone.

That player knew the routine. We had watched him perform it. He'd done it enough times that none of us could honestly say we hadn't taught it.

We taught it. He could do it. And there it was, disappearing the moment the environment changed.

That distinction has stayed with me.

A player demonstrating a skill in the environment where we taught it tells us he can do it. It doesn't tell us he owns it.

I think coaches confuse those two things all the time. We explain something and the player understands it. We drill it and he executes it. We put him in points and the behavior holds up. Maybe we even see it hold at a tournament. Somewhere in there, we check the box.

Learned.

But what do we actually mean by that word?

If a behavior shows up when the coach is organizing the environment and disappears when the coach is gone, has it been learned? If a player uses it at a tournament where academy coaches are watching but not in a Sunday practice match where nobody is, has it transferred? If he understands why it matters but doesn't recognize the moment he needs it, does he own it?

Those aren't rhetorical questions. I don't think the answers are always the same.

During one of our classroom sessions that week, we rebuilt from memory a progression we'd introduced the day before.

First, notice what's happening.

Then understand why it matters.

Practice it.

Own it.

Transfer it.

The more I sit with that progression, the more the last two words carry the weight.

Own. Transfer.

Coaching is good at creating the conditions for the first three. We help a player notice something, explain why it matters, then design the reps that put it in his hands. Then the job changes.

Ownership asks the player to start doing work the environment used to do for him. The coach used to notice. Now he has to notice. The coach used to remind. Now he has to remember. The coach used to impose the routine. Now he has to choose it.

Transfer raises the bar again. Can the behavior move from the drill to the point? From the point to the practice match? From the practice match to the tournament? From the tournament where the coach is watching to the weekend match where nobody is?

That might be a better test of learning than whether a player can reproduce something on command.

Here's the part that matters most: none of this means the summer work failed. Quite the opposite.

The player who dropped the routine on the weekend had already proven the skill existed. That's real. There's a difference between not knowing how to do something and not yet carrying it everywhere you need it. The first is an instruction problem. The second is a transfer problem. They call for different responses.

If I mistake a transfer problem for an instruction problem, my instinct will be to teach it again. More explanation. More reminders. More reps. Some of that might help. But maybe the better question is different: what has to happen for the player to notice the routine is missing before I do?

That's where this week's classroom conversation about awareness started making more sense to me. We talk constantly about accountability in sports. Hold yourself accountable. Compete harder. Stay focused. Use your routine. Do what your coach asked you to do. But accountability is hard without awareness. A player can't hold himself accountable for drifting if he doesn't know he's drifted. He can't regulate a routine he doesn't notice he's dropped. He can't solve a pattern he doesn't see.

At some point, development has to include more than helping a player perform the right behavior. It has to help him become someone who notices when the behavior is missing. That's a different job, and it changes what I think a good developmental environment is supposed to do.

We build structures around young players because they need structures. A coach reminds because a player hasn't learned to remind himself yet. A parent drives him to practice because he can't get himself there. A Training Card prompts because the player isn't yet prompting himself. None of that is a weakness in the system. Young players need scaffolding.

But scaffolding has a purpose. It's supposed to help build something that can eventually stand with less of it. Developmental architecture should work the same way. If a player can only use a skill while the architecture is actively prompting it, the architecture still has work to do.

The real measure isn't what a player does while the system is prompting him. It's what's left when the system pulls back.

That weekend practice match gave us information a perfectly organized training session never could have. It showed us the behavior existed. It also showed us ownership was incomplete.

That's useful. Because now the question isn't whether we taught it. We did. The question is what has to happen next so the player can carry it without us.

That's where the developmental handoff begins.