Game talkGame design vs UX design

 Posted by (Visited 11400 times)  Game talk  Tagged with: ,
Jun 292015

Short form: UX design is about removing problems from the user. Game design is about giving problems to the user.

In both cases you look at users’ cognitive reasoning and process capacity. And these days, we have UX designers on game teams, and they are incredibly valuable. But they are in a different discipline from game design.

Most UX designers don’t work in games. They work in website design or application software. They focus almost entirely on interfaces. In general, a UX designer’s job is to create a great experience when using something for a purpose. They therefore do as much as possible to make the interface

  • transparent, so that the user needs to think as little as possible
  • affordant, so that the user knows what possibilities it offers
  • scalable, so that it unfolds as the user develops skills
  • feedback-rich, so that the user knows when they did something
  • constraining, so that the user can’t do things that get them in trouble

What they do not do is

  • actually specify the inner workings of whatever is being used. They are usually working to provide an experience to a system already designed by an engineer, or specifying an interface to a system that an engineer will then go design.
  • make interfaces revelatory of the inner workings of the tool. Usually, we don’t want you thinking too much about car guts or lexical parsers when driving or using a word processor.

UX design in non-game applications is absolutely not about teaching the player how the guts of the software works. It’s about getting them to build a mental model that helps them get their work done. Classic examples might be the steering wheel of a car, or the entire desktop metaphor. The steering wheel is actively hiding from the user the fact that there’s a pretty complex mechanism in between the wheel and the tires. It’s instead trying to get the user to think “turn the wheel, turn the car.” This is an intentional elision of most of the actual workings of the steering mechanism. Similarly, the desktop metaphor in operating systems is intentionally trying to hide quite a lot of stuff about how the file system actually works, in order to build a consistent skeumorphic metaphor in the user’s mind, one that ties back to known cognitive patterns and is therefore easily understood.

In general a game designer’s job is to create a great experience when playing a game. They therefore do as much as possible to make the game

  • challenging. Often, we want the game to make the user think a lot.
  • explorable. We usually want the user to think there are always more possibilities in there.
  • scalable, so that players learn better play as they play.
  • crazy juicy, so that players are captivated by spectacle, well beyond the needs of feedback from a UX perspective
  • inviting of error. We want players to learn through mistakes.

In addition, game designers

  • typically do specify the inner workings of what is being used — not just the interfaces, but data structures, algorithms, formulas, and so on (often indirectly; it may be the gameplay engineer who writes the technical spec). They are intentionally creating a problem-rich environment.
  • are trying very hard to make the game experience revelatory of some of the inner workings of the game. Where UX tries to provide a likely false but useful mental model of the interior workings to the user, game design tries to guide the player towards a fairly accurate mental model.

In general, these lines get blurry. We want the way to fire your gun in the wrong direction to be as transparent as possible, so in games we try to layer great UX design on top of something that is in fact the opposite.

In game design, you’re usually trying to give players an understanding of the “machine” inside the game system. Typically, you have an interface to the game system that does in fact follow traditional UX principles: for example, moving the mouse to the edge of the screen resulting in panning a camera. That’s pretty traditional UX for an RTS. But understanding things like the overall build rates of different types of structures, so that the player ends up mastering complex supply chains and dependencies — not only is that a piece of game system design, but the intent is to get the player to actually understand supply chains. A UX approach would hide supply chains (as in fact they are hidden from our shopping experience).

UX is about clarity that hides complexity, and game design is about clarity that teaches complexity.

These days, we see UX designers who work designing UX at the game systems level. Until game teams got big enough, that’s how all designers were. 🙂 The splitting off of UX as a separate discipline that an individual performs on a game team is a result of large teams. Originally, we just had “game developer.” As teams grew and specialization started occurring, first we got content designers, then UI designers, and now we have UX designers. (I remember when designers at Origin were just called “technical design assistants.”)

Historically, though, ownership of the overall UX has fallen to whoever the game’s “director” is, who ideally is someone who has a solid grasp of every subdiscipline in the game design field; enough to manage people who are more expert than they, anyway.

  39 Responses to “Game design vs UX design”

  1. Slightly disagree, sometimes UX designers can hide complexity, but other times we do need to teach the inner workings because a false metaphor would add confusion when the simplified version falls short of expectations, or we need to reveal complexity as necessary for expert use or unusual use cases without breaking the mental model. Totally not thinking of any good examples right now…

    BTW, I was at a ux conference a couple months ago where someone lamented being unable to get game designers interested in talking at ux conferences. There’s an audience there, if you’re interested 🙂

  2. This quote “UX design is about removing problems from the user. Game design is about giving problems to the user.” may be the single best summary of the difference between the goals in gamification and the goals in game design!!

  3. UX is about helping the system provide the best possible experience for the user. If the system is a game, then the UX designer should not simply hide complexity: the UX designer should _optimize_ complexity.

  4. Carl, if you mean that the UX designer should simplify a game system that was complex on purpose towards a specific end, then I disagree. But maybe you don’t mean that by optimize? If you mean they should streamline the appearance of said complexity so that it becomes easier to understand, that’s what I meant by hide. 🙂 Hiding may be done in stages, so that more is revealed over time (good game design will do this anyway, it’s not a UX thing per se).

  5. By optimize, I mean that the UX designer should help the game designer present complexity in a way that creates the desired experience. If the complexity makes the game more interesting, it should remain, and be presented in a way that is good for the player to interact with. If the complexity doesn’t serve the game experience, it should be streamlined, hidden, or eliminated.

    Optimal complexity is the level of complexity that provides the best experience. It is not the same as no complexity at all. This is true of any system design, not just games: a system like Adobe Creative Suite must be complex to meet its users’ needs, but it needs good UX so the user can put that complexity to use.

  6. Then we’re really in total agreement 🙂

  7. […] Game design vs. UX design […]

  8. […] document, how to write a game, how to get past this impostor syndrome.  I read a piece about ux versus game design, which helped me look at game design as a less foreign challenge and more of a fun activity again. […]

  9. […] Design Principles FTW. A single game as a lifelong hobby. Do you finish one game and then move onto the next? This is the dominant pattern of play for gamers. How to be a Better Game Designer. Game design vs UX design. […]

  10. […] with my other “myth” article , it starts with me reading an essay , frothing at the mouth a bit, running out of characters on Twitter and ending up here where I can […]

  11. […] with my other “myth” article, it starts with me reading an essay, frothing at the mouth a bit, running out of characters on Twitter and ending up here where I can […]

  12. […] board game design in particular). I recently discovered Raph Koster’s article titled Game Design vs UX Design and it obviously rung a bell for […]

  13. […] Librement traduit de l’article : Game design vs UX design […]

Sorry, the comment form is closed at this time.