The Plan Should Be Wrong Eventually

What are we going to do when experience proves part of the plan wrong?

That's where I left the second essay, and I think it's an important question, because a development plan can easily start carrying more authority than it deserves. We do the assessments. We listen to the player, coach, and family, reconcile what each person sees, identify the constraints, and narrow everything down to a small number of priorities. Then we write it all down, and the document starts looking official. That's useful, but it can also be dangerous. A development plan is not a prediction of the future. It's the best developmental hypothesis we can make with the information available at the time.

Creating and periodically revisiting a player development plan is only one small piece of the individual player-development advisory work I do through Beyond the Card. Most of the work happens between those formal planning moments, because that's where the information actually accumulates: Training Cards, Match Cards, player conversations, competition, coaching observations, family decisions, and the ordinary experiences around all of them, each showing us whether the original developmental assumptions are holding up. The value sits in noticing when experience says something should evolve, not in protecting whatever we wrote down back in August.

Then the player goes back onto the court. They practice. They compete. They struggle with things everyone expected them to struggle with, and occasionally with things nobody saw coming. Something that looked like a weakness starts improving faster than expected. Something everyone thought was a strength turns out to disappear under pressure. The player grows. Their interests change. Their school demands change. A coach sees something differently. A tournament exposes a problem that never appeared in practice. A few months of experience reveal that the thing everyone thought was causing the problem wasn't actually the cause at all. That's not the plan failing. That's the plan finally getting some new information.

I think this distinction matters, because there's a natural temptation once a plan exists to start defending it. We spent time creating it. The coach agreed with it, the player signed off on it, and the family organized schedules around it. Maybe money has already been spent because of it. Changing direction can start feeling like admitting that someone got something wrong. But of course we got something wrong. We should expect to. We were trying to describe a developing human being before another few hundred experiences had happened. The purpose of the plan was never to eliminate uncertainty, only to make our current thinking explicit enough that future experience could teach us something about it. That's a very different way of thinking about planning.

If the original plan says a player needs to become more aggressive from the baseline, now we can watch for what happens when that becomes a deliberate training priority. Does the player actually recognize the situations that invite aggression, and does their shot selection actually improve, or does the increased intention just create more errors? Does the behavior show up in practice but disappear once the pressure of competition arrives, and does the player begin describing those situations more accurately over time? Maybe the original diagnosis was right, and aggression really does deserve continued attention. Or maybe three months later we realize the player has no trouble being aggressive when the situation is obvious, and the bigger issue is recognizing when the situation has changed quickly enough to act on it. What originally looked like a problem with aggression becomes a problem of perception and decision-making. Either way, the plan was still useful. It had simply helped us ask a better question.

The same thing happens with confidence. Confidence gets named as the problem in junior tennis constantly, partly because it can describe almost anything after the fact. A player misses. They're not confident. A player plays tentatively. They're not confident. They lose to someone they should beat. Confidence again. But once confidence is written into a development plan as something worth examining, experience can start putting pressure on that explanation. Maybe the player feels confident before matches but consistently gets rushed in certain patterns, or maybe they only appear confident in practice because the situations are familiar, then grow uncertain the moment an opponent changes the problem. Maybe confidence tracks preparation more than anything else, and disappears only when the player doesn't know what to do. Over time, what started as "build confidence" may evolve into something far more useful, and that evolution is the point.

The IEDE structure matters to me for exactly this reason. Intention, Experience, Debrief, Evolution is bigger than something that belongs on a Training Card or Match Card. It's a way of thinking about development at different scales. At the smallest scale, the player enters a practice rotation with an intention, has an experience, debriefs what happened, and decides what should carry forward. A match can work the same way. So can a tournament weekend. And so can a developmental year. The formal development plan gives us an initial intention for the larger period. Then hundreds of experiences start testing it. We debrief what those experiences are revealing, and the direction evolves. The loop gets larger, but the underlying logic doesn't change.

I don't think one practice, one tournament, or one bad month should automatically rewrite a development plan. Experience matters, but patterns matter more. One Training Card can catch a moment. A Match Card can tell us what the player thought after one competition, a coach can make an observation after one difficult practice, and a parent can notice something on one drive home. All of that is useful, but none of it necessarily deserves to become a new developmental priority. The interesting information starts appearing once things repeat. That shows up when the player keeps naming the same issue across several weeks, when a coach notices the same decision pattern under different conditions, or when a training priority repeatedly looks better in practice but fails to transfer into matches. It shows up when the player and coach start using different language to describe what seems to be the same problem, when a family keeps running into the same scheduling conflict between what the plan requires and what the rest of the player's life can support, or when something everyone believed would take six months suddenly starts changing in six weeks. That's when a collection of moments begins becoming a pattern, and once a pattern becomes visible, the plan should be allowed to respond.

