The Missing Link in Dutch Basketball: Connecting Player Development, Coach Development and the Game

What if one of the biggest problems in Dutch basketball is not a shortage of talent, knowledge or passionate coaches — but the fact that too many development decisions are being made without a clear connection to the players, the game or a club-wide plan?

Over the past week, I visited several clubs as they began their season training. I saw enthusiastic coaches, motivated players and a genuine desire to create better learning environments.

I also saw many coaches experimenting with alternative ways of getting players to move.

That ambition is positive.

But in several cases, it was not clear why a particular exercise or drill had been selected, what problem it was intended to solve or how it connected to the development needs of that specific player group.

Some drills appeared to have been taken directly from YouTube or social media. Others seemed to be used because they looked modern, creative or different from traditional basketball exercises.

The issue is not that coaches use YouTube, social media or new ideas.

The issue is what happens when a drill is selected before the learning problem has been identified.

A movement may look innovative while still being irrelevant to the players in front of you.

A practice may be energetic while developing the wrong habits.

A drill may be technically impressive while having little connection to the decisions players must make in games.

And if exercises are not connected to a clear player-development plan, coaches may unintentionally reinforce incorrect principles of play, inefficient movement strategies or behaviours that later become difficult to change.

That is not necessarily a coaching problem.

It is a development-system problem.

The question is not whether a drill looks good

We talk a lot about player development.

We talk about coach education.

We talk about talent identification, national teams, academies, breedtesport, selection teams, individual trainers and performance programmes.

But we talk far less about the system connecting all of them.

And that may be where one of the biggest opportunities for Dutch basketball lies.

I am not suggesting that every club in the Netherlands works the same way, nor that good development is absent. There are excellent coaches, programmes and basketball minds throughout the country.

The question is different:

How consistently are player development, coach development, technical direction and what actually happens in games connected to one another?

Because when they are not connected, development becomes dependent on chance.

A player's development can become heavily influenced by which coach he or she happens to have that season.

A coach may attend clinics, obtain licences and collect drills without receiving meaningful support with the actual problems occurring inside their own team.

An individual trainer may develop a player's moves without knowing what that player's team asks them to recognise and execute.

A Technical Committee may establish a basketball philosophy without having a mechanism that consistently turns that philosophy into daily learning environments.

And a coach may see a drill online, copy it into practice and assume that movement alone equals development.

It does not.

Before selecting an exercise, coaches should be able to answer:

What are we trying to develop?

Why does this matter for these players?

What information should they perceive?

What decision should they make?

What movement solution should emerge?

How will we know whether it transferred to the game?

Without those questions, practice can become a collection of disconnected activities rather than a coherent learning environment.

And when the player changes teams?

Much of the information disappears.

That is not necessarily a coaching problem.

It is a development-system problem.

A club-wide development model I have been working on starts from exactly this issue: development should not depend solely on the team a player currently belongs to, the individual coach available that season, or whether that coach has enough time and knowledge to solve every development challenge alone. The proposed alternative is a light development layer connecting coaches, players, technical leadership, feedback and progression.

We also need to talk about what players are actually being taught

Basketball has evolved enormously.

Our understanding of motor learning and skill acquisition has evolved.

Analytics have evolved.

Sports psychology has evolved.

Film and technology have evolved.

Yet many training environments can still look remarkably similar to those from several decades ago.

Players standing in lines.

Cone dribbling without a defender.

Predetermined finishes.

Five repetitions from exactly the same spot.

Offense running 5-on-0.

A coach demonstrating the "correct" movement and players attempting to reproduce it.

Then perhaps fifteen minutes of live basketball at the end.

More recently, some coaches have started moving in the opposite direction. They introduce unusual movement patterns, reactive exercises, coordination challenges or drills inspired by online content.

That can be useful.

But novelty is not the same as relevance.

A drill does not become developmentally valuable simply because it is unfamiliar, complex or visually appealing. The exercise still needs to connect to the player, the task and the game.

