I’ve spent more hours than I care to admit standing on waterlogged pitches, watching “modern” coaches blow whistles and launch into five-minute lectures that leave half the squad staring at their laces. They think they’re being pedagogical, but they’re really just talking to themselves while the game passes them by. Most of the glossy manuals will tell you that how to use questioning with players is about “facilitating cognitive development” or some other such nonsense you’d find in a university textbook. In reality, if you’re standing there delivering a monologue, you aren’t coaching; you’re just making noise while the players lose interest.
I’m not here to give you a theoretical framework that falls apart the moment a winger starts sprinting or the rain starts coming down sideways. I’m going to show you how to ask the kind of sharp, brief questions that actually force a player to look up from the mud and see the space they just missed. We’ll skip the jargon and focus on the practical reality of getting an answer that actually matters during a session. I’ll tell you exactly what to ask, when to shut up, and how to ensure they actually learn something before the whistle blows.
The Death of the Monologue Coaching Through Guided Discovery
The biggest mistake I see on a Sunday morning is a coach standing in the centre circle, delivering a fifteen-minute sermon while fourteen kids pick at the grass or stare at the clouds. You aren’t teaching them anything; you’re just making them wait for the next time they’re allowed to move. If you want to actually improve player decision making, you have to stop being the source of all answers and start being the one who points out the gaps. This is what people call coaching through guided discovery, but I just call it letting them figure out the game before they lose interest.
Instead of telling a winger to “get wider,” try asking why they felt so congested in that last transition. It’s the difference between a closed question—one that only requires a ‘yes’ or ‘no’—and an open-ended one that forces them to actually process the chaos. When you shift from lecturing to facilitating, you aren’t just giving orders; you are building their ability to think when you aren’t there to hold their hand. That is how you build a player who can solve a problem in the 89th minute without looking at the bench for permission.
Open Ended vs Closed Questions in Sports Finding the Right Trigger
Now, don’t get me wrong; I’m not saying you should abandon closed questions entirely. If I see a player standing with their hands on their hips while the ball is rolling toward the corner flag, I’m not going to ask them, “How did that feel, son?” I’m going to bark, “Get back in position!” That’s a closed question, and it’s necessary when the game is moving faster than your ability to philosophize. Closed questions are for immediate correction and setting the tempo. They provide the quick, sharp cues that keep a session from turning into a disorganized stroll through the park.
However, if you want to move toward improving player decision making, you have to learn when to pull the trigger on an open-ended question. A closed question tells them what they did wrong; an open one forces them to figure out why it happened. Instead of saying, “Was that the right pass?”, try asking, “What did you see in that space before you moved?” This is the heart of open-ended vs closed questions in sports: one is a steering wheel for the moment, the other is the map for the rest of their career.
Five Ways to Stop Talking and Start Making Them Think
- Timing is everything. If you wait until they’re halfway back to the halfway line after a turnover to ask why they lost possession, you’ve already lost them. You ask the question while the mistake is still stinging, or you wait until the next break in play. Don’t let the question become background noise while they’re trying to catch their breath.
- Watch out for the ‘Yes/No’ trap. If you ask, “Did you see that gap in the defense?”, you aren’t coaching; you’re just confirming what you already know. You’re looking for a nod, not a brain working. Instead, ask, “Where was the space when you made that pass?” Force them to actually locate the problem.
- Give them the silence they need. This is the hardest part for us old-timers. You ask a question, and then you have to shut your mouth. If you jump in after three seconds because the silence feels awkward, you’ve just taught them that they don’t need to think because you’ll do it for them. Let the silence sit there until someone actually has to find an answer.
- Keep it grounded in the game, not the textbook. If you start asking about “transitioning from a low block to a high press,” you’ll see their eyes glaze over faster than a frozen pitch in December. Ask them what they saw when the ball turned over. Use the language of the pitch, not the language of a coaching manual.
- Don’t use questions to lecture. I’ve seen coaches use a question as a way to smuggle in a correction—”Why did you play that ball into traffic?”—when what they really mean is “Don’t play that ball into traffic.” That’s not a question; it’s a lecture in disguise. If you know the answer and you’re just waiting for them to admit they were wrong, save your breath and just tell them.
The Essentials: What to Keep in Your Pocket
Stop being a fountain of answers; if you give them the solution before they’ve even felt the problem, they’ll never learn to think when the game gets fast and heavy.
Use closed questions to fix the immediate chaos—like “Where was your marker?”—but save the open questions for when the players have a moment to actually breathe and process.
If a question doesn’t lead to a change in how they play in the next five minutes, you’re just wasting breath and making them lose interest in the session.
Stop Being the Answer Man
Look, we’ve covered a lot of ground. We’ve moved away from the endless, soul-crushing monologues and learned that there is a massive, functional difference between asking a lad “Where was the space?” and simply barking “Move left!” If you want players who can actually think when the game gets frantic, you have to stop feeding them the answers on a silver platter. It’s about using those open-ended triggers to spark a bit of internal logic, rather than just treating them like remote-controlled cars that only move when you press a button. Remember, the goal isn’t to have a perfect, scripted session; it’s to stop the lecture and start the dialogue so they can actually process what’s happening in the mud.
At the end of the day, coaching isn’t about how much you know; it’s about how much they understand. You can have all the UEFA Pro badges in the world, but if your players are just waiting for your next instruction, you haven’t coached them—you’ve just managed them. My advice? Go to your next session, keep your mouth shut a little longer than is comfortable, and let them find the solution themselves. It might be messy, and they might get it wrong three times before they get it right, but that struggle is exactly where the real learning happens. That’s how you build footballers, not just followers.
Frequently Asked Questions
What do I actually do when a player gives me a one-word answer or just stares at me like I've asked them to solve a calculus equation?
Look, if they stare at you blankly, it’s usually because you’ve asked a question that’s too big or too abstract. You can’t ask a twelve-year-old to “evaluate the tactical transition.” They’ll just blink at you. If you get a one-word answer like “yes” or “I don’t know,” stop the session, walk over, and narrow the field. Don’t ask what they saw; ask where the space was. Give them a target, not a lecture.
How do I know if I'm actually helping them think, or if I'm just wasting precious training time with a bunch of kids who clearly don't know what they're doing?
Look at their eyes, not just their feet. If you ask a question and they immediately look at you for the answer, you’re just a human textbook and you’re wasting time. But if they pause, glance at their teammate, or actually adjust their position before the next ball rolls in—that’s the win. If they’re thinking, the game gets faster. If they’re just waiting for you to tell them where to stand, you’re just talking to yourself.
Is there a limit to this? At what point does "guided discovery" just become a way to avoid actually giving them the instructions they need to play?
Look, you’ve hit the nail on the head. There is absolutely a limit. If you spend twenty minutes asking a kid why he didn’t make the run while the other team is scoring, you aren’t “guiding discovery”—you’re wasting everyone’s time. If they’re looking at you with blank stares, they don’t need a riddle; they need a direction. Use discovery to sharpen their brains, but when the game is moving, give them the instruction. Don’t let your “method” become an excuse for indecision.