The point isn't to protect the plan. It's to maintain enough continuity to notice when the plan needs to change. That sounds simple, but continuity is one of the things junior development environments often struggle to produce. A player has a lesson on Tuesday, group practice on Wednesday, fitness on Thursday, a tournament on the weekend, a conversation with a parent in the car, another lesson Monday, then moves into the next week. Each experience may be useful on its own, but they don't automatically connect themselves. The player may be told five useful things by five different people and still have no idea which one matters most. The coach may be working patiently on something that hasn't yet transferred into competition, while the family interprets the tournament results as evidence that nothing is improving. Or the player may actually be changing in an important way, but because the ranking hasn't moved yet, everybody starts looking for another problem to solve.

A development plan gives those experiences a larger context. The ongoing process helps determine whether that context is still accurate. That's also why I think review matters more than evaluation. Evaluation tends to ask, "How good is this right now?" Review asks, "What has changed since we decided this mattered?" Those are different questions. If second-serve development was one of the three priorities for the fall, we don't simply need a new rating of the second serve in November. We need to know what the player has experienced while developing it: whether the technical change is stabilizing, whether the player is using it under pressure, whether double faults are changing, whether the player trusts it differently, whether the improvement has opened other tactical possibilities, and whether it's still the thing that deserves the same amount of attention.

Sometimes the answer is yes. Other times the priority remains important but the way we're approaching it needs to change, or the player has evolved enough that something else now deserves the attention. And sometimes we discover the original priority was never the real problem to begin with. None of those outcomes should threaten the process. They're what the process is for.

There is another reason I think the plan needs to remain movable, and it has less to do with tennis than with ownership. If adults present a development plan to a player as though it came down from the mountain complete and correct, we teach the player something about development. We teach them that knowledgeable adults identify the problems, construct the answers, and tell the player what to do. That may produce compliance. I'm not sure it produces much ownership.

A plan that is deliberately revisited teaches something different. We thought this mattered, so what have you noticed? We expected this to improve, so has it? You said this was a weakness three months ago, and your coach saw it one way. Do you still think that, and has your own experience actually supported it? What are you seeing now that you couldn't see when we started? Those questions require the player to participate in interpreting the evidence of their own development. At first, their answers may not be particularly sophisticated. That's fine. The point isn't to hand over every developmental decision to a 13-year-old. The point is to help that 13-year-old become a 14-year-old who can see a little more accurately, then a 15-year-old who can connect experiences a little better, and eventually a player who doesn't need adults to explain every change happening around them. That progression matters to me more than producing a perfectly written plan.

In fact, if we reach the end of the year and the original development plan still describes the player perfectly, I'd probably have some questions. Did the player actually change, or did we just learn something we didn't already know? Did the environment reveal anything unexpected? And did our priorities evolve as new capabilities emerged, or were we simply measuring the player against the assumptions we started with the whole time? A developmental year should produce information that wasn't available at the beginning. If it does, some part of the plan ought to look different by the end.

That's why I don't mind saying the plan should eventually be wrong. Not recklessly wrong, not poorly constructed, and not based on bad information. Wrong because the player moved, because experience taught us something, because the question got better. The plan is valuable precisely because it gave us a starting point clear enough to outgrow.

At the beginning of this series, I argued that late summer is a better beginning to the developmental year than January. It's the moment when the previous season has generated evidence, the coming school year is forcing new choices, and there is still time to make those choices deliberately. Then we put three different views of the player next to one another: what the player believes, what the coach sees, and what the family can realistically support. From there, we narrowed all the things that could be improved into the few things that deserve unusual attention now. So we begin. But beginning deliberately doesn't mean staying stubbornly committed to what we believed at the beginning.

The development plan gives us a direction. Experience tells us what that direction was missing. Debrief helps us understand what the experience means. Evolution changes what we do next. We go around again.

The goal was never to create a perfect plan for the player.

It was to help create a player who becomes progressively better at building the next one.