The intentions behind these practices are usually good.

But intention and learning are not the same thing.

Contemporary basketball skill-acquisition literature increasingly challenges the idea that skill is simply a catalogue of techniques that can be learned in isolation and later inserted into a game. Transforming Basketball, for example, highlights the disconnect between closed player-development environments and the information players actually encounter within team basketball, arguing that recycled drills and rehearsed moves frequently fail to address the specific problems players must solve in competition.

The same source raises an important coaching-development issue: basketball education often places enormous attention on what to coach — drills, offenses, defences and systems — while considerably less attention is given to how learning actually occurs, how practices should be designed and how coaches can respond to problems emerging from their own players.

That distinction matters.

Because basketball does not ask a player:

"Can you reproduce the movement your coach demonstrated?"

Basketball asks:

What do you see?

What is changing?

Where is the advantage?

What does the defender give you?

Where is the help coming from?

Can you decide quickly enough?

And can you adapt the movement to make that decision work?

That is a very different definition of skill.

Movement is not automatically development

As a Movement Sciences expert and a practitioner of the Constraint-Led Approach and Differential Learning, with more than a decade of experience in this field, I am not against movement exploration.

In fact, movement variability, adaptability and problem-solving are essential parts of long-term development.

But movement must still be connected to purpose.

Players should not simply be made to move in unusual ways because an exercise is trending online. They should be exposed to movement problems that help them become more adaptable, more perceptive and more effective in the situations basketball actually creates.

There is a difference between:

Making players move differently

and:

Helping players discover better movement solutions for meaningful basketball problems.

That difference is where expertise matters.

Poorly designed movement tasks can overload players unnecessarily.

They can create confusion without a clear learning objective.

They can reinforce inefficient coordination.

They can place demands on bodies that are not prepared for them.

And they can establish incorrect principles of play that later appear as technical, tactical or physical limitations.

The risk is not only that players fail to improve.

The risk is that they improve in the wrong direction.

This is why clubs need movement and learning expertise in-house — not as an external add-on that appears occasionally, but as part of the way player development and coach development are designed.

The objective is not to remove coaches' autonomy.

It is to help coaches understand what they are asking players to learn, how the task influences behaviour and whether the movement solutions being encouraged are appropriate for the age, level, context and development plan of the group.

Fundamentals are not disappearing

Whenever contemporary skill acquisition, the Constraint-Led Approach or representative learning is discussed, one misunderstanding appears quickly:

"So fundamentals don't matter anymore?"

They absolutely matter.

But perhaps we need to redefine what a fundamental actually is.

A technically beautiful crossover that cannot create separation is not yet functional skill.

A perfect shooting motion that collapses when the catch is imperfect is incomplete.

A player who can execute a passing drill but cannot recognise the help defender is not yet an effective passer.

A player who can perform a movement pattern in isolation but cannot adapt it to pressure, space, timing or defensive positioning has not yet developed a reliable game skill.

Technique matters.

But technique and decision-making should increasingly develop together.

One of the principles within the development model is therefore:

Train the game — not only the move.

Players repeatedly need to reconnect skill to defenders, teammates, space, timing, information and consequences. Practice may occasionally look less tidy, yet the real test is whether improved behaviour eventually appears during competition.

That does not mean eliminating repetition, direct instruction or technical work.

It means understanding what each tool is for.

A coach may use repetition to stabilise a movement.

A constraint may encourage a player to search for a different solution.

Differential Learning may create variability.

Film may clarify the information that matters.

Small-sided games may increase decision density.

Explicit instruction may help players understand a tactical principle.

CLA, Differential Learning, representative practice, film, repetition and explicit instruction do not need to become competing religions.

They are tools.

The coach's job is to select the tool that best solves the learning problem while continually reconnecting training to game behaviour.

This is where coach development and player development collide

We often organise the two separately.

There is a player-development programme.

