Only 10 weeks to go until the Mississippi Blues Marathon. This past week was a doozy with Orangetheory Hell Week Monday through Friday (recap here!). Lots and lots of intervals, which were part of my 5K training plan, plus some good strength training. I happily took my rest day on Saturday instead of Sunday.
Unfortunately, on Saturday evening I dropped my laptop squarely on my big toe. Yikes. Based on the amount of pain, I was questioning whether it was broken, but now I’ve decided it is just badly bruised. (I’ll spare you the picture.) As runners, we are often so scared about injuring our knees or dealing with IT band pain and shin splints. But sometimes just having butterfingers is what will thwart you!
I’ll start by saying that there are millions of philosophies about race training. Here I’ll share what has worked for me, and what I am planning to do for the Mississippi Blues Marathon, but this is not the only way (or even the best way) to train for a marathon. I’d love to hear thoughts about what has worked well for other people.
In short, I like to make a rough sketch of a training plan for each marathon so that I don’t get completely off-track, and so that I can anticipate holidays, travel, and work events and prepare accordingly. Usually I just jot it down on a calendar or in a Googledoc (or now, in a blog post). The most important runs for marathon prep are the long runs, so I make sure to note what my goal long run is for each week, and then I have the option to do that run any day during the week (but usually Saturdays or Sundays). I don’t generally write the week’s non-running activities (Orangetheory, pilates (upcoming post!), barre, yoga (also upcoming post!), swimming, etc.), or my run commute, in my training plan, and while I do sometimes put in shorter runs, all of those are subject to change. Each week is different, and I vary based on my own schedule and how I’m feeling. Missing a few runs isn’t going to totally kill your training. Really. I take at least one, but usually two, rest days each week. Continue reading →