That's still the right way to do UI testing. You bring in people, you give them a list of tasks to do, and you take video of screen and user. Someone then has to watch the video and mark the places where people got stuck, had to back up, or gave up. Then create a highlights reel of every problem seen more than once. The devs have to watch this.
The closest I've come to replicating the impact is to have a conference room where the team sits together and watches the usability test being streamed live.
I don't remember seeing this one on the usual lists of forms of market failure, but it's real.
Any reason for the leading zero? Is it a native language thing?
Year numbers are variable length decimal strings, not a four or five digit fixed length field. Any historian concerned with 6 AD-999 AD will likely not include a leading zero in any year figures they use. I don't see why the people of the present or the future should do any different.
Machine readable implementations, sure. Have as many digits as you wish. But for human written material, it just looks weird.
The only time I've seen UI work carried out with this level of care was for an air traffic control system, where of course the consequences of a poor design can have significant and fatal consequences.
Had it not been for that user feedback, Windows might have copied the Mac and gone with “Do It” as well and we would be living in a slightly more awkward UI timeline.
I always think about this when I look at current Apple's UI. Just a little user feedback would have gone a really long way.
I do recall ~8-10 years ago, we were building an app and did a user test; we had a phone with a webcam rigged to it so we could see from the user's point of view.
But for this you need dedicated (in multiple senses of the word) UX people, and they are both rare, and companies seem to be reluctant to hire them.
Tesler was a computer scientist. He worked on AI and Smalltalk at Xerox, and was a manager at Apple at this time.
What we need to do instead, is bring down the wall between design and development that was built up in the past decade, encourage developers in the UI field to have multi-disciplinary skills, and stop assuming every minute not spent coding or in meetings is wasted.
There was a time when tech products would start with a tutorial on the differences between clicking, right-clicking and double-clicking.
But if you want details about why those large "record the user" sessions aren't worth it, you'll have to dig into their papers.
Amazing to see the importance they gave to UX/UI and the level of sophistication they had forty years back.