The Constraints-Led Approach, with Ben Bell
I've referenced Ben Bell and his work on the Constraints-Led Approach across a few episodes now. This time I sat down with him properly to dig into it — what constraints actually are, why coaches should be using them, and what a training environment built around this approach is supposed to look like.
There's a lot in this conversation. Here are the key points.
What constraints are — and how they affect the game
A constraint, in the simplest terms, is anything that shapes or limits behaviour in the game environment. That sounds abstract, so here's a concrete version: if you play a small-sided game where the team that scores from a combination play gets two goals instead of one, you've just created a constraint. You haven't told anyone to combine. You haven't stopped the game to explain why combining is important. You've just made it worth more — and the game will start producing combinations, because the players will figure out that combinations are the path to success.
That's the power of a constraint. It changes what players attend to, what they try, what they risk. And it does it through the game itself rather than through instruction.
Constraints come in three broad forms. Task constraints — things like rules, field size, goal placement, and scoring systems — are the ones coaches have most direct control over. Environmental constraints include the surface, the space, the number of players. Individual constraints relate to the player themselves — their physical attributes, their skill level, their role in the game. All three interact constantly, and all three can be manipulated.
Why we use them
The honest answer: because telling players what to do doesn't work as well as most coaches think.
When you stop a session and explain that the midfielder should have checked away before receiving the ball, you're giving a player information they have to hold, process, and try to apply the next time a similar situation arises. By which point they've lost the emotional and physical context that made the moment meaningful. The information lands as theory rather than experience.
A well-designed constraint creates the situation again and again, at game speed, with real consequences. The player doesn't have to remember the instruction — the game keeps presenting the question until they find an answer that works. That answer, discovered through play, is far more likely to stick.
There's also a flow argument. Constraints allow the game to keep running. The coach can observe, adjust the constraint, and coach individuals in the flow rather than stopping everything for a group explanation. The session stays alive. Players stay engaged.
What we don't see when we use them
This is the part of Ben's thinking that I find most interesting — and most honest. And it's the part that sparked a conversation on Twitter recently that I wasn't expecting.
I shared a constraints study that looked at what happens when coaches deliberately manipulate the game environment. The tweet landed at nearly 19,000 views — which told me this struck a nerve. The reason, I think, is that the study surfaced something coaches know intuitively but rarely talk about: constraints don't only produce the outcomes you designed them for.
When you design a constraint, you design it with a specific outcome in mind. You want pressing. You want combinations. You want the wide players to stay wide. But players are creative, and the game is complex, and they will find solutions you didn't anticipate.
Two common examples. Add a two-touch limit to a small-sided game and players will move the ball quicker, find angles, support each other — exactly what you wanted. But they'll also stop dribbling. Stop trying to beat players. The freedom to take someone on disappears, because the constraint makes it the wrong choice every time. You got quicker passing. You lost individual bravery on the ball. That's the unintended consequence.
Goals are the same. Put two cones down as a goal, no goalkeeper, and players will shoot with precision — carefully, accurately, trying to thread it through the gap rather than blast it. No arguments about whether it went in. Great for accuracy under no pressure. But put a full-size goal and a goalkeeper in, and suddenly you get match-replicating finishing — proper technique, the decision about where to place it, the psychological challenge of beating a real keeper. Two different goals. Two completely different behaviors. Both constraints. Completely different games.
The constraint you set for the attacking midfielder has consequences for the center back. The rule that rewards playing through the lines changes how the goalkeeper distributes. The small-sided game you designed to create pressing situations is also, without you realizing it, shaping how the team defends as a unit. You only see what you're looking for. The game is producing a lot more.
This isn't an argument against constraints. It's an argument for staying curious — and for not assuming that what you designed is all that's happening. The unintended consequences are often where the most interesting learning takes place. Watch the whole field, not just the area you're coaching. You'll see things that surprise you.
Constraints and challenges for individuals
One of the most useful applications of the constraints approach is at the individual level. Rather than applying a rule to the whole game, you give a single player a personal challenge within the game.
This connects directly to the stop-and-freeze conversation — instead of pulling the whole group out of a 9v9 to address two midfielders who made the same run, you approach one of them quietly while the game is live. "Every time the ball goes to the striker, I want you to go away from the ball, not towards it." That's an individual constraint. The game continues. The player has a specific problem to solve. You can observe whether the constraint is working and adjust without disrupting anyone else.
At the individual level, constraints also link naturally to positional profiles and IDPs. If a player's development priority is receiving under pressure, you design a constraint that creates that situation repeatedly for them — without the rest of the group even knowing there's a separate challenge in play.
What a CLA training environment actually looks like
Ben is clear on this, and I think it's worth saying plainly: a constraints-led environment is not a chaotic one. It's a deliberately designed one.
The coach comes in with a clear sense of what they want to work on. They design a game that will organically produce that situation. They set it up, let it run, observe what happens, and adjust the constraint rather than stopping the game. More pressure on the defenders — reduce the playing area. Players not switching the ball — add a bonus goal for playing through a central gate. The intervention is in the design, not in constant coaching stoppages.
What it doesn't look like is a series of drills that build toward a scrimmage. It doesn't look like a warm-up, then a technical practice, then a small-sided game, then a bigger game. The game is the vehicle from the start. Everything is connected. The constraint is the coach's tool, not the instruction.
If you want to go deeper on all of this, Ben's book is the place to start. One of the clearest, most practical coaching reads I've come across.
Listen to the full episode: Ep. 48 — The Constraints-Led Approach with Ben Bell
@LeeDunneSoccer