The hardest part of using Runna for my Copenhagen Half Marathon wasn’t following the workouts. It was getting the plan to match what I could handle. After adjusting its settings, listening to my body and sticking with run/walk intervals, I cut more than 10 minutes from my previous half marathon time.
My first version of the plan scheduled 800-meter repeats and a progression run in week one. I wanted to get faster, but that much intensity right away felt at odds with the gradual build I expected. As a newly RRCA-certified run coach, I had pictured starting with easy miles, then adding strides or short intervals before moving into harder sessions.
I didn’t abandon the app. I went through its setup again until I found a schedule that felt more appropriate for my fitness and goals. That process taught me that a personalized plan is only as useful as the information behind it—and the runner’s willingness to adjust it.
Use the setup to set a realistic starting point
Runna asks about current fitness, weekly mileage, injury history and past races before building a program. Stephanie Kessell, an elite marathoner and Runna’s head coach, says to answer based on what you’re currently doing, rather than what you imagine you could manage. The plan can be changed later as your training progresses.
I entered three running days per week and used my second half marathon time, 2:48:54, as a reference. I’d run that race about a month before starting the app’s program. Based on my answers, Runna created a 14-week schedule and estimated a finish between 2:25 and 2:35.
That prediction came with the speedwork I’d been hoping to postpone. Retaking the questionnaire with different answers didn’t remove the initial workout. What did help was changing the plan’s training volume from “progressive” to “steady” and its difficulty from “balanced” to “comfortable.” The adjustment cut speed sessions from weekly to once every two weeks and shifted the projected finish to a range of 2:30 to 2:40. That felt like a target I could work toward.
The takeaway for runners using a plan builder is straightforward: choose settings that reflect your present routine and tolerance for training stress. A faster projected time may look appealing, but a schedule you can complete consistently is the more useful starting point.
Make the warmup part of the workout
A warmup helped me settle into a pace sooner, especially before faster sessions. Kessell says going straight from rest to hard running asks muscles to make a sharp transition, which can raise injury risk. Dynamic stretches followed by walking or light jogging offer a practical way to prepare.
Runna includes warmups, and I followed them. The moves addressed areas that tend to feel tight for me: a standing calf stretch, with one foot stepped back and the heel pressed toward the ground, and “open gates,” which brings a raised knee out to the side before lowering it.
When I cut the warmup short—or skipped it—the first couple of miles often felt like a struggle to find a rhythm. Ten minutes of preparation made it easier to settle in. The right routine will vary by runner, but the useful test is whether it helps you start the session feeling ready, rather than spending the opening miles trying to loosen up.
Read effort alongside pace targets
Runna supplies pace guidance, but the numbers don’t capture everything affecting a run. I used rate of perceived exertion, or RPE, to judge effort on a scale from one to 10, with 10 representing an all-out effort. Sleep, nutrition and weather can all change how a target pace feels; heat, humidity, wind and rain may call for a slower day.
The app can adjust pace targets for heat and time of day, but that doesn’t replace paying attention during a run. How you feel between sessions matters, too. Some soreness after a hard workout can accompany adaptation, Kessell says, while persistent fatigue and tired legs from week to week may point to a plan that needs less mileage, lower intensity or fewer running days.
Sharp increases in mileage or intensity can bring aches and pains. Kessell advises taking a break from running and seeking medical care if those symptoms develop. On the other hand, feeling recovered and repeatedly running ahead of pace targets over a couple of weeks may be a reason to consider a gradual increase.
Runna recommends adjustments if a runner falls short of—or beats—pace targets for more than three runs in a row. The runner still decides whether to accept the change. That human judgment matters: a string of fast sessions doesn’t tell the whole story if you’re also carrying fatigue, and a slower run doesn’t automatically mean your plan needs a rewrite.
Build run/walk intervals into the schedule
Runna doesn’t offer an advanced plan designed around run/walk racing, but I used the method throughout its workouts. I’d already tested different intervals and knew which patterns suited me: three minutes running followed by one minute walking on easy days, and 90 seconds running followed by 30 seconds walking on harder days.
A separate app, Simple Interval Timer, kept track of those breaks. Runna doesn’t have a built-in interval timer, so an external timer helped me follow the pattern without missing a walk break.
I chose to monitor workout targets by time. Runna then prompted me to speed up or slow down as needed to stay on pace. For runners with a time goal, Kessell recommends switching between time-based and feel-based targets to learn what the intended pace actually feels like. In the app, that setting is available under “manage plan,” where runners can change the units of measure.
Pairing a run/walk strategy with time targets gave me structure while preserving the breaks I knew I needed. The app supplied the workout framework; the timer and interval choices made that framework workable for me.
Give recovery its own plan
After race day, it’s tempting to return quickly to regular training. Runna’s postrace recovery plan gave me a way to start running again without attaching every session to a performance goal. Most of my runs lasted 30 minutes or less—enough to keep a routine without making exercise feel like another demand.
That lighter schedule helped running feel like maintenance while I recovered from the race. Rest can last a few days or several weeks, depending on the runner and the event, but a defined recovery phase makes it easier to avoid jumping straight back into a demanding build.
My experience with Runna came down to fitting the plan to my real training habits: I set a manageable starting point, warmed up, used effort as well as pace to guide decisions, and brought my own run/walk intervals to workouts. The app helped me organize a 14-week build for Copenhagen; careful adjustments helped turn it into training I could sustain—and a race that finished more than 10 minutes faster than my previous half.
