Notes from the Field

Putting my tournament debriefs under a microscope

I'm good at tournament debriefs. I've spent decades watching junior matches, remembering what actually happened, sorting the patterns from the noise, and helping players carry something useful into the next round. I don't hand a kid a list of instructions I could have given before the match started. I want to know what happened today, against this opponent, in these conditions.

So I started recording them.

At Little Mo Nationals I taped two post-match debriefs and part of a conversation with a parent while we watched a match together. I've been doing this more and more in my work. Record it, transcribe it, then study what I did instead of what I remember doing. Memory is generous. A transcript isn't. It shows the question you asked, the answer the kid gave, and everything you said after the kid had already gotten somewhere.

I expected to find a coach who didn't ask enough questions. That's the usual suspect. But I asked plenty, and most of them were pretty good. The problem showed up one beat later. A player would say something worth staying with, and my expertise would go right to work improving it. Usually I'd put the answer into better tennis language and then fill in whatever the player had left out. It was sound tennis. Which is exactly why it's so hard to see.

She already had the plan

One player, a nine-year-old girl, was about to face the top seed. She had played this opponent earlier in the year in Florida on green clay. She remembered the girl liked to slide on clay, and she figured the sliding wouldn't work as well on a hard court. So her plan was to make her run. Then, without me asking, she added a second piece. Stay consistent and don't hit balls everywhere.

Look at what happened in those few sentences. She went from a memory, to a difference in conditions, to a plan she could test a few hours later. Observe, interpret, test. Nobody handed her that. She built it.

Here's what I did next. I praised her consistency and compared her to a boy who gets everything back and drives his opponents crazy. I walked her back through the clay match and reminded her to attack when the chance came, which turned into an explanation of the different ways to attack besides coming to the net. None of it was wrong. What I'm asking now is whether she needed any of it right then.

The tape showed me something else I missed in the moment. A minute earlier she had offered a different idea: hitting through the opponent's forehand. I answered with a general observation about girls whose backhands are better than their forehands. She never came back to her idea. I don't know if it was a good one. I never found out.

Three seconds

The other player, a boy, gave me an even cleaner example. After we talked about his match, we moved to his next opponent. He started with reputation. The kid was the number one seed and wins every tournament. When I asked what else he knew, he shifted to behavior. The kid misses a lot and likes to come forward. I asked for his keys.

"Maybe I keep them back."

There it was. Status to observation to a tactical idea, in about thirty seconds.

My next sentence came roughly three seconds later: "So hit quality rally balls, right? Rather than trying to hit winners." His reply was one word. "Yeah."

A little later I asked whether he kept the ball deeper when he was hugging the baseline or when he played a step back. He said a step back. Good answer. Then I explained the tradeoff, because taking balls early is something I love about his game and don't want to coach out of him. Again, the tennis was fine. But he had already said "step back." What if my next question had simply been, "How will you know the extra step is helping?"

That question doesn't hold back expertise. It asks him to keep building before I finish the job for him. The same chance was there after "keep them back." I could have asked what kind of ball keeps an opponent back and waited. Eventually a player runs out of road. Then I teach. But at least I'll know where his road ended.

What the word count showed

I went back and counted words in both transcripts. Not because coaching is a talk-ratio contest, but because numbers make habits visible.

With the girl, I spoke about 68 percent of the words while we reflected on the match she had just played. When we turned to the next opponent, my share climbed to about 76 percent. With the boy, the reflection was about 86 percent me. The planning for his next round was about 94 percent. In the stretch where we built his plan against the top seed, he said 29 words. I said 482.

Those aren't grades. Automatic transcripts are imperfect, some players need more scaffolding than others, and sometimes the coach needs to explain. But the direction got my attention. Both times, the moment we moved from what happened to what comes next, I took over more of the work. And what comes next is the exact place I want players to become independent. The goal can't be a kid who needs a brilliant debrief after every match. At some point the player has to run most of the debrief in his own head, with a coach sharpening the edges instead of building the center.

This pulled apart two ideas I'd been treating as one. Helping a player understand a match is not the same as helping a player become able to build understanding. I can hand a kid a great explanation. He might even play better in the next round because of it. But if I built most of it, I improved the plan for noon without doing much for his ability to solve the next problem without me.

Talk later

What she did on her own sits at the center of the sequence I'm working with now: recall, notice, interpret, test, choose. The player reconstructs the match, tells me what she saw and what she thinks it means, and picks one or two things to test on court. The next match stops being an exam she passes or fails. It becomes an experiment.

This fits the way I already think about development through IEDE: Intention, Experience, Debrief, Evolution. What's changing is the debrief. I've mostly treated it as the place where the coach turns experience into understanding. I'm now more interested in making it the place where the player practices doing that, with the coach stepping in when the player's model hits its limit.

The parent conversation raised a parallel question. While we watched, I narrated what I saw, mostly court position and patience. I have no reason to think any of it turned into a technique conversation afterward. But the risk comes with the setup. The more technical interpretation a parent collects, the easier it becomes to slide into the role of second coach on the ride home.

Better parent education may be about what to notice, not what to fix. How a kid's court position holds up under pressure, or how quickly she gets to the next point after a frustrating one, tells a parent a lot about development without inviting anyone to repair a stroke. The most useful thing I said in that whole conversation had nothing to do with tennis. I told the parent watching your own kid struggle is one of the hardest things you do as a parent. That might be closer to the parent curriculum I want to build.

The experiment

So I'm going to run an experiment. For the opening stretch of my next tournament debriefs, I won't introduce a tennis idea the player hasn't introduced first. Questions are fine, and so is asking for evidence or pointing out a contradiction. What I'll resist, for a few minutes, is improving the answer before I know how far the player can take it.

This isn't a vow to talk less. I have too much stored up to pretend holding it back is automatically a virtue. The better phrase is talk later. Let the player get farther first, find where her thinking stops, and then use what I know to extend her model instead of replacing it.

I'm doing this in public on purpose. Most professional writing shows up after the uncertainty has been cleaned out. You get the finished framework and the confident principle. You don't get the practitioner staring at a transcript of something he thinks he's good at and finding room to improve. I think that part is worth showing.

I still believe I'm good at debriefs. The transcripts didn't change that. They changed the standard. A kid walking away understanding the match isn't enough anymore. Now I want to know how much of that understanding the kid built, and what I did in the three seconds after the answer. Over a season, I'm looking for a player who needs less of me.

That's what I'm bringing back from the field. Not a doctrine. A better instrument, and a better question.