And somewhere else there is a coach-development programme.

But separating them creates an obvious problem.

Player development without coach development becomes dependent on individual coaches.

If a player receives excellent developmental work outside the team environment but returns to a completely different learning environment three times per week, the connection becomes weak.

Conversely:

Coach development without player-development problems can become a collection of clinics.

A coach hears five new drills.

A new defensive concept.

A new offensive action.

A new presentation.

Interesting information — but what problem are we actually solving?

The Player & Coach Development model therefore combines the two:

Technical direction → Coach development → Player development → Game performance → Feedback → Next design decision.

That final arrow may be the most important one.

Feedback must return to practice design.

Games should tell us something.

Film should tell us something.

Player behaviour should tell us something.

Then the training environment changes.

Instead of coaching being:

plan → practice → game → repeat

it becomes:

observe → identify → design → test → review → redesign.

That is a learning system.

Not simply a basketball schedule.

Imagine that connection inside a club

A U14 coach notices a player who constantly misses weak-side information.

That should not simply become:

"You need better court vision."

The coach and development support identify the actual problem.

What information is the player missing?

When?

Why?

A practice environment is designed to expose the player repeatedly to that situation.

Perhaps space changes.

Perhaps the numbers change.

Perhaps scoring rewards the desired behaviour.

Perhaps a defender starts from a different position.

Film is used to help the player recognise the cue.

Six weeks later, the question is not:

"Did the player look good in the drill?"

It is:

Did the behaviour change in games?

The Master Plan formalises this through a simple cycle:

Identify → Diagnose → Plan → Develop → Review → Progress → Reconnect.

Importantly, the development information then goes back to the player's normal coach and environment instead of existing in a separate training silo.

That same philosophy applies to coaches.

A coach does not necessarily need another classroom lecture.

Perhaps they need someone to watch twenty minutes of practice around one specific question.

Why was this drill selected?

What behaviour was it intended to create?

What did the players actually perceive?

What decisions did they make?

Did the exercise resemble the demands of the game?

Then:

Support → Co-design → Test → Reflect → Share.

The objective is not to inspect coaches.

It is to help coaches solve their own basketball problems more effectively. The Master Plan deliberately distinguishes this from evaluation or control and argues that development support only works when coaches experience it as useful rather than as another authority standing above them.

One better coach may develop fifteen better players

This is why coach development may actually be the most scalable form of player development available to a club.

A good individual trainer might influence five players during an hour.

A stronger team coach influences ten, twelve or fifteen players several times every week.

Improve the coach's ability to design environments, ask better questions, recognise learning problems and connect training to game behaviour, and the impact multiplies.

This also means helping coaches move beyond drill collection.

The question is not how many exercises a coach knows.

The question is whether the coach can select, adapt and sequence tasks according to the needs of the players in front of them.

A drill from YouTube may be useful.

A drill from social media may be useful.

A drill from a professional club may be useful.

But none of those sources know your players, your season phase, your competition level, your injury history, your tactical principles or your development priorities.

The coach must do that work.

The Master Plan describes coach development precisely this way: newer grassroots coaches may need help with organisation, activity, small-sided games, age-appropriate feedback and keeping players engaged, while experienced performance coaches may need deeper collaboration around decision density, individualisation, film-to-court transfer, role-specific development and pressure design.

Same development philosophy.

Different support.

That matters because coach development should not mean making every coach identical.

There should be no mandatory X type offense.

No CLA offense.

No national "correct" practice.

No identical drill catalogue.

Coach personality and tactical autonomy remain important.

What can become shared are development principles and language.

For example:

READ → DECIDE → ADAPT → EXECUTE.

Or from a team perspective:

READ → CREATE → CONNECT → FINISH → RESET.

A shared language allows a U14 coach, U18 coach, player developer and senior coach to discuss the same basketball problem without requiring them to run identical systems.

Selection is not development

There is also a cultural distinction worth making.

Selection answers:

Who is ready today?

