A little context on why I’m obsessed with crafting and developing functionally technical, adaptable, and portable players.
When I say portable, I mean players who can walk into any environment and function for any coach, in any country, within any system. They don’t need to be re-taught how to play. They don’t shrink or panic when the structure changes. They don’t depend on a specific role to survive.
Most coaches I’ve met over the years have moments that force them to confront their own thinking. I wanted to share one that reframed mine.
The video is my oldest son at 7 years old. About a year before that he asked me to teach him the rainbow flick. I told him no as I didn’t think it had any real application. I thought I was being practical.
Fast forward to the Manchester City Cup in San Diego, his first 7v7 tournament. I’m coaching on the sideline and from kick-off he does this.
That moment bothered me in the best way. He exposed a blind spot in my framework. What fascinated me wasn’t whether the rainbow solved some immediate problem. It was the thought process: why that skill, why then? He thought he could, so he did. Thought through to execution in real time. How do we improve that connection?
If I could be that wrong about something so simple (7 year old curiosity), what else was I filtering out without realizing it? What parts of his growth was I suppressing because they didn’t fit my definition of “useful?”
Once you understand how neural networks form, how repetition and exploration physically wire the brain, you realize every constraint you impose has real consequences. Every “no” shapes the architecture. That rainbow wasn’t about a trick. It was about whether I was limiting the expansion of his technical vocabulary before it even had a chance to form.
This changed how I evaluated everything. And I’m thankful it didn’t stop there. There were other moments, with Hudson, with Hollis, and with the other players I’ve been lucky enough to train. Those moments matter because they’re not about my kids. They’re proof of concept.
They are the closest thing I have to a controlled environment. I control the inputs, the repetition density, the progression, the constraints. So when something translates under pressure, in unfamiliar environments, against different opposition, that’s real information.
That’s why, from time to time, I’ll share clips of my boys. Not to showcase them, but to demonstrate the progression from proof of concept to proof of work. To show what happens when coordination depth, bilateral fluency, repetition density, and technical range are prioritized before you layer on structure.
My mission is to craft and develop functionally technical, adaptable, and portable players. I’m obsessed with technical development. A lot of what I discuss and do is testing the theory in real time and doing my best to grow every day.