Reality slapped me hard. Since I had no mainframe experience and couldn’t code COBOL to save my life I was lucky to score an apprentice position with a firm in Greenwich, Connecticut. It was there from 9 to 5, for the next year, that I toiled at key-edit machines, JCL, punch-cards, and telegram machines (all telegrams ended with NNNN).
At night, I would fire up my trusty Apple and play or write games. I would do this until midnight practically every night. At the time, I was staying with my father who used to get pretty annoyed at this (in his words) “obsession”. He saw no value in it for several reasons.
Finally, one night, I fired back at him. I told him that I was learning; I was learning the best ways for people to interact with computers. I think I kind of meant it at the time but after saying it I realized that there was truth to it.
Which brings me to my point: The best man-machine interfaces on this planet are in games.
Games will not survive in a highly competitive environment if they have cumbersome interfaces which distract from gameplay. Can you imagine a shoot-‘em-up that required a menu traverse of Tools -> Options -> Weapon -> Shotgun -> Reload to reload your weapon in the heat of battle? It just doesn’t happen in game design.
Most game command interfaces are single hits in Verb-Noun pairs or, at most, choose Verb and then select Noun. Most game action interfaces are grab the darn thing and do something with it.
This is the way it has to work. Game interaction is so intense that anything else takes away from the focus of the game and that leads to a loss of acceptance of the game. This is why game consoles can get away with not having keyboards and offer rich value with simplistic controllers.
Somehow, we in the business world have not learned this lesson. Oh, to be sure, we’ve learned some lessons. With the advent of GUIs we’ve learned how to be non-modal and un-procedural. But we still lack, for the most part, the immersive aspect of an interface.
When we need to do something in a business application it tends to take away from our focus in what we’re trying to do. For example, if we’re trying to book a transaction in an accounting system we already have to have the chart of accounts entries in the system. If not, we have to make those entries before we can book our transaction.
A measure of the productive use of an application years ago was how many keystrokes it took to complete a given task. Somehow in the switch to graphical interfaces we lost that metric.
Perhaps it’s time to bring it back.