<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Player Research on Medium]]></title>
        <description><![CDATA[Stories by Player Research on Medium]]></description>
        <link>https://medium.com/@playerresearch?source=rss-8e7497e82347------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ee4Z_W-7sZlBRD_MHytUeg.png</url>
            <title>Stories by Player Research on Medium</title>
            <link>https://medium.com/@playerresearch?source=rss-8e7497e82347------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:30:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@playerresearch/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Organising Playtest Sessions to Get Great Feedback from Children]]></title>
            <link>https://playerresearch.medium.com/organising-playtest-sessions-to-get-great-feedback-from-children-7e05aa2302df?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e05aa2302df</guid>
            <category><![CDATA[games-user-research]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Wed, 10 Aug 2022 11:18:02 GMT</pubDate>
            <atom:updated>2022-08-10T11:22:33.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QF4-2Ubj3YAL3PnnxGL5w.png" /></figure><p>Children think about things <em>differently</em>.</p><p>For us, as adults, it’s practically impossible to put ourselves in the ‘mindset of a child’, in order to experience their interpretation of <em>our real world.</em></p><p>The same is also true for <em>virtual</em> worlds. It’s impossible to put yourself in the head of a child to emulate how they experience video games. It can make designing children’s games a difficult challenge.</p><p>Game Designers rely on having a meaningful understanding of their players’ emotions, behaviours and thought processes, in order to <em>influence</em> them through game design.</p><p>So, when making games for children it’s therefore essential to playtest regularly with real kids: to examine their behaviours, emotions and thinking, in order to adapt the game design and improve it. For Researchers conducting these playtesting sessions it’s also essential to adopt traditional playtesting protocols, both to having children as our testers, and also toward exploring the particular challenges that designing children’s games presents.</p><blockquote>Researchers must design sessions that can ‘build a bridge’ between children and adults, unlocking a window into their experience.</blockquote><h3>Adults Thinking vs. Kids Thinking</h3><p>In his book <a href="https://www.amazon.co.uk/User-Research-Kids-Effectively-Participants/dp/1484270703"><em>User Research with Kids</em></a>, Thomas Visby Snitker explains that children have their own world they are evolving in, that we have forgotten as adults. They have their own needs, capabilities, goals and success criteria, and user journeys. More than that, they express themselves differently from adults. He calls this Kids Experience (KX) in contrast with UX that would be for adults and has different scales and ways of evaluating the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*od-ovTqUmoN6Swbihn0FzA.png" /></figure><p>Kids learn and develop through play, and the form of this play evolves as they get older. Gareth Griffiths GDC talk <a href="https://www.youtube.com/watch?v=PDhmOunXk4U">‘<em>Skylanders and Playtesting with Children’</em></a><em>,</em> explores how kids from different age ranges will approach problems differently, and have very differing views of the world. For example, in the 2-year gap between a 6-year-old and an 8-year-old, the older will be more at ease with holding a controller in their hands, and will have stronger reading and greater puzzle-solving ability.</p><p>Kids between 6 and 8 will often take things very literally compared to kids from 9 to 11. The latter will already have a very strong understanding of the world and can draw upon that experience. At 8, they’ll start to draw things from the real world, as their perception is getting more acute compared to 6 year olds.</p><p>All of this makes games user research with children both <em>essential</em> and <em>complicated. </em>Let’s dig deeper into how Player Research adapts our approaches to playtesting with children.</p><h3>Playtesting with Children</h3><p>Playtesting — the act of putting real players in front of prototype games to examine the player experience — is already a nuanced and challenging activity. With children it requires yet more planning and patience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*FEFWZu4f1BZjo3-UKVrhlQ.png" /></figure><p>Often the first challenge is you deciding: <em>how old should the playtesters be</em>?</p><p>Most games have a ‘target audience’, but it’s rare that playtests can accommodate the twenty or thirty children that might be needed to truly examine broad age ranges. But just a year-or-two of difference can completely change the player experience.</p><p>Focusing our playtesting on <em>younger</em> kids means they’re likely to be more shy and less able to express their experiences. Their focus and attention are low, and they get easily distracted, especially during interviews. Data will be harder to interpret, but is likely to be the most-insightful.</p><p>Alternatively, focusing our playtesting on <em>older</em> children might unlock better <em>verbatim</em> feedback, but also skips-over any playability issues that might be specific to the youngest players in our target market.</p><p>Our advice for teams is to focus on younger children foremost, and to divide up regular playtesting sessions among specific age groups, rather than running fewer, larger playtests that aim to explore all ages.</p><h4>Creating a Safe Space</h4><p>Children tend to be more emotionally sensitive to the playtest environment than adults. Researchers must do all they can to craft an environment in which children <em>a</em>nd <em>their guardian</em>s feel safe and reassured, leading them to play comfortably and naturally.</p><blockquote>A guardian’s presence can be necessary to reassure a child, especially younger and more anxious children.</blockquote><p>Having parents/guardians nearby — in eyeshot or earshot — is an essential component of making a comfortable space for children.</p><p>Adults are also a normal part of the child’s gameplay experience in everyday life, as children play accompanied, or seek the assistance of an adult when stuck, or even asking in on play.</p><p>As such, Researchers need to be deliberate in managing the presence, proximity and involvement of the adults accompanying the children during the playtest.</p><p>Using a strategically-placed mirror in the playtest lab can be extremely helpful, both for Researchers to observe adult/child interactions, and to allow their parent/guardian to watch the child play from physically further way or without direct line-of-sight, and vice versa for the child.</p><p>Playtests are typically designed to explore the <em>child</em>’s experience of the game alone, rather than the <em>adults’ </em>interpretation. Parents are nonetheless typically keen to help their child, or overcome barriers for them, which disrupts research objectives. It’s necessary to brief the guardian that they shouldn’t feel obliged to give the answers to questions, nor to overcome any issues their children face, nor to distract. Using the child’s name when asking questions, and giving them your full attention as the question-asker will help their guardians stay neutral.</p><p>Parents/Guardians can necessarily take a more active role in interviewing, sometimes with little warning. For shy children speaking quietly, or with children you’re finding difficult to understand, the parent can be a necessary interpreter. The very shiest of children might not feel comfortable talking to anyone <em>except</em> their parent/guardian at all. You can try having the parent repeat your questions to their child, or even resort to having them take over completely. Be ready, in either case, to rephrase your questions to suit the new situation.</p><h4>Setting out a Playtest’s Content and Questions</h4><p>It’s essential to allocate the time during a single research session differently to better accommodate children.</p><p>For example, Researchers should allow more time to build a rapport with the child, and be friendly with them, than would be typical for a sessions with adults. This will allow them to be less shy in the Researchers’ presence and be more at ease with talking. Otherwise, they could shy away and just stop talking, and we really don’t want that! Using an ice breaker at the start of the session can help tremendously, for example asking about games they love.</p><p>Children will fatigue much quicker than adults, and tend to give up when tiredness sets in, unaware of any protocol to follow or that they are ‘on an assignment’.</p><blockquote>We’re working hard to craft a comfortable environment where children feel un-pressured and able to speak freely, which includes <em>“I don’t want to play this game any more”.</em></blockquote><p>Sharing a visual timeline of the session’s activities can help children build confidence, knowing what they will do and when. It will help them focus and transition smoothly from one activity to another.</p><h4>Managing A Child’s Attention During a Session</h4><p>Keeping an impartial and neutral presence is important, even if children’s excitement can be contagious.</p><p>Needing to assert control during the playtest and bring activities back-on-track can happen often. Before questioning them or giving them instructions, make sure you have their full attention. You can use their name, ask what they’re currently doing, but try to not give the impression of shouting orders at them to not close them up.</p><p>Also, to avoid losing their attention, minimise opportunities for distraction: no books, games, figurines on the shelves, magazines, or spinning chairs.</p><p>Compared to adults, children can be very energetic, and trying to keep their attention on yourself can be cognitively and emotionally demanding, and therefore energy draining. So, make sure to have more unwinding time between sessions (~30 minutes) to have time to step out of the ‘Researcher’ character and take a breath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*_VyN0TA3iRDHCBaIhEcqpg.png" /></figure><h4>Asking Questions to Children</h4><p>To better understand the child’s experience with the game and their thinking process, we suggest staying in the same room, observing the play, and ask just a few essential questions during the session.</p><blockquote>Long-form interviews typical to user research with adults are most-often not appropriate for sessions with children. Researchers will be more reliant on observational findings.</blockquote><p>To dig deeper, interviews can be performed after the playtime. Having only one child at a time avoids having their perspective biased by others.</p><p>All research with children is unpredictable, but particularly in interviews, so easily derailed by wild imaginations, boredom, distraction, or embarrassment. Interviews can be very demanding on the Researcher to adapt across participants while remaining consistent.</p><p>Be careful to not use words or phrases that could confuse them. If you see that they don’t understand a word or sentence, don’t hesitate to change it to a simpler vocabulary.</p><p>To combat child’s fatigue and engage them for longer, it’s essential to provide a lot more breaks and shorter interviews than with adults, to allow them to unwind. To break the pacing of the session, think of inserting breaks between gameplay segments.</p><p>If the interview is performed in group, ask them to take turns to answer, and direct specific questions to specific kids. It will avoid them talking over one another, and having some individuals not speaking up. Additionally, try to keep the group size between 4 to 6 people to allow each the time and space to talk. Don’t mix in children of very different ages into group interviews.</p><p>Finally, to avoid them to get frustrated and giving up the playtest all together, it’s essential to regularly use encouraging, courteous language to ensure they’re not feeling judged for forgetting or not knowing.</p><h3>Gathering and Analysing Data from Playtests</h3><p>A couple of things will need to be done differently than during a usual playtest.</p><p>As mentioned before, being in the same room as the child to observe and question them if needed is the best setup.</p><p>During interviews children might understand the question, or see the game mechanics, differently to you, so you can gather the most accurate data with observation and listening to their commentary.</p><p>If they play in groups, listening to their conversation as they teach each other, and discuss their interpretation of the game in real-time, will give you a lot of information as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*8Y34xQXlMbRM-BNsvA8h0g.png" /></figure><p>An efficient way of gathering qualitative data during interviews is to use the <a href="https://www.amazon.co.uk/Bear-Cards-Feelings-John-Veeken/dp/0980517524"><em>Bear Cards Feelings</em></a> by John Veeken. On top of being extremely adorable, it helps children express their emotions and talk about their experience in detail while using their own words.</p><p>Regarding ratings, children won’t get the full extent of a 5 or 7 points scale, so the best is to have simplified ones. You can use vocabulary as well to help children understanding what the number means.</p><p>For example, from the <em>Skylanders and playtest with children</em>, Gareth Griffiths gives an interesting type of scale:</p><blockquote>1) I really liked it — Cool! • 2) Kinda OK • 3) I really didn’t like it</blockquote><p>After rating their appreciation of the game, give some space for them to express “why” so you can gather more information. Keep in mind that this process will take longer than with adults and that an interview might be better than presenting a scale, as some might not be able to read or understand numbers just yet. The <em>Bear Cards Feelings</em> mentioned earlier can be helpful in this situation.</p><p>Thomas Visby Snitker, in <em>User Research with Kids</em>, came up with the idea of a universal scoring system that he called “KX (Kids Experience) score” that would be an UX score but especially for children and that would allow more relevant data and therefore more informed decisions. We haven’t used this scale yet, but it’s interesting to note.</p><h3>Bringing it All Together</h3><p>In summary, observation and listening skills in playtests with children are vital, they have a lot of interesting things to say. Be prepared to adapt if playtesters need to work at a different pace, need more time to explain their experiences or longer breaks.</p><p>During the playtest, you need to make sure that children are at ease but still paying attention, that they understand your questions and what you ask them to do. Try to use simple vocabulary and put yourself at their level, without being condescending. Using a simpler scale can be interesting to gather quantitative data and using the <em>Bear Cards Feelings </em>can help to gather qualitative data.</p><p>And more importantly, know your audience and the age range of the kids you’re creating or testing the game for, as the life experience and abilities will be very different from one year to another.</p><p><em>Related Reading and Sources:</em></p><ul><li>User Research with kids — Thomas Visby Snitker</li><li>5 ways to playtest with children increases likelihood of launch success — Kidsbrand insight</li><li>Interview guide — Player Research experience with playtesting with Kids</li><li>Skylanders and Playtesting with Children — Gareth Griffiths</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*NqBe58GSSUfdLEGw6YCqIg.png" /></figure><p>Written by: <a href="https://www.playerresearch.com/team/megane-lacroix/">Mégane Lacroix</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e05aa2302df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting More From Usability Testing Your Game]]></title>
            <link>https://playerresearch.medium.com/getting-more-from-usability-testing-your-game-c87662065531?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/c87662065531</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[video-games-industry]]></category>
            <category><![CDATA[games-user-research]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Wed, 17 Feb 2021 15:55:04 GMT</pubDate>
            <atom:updated>2021-02-17T15:55:04.145Z</atom:updated>
            <content:encoded><![CDATA[<p>Usability testing is <em>the most powerful</em> tool in the toolbox for game design improvement.</p><p>Getting real players interacting with your prototypes <em>early and regularly </em>in development can be uncomfortable. Yet it ensures teams are never out-of-touch with where design implementation is falling short, or headed for a design dead-end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ktQmNgV8J56wUx2O3dj5DQ.png" /></figure><p>The usability testing exercise is able to discover new design flaws and actionable improvements on the topic of a game’s ease-of-use.</p><p>By maintaining a laser-focus on what players <em>do and understand </em>it leads to game-changing insight into foundational aspects of the play experience: controls, UI, instructions, audiovisual feedback, learning curve, and so on.</p><h3>What makes a usability test work?</h3><p>Decades of usability testing have established a standardised process for how they run. The approach is adaptable enough for any genre of game, but is standardised enough to know what types of data can be expected, and how accurate that data will be.</p><p>Here’s a breakdown of our usability testing standard:</p><p>A usability test always involves a member of the public — a ‘playtester’ — playing a prototype game.</p><p>Typically between 6 and 12 playtesters are invited for perhaps 90 minutes per person, one-at-a-time.</p><p>Playtesters are invited to “play as you would normally” and directed to a game mode that’s in design flux. They might be asked to ‘think out loud’ while playing.</p><p>A trained researcher moderates the session to gather behavioural data describing <em>what the player did</em>, in context. The researcher will also run a question-and-answer session with the player to establish <em>why they did that.</em></p><p>These observations and questions are in service of design improvement:</p><blockquote>Does this prove players will comprehend our game?</blockquote><blockquote>Does our design reliably nudge players toward the fun?</blockquote><blockquote>Can players use the controls and UI in every scenario?</blockquote><p>Each aspect of the prototype design has some desired outcome in players’ comprehension of game scenarios and players’ behaviours. Afterwards, with all notes from all 6-to-12 sessions in hand, teams ask themselves:</p><blockquote>Are we OK with our designs generating these observed outcomes in players? If not, what’s the design fix?</blockquote><p>Each usability test is short, focused, and iterative, usually taking 3-to-6 workdays. These rapid quality-checks are repeated sprint-to-sprint to re-test redesigns and new content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7hg7U02JnLthpv0H4po8w.png" /></figure><h3>Perfecting your usability testing</h3><p>While the logistics of a usability test can sound simple, there are tough strategic choices to make to get the most from each test:</p><p><em>What do we test first? Which playtesters should we invite? How often do we repeat tests?</em></p><p>Let’s dive into some tips for running insightful and rigorous sessions, and get the most from usability testing.</p><h4>Formalise your ‘success factors’ for the first-time player</h4><p>Teams will have objectives for what a new player will quickly understand.</p><p>Most video games act on these objectives by including a tutorial or pre-formulated play. But even games where players are ‘thrown into the deep end’ will have expectations for what’s easy or hard to learn, even if they are unspoken: WASD to move; zombies come out at night; starvation kills you quickly; hitting a tree gives wood…</p><blockquote><em>Usability testing helps make these learnability expectations explicit, and then tests against them.</em></blockquote><p>Before your usability tests, forge a list of ‘Things the player is supposed to understand in the first minute’, then -5 minutes, then -15 minutes, and so on.</p><p>Against each thing, note if that knowledge will be <em>explicitly taught</em> or hoped to be somehow <em>intuitive</em>.</p><p>Against each thing again, consider if there are unique in-game behaviours that indicate players <em>probably</em> correctly understand each.</p><p>An example:</p><blockquote>“Inventory: In the first <strong>five</strong> <strong>minutes</strong> players will be <strong>explicitly told</strong> that they can hold 2 items maximum in their Quick Item Bar; we’d <strong>expect to see</strong> them ‘trading up’ as they find more valuable items later.”</blockquote><p>This becomes a checklist for observing your usability testing session</p><p>If playtesters cannot explain to the researchers how these mechanics work, or they don’t exhibit your target behaviours: your teaching isn’t working and it needs a fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8e7NliXw6T6EsrdLbeq6Og.png" /></figure><h4>Identify which mechanics are unclear by design</h4><p>Following on from above. Tutorials usually aren’t proposed to teach the player <em>everything</em>.</p><p>Every title has a unique threshold between teaching<em> enough for the basics</em>, and not so much to<em> ruin players’ fun of learning</em> through experimentation.</p><p>Defining that threshold is valuable. It requires teams to decide on mechanics, systems or strategies that are OK to be misunderstood or unrecognised by players, despite being exposed to them.</p><blockquote>Learnability is ‘under the microscope’ in the usability test lab. We must have a sense of what’s a pass or a fail.</blockquote><p>The prime example here is anything ‘metagame’ or associated with longer-term progression. Players need a more playtime to grok the ‘loop’.</p><p>Teams will need to be comfortable with playtesters demonstrating a weak understanding. And will need to be resilient to feedback that these elements “need more tutorials” or “this is confusing”.</p><h4>The value of a newcomer</h4><p>Playtesters are selected anew for each round from the general public. But they should never be just some random person or volunteer. Choosing the ‘profile’ of the playtester is paramount to avoiding wacky and misleading insights.</p><p>The most important elements to inviting the right people to playtest is their genre experience, platform experience, and recent game purchases.</p><p>Why these factors?</p><p>When testing the quality of your game controls, you don’t want to be handing the player a gamepad they’re unfamiliar with. Imagine the misleading conclusions one might come to, as your Xbox-savvy playtester repeatedly fails to complete a task, but unbeknownst to you are simply unsure which gamepad button is square or circle. Imagine the same scenario for a VR novice, or on a keyboard and mouse for a player used to a laptop trackpad.</p><p>We have to know playtesters’ platform experience for context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*umkuwScND-3PWWD6cMFvIQ.png" /></figure><p>The same is true of genre experience.</p><p>It’s not hard to imagine a genre-newcomer being utterly bewildered, compared to a genre-super-fan breezing through early game content. Parsing out what’s their <em>pre-existing </em>genre knowledge, versus what the game successfully <em>taught</em> the player afresh, is extremely difficult if you don’t control the player’s profile.</p><p>The balance to find is simple: select specific playtesters with minimum knowledge enough to be at ease, but not so much knowledge that your tutorials are folly. Seek out those members of the public who’ll really put your usability to the test, not those who’ll breeze through regardless. Simply ask about their most recent purchases or favourite games in related genres. There won’t always be a total overlap between <em>your ideal test participants</em> and players in the centre of your game’s <em>target audience.</em></p><p>Bringing in genre-newcomers — folks who have played fewer games than your average fan — means specifically searching outside your community fanbase who would likely volunteer to test for free. That also means paying playtesters for their time.</p><h4>“Is it Fun?”</h4><p>Of course this is the number one question, top of every team’s mind.</p><p>Closely followed by:</p><blockquote>“Is our game better than [genre leader]?”</blockquote><blockquote>“Would they buy it?”</blockquote><p>One of the major drawbacks of usability testing is how unsuitable it is for establishing a top-down, holistic view of the game’s ‘fun factor’.</p><p>Four reasons why: playtesters, sample size, environment, and timing.</p><p>With only 6 to 12 players involved there’s simply <em>not enough people</em> involved to get a strong enough read. If there’s an overwhelming consensus (all 12 players say “level 3 is terribly dull”) then that’s a good indication there’s a problem, but opinions are rarely so stark. Rigorously polling for <em>opinions</em> requires at least <em>double</em> the usability test norm: 25 to 35 players minimum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPqihhTQEsHdF2RVWhF57Q.png" /></figure><p>The usability testing <em>environment</em> itself isn’t suited to these types of ‘make or break’ questions either.</p><p>A skilled interviewer will quickly build rapport and draw the truth from playtesters. But if you ask: “would you consider buying what we’re selling, once it’s finished?” don’t expect the truth in reply. Out of courtesy or naivety, players will imagine the game being a thousand times better “once it’s finished”.</p><p>And that leads us to the most important factor: how usability tests should fit into the devcycle.</p><p>These tests improve the foundations of UI, controls, HUD, feedback — these are all typically solidified long before there’s much fun to be had. Certainly long before the build will compare favourably against the released titles that your playtesters will be using as their reference point.</p><p>Tackling ‘fun factor’ head-on is ill-advised during usability tests — wrong people, wrong place, wrong time and wrong question. Yet, a game with poor learnability or usability is rarely pleasant to play. Usability tests make games more enjoyable, even if seemingly indirectly.</p><blockquote>Less “was it fun?”, more “could players get to the fun?”</blockquote><h4>Have a ‘next test’ question bucket</h4><p>Each usability testing session tends to open a Pandora’s Box of new questions, concerns, insights and opportunities.</p><p>Watching user testing sessions as a group is incredibly valuable for this. Purpose-built playtest labs will include a soundproof observation room to keep devteam conversations flowing. A video livestream and a groupchat is the next best thing during social distancing.</p><p>A 90 minute session is typically 10 minutes of briefing the playtester and paperwork, 50 minutes of uninterrupted play, 25 minutes of 1:1 interview, and 5 minutes of wrap-up.</p><blockquote>With sessions booked back-to-back, every interview question becomes precious use of time.</blockquote><p>There is always a request for the moderator to “ask this player [XYZ]!” in the moment. A skilled facilitator will strike a balance: mainly following the interview script to capture answers comparable across <em>all</em> playtesters’, versus formulating new questions <em>specific to this player</em> or exploring unforeseen issues: going off script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8e7NliXw6T6EsrdLbeq6Og.png" /></figure><p>To help with this balance, ensure there’s a way to capture questions for the <em>subsequent</em> round of research.</p><p>A spreadsheet or chat channel to dump questions in, such that everyone involved can feel heard and have their concerns addressed in time, but without derailing the testing in progress.</p><p>And because usability testing can be scary and occasionally uncomfortable for the team, these ‘next test’ questions become a welcome reminder of a gain that’s worth the pain of doing this all again.</p><h4>Design Some Representative Scenarios</h4><p>Usability tests are designed to demonstrate natural play. Some UI design challenges can, however, sometimes only occur in uncommon or extreme situations that don’t arise in the short playtest sessions.</p><blockquote>Only letting the usability testers roam freely might not expose nuanced design weaknesses.</blockquote><p>To ensure playtesters are exposed to sensitive designs, it’s common to generate some scenarios for them to complete. For example, during usability testing on a third-person building game, we asked the playtesters:</p><blockquote>“Could you try and build a big McDonald’s ‘M’, on some flat ground?”.</blockquote><p>This activity forced players into a series of known-difficult steps: making curves, choosing a specific colour to build with, building above the characters’ head height, and so on. All in one elegant and intuitive instruction.</p><h4>Build a basic research repository</h4><p>If you can find the brainspace between iterations of your usability testing (!) spend some time capturing some metrics on how playtesters performed.</p><p>For example, if you’re building a series of ‘session goals’ or scenarios as suggested above, it’s worth tracking how game design pass/fails or errors change round-to-round.</p><p>Tracking the time taken to reach a major in-game milestone, or number of failed attempts, or number of total ‘high priority’ issues encountered on average: all valuable metrics. In doing so you’re plotting the game’s gradual improvement — and the positive impact of the research studies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7hg7U02JnLthpv0H4po8w.png" /></figure><p>Video recording the usability testing sessions is a staple action, but taking the extra step of <em>storing and categorising </em>the recordings in Sharepoint, Confluence, Trello (or whatever you use) is worth the time saved digging through old files, should you want to review them again.</p><p>There is an emerging field of expertise in the building of these ‘research repositories’.</p><h3>Summary</h3><p>Getting new players in front of your video game prototypes is a powerful and inspiring exercise. Setting goals. Observing players at play. Iterating design.</p><p>There’s a true craft to streamlining every aspect of the process: minimising bias, ensuring playtester comfort, and maximising the value of the insights you gain.</p><p>If you’d like to read more about perfecting testing, check out Player Research’s article on how to make participants comfortable when you invite them to your studio: <a href="https://www.gamasutra.com/blogs/SebastianLong/20170221/291752/What_Should_a_Playtest_Smell_Like.php">What Should a Playtest Smell Like?</a></p><p>For even more, here’s a <a href="https://www.youtube.com/watch?v=Za6JkzJfrTo">fantastic talk on ‘success factors’</a> from Glu Senior Researcher Sara Romoslawski , and ArenaNet’s John Hopson penned an article on exactly <a href="https://www.gamesindustry.biz/articles/2019-10-29-why-i-hate-fun">why it’s troublesome to ask players “is it fun”.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B44dLDjVnMMEmBXwV0HF4Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c87662065531" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Games User Research Methodology Series: Concept Tests]]></title>
            <link>https://playerresearch.medium.com/games-user-research-methodology-series-concept-tests-4875ec8ec5b8?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/4875ec8ec5b8</guid>
            <category><![CDATA[games-user-research]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[concept-testing]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Thu, 14 Jan 2021 17:38:18 GMT</pubDate>
            <atom:updated>2021-02-11T10:29:28.958Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljgotw0Yfa6vgK5EIy9nsA.png" /></figure><p>Video game ‘<strong>Concept Testing</strong>’ is a research approach, specifically tailored for the games industry, to explore <strong>design direction</strong> very early in development.</p><p>It’s a solution for teams wanting to reality-check their game ideas, and be more informed in making big decisions surrounding potential products.</p><p>Each development and publishing house has their own take on assessing potential game concepts. Understandably those insights usually surround funding:</p><blockquote>Is this a game idea worthy of our effort, time, and money?</blockquote><p>But Concept Testing — using real players — has the potential to deliver plenty more: discovering useful insights about your future audience, and seeding novel game ideas by learning about players’ frustrations and unmet needs. If ‘purchase intent’ and ‘uniqueness’ are allowed to be the entire focus of an early-stage research, then it’s a missed opportunity.</p><p>In their embryonic state these first-playables, greybox prototypes, even moodboards or visual target footage: they’re the foundations of the player experience being forged.</p><blockquote>This is where the power of understanding your player is at its most potent.</blockquote><p>At its core, Concept Testing is the act of getting a group<strong> </strong>of <strong>representative players to give useful feedback on assets</strong> that are indicative of new game ideas, all in a low-bias and secure environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92OEEKNYFETBXyNjsM1t8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7itsoYd3e_8UHDdxRPMutg.png" /><figcaption>Sample slides with quantitative (left) and qualitative (right) feedback. We always ask the mix of both types of Qs to probe not only <strong><em>whats </em></strong><em>, but also </em><strong>whys</strong>.</figcaption></figure><p>We tailor our approach to Concept Testing on a per-title basis, maximising the insights that can be gotten from players, including:</p><ul><li>Informing novel design</li><li>Prioritising potential features</li><li>Ranking and rating visual styles</li><li>Digging into what defines target audiences</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*l6CfGloY5hiCfDD0i6jMzg.png" /></figure><blockquote>Concept Tests can greenlight and inspire design pillars, feature priority, clarify target audiences, and more.</blockquote><h3>Product Vision &amp; Risks</h3><p>The first step in organising a concept test is a workshop among researchers and stakeholders. The first discussion: “What assets could we utilise to communicate our game ideas to players?”.</p><p>From our experience, the assets we know work well include:</p><ul><li>Concept art (characters, levels, setting)</li><li>Videos (gameplay, trailers, world-setting)</li><li>Gameplay prototypes (white box or more developed)</li><li>Branding assets (logos, descriptions)</li><li>In-game menu mockups</li><li>In-game stills (with or without UI)</li><li>Narrative outlines (neutrally worded)</li></ul><p>Next discussion: “What else could we learn about our future players, that might push our concept ‘over the horizon’?”.</p><p>The answers here are unique to every project and every audience. A good starting objective is to learn about comparable games players <em>haven’t </em>loved, or <em>didn’t stick</em> <em>with</em>. Ensuring future development doesn&#39;t fall into the same traps.</p><p>A Concept Test’s objectives are built around these facets: exploring what teams <em>want to show</em> and what teams <em>ought to know</em> before committing to design direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*rynvVCDHIMh6DOy4Z5NeVg.png" /></figure><blockquote>Purpose-built labs help ensure responses are unique to each participant: their genuine thoughts, uninfluenced by others.</blockquote><h4>Asking The Right Questions</h4><p>Games user researchers are expert in taking assets, questions and topics into building a survey or interview guide.</p><p>A structured questionnaire can carefully explore game assets or ideas one by one — setting, theme, character art, proposed features, and more — unrolling the concept progressively to gather detailed feedback on each aspect of the game.</p><p>Quality question-writing ensures we learn whether a game concept appeals to the target audience, but also <em>why</em> it <em>is</em> or<em> is not</em> appealing. A quality survey considers the <em>order</em> in which content is revealed; progressively rolling out different aspects of the game to gather actionable, accurate feedback about each element in turn. And because people <a href="https://dictionary.apa.org/order-effect">innately prefer the first and last things they see</a>, there’s randomisation in the survey too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*HnZ_7aJs9QH-JPn025SHgw.png" /><figcaption>The actual assets presented will be defined by what you need to discover, and what assets you have available.</figcaption></figure><blockquote>We always use a combination of quantitative and qualitative data.</blockquote><p>It’s good research process to gather a mix of quantitative. Rating scales to measure participant sentiment, and qualitative free-text fields for participants to give us rich, contextualising responses in their own words.</p><p>Interviews or discussion groups can be run to collect additional qualitative, conversational data, but only<em> after</em> individual participants have already given their own responses.</p><blockquote>The aim in a Concept Test is to gather individual responses and compare them, not capture a vanilla-flavoured consensus of the group.</blockquote><p>Other forms of influence are mitigated: players shouldn’t feel lead by the opinions of others around them,<strong> </strong>for example in focus groups where ‘<a href="https://en.wikipedia.org/wiki/Groupthink">groupthink</a>’ is strong. Assets are presented without grandiosity, culling anything that feels like a sales pitch or hyperbole. Where possible, we’ll remove the development studios’ name, to avoid the ‘<a href="https://en.wikipedia.org/wiki/Halo_effect">halo effect</a>’ or fan service.</p><h4>Running a Concept Test</h4><p>A concept testing session invites groups of participants from your target audience(s) to our custom-built playtesting labs.</p><p>As with all in-person research, participants are sought from the general public, screened to match the target audience. The most important criteria for checking playtesters is their game genre experience, and their prior purchases of similar titles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ebmFe2LnNX8_iYyGw24qXQ.png" /><figcaption>Playtesting in-person isn’t possible in a pandemic, but Concept Testing can be run remotely too.</figcaption></figure><p>Our goal in a Concept Test is to gather <em>subjective</em> feedback: opinions and feelings towards a game. And with that data, to identify meaningful trends across the whole group’s opinions.</p><blockquote>We recruit a sample of no less than <strong>30 participants </strong>for each defined target audience.</blockquote><p>Why 30+? This is a balance of research rigour and practical value. Existing academic research and our own experience highlights ~30 as the ‘Goldilocks’ of sample sizes, when seeking data on opinions.</p><p>This line-in-the-sand means researchers and stakeholders can build confidence in the conclusions from the group’s data. That it is likely-enough to be applicable across the whole audience, such that they can reliably make decisions informed by the insight. <em>Fewer</em> would be misleading, and <em>more</em> risks being both superfluous and expensive.</p><p>When comparing multiple different audience profiles, we recruit larger numbers in multiples of ~30.</p><h4>Making Sense &amp; Making Changes</h4><p>The next step sounds simple: make some sense of all this structured feedback.</p><p>Researchers carefully <em>read and analyse every response</em> from every participant, looking to identify trends and recurrent themes relevant to the research questions. Categorising and compiling using our specialist analysis software.</p><p>It’s a process that takes several days to complete, even with years of experience, templates and time-tested approaches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*BKUqSS0b7vwW4kq1ELk9Kg.png" /></figure><p>Compiling these patterns into a report, along with our own commentary, context, and data visualisations, takes another few days.</p><p>The result: Detailed feedback on each asset or feature that captures players’ first impressions, combined with the ‘why’ that lets teams react to (or ignore) feedback in confidence.</p><p>Furthermore, deeper-dives into future players’ wants, needs, and potential opportunities for diversification: fodder for design inspiration to drive the game design beyond what exists today.</p><h3>Misusing Concept Testing</h3><p>This approach of exploring a target audience in detail, and presenting game assets in turn, isn’t a ‘silver bullet’:</p><h4><em>Finding</em> a target audience</h4><p>The old adage ‘a solution in search of a problem’ is true for video games. Bringing in random people to ‘see who sticks’ is an approach best suited to soft launch, click-through tracking, or somehow else casting a wider net. Concept Testing is for clarifying a defined audience’s opinions, and validating your assumptions about their attitudes.</p><h4>Predicting future behaviour</h4><p>People are poor predictors of their future behaviour. It’s tempting to ask these players to predict future behaviour in Concept Tests —<em> “will you play this game? Will you spend in this game?”</em> — but it’s data that can forge false confidence.</p><h4><strong>Learnability, onboarding or balancing</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*H7wRwnvfM7S-WYR1urX4Bg.png" /></figure><p>Concept Tests typically won’t give much useful information on the game’s usability, learnability, onboarding. These are best suited to studies rooted in detailed observation of play.</p><h3>Conclusion</h3><p>A Concept Test is an effective method to feed player data into early game design direction. It goes beyond asking players “is this a good game’?”— delving into the ‘why’ or ‘why not’ of player’s subjective impressions.</p><p>They allow team to make more informed decisions on where to go next with your game concept — what to prioritise, what to adjust, and even whether a concept should be set aside entirely. Each led by rigorous research.</p><p>Concept testing fits nearly into a wider picture of research in the dev lifecycle, as part of a mixed-methods strategy that ensures player data is used throughout development.</p><p>See our other articles for more information about games user research and the other games user research methods to employ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*oJ66Yjg6fhTunZg-qxBIgQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4875ec8ec5b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Junior vs. Senior Games User Researchers]]></title>
            <link>https://playerresearch.medium.com/junior-vs-senior-games-user-researchers-78f71d94992?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f71d94992</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[games-user-research]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 12:54:44 GMT</pubDate>
            <atom:updated>2020-10-23T12:54:44.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDHyYd45T68_XqpWN6iDvw.png" /></figure><p>How can you recognise where you are on your career journey as a Games User Researcher?</p><p>In the world of games ‘user experience’ (UX) there are a multitude of roles, including UX Researchers, UX Designers, UX/UI Designers, Insight Specialists, and Game Analysts… to name a few.</p><p>Their day-to-day activities overlap in some areas, and differ in others.</p><p>The ways in which one develops ‘seniority’ in a role are equally diverse. What skills make a ‘senior’ versus a ‘mid-’ versus a ‘junior’? Why do experienced staff have greater value and earn more money?</p><p>Let’s shed some light on the differences between ‘junior’ and ‘senior’ Games User Researchers by reflecting on major shifts in <em>how they see the world</em>, rather than defining them by years of experience. For insights about designers try this article, which also inspired the format we use here: <a href="https://vanschneider.com/junior-designers-vs-senior-designers">Junior designers vs. senior designers</a> by Tobias van Schneider.</p><p>What makes a ‘junior’ or a ‘senior’ researcher?*</p><p><strong>One asks how much time do I have to find out?</strong></p><p><strong>The other suggests own timeline, taking into consideration the research rigour and the development schedule.</strong></p><p>In most cases the game development process is peppered with milestones and deadlines. It’s important for the research team to capture and communicate insights on features before the dev team runs out of time to implement them.</p><p>Senior researchers understand deeply that the earlier insights are delivered, the more likely the game creators will be able to respond to them, and see a positive return on investment of research.</p><p>At the same time, a senior researcher knows when it’s ‘OK’ to compromise, and when it’s not, in order to keep research results reliable. Sometimes finding a common ground is not easy and requires smart compromises and diplomatic skills.</p><p><strong>One asks for the method that is wanted.</strong></p><p><strong>The other asks for results that are needed.</strong></p><p>Researchers are often asked to perform a certain method on a game (commonly: focus groups), and a list of research questions is delivered to them. However, those two are not always in line!</p><p>Senior researchers try to help stakeholders understand pros and cons of every method available and decide together on an ideal research approach.</p><p><strong>One addresses the research questions handed to them.</strong></p><p><strong>The other explores beyond and in-between them, and envisions a wider research strategy for the title.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*1aFOsXuzqR--azSNRhDpoQ.png" /></figure><p>Focusing on the team’s immediate questions is what is expected from researchers and this is undeniably a crucial part of the job. But there’s more to it…</p><p>Consulting with stakeholders to break down and understand their fundamental problem space, then collaboratively identify and prioritise the questions — that’s a true challenge, which, when overcame, often results in forming a long-term research strategy for the title.</p><p>Considering how time and money consuming research projects could be, helping to find the perfect balance between time, money and scope of the project is one of senior researchers’ key superpowers.</p><p><strong>One tries to <em>design</em> solutions for gameplay problems.</strong></p><p><strong>The other tries to <em>define</em> where the problems come from.</strong></p><p>In many cases research reports include some suggestions for design fixes or UI alternatives.</p><p>The researcher’s role<em> is not to design</em> the whole solution, or inject themselves creatively — that’s a game designer’s or UI artist’s job.</p><p>Researcher’s expertise <em>is useful to define</em> a good fix, after making the causes and effects of the issue clear. The main goal is to help designers to create a solution that acknowledges cognitive limitations of people’s minds, Human-Computer Interaction principles and proven best practices.</p><p><strong>One delivers the findings and moves on.</strong></p><p><strong>The other keeps track if they were well-understood and supports the team also post-research.</strong></p><p>Research does not start on the first day of playtesting and does not end when the report is delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*M5dQPW_PALc3JFwBpJr4DA.png" /></figure><p>Senior researchers maintain communication with the dev team also post-research and pre-the-next-phase-of-the-research, having in mind what is the crucial part of every conversation: <em>making sure to be heard and understood</em>.</p><p>The time between projects is equally important for the research team, and can be used to keep research repositories updated, to maintain a log of key product risks and simply prevent organisational chaos by keeping things up to date.</p><p><strong>One says ‘the player isn’t taught’.</strong></p><p><strong>The other considers the value of learning.</strong></p><p>Less-experienced researchers tend to see playtester’s every misunderstanding highlighted in the study as a friction that needs to be removed.</p><p>But expecting players to understand and remember everything they see right away is an unrealistic goal.</p><p>To paraphrase Raph Koster — learning is fun, and fun is learning.</p><p>Experienced researchers understand that learning happens not only through tutorials, and that learning sometimes takes time and requires multiple attempts.</p><p>It’s a senior researcher’s role to help teams set realistic learning goals, and the plan for teaching game rules.</p><p><strong>One motivates findings with personal sentiments.</strong></p><p><strong>The other understands their personal opinions are irrelevant.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OjSK1e3pKCxNriek5Zbm3g.png" /></figure><p>Sometimes junior researchers will let personal opinions and assumptions slip into their reports. For example, they might say ‘I like the art style’ or ‘I don’t think players would skip the tutorial <em>(I wouldn’t)’</em>. Other times teams will ask for a researcher’s preferences: ‘but what do <em>you</em> like?’</p><p>While researchers might be justified in providing reasoned expert analysis of game usability, the subjective feelings about the game should not be reported without solid data from the target audience. Attitudes, emotions, and opinions are inherently subjective and extremely variable, making it very difficult to accurately predict them. Attempting to do so without good data can provide the dev team with specious and misleading ‘insights’ and priorities.</p><p>Refraining from giving personal opinions and saying ‘no’ to some questions is a core skill of experienced researchers, and it is a tough one to master.</p><p><em>*It should be noted that terms ‘junior’ and ‘senior’ used in this article reflect a broader convention in naming roles but position names and their definitions vary between studios. Above statements </em><strong><em>should be treated as guidelines </em></strong><em>for researchers, not as an unequivocal dividing line, which, most likely, doesn’t exist.</em></p><p>Written by <a href="https://www.playerresearch.com/team/ula-karpinska/">Ula Karpińska</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f71d94992" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Debug UI Ruins Game Design (and what to do about it)]]></title>
            <link>https://playerresearch.medium.com/when-debug-ui-ruins-game-design-and-what-to-do-about-it-9e8f61ca79ab?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e8f61ca79ab</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[gamedev]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Tue, 21 Jul 2020 11:52:48 GMT</pubDate>
            <atom:updated>2020-07-21T11:52:48.649Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the quintessential hallmarks of a ‘work in progress’ game is <strong>debug text</strong>. Floating gibberish flickering in the foreground of gameplay, occasionally catching your eye with an <em>&lt;ERROR&gt; </em>or a ‘<em>Missing_Texture’.</em></p><p>Thinking about the <em>design</em> of debug UI seems like misspent time. It is, by its nature, only to be used by our development team, and never to be seen by our eventual players.</p><p>Why spend more than a single moment considering practicality, or utility, or legibility of UI destined for the trash?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*SdmH4UC4LucPTktaZfr1bA.png" /></figure><p>And so, when in a recent UI design workshop I proposed a re-thinking of a prototype’s <em>debug text</em>, it raised a lot of eyebrows.</p><p>The studio’s creative team are sprinting on a fast-paced PC multiplayer game, with a range of arcade-y game modes. The internal dev play-sessions were finding loads of fun; the game was starting to shine and the team were in great spirits. But, in my visit on-site and peering over devteam shoulders to watch them play their prototype, it was clear that something was awry.</p><p>Multiplayer prototypes are almost always fun. Performing nearly any competitive activity with friends is fun; it makes player research on multiplayer games really tough. But it was clear in watching these sessions that the game the creative team had just described to me in the meeting room, and the game I was watching unfold in these play-sessions, weren’t one-and-the-same. Both were fun. But they weren’t the same game.</p><p>After a little thinking I find an unusual culprit: <strong>the debug text.</strong></p><p>The devteam were so used to the verbose debug output scrolling past on-screen that no one gave thought to turning it off during the play-sessions. It was part of the fabric of the prototype: that green floating text <em>belonged </em>there.</p><p>But, with a keen eye, it would reveal information that was designed to be unknowable or obfuscated: the <em>exact </em>status of the enemy team’s win condition, your units’ <em>exact </em>health remaining, the <em>exact</em> damage done in an exchange of fire, and undoubtedly several other variables from ‘behind the curtain’.</p><p>And of course that data was being used by the devteam to find an advantage and beat their colleagues. It was being used to win.</p><p>Consciously or unconsciously, the devteam were <strong>playing a game within their game</strong><em>. </em>A nerdier, more tactical, <em>more complex </em>version of their designed experience.</p><p>And in highlighting this at the design consultation workshop, I saw the flash of realisation behind a few eyes at the table. Uncertainty crept into the room.</p><blockquote>Which game was fun? The game design they’d imagined, or the stat-heavy game living inside it?</blockquote><h3><strong>The Oxymoron of <em>Designing The Placeholder</em></strong></h3><p>It’s clear that debug and placeholder UI doesn’t deserve <em>too much </em>thought. Certainly this devteam could have saved a lot of heartache and reviewing of their decision-making if they’d just thought to <em>turn off everyone’s debug readout. </em>Trust me when I say it’s one of those ‘obvious in retrospect’ moments.</p><p>But there’s no denying that placeholder UI will inform a player’s opinion and experience of gameplay. During internal play-sessions and user testing those placeholders and readouts will inform how players play and the strategies they use. As the devteam above found out: just because there’s no <em>final UI </em>doesn’t mean that the <em>placeholder UI</em> isn’t affecting the player experience.</p><p>So teams have the impossible task of quickly throwing together a UI that is somehow analogous to the final UI in various ways, is quick to implement, versatile to change, suitable for internal play-sessions and showcases, but also supports the team’s various technical needs for development.</p><p>Here are a few ideas and practices to help make early placeholder UI as effective as possible — particularly when you’re running early playtests and internal play-sessions — and avoid game design being accidentally undermined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*NZtgS0QZt1gn4m1H-bzrbA.png" /></figure><h4><strong>Design Ambiguity In</strong></h4><p>Variable readouts provide an ever-present and<strong> exact</strong> readout of some game variable that’s otherwise unknowable. It’s typical that placeholder UI is therefore numeric, specific, and persistent:</p><blockquote>99<strong> </strong>HEALTH</blockquote><p>In contrast, final game UI often trades-off high specificity for rapid legibility: e.g. health <em>bars</em> instead of health <em>numbers. </em>It’ll use<em> approximations</em> of distance, time, or cool-down. And show information <em>only while relevant</em> to decision-making.</p><p>Like so many things in gamedev: The designs that are quick-to-implement are in contention with the designs that better orchestrate the player experience.</p><p>Before any internal play-sessions, discuss and set some boundaries for what information should be designed as <em>accurate </em>and <em>slow to read </em>versus information that is <em>approximate </em>and <em>fast </em>to utilise by players. Perhaps you’ll find some justification to reduce the displayed accuracy of gamestate variables in your prototype, or change the way they’re presented to use symbols or simple visualisations instead of text.</p><h4><strong>Embrace Non-Visual Feedback Early</strong></h4><p>One of the easiest ways to get information out from ‘behind the curtain’ is to print text to screen. This really biases teams toward visual and alphanumeric presentation of information. Video games are primarily a visual media; a fair amount of the ‘experience of play’ can be defined by <em>what the player looks at on the screen. </em>So it’s important to control which attention-grabbing activities are permitted to be shown.</p><p>Consider how <strong>simple sounds or haptics</strong> could be used instead of a visual readout, and if they might be less interruptive, or more reflective of the final experience.</p><p>Using auditory, haptic or otherwise non-textual communication allows teams time to find the ‘game language’, and get it in front of players earlier. For an example of the value here, check out this thread on the <a href="https://twitter.com/Anghil/status/1278808690053668864">iterative process that forged an all-auditory whistle-language</a> used by The Last of Us Part 2’s Scars (mild spoilers).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Bd8Jj_If4mSSGNJZka4aFQ.png" /></figure><h4><strong>Start With Less</strong></h4><p>I propose that it is a greater risk associated with presenting <em>too much</em> information than presenting <em>too little </em>with your early prototype. Especially if most of that information is in text.</p><p>Anecdotally, it’s easier to persuade folks on the value of an <em>addition</em> of information than <em>removal</em>; playing the game day-in-day-out quickly leads to reliance on the information we’re presented. Moreover, understanding the impact of an interface design <em>addition</em> is a lot easier if you’ve got historical playtest data from <em>before you added it.</em></p><p>That said, this exists as a serious approach: <em>“The Scream Test” </em>of taking features away, and waiting to see if-and-why you get an earful from your colleagues or players, therein a metric for how much a feature is really used.</p><h4><strong>Get Everyone On Equal Footing</strong></h4><p>Like Neo in The Matrix, there are going to be some folks in-studio who can ‘see the code’ as they’re playing, to their benefit during play-sessions. Hopefully your internal play-sessions are including a wide variety of devteam members, including those that are not technically involved with the ins-and-outs of the project.</p><p>If placeholder UI is needed, make sure it’s labelled and clear, and not using in-game jargon. If <em>one person</em> is using that information for an advantage, that’s not OK. If <em>everyone </em>is using or abusing some information in-game, that’s at least consistent, and should be reflected in the feedback you capture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Au3SSZe9LbaDrYt2IMPKWQ.png" /></figure><h4>A Layer of Lies &amp; Illusions</h4><p>As noted above, debug is meant to be accurate; by definition then it’s also meant to be <em>true. </em>But certainly there is a place for lies and half-truths in displayed information.</p><p>The Apex Legends team recently shared how their internal play-sessions used <a href="https://www.gamesradar.com/uk/respawn-used-fake-names-and-disabled-voice-chat-to-test-apex-legends-amazing-ping-system/">fake player names and disabled voice chat</a> to focus improvement on their in-game ping system: you can imagine that having colleagues’ names in their internal play-sessions undermined their ability to emulate random players squadding-up online.</p><p>Consider if adding a layer of fakery or obfuscation — designed to emulate real play, or gameplay depth that doesn’t yet exist— could somehow improve the feedback you’re getting.</p><h4><strong>Toggle Everything Off</strong></h4><p>Ensure you’ve got the ability to quickly turn off any technical readouts once you’re seeking feedback on ‘fun’.</p><p>Our research teams are constantly putting real players in front of prototypes. It’s not uncommon for the playtest built to have retained some backend-only readout like a framerate counter. Even if part of the playtester’s briefing is to ignore that element (“it’s not part of the test!”), it will nonetheless grab player’s visual attention, and risks dragging them out of the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*ykSHHTejYnj9FG5dcbRBKA.png" /></figure><h4><strong>Eye-Tracking Can Reveal UI Usage</strong></h4><p>The ability to see where players are affixing their eyes in real-time is transformative for understanding how players use UI-heavy games. Eye-tracking has even been used to train eSports professionals to manage their attention and minimise ‘poor’ gaze behaviour.</p><p>Researching UIs with eye-tracking can show how players are using (or not using) UI. It’s best used for assessing individual UI elements and gameplay scenarios, and can be utilised for player research on placeholder UI.</p><h3><strong>So, Which Was Fun?</strong></h3><p>Thinking back to the playsessions I’d seen affected by debug text, the team were left with a stark question: Which game was fun? The game design they had imagined, or the stat-heavy game living inside it?</p><p>The answer, of course, was: both versions. Their eventual design will end up learning from each extreme. To move forward, the team needed to separate the player-facing from the dev-facing HUD, and see what gameplay emerged, using playtesters from the public and <em>not</em> the devteam.</p><p>And of course now they’re a now a little more careful to design their placeholder &amp; debug UI…</p><p><em>Got any other best practices for placeholder UI or debug text? Got any war stories? Post them in the comments!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e8f61ca79ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Last Days of Control]]></title>
            <link>https://playerresearch.medium.com/the-last-days-of-control-cf2ae4c4f0eb?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf2ae4c4f0eb</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 13:55:07 GMT</pubDate>
            <atom:updated>2020-06-26T12:34:05.527Z</atom:updated>
            <content:encoded><![CDATA[<h4>Fine-tuning Remedy’s Award-Winning Game Design In The Playtest Lab</h4><p>Control’s final months of development in mid-2019 saw extended bursts of iteration and change. Behind closed doors in the playtest lab, Control was being played by the general public. And in the room next door, in a soundproof observation space, Researchers studied the players’ behaviour, carefully tracking all 12 playtesters, seeking evidence of their misunderstanding or misbehaviour in Control’s unsettling world.</p><p>User research sessions like these had been a staple of Control’s development, with Remedy even building a playtesting lab in their Espoo offices. And for the final months of development, Remedy partnered with playtesting specialists Player Research for larger-scale sessions and their fresh take on Control’s player experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hntuw0MY4TMFlopZR-gVNg.png" /><figcaption>Control earned 11 BAFTA nominations in 2020 (left). Player Research’s playtesting labs in Montreal (right)</figcaption></figure><p>Elise Torfs, Remedy’s User Research Specialist, explains, “We were really eager to test out some of the features and designs the team felt made the game unique, but could potentially cause the most issues for players. For example, the navigation system and the lack of hand-holding was continually of interest to the team”.</p><p>So, what did these research sessions uncover, and what did they improve?</p><p>Remedy and Player Research share some of the changes these playtesting sessions informed in Remedy’s award-winning masterpiece.</p><h3><strong>Lost In The House</strong></h3><p>‘The Oldest House’ is the players’ unpredictable and untrustworthy host. It’s a stark, brutalist, and unnerving space, in which Jesse finds the Federal Bureau of Control’s former office workers now possessed by some unknowable supernatural force.</p><p>It had been a continual challenge for Remedy to tell Control’s complex story in this unusual and changeable environment; between the eerie drifting walls, doors and hallways appearing, the building itself was hostile, changing, and held unclear motivations.</p><p>Player Researcher Jonathan Venne explains: “Remedy shared with us right from the beginning that Control was going to be this deliberately confusing and mysterious experience. They wanted to give the player a lot of space to figure things out for themselves, particularly around the layout and meaning of the Oldest House”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRCUwVAXAoxvRSHx8DjpaQ.jpeg" /><figcaption>The FBC is haunting, beautiful, and disorientating.</figcaption></figure><p>Putting members of the general public into the game ‘blind’ was the perfect test for Control’s difficult-to-navigate world. And players certainly struggled. The deliberately-disorientating corridors left some players needing explicit guidance to get them back on the right path, which served to highlight the exact moments where Remedy could choose to design in-game interventions.</p><p>“In a playtest, we often won’t step in and assist playtesters if they’re stuck or lost”, says Player Researcher Benoit Lefort, “When players spend way too long in an area, that’s something we<em> need to know</em>. Only when we feel confident we know why players are stuck will we move them on”. Seeing playtesters struggle was an essential part of the research sessions and informed how the subsequent changes were prioritised, or potentially left unchanged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWeLTbpicHSpxkaUCCHa6Q.png" /><figcaption>Remedy explored having only the in-game signs for players to navigate</figcaption></figure><p>Remedy’s Elise Torfs explains the impact players’ struggles had on the game design: “the studies really quickly identified that some objectives were worded in a way that made them too obscure, and players struggled to understand how to proceed.”</p><p>“We ended up removing some obstacles that made it hard to progress, and re-worked the language for some specific objectives”</p><p>Despite the design team’s comfort in letting players backtrack and progress without hand-holding, the playtesters’ experience wasn’t in line with Remedy’s expectations. Remedy’s Thomas Puha later <a href="https://stevivor.com/features/interviews/control-map-almost-didnt-happen-improvements-ongoing/">explained</a> :</p><blockquote>“Players were initially supposed to navigate through the Bureau only by reading the in-world signs. Once we did the playtests, it was pretty obvious the players were not finding their way, and getting too frustrated, so we finally decided to add a map. Ultimately that was the right call”.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*ksjqkLHHGtF1sKQddVkHyQ.png" /><figcaption>The in-game map added to Control</figcaption></figure><h3><strong>The Eye Doesn’t See</strong></h3><p>Elise explains, “One of the biggest changes coming out of the first study was Player Research identifying that the doors weren’t accessible to those with red/green color blindness”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBldhzReFaZbhh5fXlJlpg.png" /><figcaption>The original design for locked doors in Control (left) using red and green to signify locked or unlocked. To players with colourblindness (right, simulated) the colours are indistinguishable</figcaption></figure><p>Players would need to be revisiting areas of The Oldest House several times during their Control playthrough, backtracking with upgraded keycards to allow access into new areas. To help players wayfind and remember rooms, the level’s stark open areas were often deliberately designed with sightlines to see both open routes and locked doors.</p><p>“The original design used a single light above the door, changing from red to green when it was unlocked,” explains Jon Venne, “but the specific hues would have been impossible for colourblind players to distinguish between them. The potential wasted time for those players would have been huge”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3MLCzKw2ea22-BKD8NpAMw.png" /></figure><p>The shipped title changed the indicator design, altering from <em>one</em> light to a <em>pair</em> of lights, glowing in yellow and red, and displayed a padlock symbol under the corresponding light.</p><p>A small change with a huge impact on Control’s colourblind players’ ability to play as intended.</p><h3>Attention Please</h3><p>Remedy and Player Research’s final collaborations focused on research exploring wayfinding and players’ progression through the house, now aided by the presence of a map.</p><p>In the playtest lab, the researchers observed 12 players at once playing through the build from a soundproofed room in Player Research’s Montreal studio.</p><p>Elise explains, “In the large-lab playtests I was really able to notice some navigational issues that would later on be fixed, observing players backtrack in places that didn’t justify it, and adding my observational notes to the playtesters’ own feedback”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q-9vuKPELA4S2EisqtTeHQ.jpeg" /><figcaption>Playtesting sessions helped Remedy fine-tune players’ journey</figcaption></figure><p>Remedy made countless tweaks based on these sessions, but one particular change stuck out for Benoit Lefort. “In playtesting of the very beginning of the first level, the initial door the player approaches swings open by itself to show a security office. Inside were brightly-lit computer screens showing lines and lines of text on the green-coloured computer screens. To players those screens stood out like a beacon: demanding their attention, and promising some answers or curios. But, the computers were <em>just a prop</em>. Although players could read parts of the text, it wasn’t relevant or meaningful. It promised to be players’ first clue, but turned out to be a flop”.</p><p>In the final version of Control, the text on the computer screens was removed, instead showing clearly-legible text warning of<em> “LOCKDOWN IN EFFECT”</em> and<em> “MULTIPLE BUILDING SHIFTS DETECTED”</em>. By knowing where players would look, Remedy could capitalise on an opportunity to slot in some precious environmental storytelling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kg4eZdiRcJMrnhRc-HL1PQ.png" /><figcaption>By discovering that players would explore this specific office, Remedy removed the old computer (left) and replaced it with meaningful environmental storytelling here (right)</figcaption></figure><p>It’s this minor issue that perhaps best exemplifies the value of researching with real players like this. By paying attention to the actual behaviour of players, developers are handed a unique power: to understand the moments where player effort and attention is wasted, and correct it in design.</p><p>In the words of Player Researcher Jhim Verame: “[It’s] possible for player’s behaviour and their thought patterns to be both totally rational <strong>and</strong> totally unexpected”.</p><h3><strong>Quality Control</strong></h3><p>There are those that worry about involving players in development processes, and the ‘watering-down’ of a titles uniqueness, but it’s clear that getting Control in front of playtesters significantly changed the game for the better.</p><p>Player Research Director Seb Long explains:</p><blockquote>“The voice of Player Research really has to be carefully maintained: to focus on data that brings game design closer to the design team’s creative vision, without undermining it. To look past what players say about a game, to really look at what they do and how they think, to improve the player experience in ways only game designers can conceive. That’s a tough — yet essential — line to walk”.</blockquote><p>For Remedy, it was a natural step for them to embed playtesting into such a risky game, and align with their studio goals of “creating longer lasting games, and pursuing strong business ownership” of their creations.</p><p><em>Did you play Control? What do you think about the improvements made to the game design? Tell us in the comments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf2ae4c4f0eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should Players Buy Their Own UI?]]></title>
            <link>https://playerresearch.medium.com/should-players-buy-their-own-ui-e87694f1a25e?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/e87694f1a25e</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[animal-crossing]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 15:24:40 GMT</pubDate>
            <atom:updated>2020-04-29T18:15:21.395Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Animal Crossing: New Horizons</em> drops players onto a near-deserted island, with empty pockets and dreams of a self-made paradise.</p><figure><img alt="A screenshot from the video game Animal Crossing New Horizons. It shows a sunset over a beach, with a character in the centre" src="https://cdn-images-1.medium.com/max/1024/1*3FFSQPO0BS997nww_kntvg.jpeg" /><figcaption>Animal Crossing is a little virtual paradise — if you’re prepared to work for it…</figcaption></figure><p>For the first few hours, players are tasked with organising their new tropical home by crafting and using handy tools: spades, axes, fishing poles. Axes chop trees and yield wood; shovels unearth fossils and buried treasure. Players have to swap between tools continuously to tidy their space.</p><p>It’s a slightly laborious process to open the in-game inventory, move the cursor to your desired tool with the d-pad, and double-tap to ‘hold’, to then resume weed-clearing or hole-digging. And so, when the in-game shop is constructed, it’s a welcome surprise to find a purchasable <strong>‘Tool Ring’: </strong>a radial quick-select menu for speedy access to those essential tools.</p><figure><img alt="A screenshot from the video game Animal Crossing New Horizons. It shows the Tool Ring interface." src="https://cdn-images-1.medium.com/max/1024/1*TEkAGGcwHbWdYrDxIAzOAA.png" /><figcaption>Animal Crossing’s purchasable Tool Ring upgrade. Image from <a href="http://www.nintendolife.com/guides/animal-crossing-new-horizons-tool-ring-how-to-quickly-switch-between-tools">NintendoLife</a>.</figcaption></figure><p>It’s a radial menu: One press shows the menu, one push of the analog stick in the direction of your desired tool, then another press to select that tool.</p><p>The Tool Ring is one of several upgrades that players can buy from infamous in-game shopkeeper Tom Nook, but so far it’s the only upgrade that’s purely for <em>quality-of-life</em> rather than unlocking some new mechanic or progression.</p><p>The Tool Ring’s only job is to <em>reduce</em> the players’ need to access and scroll through the inventory to access their tools.</p><p>But until the Tool Ring is bought and unlocked by players they must use the inventory, despite it being <em>slower</em> to complete tasks, more <em>error-prone,</em> and more <em>visually</em> <em>overwhelming</em>.</p><blockquote><strong>Why would designers force players to use a clunky inventory when a perfectly good shortcut exists?</strong></blockquote><p>And to unlock this quality-of-life feature, AC:NH asks players to save up and convolutedly buy it. Surely it could just be unlocked at the beginning?</p><blockquote><strong>Why wouldn’t quality-of-life capabilities unlock for players automatically? Why should players buy their own UI?</strong></blockquote><p>Like many seemingly counter-intuitive choices in game design, the answer is: to shape player behaviour.</p><p>Let’s discuss why player experience benefits by players buying their own quality-of-life improvements like the Tool Ring in Animal Crossing, and see if this might be a mechanic that benefits your title too.</p><h4><strong>Ramping Complexity</strong></h4><p>All games struggle with teaching players, particularly those targeting audiences with little gaming experience or little time on their hands.</p><p>If games can reduce the complexity of interfaces then there’s there’s less to teach or become overwhelmed by. As such, it’s common for games to progressively reveal UI elements piece-by-piece through the first few minutes or sessions of play. This approach leads to a more gradual ‘learning curve’.</p><p>Putting the Tool Ring in the in-game store gave players that extra learning time. But also the opportunity to pre-empt its introduction: to read the written description and understand the utility of an item to be introduced later.</p><blockquote>Any design pattern that can encourage players to concentrate and absorb information has huge value</blockquote><p>Providing quick access to tools might be necessary to pacing in AC:NH, but that doesn’t mean the resulting radial menu is easy for players to understand or interact with. It’s deceptively complicated: it’s the only radial menu in the game, and is populated by tools that’re abstractly ‘favourited’ inside the inventory: one of the most visually-dense and variable menus in AC:NH.</p><figure><img alt="A screenshot from the video game Animal Crossing New Horizons. It shows the inventory interface, covered in icons." src="https://cdn-images-1.medium.com/max/790/0*-qpXV7Sa-MEiO1cs.jpg" /><figcaption>The Tool Ring avoids players having to visually scan and navigate this colourful, complex UI. <a href="https://animalcrossingworld.com/guides/new-horizons/how-to-upgrade-increase-your-inventory-space/">Image from ACW.</a></figcaption></figure><p><em>Delaying</em> the addition of complex ideas can also empower teams to introduce <em>more complexity</em> than might otherwise have been tolerated or appropriate for a given audience, had it been introduced all-at-once.</p><h4><strong>At The Player’s Pace</strong></h4><p>Progressively revealing new UI elements might flatten the complexity curve, but the cadence of unlocking would still be controlled by the <em>game</em>, not the <em>player</em>. Particularly in free-to-play, players’ first gameplay session risks being overwhelmingly prescripted to ramp from 0-to-fun as quickly as possible, sometimes leaving players without a clue what’s going on.</p><p>The Tool Ring’s introduction isn’t just delayed, it’s player-controlled. The need to <em>purchase</em> gave hours or days of space for player to grok the rest of the game first, and even then players still had to ‘opt into’ adding more complexity by <em>actively choosing to purchase </em>that item:</p><blockquote><strong>Whether players knew it or not, they were in charge of their own decision: “I’m ready for more, now”.</strong></blockquote><p>Of course there is a risk to forcing friction on players in the short-term, and relying on them to unlock the ‘true experience’ for themselves; we’ll discuss risks at the end of this article too.</p><h4><strong>Engaging with Economies</strong></h4><p>AC:NH has multiple stores, multiple currencies, and layers of challenges and goals. The intermingling of players’ self-set goals and game-world goals (aka intrinsic and extrinsic goals) is part of AC:NH’s charm.</p><p>The Tool Ring is purchased through the notably unexciting ATM machine with ‘Nook Miles’, one of the two main currencies, tied to in-game challenges and achievements.</p><figure><img alt="A screenshot from the video game Animal Crossing New Horizons." src="https://cdn-images-1.medium.com/max/1024/1*ArfK_zmmCLxfHJRTLhre7w.png" /><figcaption>Unlocking the Tool Ring from the Nook Miles ATM machine. Image from <a href="http://www.nintendolife.com/guides/animal-crossing-new-horizons-tool-ring-how-to-quickly-switch-between-tools">NintendoLife.</a></figcaption></figure><p>Any economy-bound game knows the value of encouraging players to make regular, rewarding transactions. For AC:NH in particular, having a desirable item tied to the secondary currency in the early-game ensures that the challenges for Nook Miles aren’t totally ignored.</p><p>And when players do prioritise these optional in-game challenges, they’re rewarded with something of tangible and immediate value that helps with both their self-set and game-set goals.</p><h4><strong>Shortcuts and Longcuts</strong></h4><p>The Tool Ring is a shortcut. It’s a miniature, less-capable but quicker-to-access version of the inventory.</p><p>But the inventory still has a huge amount to do in AC:NH, and players will likely have <em>more tools than can fit in the Tool Ring. </em>This shortcut is an addendum, not a replacement.</p><p>Had the Tool Ring been unlocked from the beginning, players would have engaged far less with the inventory; in contrast to the Tool Ring it’s cumbersome and slow. Could lessened use of the inventory have damaged the player experience, or player’s understanding of the game? Without playtesting both versions it’s hard to say for certain, but I’d posit that by the inventory’s nature of constantly-changing, present-containing, item-description-giving, reminders-of-collected-items—that regularly visiting the inventory has value to the player experience.</p><figure><img alt="A screenshot from the video game Animal Crossing New Horizons. It shows the inventory interface, with ‘a present’ selected" src="https://cdn-images-1.medium.com/max/790/0*75HYUBPWrINV_ccF.jpg" /><figcaption>AC:NH inventories are filled with excitement and knowledge. <a href="https://animalcrossingworld.com/guides/new-horizons/how-to-upgrade-increase-your-inventory-space/">Image from Animal Crossing World.</a></figcaption></figure><p>And so forcing players to take the ‘long-way round’ for a while leads to better understanding of the world, and the specific value that the inventory has, which lasts even when a shortcut to some actions is unlocked.</p><h4><strong>Caveat Emptor</strong></h4><p>We’ve already touched on some risks that this approach presents. Clearly putting <em>all</em> quality-of-life upgrades behind a shop purchase isn’t wise, so what’re our options and risks here?</p><p>Depending on the prominence of the in-game store, or the number of items available to buy, players simply might never acknowledge the item exists. The newest Pokémon Sword and Shield chose to have the game volume controls unlockable via an in-game item, the “High-tech Earbuds” — a design judgement perhaps motivated by the reasons outlined in this article. But the choice to unlock them through <em>talking to a specific NPC </em>meant their unlock was easily missed by players.</p><figure><img alt="A screenshot from Pokémon showing the character that provides the high-tech earbuds to the player" src="https://cdn-images-1.medium.com/max/1024/0*sa8A7bMMvI2rAF8J.jpg" /><figcaption>Pokémon Trainers had to visit a particular NPC to unlock in-game volume options. <a href="http://www.nintendolife.com/news/2019/11/youll_need_hi-tech_earbuds_to_adjust_the_volume_in_pokemon_sword_and_shield">Image from NintendoLife.</a></figcaption></figure><p>Holding back the quality-of-life improvements, be they game volume controls or avoiding extra button-presses, disproportionately affects players with impairments, in these cases withholding tools to accommodate auditory and motor challenges. There is clearly a balance to strike here.</p><p>By making it an <em>optional </em>purchase, there’s a clear risk that players don’t recognise that the unlockable will improve their experience, and therefore never invest in it. In AC:NH the Tool Ring is listed in the in-game shop as “<strong>Tool Ring — It’s Essential!”</strong>; this on-the-nose description hints at difficulties in getting playtesters to pick it out from among the other items for sale, or not prioritising it. And so depending on how ‘essential’ your upgrades really are, or how well you’re able to describe them, there’s some risk that the purchased capability is <em>less useful</em> than your promise, or <em>useful but</em> <em>ignored</em>.</p><h4><strong>Fun and Friction</strong></h4><p>Despite the Tool Ring shortcut, there’s still <em>a lot</em> of UI busywork in AC:NH.</p><p>Much of Animal Crossing’s satisfyingly glacial progression and deliberate friction manifests in menus. These good design decisions haven’t gone unpunished by players, and there are a few key interactions that are chief among players’ gripes. For example, the inability to craft consumable items like fishing bait without crafting them one-by-one, or the need to have crafting ingredients in the player inventory, despite the presence of bulk ingredient storage in players’ homes.</p><blockquote><strong>AC:NH’s repetitive UI navigation could easily be minimised. But it’s this friction that <em>shapes player behaviour </em>that makes Animal Crossing <em>fun</em>.</strong></blockquote><p>But if player feedback is heeded, and Nintendo decide to reduce this friction in the user experience, then perhaps it’ll be Tom Nook that offers players their requested UI shortcuts. <em>For a fee,</em> of course.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e87694f1a25e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Games User Research Methodology Series: Usability Expert Analysis]]></title>
            <link>https://playerresearch.medium.com/games-user-research-methodology-series-usability-expert-analysis-5d042cdebfa2?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d042cdebfa2</guid>
            <category><![CDATA[games-user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 15:28:42 GMT</pubDate>
            <atom:updated>2019-12-17T15:37:43.938Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Usability Expert Analysis is one of many games user research methods we use at Player Research to provide actionable insight into a game’s usability and learnability.</h3><p>This article outlines when a Usability Expert Analysis might be needed, what it consists of, and how it can be utilised in game development.</p><p><strong>What is the Purpose of a Usability Expert Analysis?</strong></p><p>The objective of a Usability Expert Analysis is to identify aspects of a game that could contribute to issues with player understanding and usability. Player understanding refers to whether or not a player knows what they have to do; for example, do they understand what their next step in the game should be to achieve their objective? Usability refers to whether or not a player is able to do what they intend to do; for example, a player may <em>understand</em> what their goals are, but are they able to effectively use the controls and tools at their disposal to successfully achieve those goals?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANlBTs8klsmALsVAPB9QZA.png" /></figure><p>If left unaddressed, issues in understanding and usability are likely to negatively impact player experience when a game is released, from minor annoyances (that may have a slight negative impact on player experience) to progress-blocking usability issues (such as a core mechanic being fundamentally misunderstood). Unfortunately, most developers first hear about these issues late on in development, or even after released, when they hear the game “isn’t fun/enjoyable/good”. A Usability Expert Analysis can catch these issues quickly, and early.</p><p><strong>When Should a Usability Expert Analysis be Done?</strong></p><p>The short answer is that a Usability Expert Analysis can be carried out at any point in a game’s life cycle — if material for the game exists, a Usability Expert Analysis can be done. However, Usability Expert Analyses may be of particular value when used as an early touchpoint in the research pipeline of a game because of two key strengths:</p><p>1. A playable build is not required — Usability Expert Analyses can be performed on any testable materials. If the build has bugs and/or is unreliable, the researchers are able to work with/look past these issues fairly easily. We can even perform an analysis of wireframes, prototypes or GDDs, and this can be incredibly valuable when it comes to catching potential issues before any features are put to code. Additionally, if the build has bugs and/or is unreliable, the researchers are able to work with/look past these issues fairly easily.</p><p>2. Usability Expert Analyses are typically quicker and less expensive than playtests. Conducting them early, before the playtest cycle begins, means that any ‘low hanging fruit’ can be eliminated <em>before</em> players get their hands on the game. Removing these barriers allows for a deeper, more thorough exploration in future playtests.</p><p>Conducting Usability Expert Analyses early in a game’s life cycle can be useful for minimising issues in the long term. However, regular employment of them is vital for ensuring development remains on track and quality remains high throughout.</p><p><strong>How does a Usability Expert Analysis work?</strong></p><p>Here at Player Research the process involves a pair of researchers critically analysing a build, a feature, or any other test materials of interest.</p><p>During their analysis, the researchers aim to identify any potential issues of usability and understanding and where key user experience principles are being broken. The analysis itself involves a slow methodical approach, contextualised by our client’s aims for the research (e.g. a focus on the FTUE, or particular game mechanics).</p><p>In addition to usability issues, examples of good user-experience practice are identified; knowing what <em>not</em> to change can be just as important as knowing where improvements can be made. This also serves to provide positive affirmations for the development team — it can be hard to hear honest truths about their game, so being reminded of the best aspects confirms when they are on the right track.</p><p>Finally, the identified issues are prioritised in terms of their severity and collected into a digestible report containing actionable solutions. We’ll be writing about our report format in a future article.</p><p><strong>Usability Expert Analyses at Player Research</strong></p><p>At Player Research, we ensure that all Usability Expert Analyses are carried out by at least two researchers; this helps to increase both the thoroughness and the reliability of the analysis.</p><p>All of our researchers have relevant academic backgrounds in Human Computer Interaction, Neuroscience and Psychology. This expertise, combined with a wealth of experience running playtests, provides a unique and scientific perspective when carrying out a Usability Expert Analyses. This perspective allows us to see beyond the initial impact of a problem and anticipate how an issue is likely to have knock-on effects (positive or negative) on player behaviour in the long-term.</p><p>Each Usability Expert Analyses is bespoke to our clients. We don’t compare games to a set of heuristics, as is common in expert reviews more widely, rather we utilise our knowledge of human behaviour and psychological principles to better take into account the context in which issues are experienced. Design intent is paramount and considered throughout the analysis — it is where your intent is not met by the current and planned experience that is highlighted by our analysis.</p><p><strong>Conclusion</strong></p><p>A Usability Expert Analysis is an effective method to uncover usability and understanding issues for a game in development and is best used both early in the game’s life cycle, as well as part of a longer-term mixed-methods approach that also includes player data.</p><p>See our other articles for more information about the most common research methods we employ, and please feel free to get in contact to discuss creating a powerful and effective research strategy.</p><p>Written by <a href="https://www.playerresearch.com/team/chloe-snell/">Chloe Snell</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d042cdebfa2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX game design insights from The Walking Dead: March to War]]></title>
            <link>https://medium.com/googleplaydev/ux-game-design-insights-from-the-walking-dead-march-to-war-9ebdb3e23283?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ebdb3e23283</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[mobile-games]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 13:50:27 GMT</pubDate>
            <atom:updated>2018-03-19T13:50:27.046Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to improve your players’ experience before conducting playtests</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HY-rvoYiclKXtGa4wEJ_rA.png" /></figure><p>Here at <a href="http://www.playerresearch.com/">Player Research</a> we’ve improved gameplay experiences for more than two hundred games globally by applying our knowledge of human-computer interaction, psychology, and neuroscience. Using user experience (UX) analysis and playtest labs, we’ve worked with games studios to help them develop a true understanding of their players and how to improve their games. Working with Google Play to gather learnings from developers, we are sharing insights on the importance of great UX in game design.</p><p>In the first article in this series, we shared critical <a href="https://medium.com/googleplaydev/how-to-build-mobile-games-with-people-in-mind-cdc480967fcc">player-centric design principle</a>s across three themes:</p><ul><li>Break barriers with players to accommodating how they see, hear, think, interact, and live.</li><li>Build game structure to help players understand, learn, and progress.</li><li>Refine focus and try to find the right balance.</li></ul><p>For game development teams, using this framework can help improve their games from the player’s perspective.</p><p>In this article we’ll look at how applying these principles impacted a real game’s development, sharing some of the UX flaws identified, the design changes implemented, and their impact on key performance metrics. We hope this will help you apply these UX lenses to your own game, and see the benefit of this kind of analysis in identifying problem areas before conducting playtests with users.</p><h3><strong>The Walking Dead: March to War — game strategy</strong></h3><p>Based just outside Boston, Massachusetts, <a href="https://www.disruptorbeam.com/">Disruptor Beam</a> specializes in story-rich mobile games with social components. They previously released <a href="https://play.google.com/store/apps/details?id=com.kongregate.mobile.gameofthronesascent.google&amp;hl=en"><em>Game of Thrones Ascent</em></a> followed by <a href="https://play.google.com/store/apps/details?id=com.disruptorbeam.StarTrekTimelines&amp;hl=en"><em>Star Trek Timelines</em></a>. Their newest title, <a href="https://play.google.com/store/apps/details?id=com.disruptorbeam.marchtowar&amp;hl=en"><em>The Walking Dead: March to War</em></a><em> </em>is an epic free-to-play multiplayer strategy game, set in the world of Robert Kirkman’s long-running comic, The Walking Dead. The game’s rich visuals and gameplay aim to provide players with a gripping story and strategy experience with social elements. Joey Lapegna, Creative Director highlights how important the visual experience is in the game:</p><p><em>“We knew we were entering a space with a lot of competition, both in terms of The Walking Dead and the strategy genre. Building a visually striking game was something we knew could be an advantage for us in both areas. We felt that by recreating a distinctive looking world and creating beautifully painted characters we could transport players into a unique Washington DC during the events of March to War in the comic series.”</em></p><h3><strong>Assessing the UX of <em>March to War</em></strong></h3><p>Our objective in assessing any game’s UX is to highlight parts of the implementation that might contradict designers’ intended experience. To understand how best to apply our UX principles to <em>March to War</em>, we needed some knowledge of their intended experience.</p><p>Using the questions for the development team, provided in our <a href="https://medium.com/googleplaydev/how-to-build-mobile-games-with-people-in-mind-cdc480967fcc">introductory article</a>, Disruptor Beam outlined their vision for the game, the game’s target audience, and what their players need to understand and do. This outline acted as the basis for us to seek out any discrepancies between intent and actual player experience, using each UX principle as a lens:</p><p><strong><em>Break barriers: </em></strong><em>Accommodate how players see, hear, think, interact, and live</em>:</p><ul><li>Maintain audience-suitable complexity</li></ul><p><strong><em>Build structure: </em></strong><em>Help players to understand, learn, and progress</em>:</p><ul><li>Leverage familiarity</li><li>Provide minimal effective tutorials</li><li>Ensure assistance is nearby</li></ul><h3><strong>Accommodate how players see, hear, think, interact, and live</strong></h3><h4>Maintain audience-suitable complexity</h4><p>Testing players’ memories and attention can be a compelling gameplay mechanic. However, if players are required to memorize too much, especially around core tasks such as navigating menus, it can become burdensome and negatively impact their experience and efficiency.</p><p><em>March to War</em> uses a menu with blueprint-style icons for players to build and upgrade their Survivor’s base. The screen only shows one or two areas at a time. Because players couldn’t see other areas in the base, they’d have to remember the position of unseen areas to navigate to them, adding a layer of complexity.</p><p>Disruptor Beam wanted this UI to be intuitive and easy-to-use, and also to impart an understanding of the game structure to players, communicating the game’s depth.<em> </em>In showing only a small part of a larger map — with no option to zoom out — the scale of the survivor’s base-camp was hard to appreciate and so too was <em>March to War’s </em>content and depth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/0*QCiFBmHyiMltPO9Q." /><figcaption><em>Pinch-to-zoom view of map</em></figcaption></figure><p>This issue was easily addressed by adding a pinch-to-zoom feature and a slightly wider default view of the base camp. This view allows players to see the much more of the base and reduces their need to remember absolute positions, improving the efficiency of using the map. All players can also see more of the buildings they’d unlock later, creating a better understanding of the base-building metagame.</p><h3><strong>Build structure: Help players to understand, learn, and progress</strong></h3><h4><strong>Leverage familiarity</strong></h4><p>Leveraging familiarity reduces the need for training by relying on familiarity with real life, similar games, or referencing information that the game has shown in other areas. As Joey outlines, ‘familiarity’ can be genre specific, adding a challenge for developers who want to reach a broad audience:</p><p><em>“The genre of mobile strategy games doesn’t have a history of highly accessible UX, but highly engaged players have learned to master such games in spite of those challenges. What we saw as counter-intuitive UX when designing March of War, they saw as intuitive. So, we had to balance presenting an experience familiar to expert players of the genre but also attempt make it accessible to Walking Dead fans unfamiliar with the genre. We ultimately developed a UX that felt mostly familiar to experienced players — albeit with several usability improvements — but which was also accessible to new players.”</em></p><p>In <em>March to War</em>, similar colors were used for both positive and negative confirmation pop-ups, with red, orange, and green used interchangeably for <em>positive</em> messages such as a completed building, or <em>negative</em> messages such as an error or alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BllB79tRAcjIyp6j." /><figcaption><em>Neutral and positive messages in non-intuitive colors</em></figcaption></figure><p>This led to some mixed messages about feedback, as there was no consistent use of color players could familiarize themselves with and recognize quickly. In an easy fix, Disruptor Beam revised player feedback across all messaging and confirmations: using a green color for advantageous, red<em> </em>for disadvantageous messages, and notification-style top-mounted message for neutral feedback.</p><p>Players look for patterns and consistency in a game. When a pattern breaks it can feel disconcerting. <em>March to War’s </em>base-building section provides ‘free waiting time skips’ to speed up players’ construction of buildings. Players would quickly get into a habit of skipping waiting time for free. As it wasn’t clear when free skips would end, there was a jarring surprise when players suddenly found that they needed to wait for 15 minutes before they could skip again.</p><p>This jarring moment could be avoided by giving players the ability to predict<em> </em>when the skips would end. Disruptor Beam implemented a change that gave players enough knowledge to predict how free skips worked. Using a brief full-screen takeover message, players are told that a free skip is always given for a wait time under ten minutes. While we stress that tutorials are only one way to communicate knowledge, judicious and considered use of tutorials can be the best way to provide information to players. This solution is a great example of a minimal but effective tutorial.</p><h4><strong>Provide minimal, effective tutorials</strong></h4><p>The Disruptor Beam team were very aware of the challenges of building an immersive, rich experience like <em>March to War</em> while meeting the needs of the mobile player:</p><p><em>“We wanted the player to feel like they were transported into the world of The Walking Dead at a certain place and time and the 3D map and environment we built helped to do that. Meanwhile, we were also building a mobile game that required a quick and easy UX in order to keep players engaged. Mobile players don’t want to spend time exploring rich worlds, they want to get the task they’ve committed to completed as soon as possible. Visually communicating the information players needed to see on the map was an important challenge for us to keep the experience consistent.”</em></p><p><em>March to War</em> is an intricate game, with a lot of information to teach new players.</p><p>The game takes a mixed approach to teaching new players, from using on-screen highlighting and animations to draw players’ attentions to features, to text-based messages to explain game systems and features. Use of text matches the game’s target audience of adults well: the game has a PEGI 16 rating.</p><p>Occasionally, the highlighting of in-game elements was a barrier to understanding. In some tutorials players were presented with multiple animated icons vying for their attention. Each of these flashing effects would perform well as reward moments or effective notifications in isolation, however, when presented together players’ attention was split, and the logical flow was lost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/0*b9uOvl2D1AJ5COg6." /><figcaption><em>Calling the players’ attention to multiple areas at once meant splitting players’ attention</em></figcaption></figure><p>Similarly, when being instructed on how-to build the Survivor Barracks, players are presented with multiple elements that might draw their attention away from the Barracks itself, including blue glowing blueprint locations, and three green arrows (which show available upgrades). Although the Survivor Barracks does glow orange — rather than blue — to draw attention, the various other highlighted elements create visual clutter, reducing the effectiveness of the tutorial.</p><p>Disruptor Beam altered the flow of the tutorial. Instead of using multiple arrows, one familiar icon now guides players toward the relevant UI and on-screen controls.</p><h4><strong>Ensure assistance is nearby</strong></h4><p>If development teams can feel confident that players will figure out a game mechanic for themselves, the need for long and overbearing tutorials disappears. <em>March to War</em> lets players explore the various mission types, with their varied mechanics and rewards communicated in-the-moment.</p><p>However, one mission type in particular — resource cache missions — works differently. In most missions Survivors complete a task and return immediately, but in this mission type the Survivors march out of the base for a longer period to collect cached resources. We identified a potential point of confusion from players: “What happened to my Survivors?” To communicate Survivor status without using text, Disruptor Beam drew players’ attention to the ‘active marches’ graphic by pulsing it once the mission had begun, and glowing it green when survivors had reached the cache, encouraging players to tap the button and reveal the countdown timers that show exactly when their Survivors would return.</p><p><em>March to War</em>’s in-game economy requires players to produce resources and periodically collect them from their base by tapping an icon. Food, fuel, and lumber are needed for upgrades and new buildings. When players tapped on a resource icon to collect it, the icon simply disappeared. If players had forgotten or misunderstood what these icons were for, or what the building did, there was no assistance to help them understand the metagame. To address this, Disruptor Beam team changed the visual design of resource collection, showing the currency icon and the amount of that currency the player has collected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*Xx4NDzKpgBEnbZlx." /><figcaption>Before-and-after resource collection graphics</figcaption></figure><h3><strong>Impact of the changes</strong></h3><p>In the weeks following our review, Disruptor Beam made small changes to address the individual UI and tutorialization issues highlighted by the analysis, releasing an updated version of the game in December 2017.</p><p>The impact of these straightforward changes was reflected by improvements in several in-game behaviors. Spending of in-game resources and premium currency, completing objectives, and carrying out research to unlock new features all increased in the first session, reflecting players’ better understanding of resource gathering as a result of tweaking the tutorials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WAY592ZXn7JfVaDF." /></figure><p>The gathering and use of salvage greatly increased too, reflecting an improvement in players’ understanding of the ‘resource cache’ missions, thanks to the improvements that provide ‘assistance nearby’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W3rJJr7dU8nHZh0Y." /></figure><p>The clarified ability to skip waiting times resulted in players skipping more than before the changes, and sticking around for longer, with average first-session time being <em>double</em> that of the previous release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9JDhuLnfKK4kpGrK." /></figure><h3><strong>Summary and observations</strong></h3><p>We hope our outline of the simple process of re-thinking and assessing a game from the players’ perspective will inspire you to assess your game for latent UX issues. By focusing on breaking barriers to play and structuring learning in <em>The</em> <em>Walking Dead: March to War </em>Disruptor Beam achieved significant improvements in key metrics. It was great to work with a company so open to growing and improving, as articulated by the Production team:</p><p><em>“Disruptor Beam as a company has always been committed to continuous improvement. It’s a philosophy we take to heart when evolving and developing new ways to approach our games. Does that mean we always nail it? No. We’re still learning and growing in the art of game making everyday. Player Research gave us a fresh perspective on our game product with concrete feedback that we could make changes based on. It’s rewarding to see how those became positive experiences for our Players.”</em></p><p>This article reflects just one type of UX research. There are many other player-centric research options such as usability playtesting, play diaries, eye-tracking, and more, each providing a different lens on latent issues in the design and implementation of your vision. The combination of these measures and their integration into your development cycle helps teams better understand players’ experience.</p><p>In the next article in this series, we’ll look at an example where the findings and impact of changes aren’t so clear cut, and explore other variations of UX research projects.</p><h3><strong>What do you think?</strong></h3><p>Do you have questions about these player-centric UX principles, or have tips of your own for what makes a great UX in game design? Let us know in the comments below or tweet using <strong>#AskPlayDev</strong> and we’ll reply from<a href="http://twitter.com/googleplaydev"> @GooglePlayDev</a>, where we regularly share news and tips on how to be successful on Google Play.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ebdb3e23283" width="1" height="1" alt=""><hr><p><a href="https://medium.com/googleplaydev/ux-game-design-insights-from-the-walking-dead-march-to-war-9ebdb3e23283">UX game design insights from The Walking Dead: March to War</a> was originally published in <a href="https://medium.com/googleplaydev">Google Play Apps &amp; Games</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build mobile games with people in mind]]></title>
            <link>https://medium.com/googleplaydev/how-to-build-mobile-games-with-people-in-mind-cdc480967fcc?source=rss-8e7497e82347------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdc480967fcc</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[mobile-games]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Player Research]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 09:36:38 GMT</pubDate>
            <atom:updated>2017-12-14T14:02:56.225Z</atom:updated>
            <content:encoded><![CDATA[<p>User experience design principles to help you build games people want to play by <a href="https://twitter.com/seb_long">Seb Long</a>, <a href="https://medium.com/@harvey_2330">Harvey Owen</a> and <a href="https://medium.com/@garethlloyd">Gareth Lloyd</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsuiN_0VYxDOVHYSuyDPKg.png" /></figure><p>The audience for mobile games continues to expand globally. As a result, developers face the challenge of building games that meet the needs of a wide range of users, while wanting to differentiate their game from the crowd with a great user experience. The complexity of this challenge means that despite the best intentions, sometimes the players’ experience of a mobile game differs from the intention of the design. There are many nuanced and player-centric reasons why this might happen. The most difficult disparities to uncover are rooted in human psychology; influencing factors such as how your player audience thinks, learns, perceives, and interacts with your games.</p><p>We are <a href="http://www.playerresearch.com/">Player Research</a>; playtesting, and user research specialists. Google Play asked us to leverage our experience assessing hundreds of games, to build a set of principles to help you create an engaging, accessible, learnable, and rewarding game for all your players. Using these principles as ‘lenses’ on your game can help identify player experience risks, assumptions, and flaws. Addressing them will increase your chances of crafting an engaging, learnable, and rewarding game for all your players by factoring human psychology into game design.</p><p>The principles are presented alongside questions to ask about your audience, to discuss as a team, or to help guide your playtests with players. While not exhaustive, these questions should prompt teams to identify disparities between design intent and a player’s experience.</p><p>We’ve grouped these UX principles into two main focus areas:</p><ul><li><strong>Breaking barriers</strong>: Eliminating hidden ‘barriers to fun’ by accommodating how players see, hear, think, interact, and live with a game.</li><li><strong>Building structure</strong>: Helping players understand, learn, and progress by designing a game to be learnable, and with a clearly presented and understood sense of progression and depth.</li></ul><p>By addressing these areas, you can ensure that a game’s challenge, frustration, and confusion originate from where you intend, rather than from unforeseen consequences of design decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzehAQxovGnC1jSopxIZfA.png" /></figure><h3><strong>Breaking barriers</strong></h3><p><strong>Accommodating how players see, hear, think, interact, and live</strong></p><p>The <em>first set of principles</em> ask you to consider your players physical and psychological constraints; and whether your players can enjoy your game as part of their everyday lives. Games that break these principles are ripe for a quick uninstall. Players who immediately find frustration or confusion in their basic interactions with a game, or blockers that prevent them from understanding the game, are unlikely to progress beyond the first experience:<em> “This game just isn’t for me”.</em></p><blockquote><em>Take a look at what your games do to usher in new players. No-one says you have to implement your findings if you don’t want to, no-one says you have to dial back on the challenge in a game or sacrifice complexity. Maybe your game isn’t meant to be more accessible, [but] maybe you’ll find that it is a good idea to reconsider.<br></em> — Rami Ismail, Vlambeer (<a href="https://www.gamasutra.com/blogs/RamiIsmail/20121105/180905/An_argument_for_easy_achievements.php">source</a>)</blockquote><h4><strong>Principle 1: Audience-suitable complexity</strong></h4><p>Complexity is not just something you design into your game; as perceived by players, <strong>complexity arises from both the game’s design and players’ capabilities</strong>. You’re likely to be a master at your game; but players’ cognitive, motor, and perceptual abilities won’t necessarily match yours. Your target players — regardless of age or gaming experience — will have their limits regarding acceptable game complexity. Unless these limits are accounted for in design, games can quickly become too complicated or demanding.</p><p>Designing audience-suitable complexity means knowing who your audience are, and understanding their <strong>capabilities</strong> across functional domains, such as memory, attention, language processing, and motor skills. These functional domains can happily work in parallel, allowing us to carry out everyday tasks that draw on them all at the same time, or focus on a single domain to tackle a new or exceptionally demanding task. But, high demands in any one domain can reduce the effectiveness of the others; and high demands in multiple domains is a recipe for bad performance and confusion. So, assess the <strong>demands</strong> of your game in terms of those various domains. What changes can be made so that they match up? Could you reduce complexity without affecting the core gameplay?</p><p>By understanding the relationship between capabilities and demands, games can be designed to fit any target audience. Here are some questions you can use to assess the audience-complexity fit of your game:</p><p>Questions to ask about your players</p><ul><li>What are our target audience’s visual, motor, and cognitive capabilities?</li><li>How do our target audience vary in terms of abilities including language and numeracy?</li></ul><p>Questions to ask your team</p><ul><li>How have we ensured that our game is accessible and offers an optimal challenge considering our target audience’s current visual, motor, and cognitive capabilities?</li><li>Should we adapt our game experience to accommodate differences in abilities?</li><li>How early should we bring in users to test the experience?</li><li>How might we protect our game from ‘complexity creep’ during development?</li></ul><p>Questions to ask your players</p><ul><li>Did you feel confused at any point while you were playing?</li><li>While playing, did you feel like you had all the information you needed? Did you know where to find it?</li><li>Can you show me how to find [feature] in the menus? Were you able to use the menus easily?</li><li>Do you feel like this game is ‘for you’? Is it aimed at you? If not, who is it aimed at?</li></ul><h4><strong>Principle 2: Designing for flexibility</strong></h4><p>Designing towards your target audience’s capabilities is a great start. But no matter how well you do that, there will always be differences among your players, in terms of their experiences, preferences, and the environments where they play. <strong>Accommodating for differences among players in your target audience is just as important as defining your audience</strong>.</p><p>Games are a part of everyday life for people, so where possible games should be designed to be flexible to allow for the various contexts in which they are played. The real world offers interruptions, both on the device and off. To ensure your game fits neatly into people’s lives, make sure it supports flexible session lengths, customizable control and audiovisual settings, and accommodates for distraction and task-switching.</p><p>For example, in <a href="https://play.google.com/store/apps/details?id=com.blizzard.wtcg.hearthstone">Hearthstone Blizzard</a> built in features to accommodate long interruptions in play:</p><blockquote><em>Players returning to Hearthstone after a break often still think of themselves as experts, so a traditional hand holding tutorial could be seen as oversimplified and insulting. Instead, we offer a set of quick pop-ups to let them know what’s changed and a couple of unique daily quests to guide them back into the flow of the game.<br></em>— John Hopson, Senior User Research Manager, Blizzard Entertainment</blockquote><p>Here are some questions to ask that can help you assess flexibility in your game:</p><p>Questions to ask about your players</p><ul><li>Where, when, and on which devices are our players playing the game?</li><li>What aspects of that context could impact gameplay?</li><li>Does our projected session length match players’ <em>actual</em> session lengths, and fit into their real lives?</li><li>Do we provide enough time for players to perceive and comprehend gameplay feedback?</li></ul><p>Questions to ask your team</p><ul><li>How might we let players personalize their experience to their everyday <em>preferences and capabilities</em>, such as offering video and audio settings?</li><li>Can we design gameplay that accommodates interruptions?</li><li>How could we accommodate players returning to the game after a long period away?</li><li>Do the game controls reflect players’ ergonomic restrictions when holding their device, for example, require them to reach across the screen or potentially cover elements with their fingers?</li><li>Can we give players the option to automate, hide, or turn off gameplay features that are not core mechanics?</li></ul><p>Questions to ask your players</p><ul><li>How often do you find that you are interrupted during game play?</li><li>When your game was interrupted, what happened when you returned to the game? Was that what you expected to happen? If not, why not?</li><li>Did you change any settings in the game?</li><li>Was there anything about the game or the controls that you would have liked to be able to change?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yi7pXoB8CGviwAURA6GLKg.png" /></figure><h3><strong>Building structure</strong></h3><p><strong>Helping players to understand, learn, and progress</strong></p><p>While it’s important to address potential barriers to play, player experience also plays a role in converting an audience of first-time players into experts and fans. By emphasizing learnability and the connectivity of features in your game, you can communicate game knowledge and skills to players, and guide them along the journey you have designed. In turn, they will play the game as you have envisioned.</p><h4><strong>Principle 3: Leverage familiarity</strong></h4><p>Players learn game features effortlessly when aspects are already known to them in some way: as platform or genre standards, or because they mirror the real world. Players recognize progression structures from similar games, such as earning a certain number of stars to progress to a new area. Widely-used and immediately recognizable real-world iconography and behaviors can also be employed, such as pulling and releasing a slingshot. When designed with familiarity in mind, players can make valid, educated guesses about how items, features, or interactions will behave.</p><p>Familiarity can also come from internal consistency. As players spend more time with the game, its visual language becomes familiar and recognizable. Associating consistent iconography, terminology, and coloration with game features and functions helps players build a strong mental model of a game. Maintaining this consistency will help players to predict the function of new features, without having to be explicitly taught.</p><blockquote><em>When we design UX at King, understanding and responding to our player’s expectations is paramount. All products exist within their context, and our players have grown to recognize and expect the visual shorthand of mobile games. Adhering to these expectations (and knowing when to break them!) helps us to craft delightful experiences, where the player can focus on the fun with minimal cognitive load.</em><br>— Caitlin Goodale, User Experience Designer, <a href="https://play.google.com/store/apps/dev?id=6577204690045492686">King</a></blockquote><p>Questions to ask about your players</p><ul><li>What are the players’ norms and expectations around gameplay mechanics?</li></ul><p>Questions to ask your team</p><ul><li>Is the UI laid out in a manner that is consistent with players’ existing mental models?</li><li>How can our mechanics, features, and interactions be made more intuitive and understandable using our players’ <em>real-world knowledge</em>?</li><li>How can our mechanics, features, and interactions be made more intuitive and understandable by being consistent with <em>other aspects of our game</em>? And <em>other games</em> that our audience may have played?</li><li>Can we ensure our iconography and terminology is distinct and can be recognized quickly?</li></ul><p>Questions to ask your players</p><ul><li>What do you think these icons mean at first glance?</li><li>How might you expect this feature to work?</li><li>Did this feature work as you expected it to? If not, why not?</li><li>Was there anything in the game that didn’t work as you expected it to?</li><li>Is this feature something that you’ve seen in other games?</li></ul><h4><strong>Principle 4: Assistance nearby</strong></h4><p>New players usually start with a game by trying to play it, even if they don’t fully understand it. Motivated players will most likely learn through play, trial, and error.</p><p>But successful learning through exploration doesn’t come for free; comprehensive feedback systems and safeguards are needed as players inexpertly interact with the game while they figure it out. To learn, players need feedback that is rich, relevant, and timely, allowing them to understand their effect on the gameworld.</p><p>Learning through discovery is also more effective when players are in a safe environment. This should emphasize practice, perhaps by appropriate “chunking” game concepts into approachable trial-and-error sections. It should also allow players to recover from errors, whether by design — for example, by being generous with resources early on — or by providing options to undo in-game actions while learning to play.</p><p>Players feeling confused — or simply wanting to learn more — can also be prompted with extra information: ‘read more’ help, ‘information’ buttons, and even full-blown manuals or customer support contact information. However, avoid relying on these resources as the only way for players to understand your game. Although the instructional needs of each game are different, it’s best to enable players to learn as a result of playing with your game.</p><p>Questions to ask about your players</p><ul><li>Are your players more likely to learn by exploring your game or by relying on help?</li></ul><p>Questions to ask your team</p><ul><li>What are the ideal times (and locations) to present players with supportive information?</li><li>What undesirable errors might players make in our game, and how might we elegantly protect them from that negative experience?</li><li>How might our gameplay feedback better communicate player’s influence on the gameworld?</li></ul><p>Questions to ask your players</p><ul><li>Did you ever make any mistakes that you couldn’t recover from? If so, what happened?</li><li>Do you prefer to figure out how to play these sorts of games on your own? Could you do that in this game?</li><li>Did you see any help messages in the game while you were playing? Did you take their advice, and were they useful?</li><li>Did you go looking for further help or information about how to play? Where would you expect to find that information?</li><li>Did you feel like you knew when you were doing well or badly in the game?</li></ul><h4><strong>Principle 5: Effective, minimal tutorials</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5AAnrLnYQWCn-QJGEVLSw.png" /></figure><p>In situations where teaching methods based on player intuition, familiarity, and trial-and-error discovery aren’t effective, games need to explain themselves clearly. Tutorials, text prompts, and ‘click here’ sequences are common methods of teaching.</p><p>Excessive reliance on tutorials can overwhelm players by asking them to remember too much, or make them feel stifled by an inflexible experience. However, in the absence of other methods for players to learn how to play your game, a lack of tutorials can leave players lost.</p><p>Playtesting and iterative design can help to pin down the ‘Goldilocks’ tutorial for your audience: the right amount to teach your players the fundamental concepts and features of your game, while balancing explicit tuition with learning through familiarity, intuition, and assistance.</p><p>Questions to ask about your players</p><ul><li>Are your players likely to be particularly resistant to tutorials?</li></ul><p>Questions to ask your team</p><ul><li>Is our UI accurately communicating the game structure to players?</li><li>Can players recognize our gameplay feedback and are they able to respond as we want them to?</li><li>Which areas need more — or less — tutorialization?</li><li>Have we maximized opportunities to teach players (for example through loading screens, pause menus, teaching through menu interactions, videos, or cutscenes)?</li><li>Are we using tutorials in the right places?</li></ul><p>Questions to ask your players</p><ul><li>Are tutorials something you feel comfortable using while learning a new game?</li><li>Did you feel restricted by the tutorials in the game? Were there times where you would have preferred to learn on your own?</li><li>Were you able to understand each tutorial? Did you manage to quickly learn what it was trying to teach you?</li></ul><h4><strong>Principle 6: Clarity of depth</strong></h4><p>Once your players understand the basics, what’s next?</p><p>Clear goals give players purpose, things to work towards in a play session, and reasons to return to the game. Communicating goals in term of the structure and depth of a game — the <em>metagame</em> — fosters <em>confidence</em>, is <em>rewarding</em>, and encourages <em>retention</em>.</p><p>It’s often a challenge to communicate to players how a deeper metagame links to core gameplay loops, typically as the result of weak, abstract relationship between the two. Many games lean on familiar models to communicate basic structure and progression, such as ‘collect 3 stars’ and ‘complete the previous level to advance.’</p><p>Rewards and incentives can also be used to communicate metagame systems; but like goals, they need to be clearly understood by players. A misunderstood reward can confuse rather than reinforce players’ understanding of how and why they progress in the game.</p><p>Other players can also provide a source of depth, and potentially an endless metagame. Social interaction and competition between players — via leaderboards, player versus player, co-operative play, ‘clans’, social sharing or simply just chat — can be an incredibly engaging and may be a potentially limitless source of depth. These methods can be challenging to implement however: not only because of the technical demands involved, but also in terms of communicating how multiplayer and social interactions complement the game’s single-player content and mechanics.</p><p>These are challenging — but critical — UX issues to address, because a strong metagame means an engaged audience in the long-term. Communicating metagame systems effectively will ensure players can make confident and informed decisions about in-game purchases, and increase the likelihood that they remain active for longer before uninstalling. This is also true outside of free-to-play models: a good metagame means a captive audience for your sequels or follow-ups.</p><p>Questions to ask about your players</p><ul><li>Do your players seek out games with longer-term goals?</li><li>To what extent do players seek out this type of game for its social aspects? Do they want to play with or against other players?</li></ul><p>Questions to ask your team</p><ul><li>Are we presenting longer-term goals in an understandable manner?</li><li>How do we meaningfully communicate the presence of other real players and how multiplayer and social interactions fit into our metagame?</li><li>How might we reinforce the relationship between gameplay progression and metagame progression?</li><li>Which features are designed to bring players back, and are they presented meaningfully to players in the first-time user experience?</li></ul><p>Questions to ask your players</p><ul><li>How do you progress in this game?</li><li>What are you trying to do in this game now?</li><li>What do you need to do in this game [in the long term]?</li><li>How do you get better at this game?</li><li>Will this game get more difficult?</li><li>Can you interact with other people in this game? How?</li><li>What can you buy in this game? Can you buy things to help you?</li><li>What do you spend to buy things in this game? How do you get more of them?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86fbAfv5Zjh3ubVCxIP-QA.png" /></figure><h3><strong>Refining focus</strong></h3><p><strong>Getting the balance right</strong></p><p>We have discussed several ways in which you can make your game intuitive without adding complexity. But, remember, no-one wants a game that’s boring, ‘vanilla’, or uninteresting. Successful games challenge players and provide them with a sense of achievement.</p><p>As creative game developers, you can ignore any of these principles in the name of fun. Many successfully games use visual complexity, awkward controls, unfamiliar gameworlds, and so on. In some cases, deliberate complexity and friction can become the ‘source of challenge’ unique to the game.</p><p>However, neglecting (or making assumptions about) these principles increases the risk that your game will have unintentional barriers, and add unintended friction to players’ experiences. In short: choose your battles wisely, and try to ensure that your game is only demanding in the ways that you want it to be.</p><p>We hope that bringing these player-centric principles into development discussions will help you craft the experience you envision for your game. Careful and deliberate experimentation with these visual, motor, cognitive, and fundamentally <em>human</em> design choices will increase the chances of players finding the fun you’ve made for them, and keep them coming back for more.</p><p>In future articles, we will share the results of working with games developers to apply these principles to their game design.</p><p><strong>What do you think?</strong></p><p>Do you have thoughts on designing user experience for games and how human factors affect gamer behaviour? Let us know in the comments below or tweet using <strong>#AskPlayDev</strong> and we’ll reply from <a href="http://twitter.com/googleplaydev">@GooglePlayDev</a>, where we regularly share news and tips on how to be successful on Google Play.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdc480967fcc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/googleplaydev/how-to-build-mobile-games-with-people-in-mind-cdc480967fcc">How to build mobile games with people in mind</a> was originally published in <a href="https://medium.com/googleplaydev">Google Play Apps &amp; Games</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>