Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Get the latest Education e-news
  • Debunking Game Design Myths: UX Is Just Common Sense

    - Michael Moran

  • The solution

    So, where does that leave us? Well, it leaves us dispelling the myth that productive UX solely comes down to common sense. Sure, having proficiency and experience makes for a solid foundation, but when those pesky ‘common sense' problems still rush to the surface, you need something else to protect your efforts.

    And that something else is a strong UX process.

    See, each of our brains is overrun with biases - social, cognitive, perceptual, you name it, we've got it. That amalgamation of biases, unique to every individual, makes adhering to one ‘common sense' outlook nearly impossible... because what each of us is able to expect, recognize, and interpret will be different. And that means there's no one straight perspective - or track to perfection.

    Instead of relying on their own common sense abilities, smart developers protect themselves with system over instinct. Not only does system solve for the three issues outlined above - which I'll demonstrate for you in a second - but it also solves for the inherent biases every practitioner has.

    What does a sturdy process look like in practice? Obviously, specifics depend on the developer's game, team size, and daily task list, but the key elements remain constant:

    • Identification: Here's where you carve out time to take stock of your work and look for any issues - before it's time for release. The more time you allot to investigating and locating, the cleaner the finished (and launched) product will be.
    • Assessment: You've located the problems, now it's time to assess them. What are they? How did they happen? What subset of your audience will they affect (if they don't get fixed)? Taking the time to break each issue down will help you move through this process, but it'll also help you avoid finding the same issues in your next production cycle.

    • Prioritization: Based on your assessments, it's time to prioritize which issues you'll fix first. Here's an example:
    • You have two fixes to make. The first isn't as intense a problem for players - they can work around it without too much hassle. But, the scope of who it affects is huge. Like, impacts-a-core-game-pillar huge.
    • The second is a more intense problem for players, visibly affecting their gameplay experience, but the population of who it affects is much smaller in scope - because it only impacts a higher-level feature (irrelevant for the majority of the game).

    So which takes priority? In this scenario, the first issue does - because even though it's less impactful as a standalone problem, the number of players who'll face it (and have to adjust their play accordingly) is greater.

    • Solution: Now it's time to fix...and fix some more. Following the prioritization order you settled on, attend to the first issue and then work your way down, systematically crossing off each one. The beauty of prioritizing ahead of time? If you run out of time pre-launch, you'll still have fixed the most pressing problems.
    • Identification: Wait a second, didn't we already cover the identification phase? That we did - but surprise: this process isn't a straight line. It's a loop. And just like you can work your investigative lens in the pre-launch phase, so too should you work it after your game's been released. In fact, it's easier to critique a game - and uncover its issues - once it's live than it is to identify flaws in development.

    One more time for the people in the back? That's Identify, Assess, Prioritize, Solve, Identify. And on and on.

    The conclusion

    Now, let's back up. Remember those three reasons I laid out for you earlier - the three reasons for why those pesky ‘common sense' problems can make it into your players' field of vision?

    • Knowledge: being too familiar with your game.
    • Awareness: recognizing but forgetting to act.
    • Time: setting out when the clock's already timed out.

    Each of those reasons exists even when a UX practitioner possesses common sense - and each of those reasons can be solved for by simply implementing a process, like the one above, into your day-to-day. By setting aside time to look for, understand, and fix issues methodically, what you're really doing is outsmarting your biases. You're outsmarting the risk of seeing and then forgetting, and you're outsmarting the tick-tick-tick of that ubiquitous operational clock.

    Now look - it's not like I'm proposing something that's never been discovered or promoted before. Take any field and you'll find established methodologies for proving hypotheses. Why? Because the human brain can't be trusted to catch every detail or evade every bias - but more often than not, systems can. More often than not, processes can.

    And that takes us back to where we started. At the foot of the myth. UX is just common sense. If a developer possesses common sense, they're good to go.

    If I did my job, you now have the knowledge spear necessary to poke holes in that claim. But more than that: you now have the guidance necessary to overcome the problems that common sense doesn't solve for. You now have an actionable process.

    And that wraps us up for today. But this is a series, which means I'll be back - dispelling myths, uncovering truths, and helping developers near and far get the attention (and respect) they deserve.

    UX matters. It can make your game, or it can break it straight in two. Join me back here for Myth #2 - There's just no money or time for UX - for more insight, advice, and old-school claims debunked. Because UX deserves its time in the spotlight. And outdated myths shouldn't hold their practitioners back any longer.


    Since you made it all the way to the end, you maybe be interested in a newsletter I just started.

    I send short mobile game retention tips to your inbox every week. You'll learn something every time you open it.


    This article was originally published at, where we're building a new liveops engine for mobile games.


comments powered by Disqus