So I’m 6 months on my new position with the Whitecaps and while I’d love to say we’re using one of the fancy player monitoring systems like Smartabase, TopSportsLab or Kinetic Athlete to monitor our players physical readiness, the reality is that, for a variety of reasons we don’t yet have any of those options in place. At about my 2nd month here, I realized that it might be a while to have something to monitor training load and player fatigue longitudinally so I decided to just make my own ‘system.’ As they say, if you want something done, sometimes it’s best to do it yourself. What started as just a spreadsheet to manage the various data streams I was moniroting evolved next in to a thought exercise and then in to something a little more advanced that actually returns shockingly acceptable and reliable information on the player’s physical readiness. Over the next couple posts, I’ll detail what I was trying to accomplish and how I’ve gone about doing it to come up with a system (admittedly imperfect) that at the very least has forced me to put in to action and test the thought processes I would use with with a more expensive and flashy system.
Starting off, I had a couple goals:
- Manage multiple data streams
- Somehow make a composite of those data streams
- Translate that composite data in to meaningful information with day-to-day reliability on the reflection of a player’s physical readiness
- Visualize data to better see trends
Each one of these points has several sub-points. In my next post I’ll address the data streams that I’m looking at (or want to look at).
Latest posts by Mike Young (see all)
- Sample Off-Season Training Session with Collegiate Player - January 29, 2018
- In-Season Strength Session with NCFC - January 24, 2018
- Rett Larson on Volume - January 18, 2018