(My reading notes are piling up so here’s an attempt to clear out at least a few of them.)
Part of the play experience of many digital games is figuring out how the damn thing works in the first place. In Rules of Play on page 210:
“[…] as the player plays with FLUID, interaction and observation reveals the underlying principles of the system. In this case the hidden information gradually revealed through play is the rules of the simulation itself. Part of the play of FLUID is the discovery of the game rules as information.”
(Sadly, I could not find a link to the game mentioned.)
I did not give Donald Norman all the credit he was due in my earlier post. He doesn’t have a blind spot for games. Quite the contrary. For instance, he explains how to make systems easier to learn and points to games in the process. On page 183 of The Design of Everyday Things:
“One important method of making systems easier to learn and to use is to make them explorable, to encourage the user to experiment and learn the possibilities through active exploration.”
The way to do this is through direct manipulation, writes Norman. He also reminds us that it’s not necessary to make any system explorable. But (on page 184):
“[…] if the job is critical, novel, or ill-specified, or if you do not yet know exactly what is to be done, then you need direct, first-person interaction.”
So much written after DOET seems to have added little to the conversation. I’m surprised how useful this classic still is.
I’m reminded of a section of Matt Jones’s Interaction 08 talk—which I watched yesterday. He went through a number of information visualisations and said he’d like to add more stuff like that into Dopplr, to allow people to play with their data. He even compared this act of play to Will Wright’s concept of possibility space. He also briefly mentioned that easily accessible tools for creating information visualisations might become a valuable tool for designers working with complex sets of data.
Norman actually points to games for inspiration, by the way. On page 184 just before the previous quote:
“Some computer systems offer direct manipulation, first-person interactions, good examples being the driving, flying, and sports games that are commonplace in arcades and on home machines. In these games, the feeling of direct control over the actions is an essential part of the task.”
And so on.
One of the most useful parts of Dan Saffer’s book on interaction design is where he explains the differences between customisation, personalisation, adaptation and hacking. He notes that an adaptive system can be designed to induce flow—balancing challenge with the skill of the user. In games, there is something called dynamic difficulty adjustment (DDA) which has very similar aims.
Salen and Zimmerman have their doubts about DDA though. In Rules of Play on page 223 they write:
“Playing a game becomes less like learning an expressive language and more like being the sole audience member for a participatory, improvisational performance, where the performers adjust their actions to how you interact with them. Are you then playing the game, or is it playing you?”
Perhaps, but it all depends on what DDA actually adjusts. The technique might be objectionable in a game (where a large part of the point is overcoming challenge) but in other systems many of these objections do not apply.
“With a successful adaptive design, the product fits the user’s life and environment as though it were custom made.”
(Designing for Interaction, page 162.)
Adaptive systems explicitly anticipate transformative play. They allow themselves to be changed through a person’s interactions with it.
A characteristic of good interaction design is playfulness, writes Mr. Saffer in his book on page 67:
“Through serious play, we seek out new products, services and features and then try them to see how they work. How many times have you pushed a button just to see what it did?”
The funny thing is, the conditions for play according to Saffer are very similar to some of the basic guidelines Norman offers: Make users feel comfortable, reduce the chance for errors and if errors do occur, make sure the consequences are small—by allowing users to undo, for instance.
Mr. Norman writes that in games “designers deliberately flout the laws of understandability and usability” (p.205). Although even in games: “[the] rules [of usability] must be applied intelligently, for ease of use or difficulty of use” (p.208).
By now, it should be clear making interactions playful is very different from making them game-like.
