Good topic and questions. I see the point about average speed.

I only used a cyclo when I was doing early solo centuries. I generally ignored the speed readout because I found it distracting and got frustrated trying to "maintain" a certain mph. I used the odometer and the elapsed time, period. I have run 80 miles in 4.01 hours, but then struggled to maintain 14-16 for the last 20 miles. I've also been able to comfortably run 16mph the entire time, which goes a lot towards "pace yourself, you idiot!" self-awareness.

I'm with Ex-Pres on consistency. My main riding partner and I generally run about 18mph. I have no cyclo, and I pull 100% of the rides. She has one and keeps track of that stuff, and generally states an average at the end, per her cyclo. We've run 21 on really good days and 16 on bad days, and generally ride the same course. That is the only time I consider average to be average. As she's interested in being a better triathlete, I've convinced her to turn off the display when riding, and just try to improve her elapsed time.

Others, of course, run their HRM's and data, and I know a girl that has done that to great success, on her bike, much less so on her run, with her Ironman training. That was simply inexperience. You have to log a lot of miles at certain heart rates before you can start using that data in real time, while ignoring other variables. Lance and his coach were really the first to be able to use that type of information, because Lance could ignore or overcome a lot of the other variables (pain, etc).

With large group and charity rides, people are lining up next to the mph pace signs. A very few line up at the front and just ride away. Most end up about 2mph slower overall than where they line up. I've found my place there with the steel bikes, in the back, and while I do end up passing a large part of the field, my colleagues and I generally don't have cyclos, find it easier to overtake folks when they're spread out, and we get to see a lot of other bikes (and riders) while underway.

I'd say I normally ride 18mph, given a metric distance or less, and during this summer of very limited riding, that's more like 16mph. I only count start-finish time elapsed, less breaks. No cyclo for me, but I use a stopwatch for my breaks, and just subtract the total non-riding time from the overall time to figure an avg speed. I use 15mph as a guide for telling my wife when I'll be home. i.e. for a metric: "Honey, figure 4 hours for the ride and an hour or so for a beer and conversation, then I'll drive home."

For my workout rides I use the clock radio in the garage. Out the door at X time, in the door at Y time. 15 miles, as hard as I can in most cases, and the times are pretty consistent unless they're windy days. The time is irrelevant of clip-in time up the driveway, stops for traffic, and clip-out time in the driveway. I try to relate these times to what gearing I used that day. That's about as scientific as I get, or as accurate.

For training rides, the clock radio scheme works for me. As a runner, I simply used the clock radio when I bolted out the door, ran my run, and logged it in when I got back, regardless of any variables on the run. In the back of my mind, I simply tried to run a little faster when I could. This dropped my 10k and marathon times drastically, and a little less drastically, my 5k times (you are only so fast when going WFO). I knew when my workout runs went from 63 minutes on the clock radio to 53-55 minutes consistently that I was faster (9.6 mile route. Yep, I was decent).

It's interesting that you mention group rides and pace lines. Rarely are egos so much on display and orneriness in the extreme, especially with people who take themselves and their riding ability seriously. (You are already ticking them off by riding steel) It's hard, if you are not constantly riding with the same people, to ride to someone else's pace, unless their pace is yours. Many throw out the average "trip" speed in favor of the "pace" they're riding at the moment, and resist any attempts to bring their 14mph portion into the conversation, but the flat part with the tailwind will generally get everyone to admit they were doing 22mph....

Around here, there are two types of groups. The small group that rides together a lot, and therefore rides their pace, by themselves, all the time. They are not very supportive or jovial about having another bike in the mix. It throws off their mojo. Generally in 2's and 3's.

The larger group will predict "50 miles at 18mph" and then ride 65 at nearly 20mph, generally higher in the beginning, leaving anyone not running 21-22 in the dust quite early. It's my belief they mean 18mph for the entire ride, including off-bike stops. I've never seen them stop for more than 15 minutes, and never more than once in an entire ride. However, if you are pulling with this group, you set the speed, be it 15mph or 23mph. You just have to survive the 23mph guy in order to pull your 15mph turn! Upon requests, they'll run slower, but will have sprints right before the rest, and again at the end, generally with a breakaway. It's sort of fun, once you are self-confident enough to admit you're not where they are.

They encourage all new riders to join them, which lasts for maybe 5 miles, then they're gone. That's just the way they are; you either work up to their speed or don't.

My second wave training group will not ride over 14mph on any part of our route, unless we're coating downhill on the only hill we have. That's our protocol. We try to teach riding so that if a person keeps it up, they can run faster, but we're about learning to use the drivetrain, etiquette on the road, safety, and basic maintenance. I make sure those with cyclos "call out" if we exceed 14mph pace. My body seems to get nothing out of these rides, but that's not what they're for.