Quoted post said:Originally Posted by skip9 [IMG]/img/forum/go_quote.gif[/IMG]
Quote: Originally Posted by CalicoCat [IMG]/img/forum/go_quote.gif[/IMG]
The good thing is that you have a good long time before your target race, so you can get in some periodized training phases and properly peak for your race. Your training volume is high which isn't necessarily good or bad, you just want to use that time wisely. I don't really like the fact that you are doing VO2 intervals in the middle of your long ride. I would like it better if you had one dedicated LSD ride per week because your intervals won't really be at the prescribed intensity in the middle of a long ride. A long ride requires a lot of fuel, and is great for training your body to utilize fuel efficiently. However, trying to make those kinds of metabolic adaptations while at the same time doing intervals, you are doing neither properly, and just breaking yourself down mentally and physically.
Take a rest day after your LSD ride. Even if you think you didn't go super hard, it can take a while for the body to recover, partly because so many calories are burned during a long ride.
I would skip the 2hr endurance rides this time of year. OK as a recovery ride in-season, but it's winter, and you are cross training, so these rides aren't doing much for you other than needlessly increasing training volume.
For your intervals, instead of doing FTP one day and VO2 the next day, I would plan training phases such that you work your VO2 system for a while and then transition to working at threshold. My training plan looks like 4weeks VO2 maintenance, 4 weeks of low cadence hill climbs (with one day per week of VO2 work), and 5 weeks of threshold, and 5 weeks of VO2 build before my first peak in April.
During the winter, 4 on-the-bike days (three interval workouts and one LSD) seems to work very well for building towards early-season fitness. I don't think there is any reason to do more than that.
I wasnt 100% on the intervals on a Long Ride but wasnt sure if it could be beneficial to do them during or not. My rest day is scheduled after my Long Ride, How i have my rides above is not in order. They are as follow;
Monday: V02
Tuesday: Upper Endurance + Tempo
Wednesday: Endurance
Thursday: FTP
Friday: Recovery
Saturday: Long
You think I Should it would it be wise to do 2 sessions of FTP (Mon & Thurs) rather than a V02 considering that is my main focus atm?
Im in Australia, so its summer here [IMG]/img/vbsmilies/smilies/smile.gif[/IMG] so i thought the extra endurance ride could only help getting some more km's in the legs while i am on holidays and it is not too strenduos on the body
Sorry, I didn't realize you are Australia. During the summer (in-season) I ride 6days pew week (two of those days are active recovery), but in the winter, I skip on the bike recovery in favor of core/strength work, and, well, life. My training days are Tues, Thurs, Sat, Sun. M/W are active recovery and Fri is off. I like having a rest day before a hard interval day, and would suggest that you try something like that too. For example, if my T/R/S schedule doesn't work for you, you can do intervals M/W/F and go long on sat and take sun off. I think this will work better than back to back endurance rides on Tues/Wed which I doubt you are getting enough benefit from to justify the time. Just ride easy on tues instead. Then, you will actually get in three real training days instead of just two, and with 6 days per week on the bike, your volume is plenty high regardless. Also, you said that you had some non-target races coming up. You will have to work these into your schedule, but since you don't have to peak for them, use them as training. mentally, it is easier for me to do two interval session and one race per week than three interval session. Racing is hard, time consuming, etc., but it is fun and a great way to break up the daily grind and monitor progress. Good luck, and have fun. . . . jeez, I am kinda jealous that you are having SUMMER and planning in-season training while it is quite the opposite in chicago . . .