Your Coach
This is normally where a coach pays someone to write about them in the third person, so it sounds like a CV. I'd rather you just hear it from me.
Who am I? Sports Scientist, DCU. Inter-county footballer. Captain. I've been where you are: starting underage, fighting for a place, subbed off, dropped, injured and stuck on the sideline wondering if I'd get back to where I was.
01
As An Athlete
There's one stretch that changed how I think about all of this. I was captain of my county team, I'd done the work, everyone around the panel knew it. The team sheet went up for the Ulster Final, and my name wasn't on it. Dropped, despite the effort, despite the armband.
That wasn't the only setback in that run. I've torn a hamstring mid-championship, been hauled off at half-time in front of my own clubhouse, and spent more pre-seasons than I'd like rebuilding from scratch.
Every time, the question was the same: was this bad luck, or was something actually broken in how I was training? By the third time, I stopped accepting "bad luck" as an answer. That's when I started building what became the Dominant Athlete System.
02
As A Coach
Sports Science at DCU gave me the theory. Being the athlete who did everything "right" and still got dropped gave me the real lesson: the system around me was built for players who hadn't decided yet, not for one who had.
So I stopped trying to motivate players harder. Motivation was never the gap. The gap was structure, sequencing, and proof. I built the Dominant Athlete System to close exactly that gap, for every athlete who's already putting in the work and just needs it pointed somewhere.
I've since coached 200+ athletes through it, across GAA, soccer, and rugby.
03
As A Systems Person
Every athlete I work with gets tested at week 0 and retested at week 12, same protocol, both ends. Not because numbers are everything, but because feelings lie and stopwatches don't.
I'd rather tell you honestly that something isn't working from the data than let you train for twelve weeks on a guess. That's the whole job, really: find the one thing actually capping you, remove it, then find the next one.
To summarise it: I build the system that should already exist, then I hand you the record that proves it worked.