Successful dribbles reward the take-on the defence invites
Every season a Premier League dribbling leaderboard makes the rounds, and it always reads like a list of the division’s most exciting players: the wingers who beat their man, the ball-carriers who make defenders look foolish, the flair players fans pay to watch. Successful dribbles — take-ons completed, in the modern data language — feel like a pure measure of one-on-one ability, the stat that finally quantifies the thing coaching manuals struggle to teach. But the leaderboard is misleading in a specific way. A completed dribble records that a player took on a defender and got past him. It does not record whether the take-on was necessary, whether it advanced the attack, or whether the defender was ever trying to win the ball in the first place. Like most raw counting stats, successful dribbles reward volume and opportunity, and they quietly credit the player for take-ons the defence was happy to concede.
What a completed dribble actually records
A successful dribble is logged when a player in possession takes on an opponent and beats him while keeping the ball. That is the entire event. It does not note where on the pitch it happened, whether it broke a defensive line or spun harmlessly along the touchline, or whether the player then lost the ball two seconds later to the covering defender. It does not distinguish the take-on that created a clear sight of goal from the one that gained a yard of space no one needed. Beating a full-back on the byline to whip in a cross and beating a midfielder in your own half only to be crowded out are scored identically: one attempted, one completed. The number counts the act of getting past a man. It is blind to whether getting past that man did the team any good.
The success rate is a decision, not just a skill
Dribbling is usually reported two ways — total completed, and completion percentage — and both can be gamed by shot selection in the most literal sense. A player who only attempts the take-ons he is confident of will post a glittering success rate while attempting few; a player who takes on his man in difficult, high-value situations will complete a lower share while attempting many. The percentage rewards caution and the raw total rewards volume, and neither, on its own, tells you who is actually beating defenders in the moments that matter. This is the recurring trap of ratio stats in football: you can look elite by declining the hard version of the task, and the leaderboard cannot see the difference between discipline and timidity, or between ambition and recklessness.
The defence decides how many are on offer
The number of take-ons a player even gets to attempt is set largely by things outside his control. A winger in a possession-dominant side that spends the match camped in the opposition half will be fed one isolation after another against a retreating full-back; the same player in a team that sits deep and counters will get a handful of chances a game. Opponents matter too: some defences invite the dribble, jockeying and showing a man inside to funnel him into cover, content to let him “beat” the first defender into a trap. A take-on completed into a waiting second defender flatters the dribbler and suits the defence perfectly. When a stat’s raw total depends this heavily on formation, game state, and how much of the ball a team has, it is describing the system a player lives in at least as much as his feet.
Beating a man is a means, not an end
The deepest problem is that a dribble is never the point of a possession — it is one tool for advancing it, and often not the best one. The purpose is to create an advantage: a numerical overload, a clear cross, a shooting lane, a pass into a better attacker. A player who beats three men and then loses the ball has completed dribbles and accomplished nothing; a player who beats none but releases the ball early to spring a teammate into space has advanced the attack without adding to his dribble total at all. Successful dribbles count the flourish and ignore the outcome, which is why they can run high for a player whose end product is thin and stay low for a supremely effective one. The stat measures the beating of the man. The game is about what happens next. This is why the most valuable carriers are not always the ones at the top of the take-on chart: a player who draws two defenders and slips the ball before contact never completes a dribble, yet he has created exactly the overload the dribbler was chasing. The scoreboard rewards the outcome; the dribble column rewards the attempt.
Where the number genuinely helps
None of this makes dribble data useless — it makes it context. Take-on volume is a real fingerprint of role and style: a high total tells you a player is a designated one-v-one threat, a creator his team funnels the ball to in isolation, and that is worth knowing before you read anything else about him. Progressive take-ons, which capture whether a dribble actually moved the ball toward goal, are a meaningful upgrade over the raw count. And in combination with end-product numbers, dribble data helps distinguish the carrier who turns his take-ons into chances from the one who merely entertains. StatLine’s Premier League player tables carry the appearance and attacking lines — minutes, shots, goals, and assists — that let you place a player’s dribbling next to what his attacking actually produced, which is exactly the comparison the leaderboard omits.
How to read a dribbling leaderboard
Start by treating the raw total as a style marker rather than a ranking: it flags who takes defenders on, not who is best. Normalise for opportunity — take-ons per 90 and per touch beat season totals for comparing players in different systems — and read the completion rate alongside the volume so that a pristine percentage on few attempts is not mistaken for elite ability. Then anchor the whole thing to outcomes: chances created, shots and shot assists after a carry, final-third entries, and the goals-and-assists line that tells you whether beating all those defenders led anywhere. A dribbler who pairs high volume with real end product is doing his job; one who tops the take-on chart with nothing downstream is decorating the game rather than deciding it.
The honest read
Successful dribbles measure a real, watchable skill, and at the extremes the number still means something: a player who consistently beats his man in the final third is a genuine problem for defences. But the raw count is a volume-and-opportunity stat dressed as a talent ranking. It rewards the take-ons a system hands a player, it cannot tell an inviting defence from a beaten one, and it counts the flourish while ignoring whether the attack was any better for it. Read dribble data as a description of style, normalise it for how often a player gets the chance, and always follow the carry to its outcome. Beating a man is thrilling. Whether it advanced anything is the only part that decides matches.