Indeed, best design practices do something called "bridging the gulfs of execution and evaluation", which basically means - when you know what you want to do it is obvious from the environment how to get it done and when you have done something it is easy to tell that you have done it correctly.
See the page labeled "38" (page 8 in acrobat reader) from http://hci.ucsd.edu/132/Handouts/Norman-Cognitive-Engineering.pdf for an in-depth discussion. My ideal for walk-signal trigger feedback would again to be to put the indicator that the walk signal has been triggered in the same visual field as the walk signal, rather than in the vicinity of the button - or at least do both. This allows people to make the determination if they need to push the walk signal simply by checking the walk signal. Otherwise, they have to scan their environment for the location of the button, which is not consistently located. For that matter, street actuators should follow the same rule - if you are riding a bicycle on a street with an actuator, you should be able to look up at the traffic light and see something like a little blue LED cluster adjacent to Green/Yellow/Red light that let's you know you have triggered the signal. This would also be a great help for motorcycle operators. -----Original Message----- From: Richard Frueh The other problem is that most of us have been trained over the years that WALK buttons don't do anything. Go to Germany and push one, and it lights up. The new ones at Washington and Fairchild do this. Otherwise, it seems like nothing at all happens. _______________________________________________ Bikies mailing list [email protected] http://www.danenet.org/mailman/listinfo/bikies
