I've worked with over 100 different runners over the years and can attest that maxHRs come all across the range regardless of personal characteristics (gender, age, fitness, etc.). I've got runners in the 210s and as low as the 140s for a maxHR. But the one thing that is very consistent amongst all of them is the use of the %HRR calculation (heart rate reserve). This takes into account the maxHR (observed in a training run or race that isn't believed to be an erroneous value) and restingHR. Using those values you can find general zones that line up quite well with the current fitness based pacing that I typically schedule runners for. Admittedly though, run/walking presents a unique challenge with these zones since for small time frames you move in and out of different types of paces to generate an average pace in the same place as a continuous runner. But even with that, looking at the general trends can still be insightful.
So if someone had a:
Max HR of 175 (Look for the highest HR you've achieved in a 5k that wasn't cadence lock. Don't use 220-age as that has a huge standard deviation which makes it mostly irrelevant for many.)
Resting HR of 49 (Either from your watch, or check your pulse after you've awoken but before you get out of bed.)
HRR = maxHR - restHR = 175-49 = 126
53% HRR = restHR + (0.53 * HRR) = 49 + (0.53*126) = 49 + 66.78 = 115.78
View attachment 418113
For run/walkers who use the Galloway +2 min model for their easy/long run pacing, I typically find they fall on the lower end of the "easy" spectrum listed above if they're pacing to current fitness.