Yea, this is what we were talking about. Waze "learns" your destinations. Not necessarily your routes.
I also found that it seems to remember where you go on which days and offers that as a destination when Waze starts up. But again, it does not learn the route(s) you take most frequently, but it does learn the destinations.
When talking to my brother-in-law I said he should try Waze. He said he pretty much knows where he's going and how to get there. To that end, Waze is supposed to find the fastest or shortest route to get you to your destination. Among other variables, it calculates the fastest/shortest, based on current traffic and other conditions, and past timing for those routes, etc.
The beauty here is that instead of instructing you to take the route you always take and pushing you into a giant traffic mess (say there is some extraordinary circumstance) it suggests you take an alternate. I've learned to take the route Waze suggests. Albeit, how big of a difference can multiple routes of a 5-mile trip make? Well, yesterday I didn't listen, and drove myself right into a giant jam. Instead of 4 minutes early, I was 3 minutes late.
The segments within any given route, and how they're configured, can effect the choices Waze makes too.
This means that a given route may not have been configured in the most optimal fashion based on Waze's routing algorithm.
So, take a look at the map based on the multiple routes. Again, the beauty of being able to edit the map is that you're actually on the ground, frequently. Allowing you to enable the system to provide the most efficient route. Then you let Waze calculate the other conditions. Now you have a very effective navigation application.
From the FAQ...
Why doesn't Waze learn my routes?
The setting within the Waze app, "Auto-learn routes to frequent destinations" is misleading. Waze only learns your favorite destinations, but does not learn or store actual routes. It will pop-up with the "Are going home?" or "going to work?" messages for these frequented destinations.
Waze should always pick what it believes is, mathematically, the fastest or shortest route, depending on your settings. If, in your estimation, it doesn't, that means that there could be an error in the map somewhere along your preferred route, or there is a lack of correct speed/traffic data for that route, or lack or correct speed/traffic data on the route it is trying to send you on. If it isn't too far out of your way, take the suggested route a few times and Waze will collect and start to use that data in its routing decisions.
The reason just driving the expected or preferred route won't work automatically is because Waze could have incorrect speed data on the segments it wants you to take. If Waze thinks another road is 2x as fast as your preferred road, no amount of driving on your preferred road can change the data for the other road. Waze needs accurate data for all neighboring segments and routes in order to always compute the fastest (or shortest, depending on your app setting) route.