Having spent more than thirty years on the ice as a player, referee, and coach, I have watched the game from nearly every conceivable angle. That perspective has revealed a persistent issue in youth hockey: we too often sacrifice long-term development to maximize short-term results.
One of the clearest examples is how quickly we lock young players into positions. We put our biggest players on defense because they can control the defensive zone net front. We put our fastest player on the wing because they can chase down stretch passes. We find the position where a player is most comfortable and successful, and then leave them there season after season.
It works. It can win games. But when our ultimate goal is to develop complete, intelligent hockey players, we have to ask whether winning today's game is worth limiting tomorrow's player.
The pressure to prioritize results is understandable. Coaches want their teams to succeed, and parents want their children to feel successful. Putting a reliable player in a familiar position creates predictability and minimizes mistakes. There is nothing wrong with wanting to win. The problem occurs when winning becomes the primary measure of whether we are doing our jobs as coaches.
A young defenseman who consistently shuts down opponents may look like a great defenseman. A fast winger who repeatedly gets behind the defense may look like a natural forward. But if we never challenge those assumptions, we may be developing players who are very good at performing a role without fully understanding the game around it.
Well-meaning parents can fall into the same trap, seeing their child primarily as a center, defenseman, or winger simply because that's where the child currently looks most comfortable. Coaches reinforce that perception because it's easier to build a lineup around players who already know what to do. But youth hockey isn't supposed to be about finding the most efficient way to use a young player. It should be about giving that player the broadest possible foundation from which to develop.
A Mother Who Didn't Understand, Until She Did
I experienced this firsthand years ago, coaching a young girl on one of my 10U teams. Her mother recently ran into my wife out in town and shared something I'll never forget. During that season, she genuinely couldn't understand why I insisted on rotating her daughter through different positions instead of leaving her where she was most comfortable. At the time, she saw it as unnecessary and maybe even counterproductive.
Years later, as her daughter advanced to higher levels of hockey, the mother noticed something different: her daughter had developed an exceptional ability to adapt, read the ice, and understand what was happening around her. She finally understood why we rotated positions.
That story has stayed with me because development rarely feels efficient while it's happening. A player learning a new position may not look as good as one who has spent months mastering a familiar one. There will be mistakes, hesitation, moments of visible discomfort. From the outside, it can look like we're making the player worse. In reality, we may be giving them something more valuable: perspective.
Why Perspective Beats Repetition
Hockey is a connected game. Every decision one player makes affects the options available to someone else. A defenseman makes a first pass because a forward has created an outlet. A winger supports the puck because the defenseman needs an option. A center tracks back because the defense needs help protecting the middle. Players understand those connections more deeply when they've experienced the game from different sides of the decision.
Consider a defenseman who spends meaningful time playing center. They suddenly experience how little time and space exists in the high slot. They learn what a center sees when trying to receive a breakout pass under pressure, and what it feels like when a defenseman waits too long to move the puck. When that player returns to defense, they don't just know where the center should be. They've experienced why the center needs to be there.
The same happens in reverse. A winger who spends time on defense gains a real appreciation for puck management at the blue line and learns how quickly an offensive-zone turnover becomes a defensive-zone problem. A forward who plays defense learns that defending isn't just chasing the puck; it's stick positioning, gap control, angling, and reading passing lanes. Those lessons follow them back to forward.
The result is a player who sees more than their assignment. They begin to understand how positions interact and that's what separates elite players who moved between forward and defense, or played multiple roles within a position, during their development. Not the ability to line up in different spots, but the ability to understand how those spots depend on each other.
Where Specialization Still Belongs
This isn't an argument for rotating everyone into everything forever. Goaltending is its own discipline. The technical foundation takes years to build and doesn't transfer from skating out. Faceoff specialists, shot-blockers, and certain power-play or penalty-kill roles genuinely benefit from repetition once a player has already built a broad foundation. The point isn't that specialization is bad. It's that specialization should come after a player has a foundation to specialize from, not substitute for building one in the first place. A 10-year-old who has only ever played left wing hasn't specialized. They've just never been asked to do anything else.
Giving Players Permission to Fail
Mistakes will happen. Move a natural forward to defense, and they may turn the puck over at the blue line. Put a defenseman at center, and they may lose track of their coverage. That discomfort isn't evidence the exercise is failing. In many cases, it's evidence the player is learning.
This is where our leadership as coaches is tested. If a player is benched, yelled at, or embarrassed for a mistake made while learning a new position, the lesson they take away isn't that they learned something. The lesson is that they should avoid trying it again.
If we tell players and parents that development matters more than the scoreboard, but then punish every mistake that comes with development, our players will quickly figure out what we actually value. They'll stop taking risks. They'll stop asking questions. They'll play not to make mistakes rather than to make plays. That's the opposite of what we want.
Making Rotation Actually Work
Position rotation isn't randomly moving players around and hoping development happens. It must be deliberate, age-appropriate, and built into how you run both games and practices.
In games: With younger age groups, I recommend rotating players every few weeks or every month, so everyone gets meaningful reps at forward and defense across the season. This gives players a chance to build confidence in a position over several practices and games before moving to the next one. I've tried rotating every game, and it didn't work as well as planned. Players never got the chance to build confidence before being moved again. It's also fine to pause the rotation for tournaments, where the stakes and unfamiliarity of a new format can make experimentation riskier. Just pick the rotation back up once you're back to regular-season games. Whatever cadence you choose, make it transparent and predictable: communicate the plan to players and parents in advance, and do so consistently throughout the season.
In practice: This is where rotation is lowest-risk and highest-value. During small-area games, transition drills, and scrimmages, assign defensemen to play forward and forwards to play defense with no scoreboard pressure attached. Practice is where a player can fail at gap control or a first pass without a parent in the stands reacting to a goal against.
With parents: Tell them before the season starts, not after a bad shift. Explain what rotation is building and why a rough game in an unfamiliar position isn't a step backward. Parents who understand the plan going in are far less likely to see a mid-game struggle as a coaching mistake.
After the rotation: Talk to players about what they experienced. What did they notice from the new position? What was hard? What did their teammates need from them that they hadn't considered before? Then, when they return to their primary position, connect those observations back to their responsibilities. The rotation creates the experience. Reflection is what turns that experience into understanding.
What We're Actually Building
There will always be games we want to win, tournaments where the result matters, moments when coaches make decisions to give their team the best chance to succeed. That's part of competition, and learning to compete is, itself, part of development.
But youth hockey isn't ultimately about maximizing wins at age 10, 11, or 12. It's about building players who keep improving as the game gets faster, more complex, and more demanding. The player who dominates because they've been protected in one position may win more games today. The player who has learned to see the ice from multiple positions may be better prepared for tomorrow.
After more than thirty years on the ice, I've learned that the tournament banner eventually gets packed away. The score gets forgotten. What remains is the player's ability to think, adapt, compete, and understand the game. The scoreboard tells us what happened today. It doesn't tell us what the player is becoming.
Don't just develop the player who can play a position. Develop the player who understands the game. That's the kind of development that lasts long after the scoreboard is turned off.
