My first timed mile was a mess. Proper mess. I can still see it. Late afternoon. Bali heat just sitting on everything. Track cooking under the sun. And me, full of stupid confidence, taking off like I was about to make some kind of statement.
That statement lasted maybe 200 meters.
After that? Done. Not fully done, but you know that feeling when your body starts sending you very clear messages and you ignore all of them anyway. Heart thumping like it wanted out. Lungs burning. Legs turning heavy way too early. By the halfway point I was already bargaining with myself. By the end I stumbled over near the school’s chain-link fence, bent over, sucking in air like I’d just been chased.
When I stopped the watch it said 12 minutes 30 seconds.
And that hit me harder than it should have. Not because 12:30 is some terrible number. It isn’t. But because in my head I’d built this whole fantasy. I thought I’d just go out there, grit my teeth, and knock out an 8 or 9 minute mile because I used to lift, used to play sports, used to be “fit enough.” You know how that goes. A lot of ego. Not much patience. Then reality just slaps you in the mouth.
And I felt this little twinge in my right knee too. Just a small one. But enough. Enough to make me think, wow, I’m really trying to get injured on day one. Nice work.
I walked home feeling embarrassed in that dumb, private kind of way runners know well. Not dramatic movie embarrassment. Just that quiet kind. Sweat all over me. Pride dented. Looking around like, please tell me nobody saw me folded over that fence looking like I’d been steamrolled. I was a late bloomer with running and it showed. Badly.
But I’ll say this now because I couldn’t say it then: that ugly first mile mattered. A lot. That 12:30 wasn’t proof I wasn’t made for running. It was just proof I had no clue how to pace myself and no aerobic base worth talking about yet. Big difference. I didn’t know that then. I just knew I felt weak and stupid and way slower than I thought I “should” be.
And I hear versions of that story all the time now. One runner online talked about nearly collapsing after a 13-minute mile and feeling ashamed until other runners told her, basically, hey, you finished the mile. That counts. That matters. And it does. It really does.
Why Beginners Stress About Pace
After that first mile, I got weird about pace. Obsessed, honestly. And I see the same thing all the time with new runners I coach. They fixate on mile pace like it’s some final verdict. Like the watch is handing down a sentence.
I get it though. We all live inside comparison now. You open Instagram, Strava, YouTube, whatever, and it feels like everybody is out there knocking out sunrise runs at paces that make your own look embarrassing. You hear somebody throw around the line that “beginners run a 10-minute mile” and suddenly your 12:00, 13:00, 14:00 starts feeling like proof you don’t belong.
That gets in people’s heads fast.
I’ve had runners ask me, quietly, almost like they were confessing something, “Is 12 minutes bad?” Or, “Does it even count if I’m that slow?” And that stuff gets me every time because it’s such a familiar kind of pain. That fear that you’re somehow doing the sport wrong because you’re not moving quickly enough.
But that’s just nonsense. A 13-minute mile is still a mile. And if you’re moving faster than a walk, breathing hard, trying, learning, struggling a bit, yeah — you’re running. Speed doesn’t hand out permission slips.
And then there’s this other thing beginners do. They assume their first mile needs to tell them what kind of runner they are. Like there’s some correct opening number. 10:00, 9:30, something clean and respectable. So they go out there and try to force a result instead of just meeting themselves where they are.
That was me too.
The truth is there’s no magic beginner mile. None. A first mile in 9:30 doesn’t make you legit. A first mile in 13:30 doesn’t make you hopeless. It just tells you where you started that day, with that body, that fitness, that history, that weather, that mindset. That’s it.
I’ve coached a 50-year-old who was thrilled to break 14:00. I’ve coached a younger ex-soccer guy who ran 8:30 almost immediately. Both were beginners. Both were runners. Both had to build from where they were, not from where their ego wanted them to be.
A lot of this is mental, if we’re being honest. New runners are usually fighting that voice that says, You’re not really a runner. You’re pretending. Everyone can see it. Then they look at the watch, see a pace they don’t like, and the voice gets louder. It’s ugly. And it feeds on numbers.
I remember my second run after that 12:30 mile. I went out trying to “fix” it. Bad idea. I checked the GPS constantly. Every little split. Every little dip. And every time the pace looked slower than what I wanted, I got tighter. Started breathing harder. Started forcing it. Which made the run worse. Which made me more anxious. And then it spiraled.
That’s the part beginners don’t always hear enough about. The watch can make you stupid if you let it. It can turn a simple easy run into this whole emotional mess where you’re not even running anymore, you’re just arguing with your own expectations.
And a lot of beginners don’t yet understand the difference between training pace and race pace. That confusion causes so much trouble. They think every run should prove something. Every mile should be quick. Every outing should feel hard. So they basically race in training. Then they wonder why they’re cooked all the time and not improving.
Most experienced runners don’t train like that. Most of them do a lot of their running way slower than people realize. But if you’re brand new, nobody tells you that clearly enough. So you just go full ego and hope it works.
And then there’s the public shame thing. The fear that people see you running slow and judge you. I’ve heard that one over and over. “What if people think I’m pathetic?” Honestly? Most people either don’t care or they respect the effort. The one doing the harshest judging is usually the runner themselves. Always.
We call ourselves too slow long before anybody else does.
So yeah, beginners stress about pace because pace feels like identity at first. It feels like proof. But it’s really not. It’s just one number on one day in a body that hasn’t adapted yet.
And I’ll keep saying this because beginners need to hear it more, not less: you do not earn the word “runner” by hitting some pace. You earn it by showing up, by trying, by sticking around long enough to improve.
Why Beginners Run Slower (It’s Normal Physiology)
So why do beginners run a slower mile?
Not because they’re lazy. Not because they’re weak. Not because they “just don’t have it.” Usually it’s much more boring than that. It’s physiology. Basic body stuff. Your engine just isn’t built up yet. That’s all.
When I started really understanding this, it helped me calm down a lot. It made my own bad early runs feel less personal. I wasn’t failing some secret runner test. My body just wasn’t ready yet.
There are three big reasons beginners usually run slower: aerobic capacity, lactate threshold, and running economy. Fancy words, yeah, but the ideas are simple enough when you stop dressing them up.
-
Limited Aerobic Capacity (VO₂ max)
Think of VO₂ max like engine size. How much oxygen your body can actually use when you’re working hard. A beginner usually has a smaller engine. Or maybe not “small” forever, just small right now because it hasn’t been trained.
A totally untrained adult might have a VO₂ max somewhere in the mid-30s (mL/kg/min). That’s normal. An experienced distance runner might be in the 50s or 60s. Elite runners can be 70+.
So right away you can see the issue. If your engine is still pretty low, you’re going to hit your ceiling at a slower speed. That’s not drama. That’s just how the body works. You try to run faster than that engine can support, and suddenly you’re blowing up halfway through the mile and questioning all your life choices.
That was me early on. I couldn’t hold even a moderate jog for long without sounding like I was trying to inhale the whole neighborhood. Breathing got ragged fast. That’s one of the plainest signs your aerobic system just hasn’t caught up yet.
But this does get better. Pretty quickly, actually, when you’re new. A few weeks or months of regular running and that engine starts growing. Same pace, easier breathing. Same route, less panic. You don’t notice it dramatically at first. Then one day you realize, huh, that pace used to wreck me and now it just feels… okay.
That’s training working.
-
Low Lactate Threshold (LT)
This one matters a lot for beginners because it explains that awful moment when a run suddenly gets hard. Not gradually hard. Suddenly hard.
Lactate threshold is basically the point where your body starts making fatigue faster than it can manage it. Legs get heavy. Breathing gets rough. You feel that burn, that pressure, that “uh-oh” feeling. A well-trained runner can hold a pretty fast pace before getting there. A beginner might hit that point at a slow jog. Sometimes even a brisk walk uphill, if we’re being honest.
That’s not embarrassing. It’s just untrained.
I used to feel this around maybe the 5- to 10-minute mark in early runs. At first I’d feel alright. Not good exactly, but okay. Then all at once it felt like somebody turned the difficulty knob up. Breathing changed. Legs changed. Mood changed. It was that threshold smacking me.
Your body just hasn’t built the plumbing yet. Not enough capillaries. Not enough enzyme activity. Not enough efficient energy handling. So you hit that discomfort line sooner and at a slower pace. Again, normal. Annoying, but normal.
And yes, it improves. Easy running, especially, helps move that line. You get more room. More comfort. You can hold a faster pace before things start falling apart. That’s one of the big reasons beginners should stop racing every training run. You don’t move the threshold by frying yourself constantly. You move it by building.
-
Poor Running Economy (Efficiency)
This one gets overlooked all the time.
Running economy is just how much energy you waste at a given pace. Some runners are smoother. Some are not. Beginners usually waste a lot. I know I did. I ran tight. Overreached. Bounced too much. Burned fuel like an old truck pulling uphill. Every stride cost too much.
I always joke that I ran like a baby giraffe at first, but honestly that’s not even far off. Just awkward. Too much movement. Too much tension. Too much trying.
Two runners can have similar fitness and still perform differently because one just moves better and wastes less. There’s old research showing that among well-trained runners with similar VO₂ max, the runners with better economy often ran faster 10K times. That matters. A lot.
And the nice thing here is beginners improve economy almost without realizing it. You run more, and your body starts figuring things out. Your stride settles. Your stabilizers get stronger. Your timing improves. You stop wasting as much. It’s not glamorous. It’s just repetition doing its thing.
This took time for me. I didn’t wake up one day suddenly smooth and efficient. It was slower than that. A few strides that felt cleaner. A run where I noticed I wasn’t fighting myself quite as much. Then more of those. Then eventually the pace that used to feel awkward started feeling normal.
That’s economy getting better. Quietly.
So when a beginner runs a 12-minute mile, or a 13-minute mile, or even slower, that’s not some moral failure. It’s just what happens when the body is still early in the process.
The engine isn’t built yet.
The threshold is low.
The stride is inefficient.
That’s all.
And the word that matters most there is yet.
Not built yet.
Not comfortable yet.
Not efficient yet.
That’s how I look at it now, and it’s how I explain it to runners who feel ashamed of where they start. Your current pace is just a snapshot. Not a sentence. Not an identity. Not a ceiling.
I tell beginners this a lot because I needed somebody to tell me the same thing: your body isn’t bad at running — it’s just new to running. And if you keep showing up without doing something dumb, it will change. Bit by bit. Mile by mile. Pretty plain. Pretty unsexy. But very real.
Common Beginner Pacing Mistakes
Working with new runners, and honestly just thinking back to my own awkward, ego-heavy start, I keep seeing the same stuff again and again. Same mistakes. Same panic. Same weird little dramas around pace. So if you’re new and you see yourself in this, good. You’re normal. Nothing’s gone wrong. This is just beginner running doing beginner running things.
A few classic mistakes keep showing up in the coach’s notebook:
- Blasting the First 400m – This one is basically beginner law. You take off way too hard, feel amazing for about one lap, maybe less, and then the whole thing falls apart. I did it in my first mile. Kids do it in 5Ks. Grown adults do it too, just with fancier watches. You get that early rush and think, Oh, this is easy, I’ve got this. Then suddenly it’s like somebody dropped a piano on your back. Pace graph usually tells the story plain as day: first quarter mile way too hot, everything after that just survival. I had one athlete start a time trial at about 8:00 mile pace, which was completely unrealistic for where he was. Final lap? He was basically dragging himself through at something like 13:00 pace. That’s not a small fade. That’s a full implosion. The fix is boring but it works: start slower than your ego wants. Almost annoyingly slow. It should feel too easy at first. That’s the point. A mile is short, yeah, but it’s not a dash. Once I finally learned to stop trying to win the first stretch, I stopped needing those ugly mid-mile walk breaks.
- Glancing at the Watch Every 10 Seconds – I get this one too because I’ve done it. A lot. You’re excited, nervous, curious, insecure, all of it. So you keep checking the watch. Then you see a pace you don’t like and you surge. Then it swings too fast and you panic. Then you back off too much. Then you surge again. It becomes this messy little tug-of-war between your legs and your watch screen. I had a runner once who was obsessed with seeing 10:00/mile on the screen. If it drifted to 10:30, she’d push. If it showed 9:45, she’d panic that she was overdoing it. So every run turned into this frantic guessing game. No flow. No rhythm. Just stress. Finally I told her to tape over the watch for a week and just use the talk test. Could she speak? Could she breathe? Did it feel sustainable? Her runs got better almost immediately. Not magical. Just calmer. And more honest. Pace can move around because of hills, wind, bad GPS, heat, bad sleep, life stress, all kinds of stuff. If you stare at it nonstop, you’ll drive yourself nuts. I’m not anti-watch. I use one. But there’s a point where you stop running and start negotiating with numbers.
- Comparing to Friends or Internet People – This one is poison. Beginner runners do it all the time because the internet makes it way too easy. Your friend says she jogged a 27-minute 5K and suddenly your own pace feels embarrassing. Or you scroll past some 24-year-old string bean on Strava casually posting mile repeats that look impossible to you and you start wondering if you even belong here. I’ve seen beginners push way too hard trying to hang with faster friends, and I’ve seen people go the other direction and almost quit because they feel so behind. I coached a 45-year-old woman who kept comparing herself to her 25-year-old coworker. Constantly. She’d say stuff like, “I should be running 10-minute miles too.” But the coworker had years of running behind her. Different body. Different life. Different everything. We had to keep dragging her attention back to her own lane. She started around 13:00/mile, and after a few months she got down closer to 11:30 and finally started feeling proud of that. And she should have. That was her progress. That was her work. I still catch myself doing this sometimes, even now. You see some younger runner floating along and for a second you feel lesser. But that comparison game never ends well. Not once.
- Expecting Daily, Clean, Linear Improvement – A lot of beginners think progress should show up every run. Like if they’re trying hard enough, the watch should reward them immediately. So if they run a 12:00 mile one week and a 12:15 mile the next, they freak out. I’ve had runners almost in tears over stuff like that. They think they’re going backwards. But running progress doesn’t work like a staircase. It’s messier than that. Some days you’re flat. Some days you slept badly. Some days it’s hotter. Some days your legs are just carrying fatigue from the last week. I always tell people it’s more like watching the stock market than drawing a straight line in a notebook. There are little drops and bumps all over the place, but over time the direction should trend the right way if you stay consistent. When I first started adding distance, I actually got slower for a little while. That really messed with my head. I thought something was wrong. But my body was just adapting to more work. Then after a down week, I suddenly dropped a big chunk off my mile time. It all came through later. That’s running. It asks for patience over and over again, and most of us hate that.
- Ignoring External Factors — Heat, Hills, Surface – This matters way more than beginners realize. Living and running in Bali taught me that fast. Heat is not a small detail. Humidity is not a small detail. A hilly route is not a small detail. Surface matters too. Trail, road, treadmill, rough sidewalk, all different. But beginners will go run in 85°F (29°C) heat with thick humidity, crawl home a minute slower than last week, and immediately decide they’ve regressed. No. Maybe it was just a brutal morning. Heat can absolutely cost you 10 to 30 seconds per mile, sometimes more. Hills can wreck the pace too. Same with a rough surface or a windy route. I remember doing a mile on a treadmill in cool air and hitting about 10:30, then going outside into heavy heat and barely scraping together 11:30. Same body. Different conditions. At first I took it personally. Then I got smarter. Now I tell runners to always ask, what were the conditions? Was it hot? Was the route lumpy? Were you on tired legs? Context matters. A slower mile in ugly conditions doesn’t mean you’ve gone backwards. It might just mean you ran through harder stuff.
And look, for all the beginner mistakes, this is also where some of the best moments happen. Real ones. Not shiny movie moments. Little ones.
I’ll never forget one runner telling me she ran a full mile without walking for the first time. Pace didn’t matter. She was buzzing. Another guy noticed his easy pace had crept from 12:30 to 11:30 per mile over one summer without him forcing it, and he looked at me like he’d discovered fire. Those moments matter. They matter a lot. They’re easy to miss if you’re obsessed with what you haven’t done yet.
So pay attention to those wins. They’ll carry you farther than ego ever will.
Real Data from Beginner Progress (By the Numbers)
I’m a bit of a data nerd with this stuff. Not in a fancy lab-coat way. More in the slightly obsessive, scribbling-splits-in-a-notebook, checking old runs when I should probably be doing something else kind of way. I like seeing what changed. Mine, other runners’, all of it. Not because numbers tell the whole story. They don’t. But they do tell a story. Sometimes a pretty encouraging one, actually.
You do not need to track every heartbeat or build some giant spreadsheet to get better. You really don’t. But a few numbers can be useful. They can show you progress even when your brain is trying to tell you that nothing is happening.
Here are a few patterns I keep seeing when beginners start building their mile pace:
- Typical 12-Week Pace Progression: In my coaching notes, a beginner who starts around a 13:00 mile can often get down into the 11:00–11:30 range after about 3 months of steady training. Not always. But often enough that I’ve seen the pattern a lot. One runner’s log looked like this: Week 1 – 13:15 mile, Week 4 – 12:30, Week 8 – 11:50, Week 12 – 11:10. And I like that example because it looks like real life. The biggest chunk usually comes early, when the body kind of wakes up and goes, oh, this is what we’re doing now. Then the drops get smaller. Which is normal. Early gains come fast. After that, every extra second starts costing you more work. That’s just how it goes.
- Heart Rate vs Pace: This one matters more than beginners realize. I’ve seen runners start out with their heart rate in the 170+ bpm range just trying to hold 12:00/mile. After some training, that same 12:00 pace might only push them to 150 bpm. Same pace. Way less stress on the body. That’s a big deal. It means the cardiovascular system got better at its job. It means what used to feel like a fight now feels more under control. And that usually comes before the pace really starts dropping. I remember catching this in my own logs. My easy-run heart rate had dropped by about 10 beats after a couple months, and that was one of those quiet little moments where I thought, okay, something is working here, even if I don’t feel like some gazelle yet. The stopwatch doesn’t always show the first signs of progress. Sometimes it’s happening under the hood first.
- Weekly Mileage and Pace: Beginners ask this all the time — how much should I run each week? There’s no magic number. There just isn’t. But one pattern I’ve noticed is that once beginners can handle around 10–15 miles per week — so about 16–24 km, spread across a few runs — that’s often when the pace starts dropping in a more noticeable way. Not because that number is sacred. Just because that amount of running tends to be enough practice and enough stimulus for the body to start adapting more clearly. On the flip side, somebody running only 5 miles a week total might still improve, just usually slower. I noticed this in myself too. When I moved from running two days a week to four — and the extra runs were short and easy, nothing heroic — my pace got better faster. Makes sense. More reps. More time on feet. More chances for the body to figure it out. Up to a point, obviously. I usually nudge beginners toward that 10–15 mpw range as a good early sweet spot, if their body can handle it. And I always mean gradually. If you jump to that too quickly, you’re just asking for shin pain and frustration.
- Treadmill vs Outdoor Pace Example: I’ve got one in my own notes that still makes me laugh a little. One week I did a treadmill mile time trial and ran 10:30. The next week I did a mile on the track on one of those sticky, humid mornings and ran 10:58. That’s almost a 28-second difference, and it wasn’t because I’d suddenly gotten less fit in seven days. It was just environment, pacing, and the fact that outside is outside. This is why I always tell people: if you’re testing progress, try to be somewhat consistent about where and how you test it. Or at least don’t freak out if different settings give different numbers. Neither result was fake. Neither was “wrong.” They were just different. I eventually liked using the track more because it felt more honest to me. Maybe pride had something to do with that too. But on a hot day, I still had to remind myself not to turn one slower time into some personal drama.
- Heat Adjustment: Speaking of heat, I’ve got a rough rule from years of looking at my own training and other people’s. For every 5°F above about 60°F — or about 3°C above 15°C — I expect something like a 20-second slowdown per mile. Not exact. But close enough to be useful. So if you’re out there in 90°F (32°C) heat, that can easily make your mile 1 to 1.5 minutes slower than in cool weather. I had one beginner who was really discouraged by a 12:45 mile in the middle of summer. Same runner, cooler weather in late September, and she ran 12:00 flat with no giant change in training. Some of that was fitness, sure. But a lot of that was just not running inside an oven. This stuff matters. Context matters. You’re not a machine. If you look at your numbers without looking at the weather, you’ll end up being way harder on yourself than you need to be.
All these numbers are useful. But they’re still just clues.
Your body isn’t a calculator. It’s not some neat little formula where input equals output on schedule. It’s messy. It adapts when it’s ready. Sometimes quickly, sometimes slower than you want. The data just helps show the trend. You’ll usually get faster with training. Early gains are often quicker. Then things slow down a bit. Conditions matter. Heart rate might improve before pace does. Mileage matters, but only if you can recover from it.
That’s really it.
And honestly, one of my favorite things is going back through old logs and seeing proof that the work did something. A lower heart rate here. A minute off a mile there. A run that used to wreck me now showing up as “easy” in the notes. That stuff matters. It’s not flashy, but it matters.
Final Coaching Takeaway
Your pace right now is not your future. It’s just your starting point.
That matters. I really believe that. Because too many beginners look at one slow mile and decide it means something permanent. It doesn’t. It just means this is where you started.
I started in the 12+ minute range myself. And I got quicker. Not because I found some secret. Just because I kept showing up and stopped trying to prove everything in one run.
And honestly, that’s what I’d tell you too.
Don’t chase some heroic mile on day one. Don’t chase some internet-approved pace. Chase consistency. Chase the habit. Chase the small wins that feel almost too small to count — three runs in a week, one less walk break, breathing a little easier, recovering a little faster.
That’s the real stuff.
That’s what adds up.
One day you’ll look down at your watch and see a pace that used to feel impossible, and it’ll almost surprise you. Not because you forced it. Because you earned it slowly.
So be proud of whatever your pace is right now. 9-minute mile. 12-minute mile. 15-minute mile. Doesn’t matter. You ran it. That counts.
You’re a runner the second you start doing the work. Speed just comes later.
So lace up. Start where you are. Keep going.
And yeah — maybe one day you’ll breeze past me on the road and give me that little runner nod. I’d like that.