What your watch is actually measuring
Most running watches report cadence, but they measure it differently. Understanding how your device collects this data helps you interpret the numbers correctly.
Wrist-based accelerometers (used by Apple Watch, most Garmin watches without a foot pod) detect movement patterns at the wrist and derive cadence from the rhythmic oscillation of the arm swing. This works well for steady running but can be less accurate during very slow running, trail running with varied arm movement, or when carrying something in one hand.
Foot pod sensors (Garmin pods, Stryd, RunScribe) attach to the shoe and measure movement directly at the source. They tend to be more accurate, particularly on non-standard terrain, and provide additional data like stride length, ground contact time, and vertical oscillation.
Most modern watches provide a useful cadence estimate for training. Accuracy varies by device, placement and running conditions, so treat your watch cadence as a helpful guide, not a laboratory measurement.
What the number means — and where you should be
If you look back at a week of running data and see your cadence averaging 158 SPM on easy runs, what does that tell you?
It tells you where you are starting from. 158 SPM is a baseline, not a diagnosis — interpret it alongside pace, height, terrain and how the runner actually moves rather than against a universal 'efficient' target band.
More importantly, the number gives you context to work from. Use your current average as context; if you choose to train cadence, start with a modest change that remains comfortable rather than treating +5% as mandatory. If you are at 158, an example modest target might be around 166 SPM. The principle is always the same: a relative increment above your personal baseline, adjusted to how it feels.
The gap between measuring and doing
This is where most runners with data-rich watches get stuck. Knowing you ran at 158 SPM last week is useful baseline information. It does not tell you what to do differently on your next run.
The typical response to cadence data is passive: the runner notes the number, concludes they should probably run faster cadence, then goes on their next run without changing anything. Three months later, the number is still 158.
Cadence training requires active guidance during the run, not retrospective review after it. The reason is that cadence is a motor pattern — a rhythm that your body defaults to automatically. Changing it requires giving your motor system a different rhythm to follow during the actual movement, not just knowing after the fact that the movement was different than intended.
Watch cadence data is most useful as a baseline measurement and for post-run verification. A cadence-guided beat provides continuous timing feedback in a way a retrospective watch summary cannot, since the body responds to rhythm during the run itself, not to a number checked afterward.
Why cadence data without guidance is like a speedometer without a timing reference
A speedometer tells you how fast you are going. A cruise control system maintains a specific speed without requiring your continuous attention. Both use the same underlying measurement — but one is informational, the other is actively corrective.
Watch cadence data is the speedometer. It tells you what happened. Cadence-locked audio is more like a timing reference than cruise control: it tells you where the target is, and your body still has to match it, without requiring you to check a display or count steps to know where the beat is.
The two work well together. Use your watch data to establish your baseline and track progress over weeks. Use cadence-guided audio during the run to actually run at your target. Check after the run whether the audio guidance produced the cadence you intended. Over time, the watch data shows the results of the training: cadence trends upward, the gap between target and actual narrows, and eventually the target cadence becomes your natural cadence.
When to check your watch cadence
- Before starting a training block: measure your baseline across three or four easy runs to establish where you are.
- After a run: check whether your cadence over the session matched your target. If actual SPM is consistently below target, first check whether the target is appropriate and whether you were able to hear/follow the beat, rather than automatically increasing the target.
- Not during a run: checking a watch display during a run interrupts the absorbed quality of good running, introduces a cognitive distraction, and does not help your body maintain rhythm in real time.
