I had a friend ask Waze how to get to the McDonald's on Harbor Blvd. (supposed to be the one across from Disneyland), from where we were in La Mirada after church on the weekend of the Expo, and, well, it took him around his elbo to get to his butt. I was following. I had met him up there that morning for church, essentially going straight up "the Five" freeway on a twenty-five mintue drive. The trip back, following Waze, avoided the Five, went over to the 605, down to the 405. and was headed further south (past the 22) past Costa Mesa, when I called him and asked him where in the world he was going. He got irritated and told me to lead. We had to backtrack to Harbor Blvd. and drive up it from well below Disneyland all the way back. A twenty-five minute trip was now more than an hour, and we missed something we were trying to see.
I had told him that we could eat at the McDonald's on Harbor across the street from DL to hurry up and get to the convention, because taking the direct route (the Five), it would be right at the exit and on the way. Now, we were way below where we needed to be and would see several McDonald's along the way. So would just pick one.
The Waze app had not asked him to clarify "which McDonald's on Harbor Blvd." It apparently just assumed -- or it was taking us on the circle tour. I wondered about traffic, as we missed the first entrance to the Five. I listened to the actual real live radio news channel, which had traffic every ten minutes even on the weekends. They said that the Five was clear and moving normally with no incidents all the way from LA through Orange County toward San Diego.
So, it wasn't for traffic reasons that Waze took us around our elbow to get to our butt. And we still never found out which "McDonald's on Harbor Blvd." it was finding -- because it never clarified or asked us which one. We were just late and missed the program we wanted to see.
Sometimes a map and old media are still the best way.