Development asks:

Who could become ready tomorrow?

Those are not the same question.

A player can fail to make the first team at 14 and become an excellent player at 18.

A physically dominant U14 player may stop progressing.

A late maturer may suddenly accelerate.

A player may need another role.

Another coach.

Another developmental problem.

Another two years.

Selection is a snapshot.

Development is a moving picture.

A functioning development system therefore needs ways to continue following certain players even when they are not currently among the strongest performers.

Not to promise them anything.

Not to create another ranking.

Simply to make sure potential does not disappear because one selection decision ended the conversation.

That principle is embedded throughout the Player & Coach Development Master Plan: pathways should remain open, progression should be periodically reviewed, and development should reconnect players to the next appropriate challenge rather than permanently defining them through their current team.

The real change may be organisational rather than methodological

This is why I believe the discussion in Dutch basketball needs to move beyond:

Traditional training versus CLA.

Skills trainers versus team coaches.

Old school versus new school.

Conventional drills versus social-media drills.

Those arguments are too small.

The larger question is organisational.

Can clubs create environments where information actually travels?

Where the Technical Committee knows what coaches are experiencing.

Where coaches can ask for help without feeling evaluated.

Where player developers understand the team context.

Where movement expertise informs practice design.

Where film informs training.

Where games inform the next practice.

Where grassroots and performance basketball are connected rather than operating as different worlds.

Where late developers remain visible.

Where experienced coaches can transfer knowledge downward.

And where young coaches do not have to rediscover the entire profession by themselves.

The long-term objective should not be to create dependence on one development director, trainer or methodology.

Quite the opposite.

The development knowledge should eventually belong to the club.

The Master Plan describes the desired end state as a club where coaches can independently design more representative and adaptable practices, players understand what they are developing and why, pathways remain visible, learning moves between grassroots and performance levels, and knowledge stays inside the organisation even when individual coaches leave.

That is also how clubs reduce preventable risk.

When movement tasks, training loads and principles of play are designed without sufficient expertise, the consequences may not be visible immediately. Sometimes they appear as recurring injuries. Sometimes as poor movement habits. Sometimes as players who can perform exercises but cannot solve game problems. Sometimes as tactical behaviours that become deeply ingrained before anyone questions where they came from.

Clubs do not need more content.

They need better interpretation.

They need people who can help coaches distinguish between what looks good and what develops the right thing.

Perhaps this is the conversation Dutch basketball needs

We have many passionate volunteers.

We have increasingly ambitious young players.

We have knowledgeable coaches.

We have private trainers.

We have national programmes.

We have clubs with decades of history.

The pieces exist.

But having the pieces is not the same as having a system.

And perhaps the next evolution of player development in the Netherlands will not come from discovering another drill, another offensive system or another basketball guru.

Perhaps it will come from connecting what we already have much more intelligently.

Connecting technical direction to coaches.

Connecting coaches to player development.

Connecting movement expertise to practice design.

Connecting development to game behaviour.

Connecting games back to practice.

Connecting grassroots to performance basketball.

Connecting experienced coaches to developing coaches.

Connecting online inspiration to professional interpretation.

And creating learning environments where the player is not simply taught what movement to reproduce, but becomes increasingly capable of seeing, deciding, adapting and executing.

The question I would like to put to coaches, technical committees, player developers, players and basketball liefhebbers across the Netherlands is therefore simple:

If we designed our basketball clubs around development rather than only teams and competition schedules, what would we do differently?

Would we select drills because they are popular, or because they solve a clearly identified problem?

Would we ask players to move differently without knowing why, or would we design movement challenges that connect to the demands of the game?

Would we wait for injuries, stagnation or incorrect principles of play to reveal weaknesses, or would we bring the necessary expertise into the club before those problems become established?

Because ultimately, the scoreboard tells us who won today.

A development system determines who we might become tomorrow.

Identify. Develop. Connect. Share. Let the game show the result.