“Unproductive”? WTF.
What your watch actually means, and how to get to Productive.
Your watch compares three signals over several weeks: your recent load, your estimated VO2max and, on recent models, your HRV status. Unproductive means your load is fine but your fitness estimate is sliding, often because you're not recovering; Maintaining means you're training at your usual level, so nothing moves. In my data, Productive shows up when I train a bit more than my usual and my VO2max estimate climbs.
Km 31, Amsterdam
October 2021, Amsterdam marathon. At km 31 my legs stop following and my heart is racing. My pace drops from 6:30 to nearly 8:00 per km. I cross the line really sad about my race, and I look at my watch. Training Status: Unproductive.
WTF? After months of getting up early to train?
Five years and a lot of data later, I’ve learned two things. That label had little to do with the race itself. And the label that frustrates me most isn’t Unproductive. It’s Maintaining: you train regularly, you feel good, and your watch keeps telling you nothing’s moving. So let’s decode all of it, with my own numbers.
Your watch isn’t judging you, it’s reading three signals
The first signal is your load. On my Forerunner 955 it’s called acute load: a weighted sum of your effort (EPOC) over the last several days.1 My old 945 used a plain 7-day sum.2 Either way, the watch checks it against a range built from your own history.
The second signal is your fitness, meaning your estimated VO2max. The watch only computes it on outdoor runs with GPS and heart rate, ideally with about 15 minutes above 70% of your max HR.3 It’s an estimate, not a lab test.
The third signal is your recovery, through HRV status. The watch measures your heart rate variability while you sleep4 and compares a seven-day average with your own baseline: balanced, unbalanced, low or poor.5 Training Status reads all three signals over an extended period.6 And on watches with HRV status, it doesn’t even need a fresh VO2max estimate anymore.7 So yes, your nights count too.
Now the definition that makes everyone go WTF. Unproductive, word for word: “Your training load is at a good level, but your fitness is decreasing.”6
Read it twice. Your load is fine. What’s going down is the VO2max estimate. Garmin’s own blog says it’s not necessarily because you trained too much, and points you to nutrition, daily stress and sleep.4
| Label | Load | Fitness |
|---|---|---|
| Productive | right level | improving |
| Maintaining | enough to hold | holding |
| Unproductive | at a good level | decreasing |
| Strained | can be unusually high | held back, poor recovery the likely cause |
| Detraining | much less than usual, a week or more | taking a hit |
How I read the labels, paraphrased from Garmin support.7 The manual gives the definitions, not the formula.
Nerd note. On my 955, the “good range” for acute load is always 0.8 to 1.5 times my chronic load (the 4-week one): 170 snapshots out of 170 in my Garmin Connect data. I haven’t found Garmin publishing that ratio, so take it as what my account shows, not a rule.
So here’s your WTF moment, decoded. You come back from a run that felt great. That run fed your load, fine. But if it also produced a VO2max estimate a bit lower than the last ones, the fitness curve bends down. The label follows the curve, not how you felt.
Still true on today’s watches?
Yes. My numbers come from a Forerunner 945 (2021) and my Forerunner 955 (since March 2024), but the label hasn’t gone anywhere. The Forerunner 970 manual lists the same nine statuses, Unproductive included, built on the same inputs: VO2max, acute load and HRV status.8
Garmin’s support page lists Training Status on current models, from the Forerunner 70 and 170 launched in May 20269 to the fēnix 9 series.7 DC Rainmaker’s fēnix 9 review, published 18 September 2026, notes that Training Status hasn’t changed since the fēnix 8, apart from indoor rowing now counting.10
One difference to keep in mind: my Amsterdam case ran on the older system, a plain 7-day load and no HRV status. Same logic though, load against VO2max trend.
Maintaining, the real frustration
Unproductive stings, but it’s rare. On my 955, I haven’t seen it once in 130 weekly snapshots. The label I actually live with is Maintaining.
| On my 955, since March 2024 | Productive weeks | Maintaining weeks |
|---|---|---|
| Weekly snapshots | 49 | 54 |
| Load ratio (acute / chronic), median | 1.1 | 0.9 |
| Weeks with a ratio of 1 or more | 71% | 35% |
| VO2max estimate vs 4 weeks before, median | +0.5 | −0.3 |
| Weeks where the estimate went up | 80% | 39% |
That’s the frustrating part, decoded. Training regularly at your usual level is exactly what Maintaining describes: enough load to hold your fitness, not to move it. Garmin’s own advice is to add variety or volume.7
So how do you get to Productive?
In my data, two things line up. My load ratio sits a bit above 1, meaning I’m doing slightly more than my recent average. And my VO2max estimate climbs. That’s also why my current rule works for me: stay between 1 and 1.3.
The third signal is the guardrail. My HRV status was balanced on 683 of the 856 days since the 955 started measuring it, and just as often in Productive weeks (40 of 47) as in Maintaining ones (41 of 50). Where it spoke up was at the edge: both of my Strained snapshots came with a Low HRV status.
Which brings me to a line I highlighted in an article by Barth (Extraterrien): training is only the stimulus, recovery is what creates progress.11 Push a little more than usual, then give your body the nights it needs to turn that into fitness.
One caveat. This is one runner, and part of it is circular, since the watch builds the label partly from the VO2max estimate. The load ratio is the lever you actually control.
Unproductive: when to listen, when to shrug
My rule: I don’t change my training because of the label. I watch my acute load, more on that in my story below. That said, the label is worth a second look in a few cases.
Listen when
- The VO2max estimate has been sliding for two or three weeks. One estimate is one estimate. Three weeks of slide is a trend.
- You feel it too: short nights, stress at work, heavy legs. That’s exactly where Garmin tells you to look first: stress, nutrition and rest.7
- You’re in the middle of a training block, not tapering or racing. That was me before Amsterdam, more on that below.
Shrug when
- It’s the day after a race. In my data, the race-day label mostly reflected the three weeks before, not the race itself.
- The move is tiny. In October 2025 my 955 kept me on Maintaining for 10 days over a 0.3-point dip in the VO2max estimate, then switched back to Productive when it came back up.
- It was hot or high. Compatible watches correct VO2max and Training Status for runs starting above 22°C and days above 800 m of average altitude.7 If Garmin built a correction, heat and altitude move the estimate.
- Your profile is off. Garmin asks you to keep your age and max heart rate accurate for VO2max.3 A user on Garmin’s forums adds that a max HR set too low drags the estimate down.12
- You’re sick or injured. Pause Training Status: activities still record, the status stops judging.13 Garmin support has the steps.7
Try it · 30 seconds
What's driving my label?
Copy what your watch shows. Loaded with my Amsterdam marathon day. Or load,, or .
Load against VO2max trend, built from Garmin support's descriptions. A reading aid, not Garmin's formula, which also weighs your HRV status.
My case: Unproductive on marathon day
Amsterdam, October 2021. I went in feeling good. Six weeks earlier I’d run the Paris half with Edouard, who was lining up for Amsterdam with me, and it had felt pretty easy. For months I’d been getting up in the morning to train. Back then, training plans didn’t really adapt to you, so I followed a fairly strict one, and I was happy I’d stuck to it.
Or at least that’s how I remember it. My Garmin data is less flattering. Over the 12 weeks before the race I averaged 34 km a week. My biggest week was 52 km, my longest run 22.8 km, and look at that zigzag. Long runs and intervals, yes. Big volume, no. Maybe the one piece of advice nobody gave me: a marathon asks for volume.
Weekly running km before Amsterdam
Race day, the first 30 km went well. Slower than I’d planned, but I felt confident: 6:30 per km on average. Meanwhile my heart rate crept from the mid-140s to 163 at km 30, at roughly the same pace. Then the wall. From km 31 my legs just stopped following: 7:42 per km over the last 12.6 km. I was really sad about my race.
And then the watch served me Unproductive. Not a huge surprise after that finish. But after all those kilometres, all those mornings? It twisted the knife.
That was 17 October 2021, on my old Forerunner 945: 42.6 km, 4h52 on the watch. Five years later, here’s what the data says.
Here’s the twist. The marathon didn’t cause it. It switched me from Detraining to Unproductive, because 42 km pushed my 7-day load back into range: 201 the day before, 424 on race day, for a range of 281 to 640.
And Unproductive wasn’t new. I’d already been there from 2 to 13 October, during my heaviest weeks (7-day load between 516 and 543). What was moving was the VO2max estimate: 52.9 on 23 September, 50.3 on race day. Minus 2.6 points in 24 days.
Fitness: my VO2max estimate, fall 2021
Load: my 7-day load against the good range
| Dates (2021) | Status | Load vs range |
|---|---|---|
| 24 to 30 Oct | Detraining | 14 to 37, far under |
| 17 to 23 Oct | Unproductive | back in range after the race |
| 14 to 16 Oct | Detraining | 201, under |
| 2 to 13 Oct | Unproductive | in range, then under from 12 Oct |
| 23 to 27 Sep | Productive | in range, VO2max at its high |
So on race day, the watch was repeating what it had said for two weeks. The race only changed which side of the range my load was on.
On my 955 today, the label is rarer. In 130 weekly snapshots since March 2024: 54 Maintaining, 49 Productive, zero Unproductive. Maintaining is my watch’s favorite word.
What changed after
After Amsterdam I nearly stopped running. In my memory, for a year, maybe two. My data says 12 runs and 66 km in the seven months after the race, none longer than 9.3 km. I haven’t run a marathon since, but plenty of half marathons and trails.
What changed is how I train. I started following my watch’s daily suggested workouts, and it turned into a virtuous circle. I wanted to run as often as possible. I was so disappointed when the watch told me to rest because I’d slept badly that I started making sure I slept well and didn’t drink too much.
Sure, you always chase Productive. And it’s so frustrating to get Unproductive or Maintaining when you did everything the watch asked. Often it’s only because it decided your VO2max dipped a little.
So today, I don’t change my training because of the label. I watch my load ratio, acute load against chronic load. My goal is to stay between 1 and 1.3: that’s my sweet spot. It feels like I’m not training much. But since then, no pain, no injury, and I’m always happy to head out, unlike the weeks when I pushed my body way too hard. My game now is to stay inside that range, and watching it go up has been a real pleasure. It rewards consistency more than big sessions, and I think that’s what running is about.
You’re not the only one who went WTF
On r/Garmin, the most upvoted posts about this label are jokes and consolation threads. Votes as counted on 24 August 2026.
“I just ran a marathon and Garmin says I’m unproductive. Unbelievable. Like, yes? Do you think marathons are productive training?”
64 votes14
“Unproductive implies you didn’t work hard enough whereas ineffective may suggest hard work”
145 votes, top comment of its thread15
“‘maintaining’ after your best training week makes me depressed haha”
13 votes16
The threads behind them: “Training Status showing unproductive even after destroying a planet” (372 votes), “FYI: An Unproductive Training Status does not mean we hate you” (216 votes), and “Took me months to understand this about Garmin Training Status” (159 votes, 75 comments), where a member explains the whole load mechanism for free.
And the other side, so we don’t kid ourselves: “Unpopular Opinion: the training status feature is great” got 65 votes and 41 comments. Some runners like it, and say so.
The second quote nails it. The problem is half the maths, half the word. “Unproductive” sounds like a verdict on your effort, when it describes a trend in an estimate.
So what do you do tomorrow morning?
In my experience, Unproductive is your watch’s clumsy way of saying you’re not absorbing what you’re doing: too tired, or ramping up too fast. Garmin’s support page points the same way, to stress, nutrition and rest.7
So step back. Open your acute load chart, check you’re not climbing too fast, and enjoy your next run.
Next question: is there a number on your watch that says you’re ready for a marathon? Before Amsterdam, mine said my load was at a good level. You know how that ended.
All sources below were opened on 23 September 2026. Also used: my own Garmin Connect account (daily Training Status around Amsterdam 2021, running activities 2021 to 2026, weekly snapshots June 2022 to September 2026).
Footnotes
-
Garmin Support, Garmin VO2 Max Requirements ↩ ↩2
-
Garmin Blog, Garmin training status and how to use it, 5 February 2025 ↩ ↩2
-
Garmin, Forerunner 955 Owner’s Manual: Heart Rate Variability Status ↩
-
Garmin, Forerunner 955 Owner’s Manual: Training Status Levels ↩ ↩2
-
Garmin Support, What Is the Training Status Feature on My Garmin Device? ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8
-
Garmin, Forerunner 970 Owner’s Manual: Training Status Levels ↩
-
Garmin Newsroom, Forerunner 70 and Forerunner 170, 12 May 2026 ↩
-
DC Rainmaker, Garmin fēnix 9 Series In-Depth Review, 18 September 2026 ↩
-
Barth (Extraterrien), Cette technique respiratoire accélère la récupération (en 10 min/jour), 1% Performance newsletter ↩
-
Garmin Forums, Training Status stuck on Unproductive ↩
-
Garmin, Forerunner 945 Owner’s Manual: Pausing Your Training Status ↩
-
r/Garmin, comment on running a marathon ↩
-
r/Garmin, comment on the word “unproductive” ↩
-
r/Garmin, comment on Maintaining ↩