The Case Study: Kane, McDermott and the Tottenham Blueprint
John McDermott joined Tottenham Hotspur in 2005 to head up academy coaching — the role that defines how a club thinks. His programme was a long-term, technique-focused curriculum, described by the English media as "Dutch-style" — ball mastery and 1v1 play as the foundation, physicality as a secondary criterion.
The core philosophy behind it sounds straightforward, yet it was radical: players were recruited and retained for their technical ability, not their physical attributes. Up until around the age of ten, technique was virtually the sole focus of development.
An unassuming lad from Walthamstow entered this system. McDermott's description of the 13-year-old Kane is unsparingly documented: ten per cent behind in agility, thirty per cent behind in jumping power, slow — in his words, the "runt of the litter", thirty per cent behind the group.
Why did the club keep him anyway? McDermott's answer provides the central lesson of this guide: Kane had something unmeasurable — an extraordinary mental drive to improve. He wanted to get better, and he worked harder than anyone else to make it happen.
The rest is history — but the details are what matter: Kane was not shunted aside; he was developed. Four loan spells across different leagues, years of patience when other clubs would have released him long before, and an environment that — in McDermott's words — addressed training, technique, tactics, nutrition, social, and psychological factors simultaneously, underpinned by "faith in the plan". At 21, his career took off. The slow boy had matured into a complete striker — and the academy that stood by him became a blueprint for England's wave of talent, producing players like Winks and Skipp.
The takeaway for every club: Tottenham did not spot Kane because he looked exceptional — but because their system was designed so that someone like him would not slip through the cracks.
Mechanism 1: The Relative Age Effect
To understand why late developers are lost everywhere, you need to look at two mechanisms. The first is the Relative Age Effect (RAE) — one of the most robust phenomena in talent research.
The principle: Age groups work with cut-off dates. A child born in January plays in the same age group as one born in December — yet is almost an entire year older. In adulthood, that gap means nothing. At nine years old, it represents an eighth of their entire life: a full year's head start in physical growth, coordination, and experience.
The consequence: Relatively older players appear more talented — they are taller, quicker, and more assertive in challenges. They are scouted more frequently, picked for representative squads, coached better, and given more encouragement. What began as a mere calendar advantage turns into a developmental head start that compounds over time. Consequently, the first quarters of the year are overwhelmingly overrepresented in representative and professional academy squads worldwide.
The double irony: In the long run, the tables often turn. Relatively younger players who battle through despite their physical deficit frequently develop the very tools that matter later on — technique, game intelligence, and problem-solving — precisely because they could never rely on raw physical size as a shortcut. Discarding them early means discarding your potentially best players.
Any coach can test this effect in their own squad: note down the birth months of your starting eleven. The result is almost always eye-opening — and the first step toward correcting it. Further reading: Spotting Talent in Football.
Mechanism 2: Growth and Biological Age
The second mechanism has an even bigger impact than cut-off dates: biological maturity. Children of the exact same chronological age can vary by years in their physical development — one 14-year-old might biologically be 16, while another is effectively 12.
The adolescent growth spurt as a disruptor: Around the pubertal growth spurt (in boys, usually between 13 and 15), limb levers, centre of gravity, and coordination change faster than the nervous system can adapt. The typical outcome: a temporary dip in performance — a player who was agile yesterday suddenly looks clumsy, loses duels, and trips over their own feet. Injury risk spikes alongside this.
The misinterpretation: It is precisely during this phase that crucial selection decisions are made — U15 selections, representative trials, and academy intakes. If you fail to factor in biological age, you mistake maturity for talent and a temporary growth slump for stagnation. At 13, Kane was not a poor footballer — he was biologically young.
The takeaway: Physical data in youth players is virtually meaningless without maturity context. A 30 per cent deficit in jumping power means something completely different in an early maturer compared to a boy who has not even begun his growth spurt. Modern academies estimate biological maturity (using growth velocity and maturity offset equations) and assess all physical metrics through that lens. Grassroots clubs do not need sports science labs — you simply need awareness and simple tools: measure height regularly, record growth spurts, place performance dips in biological context, and adjust training loads accordingly. Background: Athletic Development in Youth Football and Injury Prevention.
Why Clubs Systematically Discard the Wrong Players
Neither mechanism would cause harm if selection decisions accounted for them. Yet they rarely do — for understandable, but entirely avoidable reasons:
The eye is drawn to dominance. The early maturer wins games today. The late developer hints at what they might deliver in three years' time. Trials and scouting are snapshots — and snapshots naturally favour physical power.
Competition rewards the present. Coaches judged on league tables field their most physically mature players. Every league-table mindset in mini football amplifies this effect — which is precisely why governing bodies are dismantling league tables at the youngest age groups: New Game Formats in Children's Football.
Nobody tracks the discarded. Selection errors remain invisible: once you release a 13-year-old Kane, you never see him again — so the system never learns. Success among those kept seems to validate the original decision. It is classic survivorship bias within club football.
One player, one impression, one decision. Without documented developmental journeys, the latest impression dictates the verdict — and a late developer's latest impression during a growth spurt is almost always their worst.
The antidote lies squarely in Tottenham's principles.
What Tottenham Did Differently: The Five Principles
1. Technique as the selection currency. Recruitment and retention hinged on ball mastery, game understanding, and 1v1 quality — attributes that biological age barely distorts. When you select based on technical ability, you select independent of maturity — safeguarding your club from scouting's costliest mistake: mistaking athleticism for football ability. Training resources: Teaching and Learning Football Technique and Coaching 1v1 in Football.
2. The long-term plan. A development pathway spanning over a decade shifts the evaluation window: when you think in twelve-year cycles, you do not panic over an awkward fourteenth year. McDermott's phrase "faith in the plan" captures exactly that: institutionalised patience.
3. Taking the unmeasurable seriously. The decision to keep Kane came down to a quality absent from any physical testing protocol: willingness to learn. Tottenham fostered a culture that weighed this criterion against every test score — more on that below.
4. Holistic development. Training, technique, tactics, nutrition, social skills, mindset — late developers require the complete package because their journey takes longer. If you offer only football drills, you will lose them during the difficult spells. A model also seen elsewhere: Character Development in Football.
5. Managing match minutes. Kane's four loan spells were carefully curated developmental steps: genuine competitive matches at an appropriate level rather than sitting on a bench at a level too high. For grassroots clubs, this translates to flexible movement between first and second teams, across older and younger age groups, always guided by one question: "Where is he learning the most right now?" Related model: The Chelsea Academy Model.
Measuring the Unmeasurable: Willingness to Learn as a Selection Criterion
A "mental drive to improve" might sound like vague intuition — yet it is entirely observable when you know what to look for. Here are six indicators coaching teams can systematically track:
1. Response to coaching: Does the player visibly apply feedback in their next attempts — or do they repeat the same habit?
2. Behaviour following mistakes: Do they demand the next ball or hide away? Their reaction after the third misplaced pass is what counts, not the first.
3. Self-initiative: Do they stay behind after training? Do they ask questions? Do they practise at home? (Solo Practice Ideas)
4. Application when benched: How do they train during weeks when they have not been selected to start?
5. Attitude towards stronger peers: Do they seek out the best opponents in training — or stick to comfortable matchups?
6. Quality of questions: Players driven by growth ask different questions ("What can I do to improve?") compared to status-driven players ("Why is he starting ahead of me?").
The key: these indicators belong in your regular evaluation framework — alongside technical and tactical metrics. In Coach OS, mental attributes (ambition, concentration, confidence, team spirit) capture precisely this dimension; evaluated across seasons, subjective gut feeling turns into a documented trajectory. Documented trajectories are the ultimate safety net for late developers: they highlight the upward curve where a single snapshot shows only a physical deficit. Methodology: Player Evaluation in Football and Tracking Player Development.
Late Developers in Training: What They Need
Retaining players is not enough on its own — late developers require an adapted learning environment:
Technical superiority as a strategy. The pre-growth spurt years present an opportunity: unable to dominate physically, these players have both the time and incentive to excel technically and cognitively. Focus areas: ball mastery, first touch, decision-making quality, scanning — the exact toolkit that pays double dividends once physical growth catches up.
Protection under pressure, challenge in learning. In competitive matches against early maturers, late developers need roles where they can succeed (playmaker rather than target man, half-spaces rather than aerial duels). In training sessions, they need stronger peers as a benchmark.
Aligning training loads with biology. During peak growth spurts: manage training volume, regulate jumping and sprinting loads, and prioritise mobility. This prevents typical overuse injuries — and stops the frustrating cycle of injury and lost development. Fundamentals: Strength Training in Youth Football and Mobility and Flexibility.
Reassuring, open communication. The most important words a 14-year-old late developer can hear is an honest explanation: "Your body will catch up later — this is normal, well-documented, and our development plan accounts for it." When players understand what is happening to their bodies, they stay the course. Mental support: Mental Toughness in Football.
Bio-Banding and Other Tools
Professional academies have developed practical tools to tackle maturity disparities — many of which translate directly to grassroots setups:
Bio-banding: Players are grouped for specific training sessions or tournament formats according to biological rather than chronological age. Suddenly, early maturers must problem-solve against peers of equal size instead of bullying opponents; late developers can showcase their technical game without being physically overrun. The Premier League has run structured bio-banding tournaments for years. Grassroots equivalent: tailored cross-age training groups and festival days organised by size and maturity.
Tracking birth quarters: While some associations experiment with rotating cut-off dates, the crucial step for clubs is awareness: include birth quarters alongside every scouting sheet and squad list.
Playing across age groups: Allow a biologically younger 14-year-old to gain minutes with a younger age group, and move an early maturer up an age group — flexibly and based on specific learning objectives.
Development squads over selection squads: Move away from a rigid "first team versus discarded players" mindset toward fluid squads where moving between groups is standard practice and clearly communicated. Selection becomes a status check on current progress, not a permanent verdict.
The Scouting Sheet That Protects Late Developers
Selection mistakes happen on paper — which means they can be prevented on paper. A maturity-fair scouting template differs from standard sheets in four key ways:
1. Header with developmental context. Alongside name and position, note the birth month and an estimated maturity stage — before writing down a single observation. The scout must know who they are assessing: a biological 15-year-old or a biological 12-year-old in the same chronological age bracket.
2. Separate columns for "current level" and "projection". What is the player showing today — and what portion of that is independent of physical maturity (technique, perceptual scanning, decision-making, coachability)? Requiring scouts to separate these two assessments stops them from conflating the two.
3. Mandatory criteria for the unmeasurable. Response to feedback, body language after mistakes, off-the-ball work ethic — sections that remain blank if a scout only watches who scores goals and wins shoulder barges. Blank fields are an immediate flag: go back and observe again.
4. Multiple observations as a non-negotiable rule. Never make a final assessment based on a single match. The sheet should mandate at least two observations, ideally with one during a training session where attitude and learning behaviour are most visible. Complete guide: How to Become a Football Scout.
This exact template works internally, too: internal squad allocations (U13A or U13B? Trial nominations?) become vastly more equitable when filtered through this framework.
Training Mixed-Maturity Groups: A Sample Session
Every youth squad is a mixed-maturity group — the only question is whether your training session accounts for it. Here is a 90-minute U13/U15 session designed to challenge both early and late developers:
Block 1 — Technique under constraints (20 minutes). Ball mastery circuit with tiered difficulty levels: each station features a core task and an advanced option (tighter space, weaker foot, cognitive cue). Players self-select — allowing coaches to observe who actively steps out of their comfort zone. A completely maturity-neutral assessment: Coaching Ball Control.
Block 2 — 1v1 duels in matched maturity pairs (20 minutes). Pair players deliberately: physical equals against each other (agile and small vs agile and small), followed by mixed pairings with adapted constraints — early maturers may only finish with a maximum of two touches; late developers are given safe passing escape zones. Both train right at their learning edge.
Block 3 — Small-sided game with technical incentives (30 minutes). 6v6 match; goals scored following a third-man combination or a successful 1v1 dribble count double, while direct long balls over the defensive line count single. This rule negates raw physical advantage and directly rewards sustainable football habits.
Block 4 — Free play (15 minutes). Unconstrained football — honesty demands this: late developers must learn to find tactical solutions in unshielded match conditions. The coach observes and takes notes for individual player reviews.
Debrief (5 minutes). Team circle question: "Who tried something today that they haven't mastered yet?" — reinforcing willingness to learn, the defining criterion behind Kane's development.
How the Major Systems Are Responding — and What It Means for You
The late developer challenge is widely recognised, and leading football nations are tackling it in different ways: England pairs the EPPP academy system with bio-banded tournaments and extended observation phases (the system in detail). Germany is reducing early selection pressures by introducing smaller match formats and removing league tables in junior age groups (the reform in detail). Belgium gained international acclaim with its "Futures" programme, where biologically delayed talents compete in dedicated representative squads against younger opposition. Scandinavia prioritises delayed selection across the board — broad, inclusive participation well into adolescence.
The common denominator across all models: they extend the developmental window, giving players time to show their potential and decoupling selection decisions from momentary physical maturity. Every grassroots club can implement this on a local level without waiting for federations: delay hard cuts, keep squad boundaries fluid, and document progress over time. Protecting late developers is not a matter of budget — it is a matter of institutional patience.
The Parent Factor
Late development directly affects families. Parents watch other children shoot up in height while their own child waits — frequently reacting with anxiety, club transfers, or resignation. Three approaches make an immediate difference:
Education before the crisis hits. Host a short parents' evening each season covering RAE and growth spurts — using Harry Kane's story as a case study — to prepare parents before performance slumps occur.
Data instead of hollow reassurance. Saying "he's doing fine" reassures nobody. Showing a documented two-year development curve does.
The biography library. Kane is far from an isolated case — from Luka Modrić to Sven and Lars Bender, late-maturing pathways to elite football are extensively documented. Share these examples in your parent communications: they provide reassurance and build patience.
What Your Club Can Specifically Change
1. Make birth quarters visible — on every squad sheet and scouting report. What gets measured gets managed.
2. Track height and physical development — record height twice a year, note growth phases, and evaluate performance data in context.
3. Embed technique and coachability into evaluation sheets — and consistently prioritise them over short-term physical dominance.
4. Document development over time — trajectory always trumps the single snapshot.
5. Avoid final selection verdicts before age 16 — postpone release decisions during peak growth periods or provide alternative squad pathways.
6. Organise flexible match minutes — across age groups and teams, driven entirely by individual learning needs.
7. Align the club community — ensure parents, coaching staff, and club leadership share a unified, patient development philosophy.
Case Study: Two Players, One Age Group
To see how these mechanisms play out week to week, consider this typical profile found in virtually every U15 squad:
Player A, born in January, early maturer. At 13, he is a head taller than average, the quickest player on the pitch, starts every match, and earns representative call-ups. His playing style: pure pace and power solve almost every problem. The uncomfortable truth: he has barely acquired any new technical skills over the past two years — because he hasn't had to. His evaluation curve across maturity-neutral attributes is completely flat. Forecast without intervention: at 16, once the rest of the age group catches up physically, he loses his single advantage — with nothing behind it. What he needs: technical demands, bio-banded matches against physically equal peers, and tactical tasks he cannot solve with athleticism alone.
Player B, born in November, growth spurt still ahead. At 13, he is the smallest in the squad, loses physical duels, and gets overlooked at trials. His playing style: sharp first touch, scanning, finding space in tight areas — because he never had the physical option. His technical and tactical understanding curves have risen steadily for two years. Forecast without intervention: he walks away from football at 14 due to a lack of playing time and recognition. What he needs: documented progress reports as tangible proof, clear reassurance, protected game time — and a club that evaluates his developmental trajectory rather than his height.
The punchline: both players require targeted support — yet traditional systems see only one. The early maturer is praised as a standout talent (and left unchallenged), while the late developer is dismissed as a squad filler (and lost to the game). A maturity-fair system challenges Player A and protects Player B — ensuring that three years later, you have two capable footballers instead of none.
Common Mistakes
Turning late development into an identity. Constantly labelling a boy as a "late developer" creates a self-limiting identity. Keep that classification within coaching meetings and one-to-one reviews — on the training pitch, he is simply a footballer.
Confusing patience with a lack of standards. Late developers require time, but they also require challenge. Shielding them from all difficulty does not develop them — Kane was supported, but he was held to high standards.
Waiting solely for a physical spurt. Not every late developer turns into Harry Kane. The objective is not "keep everyone on the off-chance they explode", but rather "never lose a player whose technical and tactical game shines simply because their biology lags behind".
Neglecting early maturers. The other side of the coin: early maturers who rely purely on size often fail to develop core technical habits — falling away once peers level the playing field. They equally require tailored challenges (bio-banding, technical constraints).
Assessing players once a year. Biological maturity is a continuous journey, not an annual badge. Use biannual check-ins rather than definitive end-of-season verdicts.
How You Recognise Progress
- In squad statistics: The birth quarters across your squads begin to balance out. The proportion of November and December births in representative selections rises.
- In player trajectories: Players demonstrating steep development curves stay in the system — even if their current physical output sits behind their age group.
- In player stories: Developing your own "Kane" — the 17-year-old you almost released at 13 who now anchors your senior side — reshapes club culture more than any strategy document.
- In coaches' language: When sideline talk shifts from "he's just too small" to "he's biologically young — let's look at his development curve", your club has genuinely evolved.
The Late Developer Checklist
Ten questions for coaching teams and football directors:
1. Do we track the birth quarter distribution across all squads and trial nominations?
2. Do we record height and growth phases at least twice per season?
3. Do we select based on technique, game intelligence, and coachability — systematically documented rather than judged on gut feeling?
4. Does every player have a development trajectory tracked across seasons — showing their learning curve?
5. Are our squads fluid in both directions — with no irreversible cuts made before age 16?
6. Do we actively adapt training loads during rapid growth spurts?
7. Do we arrange flexible match opportunities across teams and age groups?
8. Do we conduct supportive one-to-one reviews with struggling late bloomers — addressing biology, development plans, and long-term perspective?
9. Are our parents informed — about RAE, growth slumps, and the Kane precedent?
10. Do we stretch our early maturers appropriately — preventing them from relying solely on physical dominance?
Every "yes" safeguards talent that traditional scouting would have written off. And question 4 provides the foundation for all the others: without documented development over time, the remaining nine points remain mere guesswork.
Further reading: Athletic Bilbao: Inside the Lezama Academy.
Frequently Asked Questions
Five Takeaways on the Late Developer Question
To conclude, consider the shift in perspective that underpins this entire topic: for a club, a late developer is a development case study — for the boy himself, he is simply a child who loves football and feels that he is currently coming up short. Every structure detailed in this guide exists for one specific moment: that cold Tuesday evening when that young player decides to stay and practise rather than walk away — because someone at the club believed in his long-term curve.
1. Kane's numbers are the benchmark: 30 per cent behind physically at 13 — yet world-class, because an academy system gave him time.
2. Two mechanisms distort talent scouting: the Relative Age Effect and biological maturity. Failing to account for them means cutting the wrong players.
3. Technique and coachability are maturity-neutral currencies — recruit and retain based on these qualities, not short-term size.
4. Development curves beat snapshots: Documented long-term progress is the late developer's ultimate lifeline.
5. Never make irreversible cuts during peak growth spurts — and structure match minutes around learning needs rather than squad hierarchy.
All Articles on Talent and Development
- Spotting Talent in Football
- Talent Development and Scouting
- The Golden Age of Learning
- Developing Talent Rather Than Buying: The Chelsea Model
- Character Development: The Right to Dream Model
- The English Youth Football League System
- Strength Training in Youth Football
- Mental Toughness in Football
- Tracking Player Development
Coach OS: Seeing the Curve, Not Just the Moment
Clubs lose late developers in the moment — and develop them through the long curve.
Coach OS documents that exact journey: player evaluations across 17 attributes season by season, physical and mental growth visualised over time, with full training history for context. When trials label a player "too small, too slow", the development curve reveals what is really happening — safeguarding the next Harry Kane at your club.
→ Try 30 days free: coach-os.com