troyv wrote:So my original thinking was that if we were to use a network topology as an analogy, the router (Waze) would just send packets (users) down a certain segment (road) and see what the results were. If the packets (users) made it down a certain segment (road) OK, then the router would send more. That's great in the network world, but if Waze were to guide a user on to a rocky hiking trail in the forest using their Ford Taurus, that would be a bad thing. Basically, we shouldn't treat users as packets in a network.
You're reminding me of Paul Baran's hot-potato routing http://www.rand.org/about/history/baran.html .
troyv wrote:What if we took advantage of users and had a "get me out of here" button on the client. If that button is hit, Waze would attempt to guide the user to the closest well driven road as quickly as possible. Not only would it do that but it would take a note as to what road the user was on. When Waze was tempted to route another user that same way, it would see that a previous user wanted off of that road. Waze then would have learned a little bit to avoid that road segment when routing for future users.
If Waze uses any other than the route the user took in, it will probably be worse than the one they are on at the moment. The user knows how to get out of there: reverse direction ... then wait for Waze to start suggesting a reasonable alternative.