At the moment, I’m in the middle of developing a readiness profile for each player using a battery of tests. It started very rudimentary but is evolving rapidly each week based on discussions with other professionals, examination of existing research on the topic, better use of our current technology and adding new high and low tech systems and processes as I learn more. Right now, I’m using a host of things to monitor physical load (I’ll get in to this in a later post). It’s necessary to not place all your eggs in one basket because single assessments may not give a complete picture and in some cases, it is logistically impossible to obtain all data for every player every day. And a single lost data point, if you’re only relying on one or two, could completely undermine what you’re trying to accomplish. So the trick is in utilizing multiple sources of information to ensure you have what you need and then putting them all together in a manner that works for you.
Mike Young
Latest posts by Mike Young (see all)
- Brilliant Hamstring Injury Observations from Dave Joyce - September 26, 2018
- Sprint exposure for speed enhancement AND injury reduction - April 4, 2018
- Variance in the Soccer Warmup - April 3, 2018
Mike,
Could you share a screenshot of what you are seeing daily, weekly, and monthly?
Thanks,
CV
Screen shot wise it’s nothing to look at because most of crunching is done across multiple pages. I’m using Pages (so I can make data accessible via iPad app while on field) and I put in data streams manually or via import from several sources (my eval of session, player evals, inclusion of extra fitness sessions, test data, game minutes, prozone data, Polar HR data, and I have modifiers for travel stress). It’s something I’m still working on to get right and bringing together multiple data streams.
Thanks,
Just trying to see what others do. It’s not easy as many of the Hardware doesn’t use API to push the data passively to a central location.
CV