<?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 Dupla Studios on Medium]]></title>
        <description><![CDATA[Stories by Dupla Studios on Medium]]></description>
        <link>https://medium.com/@duplastudios?source=rss-f4a1d2375e79------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CK5WAG-F1wUh1GpPU_smIQ.png</url>
            <title>Stories by Dupla Studios on Medium</title>
            <link>https://medium.com/@duplastudios?source=rss-f4a1d2375e79------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:14:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@duplastudios/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[Facilitating product success — The 3 steps to getting the most out of your usability study]]></title>
            <link>https://medium.com/@duplastudios/facilitating-product-success-the-3-steps-to-getting-the-most-out-of-your-usability-study-64a4ae3995bf?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/64a4ae3995bf</guid>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[tips-and-tricks]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Wed, 12 Sep 2018 18:10:52 GMT</pubDate>
            <atom:updated>2018-09-12T18:10:52.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1TbG5OJjqGawd7qSiDXUQ.jpeg" /></figure><p>Usability has been around for a lot of years. Some people trace its growth from the early 1900s when Frederick Taylor published his “Principles of Scientific Management” in which he described time and motion studies. Today, usability is one of the basic building blocks of creating a great user experience. If a product or service is unusable, then your customers will not stick around waiting for improvement. This is especially true in the age of agile and lean development methodologies. One of the primary principles of agile development, for example, is rapid and continuous contact with the target user.</p><blockquote><em>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. </em><a href="http://agilemanifesto.org/principles.html">(Agile manifesto)</a></blockquote><p>The only way to know for certain if you are satisfying the customer is to contact them. If you are delivering on a continuous basis, you need to be continually asking them. Usability is one method used throughout much of the software development industry to gather rich and full information. Unlike online surveys which are typically answered by those who either love or hate the product or telemetry which tells you what the behavior your users are attempting but lacks the “why” behind the behavior, usability provides the illuminating insight that will help move the product forward.</p><p>Usability does have drawbacks. Usability can be costly in terms of time, depending upon the target profile of your user base. It can also be costly in terms of money if you want a very clean, rigorous result. However, doing regular usability studies while a product is in development reduces costly churn. <strong>Early testing allows you to discover things that don’t work before they get committed to code.</strong></p><p>In my experience, the primary determinant of the usefulness of a usability study is the product team’s investment. Some teams see usability as a checkbox to complete on the road to shipping a product. More than once I have watched teams hire a researcher to run the study, sit through the report presentation and vow to prioritize the findings with the product backlog. Then late in the cycle, the usability bugs are de-prioritized as the product team attempts to hit its glide path to ship.</p><p>The temptation to slip usability bugs is understandable — there is usually an overabundance of bugs to squash and there is always documentation on how to overcome the usability issues. Despite the issue of whether the target users will actually read the documentation. In truth, a prepared team can assimilate the usability feedback with hardly a pause in the normal work streams. Further, early testing can reduce the number of bugs that the team has to fix at the critical end-game.</p><p>Here are a few things that a team can do to be ready to incorporate usability sessions into their work stream without major disruptions:</p><h3>1) Prepare!</h3><h3>Consider whether you need to do a study in the first place.</h3><p>Participants can be costly (after recruiting and gratuities) and so are researchers. However, doing an expert review is vastly cheaper than taking a raw prototype in the lab. Usually, an expert review is only an hour or two of the researcher’s time, but it can save you thousands of dollars in the lab. It is not that the usability researcher has a better opinion, but they have a different perspective. They leverage psychology and HCI (Human-Computer Interaction) theory to see where issues could arise. They can usually suggest changes that will eliminate some of the most egregious usability issues before you let your target users see it. An experienced researcher will have seen hundreds, if not thousands, of users interacting with software, so they can bring that experience to bear in novel software experiences. An expert review will identify any big usability issues that could hide other critical usability issues, making your usability study vastly more informative.</p><h3>Know what you want to test and share existing data.</h3><p>PM, Marketing, Product Planning (and CSS if you have already shipped the V1 product) all have some contact with customers. This is a great source of data that can help define the protocol for a great usability study. What are the top-of-mind questions that have arisen in conversations with customers? What are the most common CSS calls? Those are great sources of research questions the researcher can use to craft tasks. Using this data can ensure that you are not just making changes to the product with new features, but also improving the quality and satisfaction for your customers.</p><h3>What data did you use to come up with your designs?</h3><p>The design is never created in a vacuum. Giving your researcher the background of where the designs originated can help them understand where you started. Knowing the origins of the design will helps the researcher understand the inherent bias of the design decisions. Bias is not a bad word here, everyone is biased by their experiences. Making assumptions is almost a requirement at the very beginning of product development. Letting your researcher know what the assumptions are can help them ask questions that will challenge whether those assumptions are accurate or not. This can be hard on the team, and some tightly held opinions may have to get sacrificed for the betterment of the product. However, it is better to discover those in the lab than in the post-shipping customer forums where the court of public opinion can cause user abandonment and give fodder to your competitors.</p><h3>Know who you are building for so that you don’t confound your results.</h3><p>It is critical that the profile, meaning the unique description of behaviors and knowledge of your target users, is explicitly defined and ratified by all stakeholders. Early in my career, I performed a study on a profile defined by a PM only to discover in the report presentation, after running the study, that the marketing team had a completely different definition of the target audience. It wasn’t that the results were wrong, but changing the product to suit the users we tested would not have put the product where the market opportunity was the most promising.</p><h3>2) Participate!</h3><h3>Attend as many usability sessions as possible.</h3><p>It may seem redundant. You are hiring an expert so why not just wait for the report? However, by sitting through at least a few studies, you gain a visceral understanding of how big an issue is and how the users reacted to it. You might find an inspired fix after seeing the behaviors that the participant attempted when they ran into the issue.</p><h3>Talk to the researcher after each session.</h3><p>I have run studies where I called out an issue after just one participant demonstration. I have also downplayed an issue where multiple participants demonstrated a behavior. In the first case, the issue was of such significance that the user would never be able to recover, which would have resulted in severe data loss. In the latter, the background of those specific participants was not an exact match for that scenario, so their failure was due to inexperience in the space, rather than the lack of information in the UI. We also verified that the tasks we ran were not feasible by a novice, something that was a dispute within the team. A researcher’s experience can help keep you from chasing red herrings but also spot camouflaged pitfalls. Debriefing will ensure the best chance of capturing all the important feedback and getting it in the final report.</p><h3>Take your own notes.</h3><p>Again, this may seem redundant, but sometimes a new nugget appears that your researcher missed in the hectic lab environment. You have a unique experience with the product and may spot a new piece of data because of that. In the debrief, compare notes and talk about what you have seen. It can also save you from following a red herring and making changes to the product when it is not needed.</p><h3>Log your own bugs.</h3><p>First, I have to say that you should follow the bug logging plan of your team. However, as a general recommendation, if you see something, say something. Logging bugs will ensure that no issue falls through the cracks. Later in triage, bugs can be reconciled as duplicates. The researcher typically won’t get to it until after the final report. Another reason to file bugs as you see them is to ensure that the bug contains all of the relevant information for your team to understand. A consultant researcher or a vendor may not know all the bug conventions of your specific team. A team member writing the bugs ensures that the issue is categorized and described correctly, so it is triaged in the most efficient manner.</p><h3>3) Follow up!</h3><h3>Attend the report presentation.</h3><p>Typically, the researcher will have some suggestions about how to improve the product/service. However, they may not be the subject matter expert, so their suggestions may not work. The suggestion might not be feasible due to technology constraints, timeline constraints, or business reasons. The researcher might not be privy to all of those factors, so your attendance and participation at the presentation will help to create better bug entries and more efficient solutions. Participating in the report presentation will help the team take the right information back to their desks.</p><h3>Make sure you are completely clear about the recommendations.</h3><p>Recommendations are based on insights the researcher has gleaned from their notes, user behavior, psychology, sociology, product heuristics, etc. You can improve the outcomes by asking for clarification, demonstration or even illustrations of the recommendations. The product team will be doing the work to fix the product based on the feedback. However, the researcher may or may not be working on the product or feature at that point. It’s important to understand the design implications of the recommendations. Otherwise, it is difficult to fully weigh their importance when compared to the rest of the bugs.</p><h3>Incorporate usability findings and recommendations into already existing bugs.</h3><p>One of my professors in graduate school told me that psychology was “the science of rediscovering the obvious”. If the product is in development for longer than a heartbeat, then it probably has a test team already filing bugs against it. A proficient test team is probably already filing usability bugs. Bugs logged from usability session and usability bugs logged from the test team are a bit different from one another. It doesn’t matter how good a test team is, they really just have a hunch that a target user <em>may </em>experience the issue. The usability data provides the support for that hunch. Linking the test bug with the usability study findings will help prioritize the right issues. It also helps identify the right bug categories which allow for more accurate cataloging of other issues.</p><h3>Conclusion</h3><p>The success of a usability study relies on the skill and expertise of the design researcher you hire/use. However, as a stakeholder in the product outcome, you can influence the outcome for the better by following these tips. This post is based on usability work I have done both as an internal employee at large software corporations and as a consultant. However, I have found that I still learn from every new engagement. Every new usability session has something to show me. I would like to hear from other teams about what you would like to see from your usability research? Alternatively, if you are a practitioner, what tips am I missing from my list above?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64a4ae3995bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX in the Game Development Process — Part 3: End Game]]></title>
            <link>https://medium.com/@duplastudios/ux-in-the-game-development-process-part-3-end-game-3e621e282d29?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e621e282d29</guid>
            <category><![CDATA[creative-process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 03:50:37 GMT</pubDate>
            <atom:updated>2017-01-04T04:00:59.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*sgx0PeiAxkB5qUnbI79S-g.png" /></figure><p>Every great creation is about 1% inspiration and 99% perspiration. The end game of game development is all about perspiring to perfection.</p><h3>Iteration</h3><p>Iteration is the phase in the software development process that people are probably most familiar with. This is when the heavy lifting happens by the product team. They are extremely busy coding the game and driving down the bug count. The objects, actions, objectives, and leveling rewards, all need to be fine-tuned in the Iteration phase. This is when having a user-validated concept from the Ideation phase pays off.</p><p>If the story and mechanics are already vetted by potential users, and the game demonstrated that target users found it to be interesting and engaging, then the Iteration phase is much smoother. If the concept has not been vetted, then Iteration will be messy and conflicted.</p><p><strong>The Iteration phase allows the product team to get insights into the perception of “fun” by their target customers.</strong></p><p>This is where User Experience can be the “Sherpa” to success. The UX team may not be able to climb the mountain for the team — after all, they generally do not own any code. However, they can, through several different methods, help the team understand and capitalize on opportunities illuminated through user testing and qualitative data.</p><p>If the concept was not vetted with customers, the team can get mired in “discussions” of what a user may want, or think, about a feature, level, or some game mechanic. Early testing saves arguments and development time in the end.</p><p>There are a couple of common methods that are employed to iterate towards success:</p><ol><li><strong>Usability Testing</strong>, where<strong> </strong>a set of target users are brought into a lab and attempt to play the game or section of the game. Meanwhile, a researcher watches and records areas where game mechanics may need to be revised or rewritten to make the interactions less cumbersome, better aligned with the story, or more natural.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uU22l5tWK5KpVVwBkQF4-w.jpeg" /><figcaption>A typical usability test setting</figcaption></figure><p><strong>2. “Playtesting”</strong>, where a large group of target users play the game and rate it on genre-specific subjective metrics via survey and post-study discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*v9QQzYVPXiTm0tG4F9lkug.jpeg" /><figcaption>Target users in a playtesting environment</figcaption></figure><p><strong>The difference between a Usability Study and a Playtest is the type of information uncovered.</strong></p><p>The usability of the game reveals where the mechanics, or the interactions, in the game need to be reevaluated. Discussions with the target user can point to specific interactions that need to be addressed. A “Playtest” can reveal target users’ subjective ratings on any number of qualities. It can help a product team identify where in the game the goals, objectives, and deterrents (challenges), need to be tweaked to create the right emotional response.</p><p><strong>Tuning the emotional response is one of the most difficult portions of game design.</strong></p><p>Casual games might differ than more action-based games, but the idea is essentially the same. When people are emotionally involved in a game, they will play it more often for longer periods of time. Playtesting can illuminate how users feel during specific points in the game. It can also be used to adjust the difficulty to maximize the impact of the story arc.</p><p><strong>The pace of a game can greatly impact its user experience.</strong></p><p>Pace, also known as flow, is a huge topic and could cover a whole chapter in a book. Suffice it to say that nailing the flow for any given portion of the game is essential to keeping subjective measures, such as fun, high. Playtesting can tell where, in a game, users lose focus, disengage, or just get bored.</p><p>During a playtest, interviewing individual players is cumbersome and inefficient. Therefore you need to use a tool for large scale investigations such as surveys. Surveying the target users before, during and after gameplay can be very revealing. It can also be used to track a game’s progress towards their KPIs (Key Performance Indicators). KPIs are metrics that are gating factors for release.</p><p>Some common UX KPIs are below, but the specific KPIs are very much specific to the game/product being built:</p><ul><li><strong>Fun:</strong> a slippery concept that is difficult to operationally define, but is central to game creation. The target level of ‘fun’ can be decided within the team, but most often it is defined by a competitor. Game development teams can be heard to say, “I want this to be as fun as World of Warcraft”, or whatever the genre of the game being developed. UX research can determine whether that goal is hit.</li><li><strong>Ease of use: </strong>how easily can users interact with the game to accomplish their goals. This is not the same thing as the game’s difficulty rating. This is an evaluation of how easy it is to interact with the game, not the level of skill necessary to complete the game. I like to think of the old game of horseshoes. Almost anyone can throw a horseshoe, but it takes some skill to achieve the goal of the game and hook the post (throw a ringer). The usability of the game (throwing the horseshoe) is not an indicator of the difficulty of the game.</li><li><strong>Visual appeal:</strong> how well does the look and feel of the game meet or exceed target users’ expectations? This is a measurement that can be compared to competitive products to get a relative score. It is a moving target, as trends change and technology improves, so visual appeal is a metric to be constantly rechecking.</li><li><strong>Performance:</strong> how well does the game keep up with the users’ input and expected output? This data can inform system requirements to make the game run optimally and meet users’ perceptions of acceptable performance.</li></ul><p><strong>Post-playtest focus groups can reveal insights into what the participants found to be too challenging, or distracting.</strong></p><p>Basically, the research is aimed at uncovering any moments during gameplay that pulled the user out of their immersed state (if immersion is a goal). The follow-up focus group can shed light on survey scores from the playtest. Surveys typically tell you what is going on, but they cannot tell you why. The follow-up focus group can tell you why the game scored the way it did.</p><h4>Measuring an experience over time</h4><p>At this point, you might think, “This is great if I am building a game that is meant to be played for only a couple of hours, but how do you figure out if a game is fun over a long period of time, maybe even hundreds of hours?” UX can help here too.</p><p>User Experience research “borrows” from other social science methodologies. Qualitative research methods offer several options to uncover users’ impressions of a game over time. Longitudinal studies have long been an acceptable method of studying groups of people over time. Some examples of these methods include: diary studies, one-on-one interviews, contextual inquiry, among others.</p><p>Frequently, when a game is being prepared, the development company sponsors a “beta” which allows many users to play the game with the intent to find bugs in the code, which cause the game to crash or misbehave in some fashion. UX can piggy-back on that effort and enhance the feedback to find not only bugs in the code, but also the parts of the game that are not performing at the quality bars that the team has decided upon (or perhaps defined through competitive analysis).</p><p>Whether doing a diary study, which has beta users fill out a short questionnaire every time they play, or weekly feedback meetings, having regular contact with the target users about the experience can ensure that the release will be a success.</p><h3>Production</h3><p>The UX team should be ramping down their efforts at this point. They should not be coming up with new experiences, but they should be refining the experiences that already exist. Design, at this time, is refining the shell and ensuring its seamless integration into the game as well as ironing out any game mechanic problems. User Experience research is finishing up the usability studies and preparing for a pre-release benchmark.</p><p>The benchmark study is exactly the same protocol as the competitive benchmark that was prepared and executed in the Ideation phase. A benchmark at this phase of development measures the game against the goals established from the competitive benchmark. How and when to handle areas where the game did not pass the benchmark is a decision that the product team has to decide at some point during the late production phase.</p><p>Ideally, the KPIs were decided at the beginning of the development and remain in place until shipping. If the game did not reach its ‘fun’ goal, then it needs to be tweaked (hopefully that was caught long ago in user testing). If the ‘ease of use’ score is low, then something needs to be simplified. If the ‘visual appeal’ score is low, then some redesign may be in order. However, if the product team and the UX team have been in communication throughout the development cycle and the product team has responded to the feedback that users have provided, then the game should pass the benchmark, or better, surpass the competitive scores.</p><h4>Agile and Lean Development</h4><p>Even though this series is laid out in a waterfall format, it still applies to agile and lean methods, however, the chunks of work are significantly smaller. Adapting to a different development cycle is a topic that has been covered extensively on the Web. We did not want to rehash that topic here.</p><h3>Epilogue</h3><p>This series has been simplified tremendously to keep the blog posts from being too long and boring (it may be too late). In-depth UX plans for a game should be developed in tight collaboration with the product team. Resourcing, timelines, and game ambition, among other more dynamic factors, can impact whether you will release a great game. There are many, many variables that I did not include here that need to be weighed and incorporated when determining the likely success of a game.</p><p>This series is not meant as an instruction manual, but rather an summary of the touch-points where game development organizations may want to consider reaching out to User Experience professionals.</p><p>Allowing UX into the process early on will not only help reduce costly code churn late in the cycle, but it will also reduce CSS calls post-launch. With the speed and reach of social media and the ability to review products online nearly instantly, putting out a mediocre game and fixing it after release is not a recipe for success. However, utilizing UX experts at the appropriate times can greatly improve your chances.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e621e282d29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX in the Game Development Process — Part 2: Converge]]></title>
            <link>https://medium.com/@duplastudios/ux-in-the-game-development-process-part-2-converge-523a780c7e2b?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/523a780c7e2b</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 00:29:26 GMT</pubDate>
            <atom:updated>2016-11-23T00:29:26.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuNfEaVFuiKDBwWs1Us-ug.jpeg" /></figure><p><em>In this blog series, we walk through the game development process and point out key moments when adding UX Researchers and Designers into the discussion can reduce time, increase momentum, and positively influence the final product.</em></p><p>In the last post, we discussed the <a href="https://medium.com/@duplastudios/ux-in-the-game-development-process-part-1-ideation-15228b71fddc#.v1w195uos">first phase of the game development process: Ideation.</a> During this initial phase, the game’s basic story is laid out, and game features classified as “must haves”, “nice to haves” and “table stakes” are defined. During Ideation, divergent ideas are imagined, encouraged, explored, and their relative importance is weighed.</p><p>In this post, we will cover ways in which UX can help the game development team during the Convergence phase — the time of the process when choices start being made.</p><h3>After Ideation — Real Choices</h3><p>The second phase of game development is about a convergence of ideas. Convergence is the time when you eliminate all of the undesirable ideas and focus on one or two ideas that appear to be winning, plausible directions. Once that is done, it is time to scope the project. It is time to make choices.</p><p>During the Convergence phase, the team will be busy storyboarding, digging into the preferences of their <em>best bet</em> target audience, and defining the game mechanics, reward structure, and visual style. The game artists are developing the characters, the effects, the landscape. The “universe” of the game is becoming clear and the game is starting to look like something that resembles a story.</p><p>As decisions are made, the game starts to converge on a unified environment and the list of details that need to be figured out starts to grow.</p><p><strong>How does User Experience help with the Converge phase?</strong></p><blockquote>Between UX Research and Design there a several big areas that they can tackle, most importantly: feature prioritization, shell and menu design, and game interaction design.</blockquote><h3>Can’t Make It All — Cliffnotes On Feature Prioritization</h3><p>There are three primary groups of features that every product has. There are “must haves”, “nice to haves”, and “table stakes”. Sometimes, “table stakes” and “must haves” are confused. The distinction is that “must haves” are features that drive potential customers to your product. “Table stakes” are the features that, if not present, will drive your customers away from your product.</p><p><strong>Unfortunately, “must have” features get all the attention.</strong></p><p>“Must haves” are the parts of the game that make it into the demos and press releases and, quite frankly, make the game sexy. “Table stakes” features are more often than not, essentially invisible. Because of that, they are sometimes put on the back burner.</p><p>The unfortunate outcome of putting them off is that it becomes easy to slip them off the work item list altogether or give them only cursory attention late in the development/iteration phase. By this time, it is probably evident that this discussion of “table stakes” versus “must haves” comes to a critical junction when establishing the timeline.</p><p>There are way too many factors that go into establishing a timeline for game development to address here. However, ensuring that the timeline has space to land, the “table stakes” items can make the difference between a hit and a mediocre game. This becomes a real pinch for teams, especially when using Agile development practices or Lean engineering to develop the game.</p><blockquote>We have found that the best way to keep the balance between “must haves” and “table stakes” is to have regular frequent contact with the target audience.</blockquote><p>Gathering user feedback can cause turmoil as well. The audience is seeing a partially finished game and everyone knows that. It is tempting for the team to want to caveat the work as it is shown to the audience. By caveat we mean focusing the attention of the users who are providing feedback on one or two aspects of the game — like target acquisition, or steering mechanics. However, doing so can make your test audience gloss over and forgive problems and issues in “table stakes” items.</p><p>In some cases, for example, when trying to nail down a specific interaction, providing caveats will help focus the feedback of the audience. However, letting the game stand on its own each time it is shown to potential customers can ensure that the list of feature priorities is correct and the balance between the “must haves” and the “table stakes” is maintained.</p><blockquote>Playtests, usability sessions, and 1:1 interviews are all valuable tools in determining whether a game has moved too far towards “must haves” and too far away from “table stakes”.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4qmPxBpLMDYMv7HqsAHs0Q.jpeg" /><figcaption>An example of a playtest environment (souce: g<a href="http://www.gamasutra.com/view/feature/3963/the_silent_revolution_of_.php?print=1">amasutra</a>)</figcaption></figure><h3>Keeping Them From Leaving</h3><p>During the Convergence phase, UX Design initiates their design of the “shell”. In this case, we define the “shell” as the parts of the game that are not part of the play mechanics. This could include the menus, game settings, options, etc.</p><p>In a well designed game, the menus should not be a harsh contrast to the actual game, even though menus are, for practical purposes, a wrapper. The best shell design works under the same paradigm and universe as the game itself. If the game has a rotary menu system, the shell should match that as well. It doesn’t have to be exactly the same, but familiar.</p><p>It takes a good designer to fit all of the dry shell necessities in an efficient way within a game that is created for fun. A good game immerses the target audience in new environments, and a good shell design should not make them surface too abruptly.</p><p>Dirt2 was a racing game that did a good job of keeping the theme of the game in mind as the user traverses the non-gameplay portions. For example, the player moves through different in-game geographies when moving from one type of menu to another, which keeps the groupings logical and their locations race-like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/284/0*CBqfb0GNkGf5mowT." /><figcaption>Menu selections took players to new geographic locations in the game</figcaption></figure><p>The menu titles appeared as if written on duct-tape, much like the participant areas of a real race settings. These bits of authenticity helped to keep the player immersed in the racing world while facilitating their navigation both in and out of the gameplay itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x20cL5NeIDSFg0eX.jpg" /><figcaption>Dirt2 used authenticity to keep players immersed</figcaption></figure><p>Shell efficiency is as important as the look and feel. After all, players want to play and not mess around with optimizing the game for their specific needs. Keeping the menu system and game options as efficient as possible should be the priority.</p><blockquote>User Experience Design can accomplish that through workflow identification, wireframing, and prototyping. User Experience Research can run usability sessions to identify any problems with the workflows or bring wireframes into the lab to ensure ‘ease of use’.</blockquote><p>There are quite a few resources on the Web that can provide examples of good shell design. There are many more examples of bad shell design. Bringing design into the conversation when the team is converging can help games stay out of the bad category. Being part of the early discussions ensures that the designers understand the game itself to produce the most efficient and appealing shell design.</p><p>User Experience Design is also integral to the in-game play as well — helping engineers think through the different actions that a user will have to do, and mapping that workflow to the most logical control arrangements. UX Design can help identify when a game is putting too much complexity into an interaction. User testing of the interactions can identify the usability problems, but designers need to figure out how to fix issues uncovered by said testing. More on that in the next post.</p><p>If we imagine that at this point we have a game concept, some initial art, a story arc, and some shell design complete — all of which have been shown to users for initial feedback — the hard work to make the next big hit really enters high gear.</p><p><em>This is part 2 of a 3-part blog series on how UX can fit into the game development process. Check out </em><a href="https://medium.com/@duplastudios/ux-in-the-game-development-process-part-1-ideation-15228b71fddc#.d5xi48y7e"><em>Part 1: Ideate</em></a><em> and stay tuned for Part 3: Iterate &amp; Produce.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=523a780c7e2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX in the Game Development Process — Part 1: Ideate]]></title>
            <link>https://medium.com/@duplastudios/ux-in-the-game-development-process-part-1-ideation-15228b71fddc?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/15228b71fddc</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[games]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Tue, 08 Nov 2016 20:27:29 GMT</pubDate>
            <atom:updated>2016-11-23T00:31:59.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*OEyuATfBJlAfzdnVh5N6Ag.jpeg" /></figure><p><em>In this blog series, we will walk through the game development process and point out key moments when adding UX Researchers and Designers into the discussion can reduce time, increase momentum, and positively influence the final product.</em></p><h3>Let’s Start With Phase 1: Ideation</h3><p>The ideation phase of any product development is arguably the most messy of all phases.</p><p>This is the time where the ideation cauldron is brewing a heady mix of marketing data, people’s pet projects, and usually at least one technology/innovation idea. At this time, any idea is valid and validation of an idea is not necessary for it to be taken seriously.</p><p>For those in the User Experience (UX) discipline who are following along — this is where ideas diverge.</p><h3>Tap Into What Your Gamers Want — Even If They Don’t Know What They Want</h3><p>Into the cauldron of game ideation, UX can bring a simple dose of reality to help define the canvas of innovation.</p><p>Real data from customers — or potential customers — allows the team working on the game to rationally decide which ideas need to be developed and matured and which ones can be dropped off to the side. This is not a groupthink, or design by consensus.</p><p>The data brought by UX Research skirt the edge of marketing and ethnographic methods. Using a mix of focus groups, surveys, and industry reporting — in other words, a mix of original and secondary research — allows the illumination of which concept ideas are truly outside the range of plausible successes. That means that we cannot guarantee a sure hit but we can definitely eliminate clear misses.</p><p><strong>“But I know several games that were surprise hits”, you might say.</strong></p><p>To be clear, this post is about a reliable method of producing a successful product. There are many surprise hits which did not use this process — the so called “one hit wonders”. However, a repeatable method allows the game developer to tap into the zeitgeist of their target gamers, even if the gamers themselves don’t know what they want — <em>Insert old saying by Henry Ford here about asking customers what they want</em>.</p><p>This process does allow for a practical approach when there is not a clear path to follow. It can point in the right direction when there are too many diverging opinions, which can cause a team to stagnate and wallow in opinion. In summary, it can’t tell you exactly what to build, but it can keep you from building the wrong thing.</p><h3>Turning Undecided Gamers Into Customers</h3><p>Ideation is the time when a game manufacturer has a whiff of an idea and is trying to determine the concept, genre, and classification of the game they want to develop. Alternatively, the game developer already has a baked concept, but doesn’t know if it resonates with an audience. The concept could be a sure thing, but the developer doesn’t even know who their audience is.</p><p><strong>Questions that are typical for this phase:</strong></p><blockquote>Would 18–35 year old males like a turn-based fantasy game that incorporated Steampunk themes and elements of time travel and an iconic messiah protagonist?</blockquote><p>Research can find out.</p><p>Much like TV shows and movies test concepts with a variety of focus groups to narrow their advertising, the game industry can do something similar to identify whether a game concept has legs — that is, whether it can become a successful product or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wLC5Cj_6MhHx8tiOKQ1Iig.jpeg" /><figcaption>An example of a focus group setting (Source: <a href="https://circajoylynn.wordpress.com/tag/chain/">https://circajoylynn.wordpress.com/tag/chain/</a>)</figcaption></figure><p>For example, with focus groups, you can narrow your focus early and target the people who will likely buy the game when it comes out. You can also eliminate some of the unnecessary features that will not improve the breadth of your customer pool and zero-in on those elements which could turn an undecided gamer into a customer.</p><p>Another situation that we typically see is when someone’s pet project becomes the root of a game design.</p><blockquote>My Principal Artist wants a space setting and spaceship set pieces. Is that interesting to our target customers?</blockquote><p>Could be. Researchers can find out.</p><p>With the right set of stimuli, a UX Researcher can find out through several methods, whether the space setting would increase or decrease interest with the type of game you want to build.</p><p>Additionally, research doesn’t need to be relegated only to preference data, but can also be used to help decide game mechanics.</p><blockquote>Does this game play better as a first-person shooter or as a third person strategy game?</blockquote><p>Well, it depends on who you want to sell to, but guess what? Research can point you in the right direction.</p><p>Typically, if doing the sort of exploration we are talking about in the ideation phase, the more ideas you put in front of the target audience, the clearer the opportunity becomes.</p><p>Focus Groups are not the only way to connect with target users — surveys, forums, competitive reviews, and other methods are also capable of revealing the target users’ thoughts on concepts and ideas. Having someone sift through the information and find the insights is exactly what UX professionals are trained to do.</p><h3>But, Not Every Question Needs Research</h3><p>While we are on the subject of research, we want to emphasize that not every question needs to be answered with customer data. In fact, in deciding between a 1st and 3rd person shooter game, we would probably reach the conclusion that this is a design decision, rather than one driven by UX Research. Some people may be asking, “What is a design decision versus a user-driven decision?” However, that is a subject for another blog post at another time.</p><p>Of course, this is merely the beginning of a journey. It’s really only the first step. Next we start to converge, bringing ideas from multiple vectors and wrapping them into a coherent story.</p><p><em>This is part 1 of a 3-part blog series on how UX can fit into the game development process. Check out </em><a href="https://medium.com/@duplastudios/ux-in-the-game-development-process-part-2-converge-523a780c7e2b#.15avqwo0x"><em>Part 2: Converge</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15228b71fddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Swarms: A Design Process With A Twist]]></title>
            <link>https://medium.com/@duplastudios/design-swarm-a-design-process-with-a-twist-41f36a93b80f?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/41f36a93b80f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 18:02:40 GMT</pubDate>
            <atom:updated>2016-10-27T00:17:13.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_LejqcYLkgTIxLNhbQ5Vw.png" /></figure><p>On October 2016, at the <a href="http://2016.seattleinteractive.com/">Seattle Interactive Conference</a>, the founders of Dupla Studios participated in <a href="http://surya-vanka-8hb7.squarespace.com/">Design Swarms</a>: a design process with some interesting twists created and facilitated by <a href="http://www.idsa.org/members/surya-vanka">Surya Vanka</a>, Principal of <a href="http://authentic.design/">Authentic</a>. We spent 6 hours with groups of 7 people, most of whom had never met each other beforehand.</p><p>We felt inspired by the process and would like to share some key insights with our community of designers, technologists and innovators.</p><h3>But First, Some Context:</h3><h4>The Problem</h4><p>The World Health Organization estimates that 1.8 billion people drink from contaminated water sources, and 3.4 million die each year from water borne diseases such diarrhea, cholera, dysentery, typhoid, and polio. If you stop and look at your watch for 90 seconds, it might be shocking to realize that during that time, a child died from drinking contaminated water.</p><h4>The Tech</h4><p>During this Design Swarms, we worked with the <a href="http://www.cascadedesigns.com/msr/global-health/se200/product">MSR Community Chlorine Maker</a>, a device that allows communities in low-resource settings to take control of their own supply of drinking water by producing their own chlorine on-site. The device automatically manages the technical aspects of chlorination (such as the right proportions) so communities with no experience in chlorination can effectively treat water safely and reliably.</p><h4>The Challenge</h4><p>The proposed challenge for this day was to devise a disruptive approach by which the Community Chlorine Maker can become available to every low-resource community in Kenya.</p><h3>The Design Swarms Process</h3><p>The Design Swarms process borrows from the traditional user-centered design process as well as agile practices, but it adds some interesting twists, which we believe would be beneficial to any future design activities you might have. From a one-day intensive sprint, to one that lasts one month, to longer ones that last a few months — the process can be beneficial to your creative endeavors.</p><h4><strong>Step 1. One shared collaboration surface (Phase I: Orient)</strong></h4><p>Before joining our first Swarms, we were wondering what would we be using as a shared collaboration space. What kind of a tool could we use that would allow 7 people to contribute to a single solution?</p><p>The Design Swarms process provides an essential piece to start with: a shared collaboration surface that is not just a blank canvas. The Swarms organizers provided a map (actually 2 maps) guiding the team through the process, with some time-specific suggestions to keep us focused throughout the exercise, such as “Start with the person not the tech”. We found the maps both provocative and focusing, providing an invitation to fill-in all the blanks while keeping the group moving in a unified direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMF50yM_99yLuXzNS5KZig.png" /><figcaption>The Design Swarms collaboration canvases (Part 1 at the bottom and Part 2 at the top)</figcaption></figure><h4>Step 2: Start by bonding with your team (Phase I: Orient)</h4><p>A few days before the Design Swarms even started, the Swarms facilitator and leader Surya Vanka sent an e-mail to each team asking us to introduce ourselves to one another.</p><p>We followed the simple template for our introductions:</p><ul><li>Who are you, what do you do, and where do you work?</li><li>What are you passionate about?</li><li>What are you good at (What’s your superpower)?</li></ul><p>Because of the intros, we already electronically knew about each other before sitting at the same table. That made the initial bonding a lot easier as we first sat down to work together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/302/1*xb7enQ-Ghz7N0PeR8cLN5Q.png" /></figure><p>The first activity at the Design Swarms was to post on the leftmost part of the canvas our team logo and name (which we had only a few minutes to come up with) as well as sticky notes with our individual self-assigned superpowers.</p><p>Some examples of the superpowers in one of the groups: Loving, empathy, observant, aware, conscious, creative thinking, translating insights into designs, project management, listening, adventurous.</p><p>At Dupla Studios, we believe that trust is the basis for every good team collaboration. We also believe that you will get the best out of a group by knowing and respecting each person‘s unique contribution to an effort.</p><h4>Step 3. The design brief (Phase II: Frame)</h4><p>After bonding with our newly-formed teams, we were given background on the problem we were about to tackle: how to reduce the number of illnesses and deaths due to the drinking of contaminated water in under-developed communities. More specifically, we were working with communities in Kenya.</p><p>The design brief had pretty much what we wrote at the start of this post: The Problem, The Tech and The Challenge.</p><p>Finally, the brief described the expectations of the outcome:</p><ul><li>An evocative storyboard that brings our solution to life</li><li>A 15-second video tagged #designswarms</li><li>A 3-minute presentation</li></ul><p>Ready? Set. Go!</p><h4>Step 4. Interviews with Subject Matter Experts (Phase II: Frame)</h4><p>We had to quickly understand the problem space, the technology and the culture of the place where the problem had to be solved (Kenya). We started by doing secondary research online but we also had access to a set of Subject Matter Experts (SMEs).</p><p>The interesting twist in this phase is this: We had 6 groups, limited time and a limited number of experts. Each group was provided a limited number of cards that we could use to trade for 10 minutes of consultation with an expert. The limited time with the experts made every question intense as we did not want to waste our time asking questions that did not move our ideas and understanding forward.</p><p>One note about the experts: Not all experts could help with every part of the Swarms. Choosing the right expert to talk to was a combination of where in the Swarms you spoke with the expert and their specific specialty. We found that their specialties weren’t clear, so we ended up talking to an engineer early in the process when most of our questions were about the people and the culture.</p><p>In retrospect, it became apparent that we needed 3 types of SMEs: Experts on the problem of distribution (operations experts), experts on the technology itself (the MSR Community Chlorine Maker) and experts on the culture of the people who will be using the solution (Kenya).</p><h4>Step 5. The persona spectrum (Phase II: Frame)</h4><p>It was then time to devise personas. Who will we be designing this for? We created a persona spectrum, starting from the least able persona (the one who needs it the most) to the one who needs it the least.</p><p>We asked ourselves: “Who are the people who can impact the problem?”. That helped us pick who we’d be designing for as well as scoping our solution. Naturally, these personas were based on limited secondary research and limited time with the SMEs, but they did provide a rough profile that we could use to make simple design decisions.</p><h4>Step 6. Ideation and diversion (Phase III: Ideate)</h4><p>Now it was time to ideate. Each team member had to come up with at least 7 ideas in a short amount of time. Having a short amount of time is crucial so you keep generating ideas without having the time to overthink any of them. This is roughly equivalent to the time in a classic design process where ideas diverge from one another.</p><p>During this phase, we were following the guidelines below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tuv-a2uFbrwCaq9G8taDag.png" /><figcaption>Credits: Cindy Chang</figcaption></figure><p>The intriguing twist for this portion was that we not only wrote out an idea, but also added a simple illustration of the idea (as seen in “Be visual” above). This proved to be super helpful for us to be able to quickly identify an idea, group them with other affinities and see graphically those things that belonged together. It made it very fast to create affinity for ideas that may be combined together to form an even better idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*fn5dPCNORY1_Vj-GvA-Cjw.png" /><figcaption>Example of on of the team’s visual ideas.</figcaption></figure><h4>Step 7. Steal like an artist (Phase III: Ideate)</h4><p>Now that we had all those great ideas and they were easily communicated via the shared collaboration space, it was time to officially let them be stolen and also steal from others. Every group left one person on the table to explain the ideas on their home board, while the other people in the group went around stealing ideas from other teams.</p><p>There was only one rule that had to be followed: You needed to redraw the stolen idea and add it to your own board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*I7yKKF0XhVRfQ80iL7a08A.png" /></figure><h4>Step 8. Pick 5 most promising directions (Phase III: Ideate)</h4><p>With the ideas on the board (stolen or not), it was time to start converging into the 5 most promising directions. Those were in written format, with specifics for each.</p><p>It followed the format:</p><ul><li>What’s the main idea</li><li>What are some specifics about how that idea will be implemented</li></ul><p>This is when the illustrations really paid off. It was easy to spot ideas that could be strung together or ideas that built on one another. We thought it made the convergent process much easier than the classic affinity diagramming with only text written on post-its.</p><h4>Step 9. Written description of the decided direction (Phase IV: Iterate)</h4><p>This is the time in the design process where we make our bet. We chose a direction that wove our best ideas into a cohesive story.</p><p>In this phase, we had a written description of the decided direction, which directly informed the final storyboard. Having a written description of all the key points in the story was essential to move from a bunch of ideas into a story line. It made the final process of storyboarding a lot faster and smoother.</p><h4>Step 10. A storyboard that brings your solution to life (Phase V: Deliver)</h4><p>The final delivery was a 12-frame storyboard that brought the solution to life. The storyboard had the selected persona as the main character and wove many of the previous ideas into a compelling story that we later presented in a short 3-minute presentation to a panel of judges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ax7ZURwerAxg-ZrcMClbUg.jpeg" /></figure><p>It was a very interesting and fun exercise. Many of the twists were very useful even in a classic design process and we hope to leverage those in our own work. If you are interested in the outcome of past and future Swarms in the real world, you can get more information by contacting <a href="https://twitter.com/suryavanka">Surya Vanka on Twitter</a>.</p><p>We thank Surya for the opportunity to have this experience and to provide us an avenue to put out some of our ideas for social change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41f36a93b80f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design + Research: What Does It Mean To Be More Than Additive]]></title>
            <link>https://medium.com/@duplastudios/design-research-6c8c0705ed48?source=rss-f4a1d2375e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c8c0705ed48</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Dupla Studios]]></dc:creator>
            <pubDate>Thu, 25 Jun 2015 05:42:40 GMT</pubDate>
            <atom:updated>2016-11-20T01:45:36.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5BdCazi1xGtcJdO3k4uvQ.png" /></figure><p>We believe that great products are designed by hot teams comprised of different disciplines. While we recognize that multiple disciplines are essential to the success of a product, our expertise is in user experience (UX) research and design, and we know from experience that the two disciplines tightly integrated are greater than the sum of its parts. This is probably something that every UX professional will think it’s obvious, but after 15+ years working in the industry, we’ve noticed that this is something that very few actually practice.</p><p>We would like to share our 5 principles to creating great experiences that leverage the best of design and research.</p><ol><li>Together from the start</li><li>Product success over personal showmanship</li><li>Ego has to be left at the door</li><li>Good user data trumps anyone’s opinion</li><li>Know your superpower</li></ol><h3>1. Together From The Start</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qLVrfMI6Aj0g5FTpcr5Fcw.jpeg" /></figure><p>In the years that we’ve been doing product design, we’ve seen a common misunderstanding of the way that design and research work together. This could be illustrated in an image of two right triangles balanced on top of each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*zXGmoFY1GCpOqtfP3V-t_Q.png" /></figure><p>In the beginning of a product, research is under a heavy workload identifying users, their explicit and implicit needs, their workflows, as well as their habits and practices. In many groups, design is a passenger on these trips, attending some of the research, but the researcher carries the responsibility of creating all the collateral, protocols, reports and presentations.</p><p>As the product moves forward and the initial research is complete, the data becomes more tactical and specific to the product workflows and less about the generative research. Meanwhile, design is ramping up starting to deliver explorations and screen flows that exemplify the workflows. Their heaviest workloads are still ahead of them: designing brand and personality, design patterns and style guides. We have seen many researchers distance themselves from those decisions and only interact with the designers as usability data becomes necessary. Likewise, we’ve seen designers not participate in the generative research phase. Sometimes for lack of managerial support, or because they are too busy, but most times it’s because they are not interested. Some designers just wait for a report to come in, with all the insights already defined for them.</p><p>This is not a single point of failure — it is a common separation — especially in large corporations where individual contribution is valued more than product success (we will talk about this later in this post). Some researchers feel more comfortable talking to designers than other researchers, and some designers are more comfortable in the lab or out in the field than other designers.</p><p>A designer joining in on ethnography research is invaluable for creating a thorough understanding of the target users and their needs. Some insights come from direct observation and having two pairs of eyes is always better than only one. The same goes for participation in usability studies. What a designer gets by watching body language, user actions, comments and struggles is much more than what she gets by reading a report that has been “thrown over the fence”.</p><p>The same is true for the researcher. By the end of the generative research phase, he has an intrinsic knowledge of the users. More knowledge that can be put into words, images, or a report. More knowledge that can be expressed. Knowledge that is invaluable in the iterative design phase that is about to start. Researchers should have responsibility for driving those insights into the design and suggesting interactions that bridge the gap between the user’s knowledge and the current workflows.</p><h4>The separation leaves gaps where the truly amazing design can slip through, get lost, and never make it into a shipping product.</h4><p>This does not mean that researchers need to be able to design or designers would be better at their jobs, if they knew how to run a research effort. While they are great skills to know, in a truly collaborative environment, it is not necessary.</p><p>We witnessed this in a couple of groups, at large corporations, where the design researchers were churning out usability studies at about one every 3–4 weeks. This behavior was not just encouraged, but performance reviews, advancement, and bonuses were explicitly stated to be tied to the pace. The designers on the project barely had time to digest the research before they were iterating on the design in preparation for the next study. The researchers never had time to review the designs prior to beginning the next study.</p><p>Now, some of you out there might be thinking that the researchers or the designers should have slowed the pace and forced collaboration. However, some design managers explicitly stated that they did not want researchers to provide suggestions for fixes, which created resistance to a deeper collaboration. Between the way people are rewarded, to how managers make decisions, the two disciplines are seen as separate. This needs to change.</p><h2>2. Product Success Over Personal Showmanship</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIIJZw55_LCs7fg1dDXYKg.jpeg" /></figure><p>Corporations vary significantly in the amount of time and investment they put into user experience. However, the corporation’s reward systems are built around the antiquated fiscal schedule: bonuses, raises and reviews are all conducted on a schedule that fits nicely with quarterly or yearly earnings reports and shareholder meetings. Frequently, this imposes artificial points in time when employees are measured. These reviews sometimes happen before one can determine whether or not the product is a success or a failure. Because of that, reviews of the work done by UX professionals become about their individual contributions and not the success of the product or the team they are working with.</p><p>This is not the only reason, but it creates a lot more dickheads. We use the word dickheads here in reference to an amazing Medium post that really resonates with our way of thinking: <a href="https://medium.com/@rhysys/no-dickheads-a-guide-to-building-happy-healthy-and-creative-teams-7e9b049fc57d">No Dickheads! A Guide To Building Happy, Healthy, and Creative Teams</a> by <a href="https://medium.com/@rhysys">rhysys</a>. Below is a quote from the post that we couldn’t agree more.</p><blockquote>“My definition of a dickhead is a person whose ambition for themselves or their own career is greater than their ambition for the project or team”.</blockquote><p>It takes a team of great people to create great products, not individuals working separately each with their individual goals. The success of the product is what everyone should be rallying around, not their next bonus or promotion.</p><h2>3. Ego Has To Be Left At The Door</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TG7CwlWq9ULy00pd4Lasmw.jpeg" /></figure><p>If you are a user experience designer or researcher, chances are that you are working on some sort of digital product: an app, a website, etc. The product you work on is used by a set of people — it’s users — and serves the ultimate purpose of improving the lives of those people in some way.</p><p>The purpose of your work is to make the best possible product. Decisions should always be made taking into consideration what is best for its users and thus, for the product.</p><p>It takes letting go of ego and working towards something greater than yourself. And it’s also not about one person being the hero, it’s about a team of people working together towards a shared goal: shipping the best possible product that users will love. In the end, the user is the hero. Not you.</p><p>After all, product design is about improving the lives of people, so it should be a no-brainer to come back to the very basic reason of why you do what you do. Are you a designer or researcher because you want to solve tough problems and make the world a better place? Or are you interested mostly in advancing your career or other interests?</p><p>We know of one corporation where a new team was started to develop a product in partnership with another big corporation. The UX lead was cherry picked to lead the effort and built a team made up of senior researchers and designers, each with a record of doing high-profile work. Unfortunately, each brought with them an ego and career ambitions that were exclusively about increasing their prestige within the organization. Snarkiness, backstabbing, and bullying ensued. The project stalled in arguments that could not be resolved as each “rock star” felt they knew what was best and were completely unwilling to compromise. Needless to say, the team imploded, the participants disbanded and the partnership fell apart.</p><p>Being on a team and being part of a team are two different things. Making reliably great products is a team effort, not a hero journey.</p><p>This reminds us of the old saying:</p><blockquote>“We have two ears and one mouth so that we can listen twice as much as we speak.”<br>― <a href="http://www.goodreads.com/author/show/13852.Epictetus">Epictetus</a></blockquote><p>Or as one of my old teachers used to say, “You have two ears and one mouth, use them accordingly.”</p><h3>4. Good User Data Trumps Anyone’s Opinion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F-DyzmVD3et8DvBLvbDiiA.png" /></figure><blockquote>“Without data you are just another person with an opinion.”<br>— W. Edwards Deming</blockquote><p>In user experience, the user is the king. You really shouldn’t waste your time arguing with the king.</p><p>We’ve all seen users blaming themselves in usability lab studies. It is human nature to blame yourself and not the product. But the blame is on the people designing the product, not the users. Observe. Listen. And iterate the hell out of your design until you have removed all its problems.</p><p>The wife of the HIPO’s (Highly Important Person with an Opinion) likes blue? Great! She can go buy a blue car, or a blue pair of earrings. Remember: it should always goes back to the users of the product. If they can’t use it, don’t like it, or already love their current solution, then your product will atrophy and die.</p><p>Is there any real difference between a system crash that completely shuts down an application or program and a product that is so confusing that the user doesn’t know how to use it in the first place? In either case the users cannot achieve their goal. Although there may be an argument that if a system crash happens, people are much more willing to blame the development, while merely confusing products, prompts users to blame themselves. In corporations that seems to be an acceptable trade-off.</p><p>The beauty of a designer working alongside a researcher, is that they can iterate the designs based on real observation and real people’s feedback. Since they are hearing from users from the get-go, the designs are based on real human needs, and not assumptions, from the very start.</p><p>Speaking of assumptions: we recommend that you write down your team’s assumptions about the product and go test them. We watched a large company invest huge sums of money without spending a little bit, relatively speaking, on testing the assumptions of the product team. We know untested assumptions can ruin an entire product. True story. Hundreds of thousands of dollars, lost.</p><h3>5. Know Your Superpowers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fu0bQ1dBWQe_zi4aKP-vZg.jpeg" /><figcaption>Illustration by digital artist Marko Manev</figcaption></figure><p>This may sound trite and cute, but we mean it. We have been concentrating this post on the specific disciplines of design within the larger product development structure. Now, we want to turn our attention to the link between the user experience disciplines and their relationship with the rest of the disciplines needed to ship a quality product. Knowing your superpower is really just about knowing what are the special skills that you bring into the mix when creating a product or service. What does research and design bring that no other disciplines can?</p><p>In nearly every team we have worked on, user experience has touched more surface areas of the product than almost any other discipline. Our net is large and usually encompasses the entirety of a product or feature, while program managers, developers, testers and writers tend to dig deeper into a specific area.</p><p>Our disciplines can learn a lot by going deep into the technology, but going too deep can keep a product in a specified path and can limit the innovation and exploration. It is very important when going deep into the technology of a product to recognize that you are developing a bias and you should deliberately break the boundaries of the technology, so that you can find that next big step forward.</p><p>Nevertheless, design and research should look at the product differently than the development team. We need to see the product from the users perspective and that is our special sauce, our superpower, you might say. Having research to develop insights into how users behave and why, is key to developing not just a logical design but a “human-powered” design.</p><p>Putting designers in research allows them to feel the frustrations of the user and that empathy can create passion and energy to do better. Certainly, the same is true for the other disciplines that make up a product development team, however in the end, user experience creates the bridge between what is now and what could be in the future. Know what you’re best at and what your partner is best at, then leverage each other. You should work and interact as a unit to product teams or clients. The sum will be much greater than the parts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c8c0705ed48" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>