Two examples:
My VO2 max widget graph Y axis goes from 0 to 100 in the widget view, although the range presented for my historical values is only about 10% of that. Further, 25 to 55 is the most likely range covering 95% of all users... scaling in a way that makes changes visible (i.e. smaller Y range) would be much more useful. (The full graph scales a bit more sanely than the widget, ranging from 10 to 60 - still, all of my numbers are in the 40s...)
My Lactate Threshold graph has 2 axes, one for heart rate and one for pace. The HR axis is sane, roughly auto-scaling to the HR ranges shown for my history. But the 2nd Y axis, for pace, is a bit nuts - it ranges in the widget from a 3:22 mile (!) to a 13:25 mile. In the full view, it ranges from a 2:15 mile (!!!) to a 13:25 mile. Such a wide range compresses the graph and makes changes indistinguishable.
Thanks,
-Eric