Building Your Basketball "Menu": Why the Order You Learn Skills Matters More Than How Many You Know

If you've spent any time around basketball development content, you've probably heard the Kobe Bryant story — the "menu" philosophy. Instead of trying to improve everything at once, Kobe would isolate one skill for months at a time. Six months on nothing but his shot. Six months on nothing but creating his own shot off the dribble. Skill by skill, he built a menu he could pull from in any game situation. Within two years of committing to that process, he'd caught up to and passed most of his competition.

It's a great story. But it leaves out the part that actually determines whether a young player benefits from it — and it's the part I think about most as a coach.

Where This Comes From

I grew up on Michael Jordan videos before I grew up on Kobe. Jordan talked constantly about not having weaknesses — working his finishing, his jumper, his threes, his defense, his rebounding, his passing, until there was no hole in his game to attack. That planted something in me early: the drive to be complete, not just good at one thing.

By the time I was old enough to train seriously, Kobe's menu philosophy gave that drive a structure. I'd go to the court and shoot fifty makes of one layup type. Then fifty makes of one type of pull-up jumper. One skill, isolated, repeated past the point of boredom. What let me actually stick with that — long enough for it to mean anything — wasn't discipline. It was that I genuinely loved it. The repetition didn't wear on me the way it wears on most kids, and that's what let the skills eventually show up in games instead of just in practice.

That's the piece I want to unpack, because it's the piece most menu-building advice skips entirely: having a skill and being able to use it in a game are two different things, and the gap between them is where most young players get stuck.

Why a Drilled Skill Disappears in Games

I train players across every age and skill level, and the pattern is almost never about talent. It's about what happens to a skill between the training gym and game day.

At training, a player is free. Mistakes don't cost anything. There's no one keeping score in a way that matters, so the game feels light and the skill flows. On game day, that same player is suddenly playing against an unknown opponent, in front of teammates, parents, and a coach — and all of that becomes noise. What will my teammates think if I mess this up? What will my parents say in the car afterward? What does the coach think of me right now? That noise is enough to shut a skill down completely, even one the player has drilled hundreds of times.

Here's the part coaches don't say enough: under pressure, a player doesn't perform their best skill. They perform their default skill.

A basketball game moves too fast for conscious thought. You don't get time to decide — you're reading and reacting on instinct, on whatever's automatic. If a skill hasn't been drilled to the point of being unconscious, it doesn't exist in that moment, no matter how good it looked in an isolated training rep. That's the real reason "he can do it at practice but not in games" happens. It's not a confidence problem in isolation — it's an integration problem.

How I Actually Build the Menu

Every player I train starts the same way, before a single skill is even discussed: I try to understand who they already are on the court.

If I can get footage, I watch it — footage tells me how a kid actually reacts under real pressure, not how they think they play. If I can't, I ask the parents what they see, and I ask the player the same questions. I'm not just collecting information here — I'm checking whether a young athlete has honest self-awareness about their own game. That awareness matters later.

Then I watch how they move. Every player has a physical trait or instinct that's already theirs — speed, strength, footwork, size, rhythm — and my job is to name it for them before we do anything else. Because the first session isn't about fixing a weakness. It's about proving to a kid that they already have an advantage nobody gave them. That's the first item on the menu, and it's not a skill — it's confidence, built on something real.

From there, the actual skill work is the easy part. Skills are just time — the more focused time you put in, the more you get out. What's hard, and what I think is the actual coaching job, is choosing the order.

If you start a kid on the weakest part of their game, they won't see results for a long time, and they'll feel worse about themselves the whole way through. Instead, I look for the skill they're already about 70% of the way to — something close enough that a small adjustment produces a visible, immediate improvement. That early win creates momentum. It's a snowball, and it rolls in the right direction: skill one gets integrated into games, confidence goes up, skill two goes faster because they trust the process now, and so on down the menu.

Why the Menu Order Is Different for Every Player

Two players the same age can have completely different menus, in a completely different order — and both be exactly right.

One athlete I train is strong and confident, with a gymnastics background. Her footwork and hand speed lag behind her strength, which means her handle is a little slow and easy to steal, but she rebounds like someone twice her experience level. Her menu starts with footwork and ball-handling speed, because that's the gap between what she already has and what will let her use it.

Another player I recently started with is brand new to the sport — first season, naturally tall, naturally athletic, and already comparing herself to more experienced teammates ahead of tryouts, which was making her anxious. Five minutes of watching her move was enough to see it: her foot speed and her handle off a pivot were already ahead of most players her age. That's her advantage, whether she grows another six inches or not. If she's tall for the rest of her life, she's a point guard — and a point guard's job is to create separation without over-dribbling, because the more touches a smaller, faster defender gets on the ball, the more likely it gets stolen. So her menu starts with intentional, elite-speed footwork, aimed at teaching her when not to dribble as much as how to.

Both players are working toward the same underlying principle — footwork that supports the rest of their game. But the order, the pace, and the specific drills are built around what each of them already has, not a generic progression. That's the whole point of a menu: it's built for the player in front of you, not the average player at that age.

What Parents Can Actually Do

If there's one thing I want a parent to take from this, it's to stop comparing your child's timeline to anyone else's. Every player develops at their own pace, and that pace is shaped by more than just the hours put in.

The best thing you can do isn't a drill or a program. It's showing up. Go rebound for them. Go pass to them. Be part of the journey, not just the audience for it. And especially before the age of twelve or thirteen, resist the urge to review the game on the drive home. Kids already know if something happened in the game and can review that with their coach — what most kids need to hear from a parent afterward is simply, "I loved watching you play." The moment it turns into homework — what did I do wrong, what do I need to fix — is the moment a kid starts playing to avoid disappointing someone instead of playing because they love it. And love is what makes a player willing to put in the boring, repetitive reps that skill-building actually requires.

I'd also say this, from my own experience: you don't know another kid's story. I had real drive as a young player, but a lot of it early on came from wanting to be accepted by people who were never going to accept me, no matter how good I got. I had talent, but for a long time I was building my game for the wrong reasons. In hindsight, when people look at a player and wish they had that player's skill, they usually wouldn't actually want the story that built it. You can't want the view without the climb — and you don't know what someone else's climb cost them. Your child doesn't need someone else's story. They need the time and support to build their own.

Want to know what should be first on your child's menu? We start with a simple conversation — and five minutes of watching them move. Book a Session with SiSU