Why Work Is Looking More Like a Video Game
james_bong666 writes "According to the New York Times, business software vendors can learn a great deal from how video games are designed.
This makes a lot of sense — how many professionals like working with their software in the office as much as gaming after hours? Developers can deal with looking at tables and grids full of data to make decisions and get things done, but other types of workers (executives, salespeople, etc.) have little to no attention span and need a picture to be worth a thousand words, i.e. their software designed completely differently."
Actually it's not the interface that makes the game fun... There are some games that have great interfaces - that I personally do not find fun to play (CIV, WoW), etc. I also disagree with this statment: "other types of workers (executives, salespeople, etc.) have little to no attention span and need a picture to be worth a thousand words" I fail to see how employment position is a realisic and valid way to determine attention span.
These people don't need their software designed completely differently, they just need it designed better.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
I think TFA is missing the point. After reading it, I came away with "If we make work less like work and more like fun, then it will be fun." However, fun does not equal associating pictures, likes/dislikes, favorite colors etc with a business contact. I think the point is that if your job requires you to use a CRM system, then it is not fun by definition, and no amount of reskinning that interface is going to make it more enjoyable.
I agree that the ideas of connection, management and cooperation within MMORPG are potentially interesting in the context of managing large companies, but the "making work like a videogame" metaphor doesn't work for me.
yskel
This has parallels with what I am learning in medical school (yes, a med student who reads slashdot *gasp*). We are taught that we cannot use medical jargon to explain things to patients, because our level of training and experience is completely different from that of the average patient. This is also true in software, but I don't think developers are taught this point. This often results in the user not understanding what may have been obvious to the software designer, and a program that is not popular with the public. In both fields, I feel one must think at the level of the end user. In medicine, it is to provide the best health outcome by promoting understanding. We do this because we recognize that not everyone is health literate. In software, I think to be successful, it is also important to recognize that not everyone is tech literate, and design products accordingly.
I don't think it's a matter of work imitating games, I think it's that application developers are now going down the same usability design paths that games require. Most people aren't required to play games, so the successful ones are the engaging ones, the games that give you a clear idea of what you need to do, and clearly present the required information. People like overcoming challenges when they think they see the way to do it. At work people are often dealing with scenarios where they would like to do a good job, but may not have the information on what is required, or they are dealing with too many factors to filter the wheat from chaff. They may lose focus because they have forgotten what their goals are. Most of management training revolves around how to present information to people, which provides the feedback loop people need to do their jobs. The idea that this is starting to show up in applications is an interesting, but natural step.