9 Replies to “#epicfailWIN: Why failures rock”

  1. My epic fail was in October on my 50 miles race. I made a number of mistakes and ended up quitting at the turnaround (25 miles). At the time I said that ultra running wasn’t in the cards for me. However, I have made some changes in my training and plan to try again in May – this time will be much better!!!

  2. Great idea, Cait! My epic fail win was the first time I ran the Blue Ridge Half Marathon (over 3600 feet in elevation change). I was just not mentally prepared for the challenge the course was going to present. But I came back the next year (2013) and bettered my time by 22 minutes. That was really saying something since they had made the course more difficult.

  3. I love this topic, Cait…very inspiring! My #epicfailWIN is pretty wussy compared to what you and many others have overcome, and I am VERY thankful that I haven’t had to get through any serious obstacles.

    Mine was making it to the starting line, and then the finish line, of my first marathon after injuring my hip flexor, glutes, and hamstring about 7 weeks out from the race. I was limited to reduced training the rest of the way…just moderate jogging and no really long runs. Talk about an irritable and depressed low-mileage runner!

    My main takeaways were that sometimes injuries happen without you necessarily doing anything wrong (or at least not realizing you were doing anything wrong), and that you can’t beat yourself up over things you can’t control. And it has made me really want to push myself out of my comfort zone for my next marathon.

    • It’s important to celebrate every important lesson learned and victory. I’m glad you’re all back healthy but I WILL argue the fact that you can’t learn from injuries in the hips and glutes. Actually my latest post kinda explains, most runners are tight there in general and that can set you up for injuries…so the takeaway is get to stretching! 😉 hehe.

  4. Pingback: My epic fail win | Turkey Runner

Leave a Reply

Your email address will not be published. Required fields are marked *

*