<?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 Yang Chen on Medium]]></title>
        <description><![CDATA[Stories by Yang Chen on Medium]]></description>
        <link>https://medium.com/@yangchen?source=rss-76d25fba7cc5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*imfJWc-GR3JC4u_ua8QFEw.png</url>
            <title>Stories by Yang Chen on Medium</title>
            <link>https://medium.com/@yangchen?source=rss-76d25fba7cc5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:28:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yangchen/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[UX methods: Automated Remote Research]]></title>
            <link>https://medium.com/uwaterloo-voice/automated-remote-research-b2bff0fd9769?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2bff0fd9769</guid>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Mon, 18 Dec 2017 02:28:58 GMT</pubDate>
            <atom:updated>2019-02-01T21:15:25.033Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A second post in a series on UX method</em>s</p><p>It’s 6 p.m. in a cold, wintery Moscow, Russia. Alexandra, a 21-year old college student is studying at home when she receives a notification on her phone — she has been recruited to complete a usability test on Amazon.com. After following the link to the site, Alexandra is prompted to complete various pre-determined tasks while thinking aloud. Within 30 minutes, she completes the set of tasks and receives $30 in compensation.</p><p>Halfway across the globe, it’s 9:00 a.m. on a rainy day in Seattle. Brendan, a user experience researcher for Amazon, receives a complete audio recording and screen capture of Alexandra’s test session. He doesn’t have time to open it though (at least not right now) — it’s only one of dozens received from users around the world, each a data point in a usability study of Amazon’s latest new feature.</p><p>The above scenario illustrates how automated remote research can be used in the real world. <strong>Automated remote research</strong> (alternatively, <em>unmoderated remote research</em>), is a user experience research technique used as part of the product design process. It involves using an online software program that records the screen and/or voice of test participants, as they complete a set of pre-determined tasks using your website or application. It allows for software designers to determine if users can use the product to easily accomplish relevant tasks.</p><p>In general, usability studies answer the question of whether or not a design is easy to use and intuitive for the user [1]. It usually follows something like this: a product or experience is put in front of a test participant. The participant is then asked by the moderator to complete a series of tasks while they are observed. The moderator listens to the participants as he/she “thinks aloud” during the process (see “Method 87 — Think Aloud Protocol” from <em>Universal Methods of Design</em>” by Martin and Hanington). However, in-person usability testing can have many drawbacks [2]; the tests are very time-consuming, as one facilitator running the study can take days just to do a few people, which also can be difficult to recruit. As such, these studies are conducted with small sample sizes, which may not be entirely representative of a diverse user base. Also, the testing is done in the context of an environment that is usually not representative of the real-world use of the product.</p><p>This is where remote usability testing comes in — tests are remote and anyone with internet access can click a link and complete a study. The tests can be done in parallel at any time, resulting in high time-efficiency. The remote testing software can even recruit participants automatically for you. It’s also time efficient because you don’t need to schedule anything, as the user can do it at their own convenience. As such, larger sample sizes can easily result without much extra work for each additional participant. This can reduce the margin of error, allow for more significant insights, and be more representative of a range of users [1]. Also, since users can do it wherever they want, they are more likely to test the product in the context of the actual environment they would be using it in. An example that highlights this benefit would be a fitness app to help a user work out in the gym. Testing the app while the user is actually in a gym is much more realistic than testing it in a controlled office setting, which can reveal insights that otherwise would’ve been missed. Typical questions that automated remote research studies can answer include the following:</p><ul><li>What percentage of participants able to successfully complete a task that involves using the product?</li><li>How long does it take on average for users to complete the task?</li><li>Do users have trouble completing the task? If so, where do they run into the issue?</li><li>What is the most common flow or click path that users take in the interface to get to where they need to be in order to complete the task?</li></ul><p>Notice that most of these questions are quantitative measures — the automated remote research method’s biggest strength is that by easily getting large sample sizes, numerical statistics can be easily generated and used to measure the user experience of a product. However, more qualitative insight on <em>why</em> a user behaves the way they do should not be ignored either — this can be accomplished by evaluating the video and audio recordings and seeing exactly how the user is interacting with the product, as well as using other research methods.</p><p>Automated remote research should not be confused with moderated remote research. In a moderated remote study, the moderator or facilitator is in a different location than the user, and is sharing screens with the participant in real-time. This is where you can see some cons to the unmoderated method — since a facilitator isn’t present when the participant completes the study, there isn’t any way to respond to comments or ask detailed follow-up questions specific to the test participant based on their experience with the tasks. The follow-up questions will have to be created pre-emptively and hopefully capture relevant information. Also, the facilitator can’t help the user if they get confused about a task and get sidetracked, or start to forget to think aloud. As such, an automated remote research study is best suited for the following use cases [1] [2] [3]:</p><ul><li>The tasks being tested are direct and specific, so users are unlikely to get off-track.</li><li>A large sample size is needed because you need a high degree of confidence (E.g. a feature’s design is critical and will have a major impact.)</li><li>You want to reach a broad, diverse range of users that are geographically dispersed and difficult to bring in for an in-person test.</li><li>It’s necessary to test the natural use of the product in the context or environment of its real world usage.</li><li>There’s limited time available to get actionable results</li></ul><p>The cases that are not suited for automated remote studies [4]:</p><ul><li>When you want to have tight control over confidential test material.</li><li>The users don’t have reliable or any internet access.</li><li>The visibility of the user’s face, body, or eye movements is important to the study.</li></ul><h4>Method</h4><p>The method for automated remote study can be broken down to 5 easy steps:</p><ol><li>Define the <strong>study goals</strong></li><li>Select the appropriate remote research <strong>tool</strong></li><li>Create clear <strong>tasks </strong>with defined <strong>success and failure measures</strong></li><li><strong>Recruit</strong> customers (if needed) and send out the test with <strong>clear expectations</strong></li><li>Summarize and <strong>analyze results</strong></li></ol><p><strong>Step 1: Study Goals</strong></p><p>Determine the goals of the study before jumping into the study. Without well thought-out goals and requirements, the study design may lead to less actionable or relevant data [5]. Identify the overall research objective, as well as the research questions that need answering. For example, a research objective can be “Evaluate the effectiveness of a booking application”, while research questions can be “Do users understand the field labels?” and “Do the error message help users along the process?”</p><p><strong>Step 2: Select appropriate tool</strong></p><p>There are many remote research tools available, as seen by Figure 1. For our purposes, we are most interested in the bottom-left quadrant. Even in that quadrant alone there are also many automated tools that prompt users to perform a series of tasks and records what they do, and how they do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yf2fbtCpx0nwBhxO7fRuYA.png" /><figcaption>Figure 1 [6]: Examples of remote research tools sorted by qualitative vs. quantitative methods, and conceptual vs. concrete ideas that users are testing.</figcaption></figure><p>For automated remote studies, the tool should have screen and audio capture capabilities. Ideally, the tool should also have the ability to give pre-test and follow-up surveys to the user. This can be used to gain insight on the context of their use and capture more qualitative insights (E.g. “On a scale of 1–5, how easy was it for you to use the app?”). Some tools also provide services to automatically recruit participants for you, saving you time. Examples of tools include <strong>Loop11</strong> and <strong>UserTesting.com</strong> for desktop, and <strong>Lookback </strong>for mobile applications or websites.</p><p><strong>Step 3: Tasks</strong></p><p>The tasks in the study should match up with the research goals and questions. It’s very important to get the tasks and the wording of the tasks exactly right for automated remote research, since you can’t be there while the user is going through the test. Participants should be provided enough detail to complete the tasks successfully, including any fake data they may need while interacting with the prototype (e.g. fake credit card information). The task shouldn’t include too much detail, however, as it may confuse the user or completely give away how to do it, which would defeat the purpose of the test. The tasks can also include context of use to provide a more realistic scenario to the user (e.g. “Imagine you are planning a vacation to Banff National Park…”). Each task should also have clearly defined success and failure measures to allow for easy analysis later on.</p><p><strong>Act 4: Recruit and Send out the Test</strong></p><p>As mentioned earlier, some tools automatically recruit participants for you to complete the study. Other times, it may be necessary to recruit your own users, especially if you have a specific target demographic. This can be achieved through e-mailing an existing mailing list of customers, or by intercepting customers that are using the product if it’s already live, and offering an incentive for completing the task. The test should also set clear expectations for the participants to prevent frustration or surprises during the test, which can lead to higher quality data and completion rates [5]. This can be done by letting them know things like the time commitment for the study, the compensation, number of tasks, device requirements (e.g. audio and video will be recorded), etc. Once the entire study is put together, a pilot should be done with another person on your team to ensure everything runs smoothly. Then, the test is sent out, and you wait for the results to come back!</p><p><strong>Act 5: Analysis</strong></p><p>After the study is complete, analyze both the quantitative data and qualitative data. The quantitative data may be analyzed automatically by your research tool — it may provide graphs showing how many users were able to successfully complete the tasks, or give you an average score for how high your participants rated their experience with a certain feature. The qualitative data can be taken by watching the video and audio of the participants’ test sessions, which can be done with other stakeholders on your team to fully understand the insights. Notes can be taken down on sticky notes and clustered to help form meaningful and organized conclusions [7] (see “Chapter 17 — Learn” in “Sprint”.)</p><p><strong>Summary</strong></p><p>In summary, automated remote research is a powerful tool that allows you to time-efficiently evaluate the usability of a product through quantitative measures (success rates, task complete time, etc.) and qualitative measures (video and audio recordings, etc.)</p><h4><strong>Case Study #1</strong></h4><p>The Design and Usability Center at Bentley University conducted a usability study on ordering groceries from Amazon.com using the automated remote usability testing method via UserZoom [8]. They had 100 participants that had an age range of 18–55. A pre-study survey indicated that the main reason users would consider buying groceries online is for convenience and time. This is valuable insight, as it indicates a goal for the usability of the product should be that the interface should be extremely easy to use and allow users to shop quickly. They had three tasks — for example, the second one was “You want to buy Skippy Peanut Butter with a discount you heard about on Amazon.com. Please write down the discount code.” This is a well-written task: it puts the user in a scenario with some context, and the task is very specific with a well-defined validation criterion (whether or not they get the correct discount code.) They also had questionnaire at the end of the study that asked the participants to rank things such as ease of navigation and product search on a Likert scale from 1 to 5, providing concrete insight on how much the users actually enjoyed using the product.</p><p>The second tasks’ results revealed that 47% of participants thought it was very difficult to locate the code, based on the post-task survey. As seen in Figure 2 below, a heat map was also automatically generated to easily see where users went to find the code and whether or not they were successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1P7WG_dN5MiK5OHb10_Lvw.png" /><figcaption>Figure 2: Heat map of where users interacted and clicked on the Amazon website in order to find the discount code.</figcaption></figure><p>Overall, the study revealed that the usability of the site to perform the given tasks were poor — 53% of participants thought the navigation was very difficult, and 55% of participates said they wouldn’t purchase their groceries in the future from Amazon. Although this maybe be because some people would never buy their groceries online regardless of the retailer, it’s valuable to have as a benchmark on the next iteration. The main obvious issue was that the gourmet / grocery was built like the book store, which is not useful for users. The automated remote method was able to efficiently quantify how big the issues were and revealed user’s thoughts and frustrations.</p><h4><strong>Case Study #2</strong></h4><p>Because automated remote research provides a lot of sound, quantitative data, comparison studies between products can be easily done. For example, in “User Experience Magazine,” Tom Tullis did a comparison study on two websites that had information on the Apollo space program, one being the official NASA website, the other being the Wikipedia article. He had a total of 130 participants. Each participant answered questions related to the Apollo space program, answers to all of which can be found on both websites. Again, these tasks have clear defined success measures (either they get the answer correct or don’t). Users were randomly assigned to one of the websites to complete the questions, of which the set-up can be seen in figure 3. Another benefit of the automated remote research study can be seen here, where a large sample size would be needed in order to do this research method of randomly assigning two different products to compare them without having a result that is bias and has a large error margin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceDR9Fmz48RCmpVdzyHFVA.png" /><figcaption>Figure 3: An example of what the participant would see during the automated remote research study.</figcaption></figure><p>The results indicated that test participants who used the Wikipedia article to answer the questions got significantly more tasks correct than users of the NASA website (71% correct vs. 58% correct), and were on average 23 seconds shorter at answering them. They also rated their experience of completing the tasks as significantly easier on a 5-point scale (3.1 vs. 2.6). The accuracy, time, and rating were combined into an index to provide an overall usability score for each task. As seen in figure 4, the users who had the Wikipedia article as a reference to complete the task had overall higher usability scores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*-DDf8bUULOgnyN_Wr86HEg.png" /><figcaption>Figure 4: The average usability score for each task given to users.</figcaption></figure><p>Again, this shows the power of the easily quantitative automated remote research study. The numbers were obtained and analyzed, and used to quickly compare between the two products. Beyond the numbers, the open-ended questions also helped identify usability issues that may indicate <em>why</em> the NASA website got lower scores. For example, an example of one the comments for the NASA website was “Search on this site is next to useless”. This indicates that the search function is something that users attempted to use to complete the tasks but were unable to use it, and thus needs improvement.</p><h4><strong>Case Study #3</strong></h4><p>Another example of automated remote research illustrates how it can be used not only for fully functioning websites, but also for lower fidelity prototypes. UserZoom built a wireframe for a website using Azure, and had participants add a pair of women’s shoes to their online shopping cart, as seen in figure 5. [10]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zhra1z1FMaoqJTIRQu164A.png" /><figcaption>Figure 5: Home page of website prototype.</figcaption></figure><p>UserZoom was able to validate the success of the user by noting if they were able to reach the correct URL. As seen in figure 6, a clickstream flowchart was produced to show what percentage of users navigated to which parts of the website. 90% of users were able to successfully complete the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySGUOGlcWRtyLBMDxy39BQ.png" /><figcaption>Figure 6: Clickstream from the usability study</figcaption></figure><h4><strong>References</strong></h4><p>[1] S. Lanoue, “What is Remote Usability Testing? | UserTesting Blog”, UserTesting Blog, 2015. [Online]. Available: <a href="https://www.usertesting.com/blog/2015/11/30/what-is-remote-usability-testing/">https://www.usertesting.com/blog/2015/11/30/what-is-remote-usability-testing/.</a> [Accessed: 04- Jul- 2016].</p><p>[2] C. Gray, “How to Run an Unmoderated Remote Usability Test (URUT) -”, UX Mastery, 2015. [Online]. Available: <a href="http://uxmastery.com/how-to-run-an-unmoderated-remote-usability-test-urut/">http://uxmastery.com/how-to-run-an-unmoderated-remote-usability-test-urut/.</a> [Accessed: 04- Jul- 2016].</p><p>[3] A. Schade, “Remote Usability Tests: Moderated and Unmoderated”, Nngroup.com, 2016. [Online]. Available: <a href="https://www.nngroup.com/articles/remote-usability-tests/">https://www.nngroup.com/articles/remote-usability-tests/.</a> [Accessed: 04- Jul- 2016].</p><p>[4] “Remote User Research &amp; Usability Methods | UX Magazine”, Uxmag.com, 2016. [Online]. Available: <a href="https://uxmag.com/articles/remote-user-research-usability-methods.">https://uxmag.com/articles/remote-user-research-usability-methods.</a> [Accessed: 04- Jul- 2016].</p><p>[5] “12 Best Practices Remote Unmoderated Usability Testing”, UserZoom zooming in on the customer experience, 2014. [Online]. Available: <a href="http://www.userzoom.com/uxguide/12-best-practices-remote-unmoderated-usability-testing/">http://www.userzoom.com/uxguide/12-best-practices-remote-unmoderated-usability-testing/.</a> [Accessed: 04- Jul- 2016].</p><p>[6] B. Martin and B. Hanington, Universal methods of design. Beverly, MA: Rockport Publishers, 2012.</p><p>[7] J. Knapp, Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon and Schuster, 2016.</p><p>[8] “Lab + Online Usability Testing — UserZoom zooming in on the customer experience”, UserZoom zooming in on the customer experience, 2010. [Online]. Available: <a href="http://www.userzoom.com/casestudy/lab-online-usability-testing/">http://www.userzoom.com/casestudy/lab-online-usability-testing/.</a> [Accessed: 04- Jul- 2016].</p><p>[9] T. Tullis, “Automated Usability Testing: A Case Study”, User Experience Magazine, no. 7, p. 3, 2008.</p><p>[10] “UserZoom | Remote Prototype Usabilty Testing Case Study”, UserZoom zooming in on the customer experience, 2014. [Online]. Available: <a href="http://www.userzoom.com/casestudy/remote-prototype-testing/">http://www.userzoom.com/casestudy/remote-prototype-testing/.</a> [Accessed: 04- Jul- 2016].</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2bff0fd9769" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uwaterloo-voice/automated-remote-research-b2bff0fd9769">UX methods: Automated Remote Research</a> was originally published in <a href="https://medium.com/uwaterloo-voice">uWaterloo Voice</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Studying abroad in England]]></title>
            <link>https://medium.com/@yangchen/my-first-impressions-studying-abroad-in-england-66a8c35c081a?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/66a8c35c081a</guid>
            <category><![CDATA[england]]></category>
            <category><![CDATA[leeds]]></category>
            <category><![CDATA[university-of-leeds]]></category>
            <category><![CDATA[study-abroad]]></category>
            <category><![CDATA[musical-theater]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Thu, 23 Feb 2017 08:00:00 GMT</pubDate>
            <atom:updated>2017-12-08T07:16:36.410Z</atom:updated>
            <content:encoded><![CDATA[<h4>My first impressions</h4><p>It’s been a whirlwind couple of weeks since I left my hometown of Toronto, Canada to embark on my first ever trip to Europe and my international exchange here at Leeds. Melanie (a classmate who is on exchange at the University of Madrid) and I both had never been to Europe before, so we came up with a crazy idea —we decided there’d be no better way to be introduced to Europe than a week long, action-packed Europe extravaganza: Iceland, Germany, and Czech Republic, all in a week. Within a week’s time, I had taken more than 10 long-distance trains, buses, and flights! By the time I arrived in Leeds, you could say that I was definitely ready to settle.</p><p>My first week at Leeds was like first year (or fresher’s, as they call it here) all over again, and I was already eager to “un-settle” again. It certainly helped that everyone here at Leeds, both exchange students and locals have been nothing but kind, open, and welcoming. When I walked into the giant Conference Auditorium for our meeting with all the exchange students, I couldn’t help but feel like all of us were embarking on this exciting journey together. Meeting people from all over the world has been really easy, as you have something immediately to bond over (“Where are you from?”). One of my favourite events from orientation was the City Chase — running around the Leeds city center, discovering what a lively and charming city Leeds is. Our group bonded over how happy we were to have made it back to the finish line just in nick of time to avoid a 30-point penalty. Although we didn’t win, we were still pretty proud of our 380-point total, and learned so much about what the surprisingly urban city Leeds had to offer us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/0*IOS8dd0U5MlKCFq8." /><figcaption>My City Chase team as we took a short break to take a selfie!</figcaption></figure><p>I chose to study abroad at the University of Leeds because research indicated it had one of the best student experiences in England, and the student union claimed to be the “biggest and best” in the UK. After being here for a month, Leeds has absolutely exceeded expectations — the Leeds University Union building itself is amazing, with its multitude of cafés, restaurants, and spaces available for clubs and societies. The fact that the “Give it a Go” and “Get Out, Get Active” sessions were organized for students was incredible. I knew I was specifically interested in music and performing groups, and I was blown away by the sheer amount of quality societies here — two musical theatre ones, an opera society, two a cappella groups, and even more theatre groups. This doesn’t even count the LUU Music Society, which boasts three choirs, two bands, and four orchestras.</p><p>This was not only impressive in quantity however; I recently went to see OperaSoc’s production of “Don Giovani.” I was extremely impressed by quality of the show, and the fact that it was only a university production blew my mind. It only made me more pumped about performing in my own show, “Merrily We Roll Along” in March, produced by the LUU Musical Theatre Society. Auditioning for it was nerve-wracking, as I had never been in a musical before, but I felt Leeds was encouraging me to not be afraid to try new things. To my pleasant surprise and excitement, I was cast, and now I am fervently rehearsing my lines and notes between a tight rehearsal schedule!</p><p>Back home at the University of Waterloo, I’m the musical director of a co-ed a cappella group. By coming on exchange, I thought I had given up the chance to go to the International Championship of Collegiate A Cappella (ICCA) with my group, which we made it to the Semi-Finals of last year. However, when I found out there were two a cappella groups here at Leeds who were participating for the first time in the very same ICCA competition this year, I just knew I had to get involved somehow. I eventually got in touch with the right people, and I had the chance to help their preparation of the competition sets. Once again, I felt so warmly welcomed to their community, and I’m even heading off to Edinburgh to support their performances at the quarterfinals! It just goes to show the more you put yourself out there, the more you can receive. I think I’ll stick to that mantra for the rest of my time here at Leeds. Onto more adventures!</p><p><em>Re-posted from </em><a href="https://leedsunibound.wordpress.com/2017/02/23/yangs-first-impressions-of-leeds/"><em>Leeds Study Abroad Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66a8c35c081a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Putting together the first annual Canadian A Cappella Conference (CanACC)]]></title>
            <link>https://medium.com/@yangchen/putting-together-the-first-annual-canadian-a-cappella-conference-canacc-e6fe5e5e2fbc?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6fe5e5e2fbc</guid>
            <category><![CDATA[a-cappella]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[event-planning]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 08:00:00 GMT</pubDate>
            <atom:updated>2018-05-21T05:32:23.111Z</atom:updated>
            <content:encoded><![CDATA[<p>Personal Project | February 2015 — October 2015 <br>Winner of Best New Initiative — Fall 2015 from FEDS</p><h4>What is CanACC?</h4><p>The 1st annual (now 3 times going on 4!) Canadian A Cappella Conference was a one-day event held at the University of Waterloo that brought together over 100 singers from 4 universities/colleges across 9 distinct a cappella groups. The event consisted of round-tables, workshops, and a showcase concert that brought collegiate a cappella from schools outside UW to campus for the first time.</p><h4>Where did the idea come from?</h4><p>The idea for the conferenced was conceived on a bus ride back from the 2015 ICCA competition. We were able to meet a lot of groups there and connect with like-minded people who were all passionate about the same thing — a cappella. Unfortunately, the ICCA competition is primarily American, and we knew that there were many Canadian groups that UW have not been able to connect with much. Canadian a cappella at colleges/universities is also very behind compared to the States in terms of how well developed and prominent it is. Although the a cappella scene with over 100 singers and 5–7 groups at Waterloo is a very strong community, there wasn’t much contact with groups outside our school. As such, I wanted to create an event that brought together different Canadian a cappella groups in a non-competitive setting to learn and share beautiful music together and build a strong Canadian a cappella community. In the summer of 2015, I recruited a team of 10 volunteers to organize Canada’s first Canadian A Cappella Conference (CanACC), was a one-day event held at the University of Waterloo. We organized it in one month.</p><h4>Logo Design Process</h4><p>Aside from being co-chair of the conference which involved organizing workshop leaders and attendees, planning conference programming, and designing attendee experience, I also worked on a submission for the logo. The main themes I wanted to convey in the logo were music and Canada. The most obvious representation for Canada is the maple leaf, which is instantly recognizable and also has a strong colour associated with it. Because of that, then it will make sure the logo isn’t perceived as bias towards any of the group attending, as many of the groups also have strong colour associations. Unfortunately, there isn’t a wide range of visual representations for music or a cappella without the logo becoming too complicated or busy. I tried out a couple sketches, playing with music notes as well as audio waveforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Qcm2i7mFhEQF2H0P2JoqGg.png" /><figcaption>Initial sketches of logo design ideas.</figcaption></figure><p>One of my favourite ones I made was the one with the maple leaf breaking off into music notes — I thought it was really fitting because it shows that we can unite as Canadians through music, and we can build community through music, which was the main goal of our concert. Also, the large number of small music notes represent us as singers, since a cappella is all about individual voices joining together to be bigger than the sum of its parts. The downside of that logo was scaling: for small scale usage, the tiny details of the notes would be difficult to print and see. The logo was primarily being used on small promotional items and branding at the top of some documents, so unfortunately it would be unfeasible to continue with that concept. Eventually, after iteration and feedback, we ended on something like this, (when CanACC was hosted<em> </em>for the 2nd time by another school!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Boo8bY5l3nNxI7qLfG6xaA.png" /></figure><h4>Result</h4><p>The event was a really great success and everyone had a lot of fun meeting, learning, and enjoying beautiful music from each other. It brought together over 100 singers from 4 universities/colleges across 9 distinct a cappella groups. The event consisted of round-tables, workshops, and a showcase concert that brought collegiate a cappella from schools outside UW to campus for the first time. The event was so successful, that it’s been turned into an annual event, that saw McMaster University hosting it in 2016, and Wilfred Laurier University hosting it in 2017.</p><p>I also championed getting feedback from our conference participants, and got really great feedback on what we did well for the first ever conference and what we could do even better for next year — actually, one of the participating groups, <em>Macappella (</em>a co-ed group from McMaster University) was so inspired that they wanted to take on hosting the conference in 2016, and it was an absolute success yet again. It’s really cool to see such a network and community building in Canada already!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4VZjUo7HKnc2TmVZb_XQg.png" /><figcaption>Group picture of all CanACC attendees, volunteers, and leaders!</figcaption></figure><h4>Retrospective</h4><p>I didn’t have a lot of time to put together the logo as we were under a time crunch to get materials printed with the logo. If I could go back, I definitely would’ve wanted to explore some of my initial sketches in a higher-fidelity format using Sketch, particularly the one with the maple leaf breaking into musical notes, and variations on that as well — for example, having the musical notes fall in from the top to create a sense of “falling into place” as opposed to “breaking away,” and seeing if I could reduce detail to increase small-scale reproducibility.</p><p>For the actual logo that we chose, I also wish I could’ve picked a better font that was less generic. I also would’ve explored more how to make the logo more contained and united, as the elements in the logo feel somewhat spread out and not connected well with each other — the round, smooth waves clash somewhat with the pointiness of the maple leaf, and the spacing is a bit inconsistent.</p><p>I think the overall logo is not exactly the most inspiring piece of design I’ve done given the short timeframe, but it gave our conference something visually to rally around and an elevated sense of professionalism.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6fe5e5e2fbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX methods: Card Sorting]]></title>
            <link>https://medium.com/@yangchen/card-sorting-a-simple-and-effective-ux-research-tool-74befc3ef4ef?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/74befc3ef4ef</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-workshop]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Fri, 15 Apr 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-12-18T02:35:42.798Z</atom:updated>
            <content:encoded><![CDATA[<h4>A simple and effective UX research tool</h4><p><em>A </em><a href="http://old.boltmade.com/blog/2016/04/card_sorting_workshop"><em>re-post of a blog</em></a><em> I wrote while working at </em><a href="https://medium.com/u/e958b85a8078"><em>Boltmade</em></a><em> as a UX designer &amp; researcher. Boltmade has since been acquired by Shopify, where I also worked as a designer.</em></p><p>Card sorting is a design research tool that helps you design your product (e.g., a website, an app) so users can more easily find what they want. Card sorting is usually used near the beginning of the design process, and can be used to guide the design of the navigation menu and the overall structure (information architecture) of the product.</p><h4>Why Card Sorting?</h4><p>Card sorting is effective and simple. There are many reasons to use it:</p><ul><li>Easy to conduct (can be set up by anyone!)</li><li>Inexpensive (can be done with just paper and pens!)</li><li>Quick (can see patterns from as little as 5 card sorts!)</li><li>Powerful insights and results (can reveal a lot about how users think!)</li></ul><p>Card sorting is all about bridging the gap between how a user understands the subject and how a website or app can match that understanding and present information or functionality to users in a way that’s easy to find.</p><h4>How does Card Sorting work?</h4><p>The process of a card sort is exactly what it sounds like — participants (ideally, people who would normally use the website or app) categorize things written on cards into different groups that just simply make sense to them. The cards contain either content or functionality that the website or app would have.</p><p>Card sorts can be open or closed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*He40tePz0c_LCLXuCeSoMw.png" /></figure><p>Card sorts can also be team or individual:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U2gh59RaRYjwTTgwUF1nuw.png" /></figure><p>Card sorting can return valuable insights using any combination of open vs. closed and team vs. individual, so don’t let scheduling or other logistical challenges stop you from giving it a try!</p><h3>Learning from Card Sorting</h3><p>Last week, I led a Boltmade Session (free community tech workshops hosted by Boltmade) to explore these concepts. We had a lot of fun learning and discussing how card sorting can be used as an effective UX research tool, and also performing a couple of card sorts ourselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c8PGFD8QjwY-qljs.jpg" /></figure><h4>Activity #1: Museum Sort (an open, team sort)</h4><p>With the first activity, we were able to get a sense of what a real participant would experience in a card sort. In teams of 2 or 3, everyone sorted a set of 54 cards that had been pre-printed with the names of museum exhibits such as <em>Chinese Architecture</em>, <em>Terry Fox</em>, and <em>Bronze Age</em>. Because this was an open card sort, teams also had to generate their own categories to put cards under.</p><p>Many good discussions and questions came up during the sort:</p><ul><li>How should cards be sorted? By chronology? By subject? By type of exhibit?</li><li>Where should <em>Kid’s Zone</em> go, since it doesn’t quite fit with anything else?</li><li>Should <em>World War I</em> be categorized under <em>World History</em> or under <em>Canada</em>? Who is the museum for, and what does the exhibit actually cover?</li></ul><p>All of these struggles and debates about which cards to group together are perfectly normal during a card sort, as there is no one right answer. These discussions that happen during the activity of sorting are very useful when working on a proposed design; much of it might have been missed if we had only looked at the final outcome of the sort.</p><p><strong>Key takeaway</strong>: The <em>process</em> of card sorting and the reasonings that come out of it are as valuable as the <em>product</em> of the groupings that are generated as a result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SX-7eUdHYGo9NAY6.jpg" /></figure><h4>Activity #2: Website Sort (a closed, individual sort)</h4><p>In our second activity, we saw how a card sort done individually and online is different from a team, in-person sort. We also saw how a closed card sort can be used to improve an existing site.</p><p>Using a tool called <a href="https://www.optimalworkshop.com/optimalsort">OptimalSort</a>, we sorted content from the website for Banff National Park into predefined categories that were taken from the existing website. This card sort was very easy to analyze because the online tool did all the work automatically. At a glance, it was easy to see that some content on the existing site didn’t match our expectations. For example, most of us grouped <em>Top 10 Things to Do</em> into the <em>Activities</em>category, but on the actual website it is under <em>Visitor Information</em>, where few of us placed it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/0*atoTJa3UCrwWvKHl.png" /></figure><p>We speculated that <em>Top 10</em> had been placed under <em>Visitor Information</em>because website visitors are likely to explore that section and thus be more likely to discover it. Interestingly, on the current website, there are no sub-categories under <em>Activities</em>. Card sorting results suggest that either the website navigation structure should be reconsidered, or alternatively, the <em>Activities</em> section could be removed so that users don’t try to find activity information under it when it’s not actually there.</p><p><strong>Key takeaways</strong>: Card sorting results should not be taken at face value as the final answer. It is one data source to consider, and should be triangulated with other information, criteria, and informed intuition when creating a proposed design. Follow-up evaluation such as usability testing is also important.</p><h3>Card Sorting Key Points</h3><ul><li>Card sorting is simple and effective</li><li>The discussion that happens during a card sort is just as or sometimes even more valuable than the actual outcome of the card sort</li><li>The results of a card sort are a great data point, but should be considered along with other research and informed intuition</li></ul><h3>Further Reading and Resources</h3><ul><li><a href="https://drive.google.com/file/d/0BxweIS5mqsD0andQUWZucFlIT2c/view?usp=sharing">Boltmade Session slide deck</a></li><li><a href="https://drive.google.com/file/d/0B_I4V5G3NfuFdF85eFEyVTZ2TUU/view?usp=sharing">Boltmade Session activities</a> (Card Sort Analysis)</li><li><a href="http://boxesandarrows.com/card-sorting-a-definitive-guide/">Card Sorting: A Definitive Guide</a></li><li><a href="http://rosenfeldmedia.com/books/card-sorting/">Card Sorting: Designing Usable Categories</a> by Donna Spencer</li></ul><p><em>Thanks goes to Kimberly Tee for her assistance with writing this article and the workshop!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74befc3ef4ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring mobile design for the online PlayStation® store]]></title>
            <link>https://medium.com/@yangchen/explore-mobile-design-for-the-online-playstation-store-a386e52962a9?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a386e52962a9</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[mobile-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Thu, 03 Sep 2015 07:00:00 GMT</pubDate>
            <atom:updated>2017-11-14T04:36:22.421Z</atom:updated>
            <content:encoded><![CDATA[<p>Sony (SNEI) | May 2015 — August 2015</p><h4>Introduction</h4><p>Sony Network Entertainment International (SNEI) develops the online network infrastructure to provide top-quality entertainment around the globe through games, videos, music, and other services. I worked as a user experience (UX) design intern at SNEI over the summer of 2015, and was responsible for evaluating and improving the user experience of the PlayStation web store.</p><h4>What is the PlayStation Store?</h4><p>The PlayStation web store is a digital media store that offer PlayStation console owners a variety of downloadable content for purchase or for free, such as full console games, add-ons, movies, and TV shows. The store exists in three main platforms: a native PlayStation app, an online desktop store, and a mobile web app embedded within the PlayStation® App, which has over 100 million downloads on Android. Although most users purchase and download content through the console store, usage of the web version is increasing and has unique use cases, as discovered through user research.</p><h4>Design Problem</h4><p>My work focused on the online . The store has all the basic, primary user functions of an e-commerce website: the ability to browse, search, and purchase products.</p><p>The current state of the store has a lot of room for improvement. My fellow intern Wynn and I performed an heuristic evaluation of the site and collectively found around 200 issues relating to visual layout, UI, and UX. One set of guidelines we used was Contrast, Repetititon, Alignment, and Proximity (ie. “C.R.A.P.”), coined by visual designer Robin Williams. Although it was originally intended to be used for visual design, these principles can be applied to evaluating user experience as well — for example, repetition refers to having things that look the same should perform the same function, which matches <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Nielsen’s usability principle</a> of having “consistency and standards.” For example, both call-to-actions below perform the same action of bringing users to a new page, but one has an extra arrow that might confuse users as to if it performs a different function than a button that only has one arrow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/0*KL1H5RaCxzKaGD6B.png" /><figcaption>Two screens from current mobile version of online PlayStation Store showing two buttons that have inconsistent arrow design for the same function (going to another page.) This “In Cart” button can also be clearer about what clicking the button does.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/0*vfK99vv7cbr-RLQH.png" /></figure><p>While top priority issues were being fixed for the short-term, we were tasked with the project of completely revamping the design and exploring new design directions that the PlayStation store can take.</p><h4>User Research</h4><p>I first started off the process by creating personas to see how we could empathize with the users and their current frustrations with the PlayStation store, both the console and online version. This was especially important as I was not a regular user of any PlayStation products. Although I own some older generation consoles, I had never used the console store or the web store since its launch in 2011.</p><p>Although I was unable to recruit participants for interviews as primary research due to time and budget constraints, I was able to do secondary research by going through many forum sites, both official PlayStation ones and non-official. I captured quotes that had to do with how PlayStation users were interacting with the PlayStation store, especially the web version. I looked for both overall goals and context for using the website version, and particularly any points of frustration with the website. Once I collected around 50 quotes or so, I was able to see some patterns and was able to group the quotes into what would become the foundations for the different persons.</p><p>I also explored some general research on e-commerce usage — I came across a <a href="https://www.nngroup.com/articles/ecommerce-shoppers/">neat article from Nielsen Norman group</a> that grouped e-commerce users into different types of shoppers, each having distinct use cases and motivations when using an online store. I saw some potential overlap between these groups, the quotes I collected, and internal PlayStation “gamer” personas, and incorporated them into 6 distinct personas, two of which can be seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y-iU0LDkI_0NqmPy.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MwFAtwm-_ZEF5ox1.png" /><figcaption>One of the personas created for the PlayStation Store re-design. Some of the most common use cases for using the online PlayStation store seen from secondary research are reflected in this persona.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ohq8y5BhHrJsHSEL.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MlM3kNxaKt1u5gDx.png" /><figcaption>One of the personas created for the PlayStation Store re-design for a secondary user. Persona mainly came from complaints regarding the categories on the website and difficulties surrounding discoverability and findability.</figcaption></figure><h4>Competitor Analysis + Mobile Inspiration</h4><p>I then looked into how other e-commerce sites were designed, especially on mobile. An e-commerce store has many functions, so to elegantly present it on small screen is no easy feat. I also looked at search design on websites that were not e-commerce. One main thing I began to notice is that many e-commerce sites were clearly designed mobile-first. Even on the desktop version, it had elements that you usually only saw on mobile, such as a hamburger menu and interaction items/areas that took up a large percentage of the screen. I printed some of my favourite ones and labelled both interested and flawed UI interactions and UX points (particularly searching and check-out) flows, as seen in the following photos:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rG0TUelD-eR4yuzR.jpg" /><figcaption>Part 1 of Mobile UI/UX Moodboard. Edwin (European clothing brand) had a strong sense for good mobile user interaction for the e-commerce shopping flow.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_pCIOh2HhipjNd6c.jpg" /><figcaption>Part 2 of Mobile UI/UX Moodboard. KFC had a surprisingly well designed website that was clearly mobile-first.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IyQ3ucTe-6Gf1QmN.jpg" /><figcaption>Part 3 of Mobile UI/UX Moodboard. Fivefootsix had a great full-screen mobile menu, and Indochino had a great mobile filtering/sorting interaction.</figcaption></figure><h4>Conceptualizing Design Goals</h4><p>Based on the user research, competitive analysis, our mood board, our own design intuition, design heuristics, and new PlayStation Store branding guidelines (which we also made but unfortunately am not allowed to share), Wynn and I came up with about 30 qualitative descriptors that we think a user would use to describe the overall user experience of the new PlayStation store. We then wanted to see what more people thought about our goals to identify the ones that are the most important. Again, since we didn’t have access to regular users via recruiting, we did a card sorting exercise with various employees at SNEI Waterloo. This is obviously less than ideal as it doesn’t truly represent our user base, and presents a bias towards people that are very technical and close to the product. However, almost all of the employees were regular users of the PlayStation and PlayStation store, so they represent at least some of the user base. It also allowed a unique opportunity for our developer-heavy group to contribute to the product vision.</p><p>In the exercise, the employees were asked to sort the words into three tiers of importance, with the 1st tier being the most important. Some keywords were also added in by the employees during the exercise. In the following table, the user experience keywords are shown in order of their overall score.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*laRyA5jtoCRc1z1l.png" /><figcaption>Table of calculated results from UX goals sorting exercise.</figcaption></figure><p>The overall score was calculated by giving three points every time it was sorted into 1st tier, two points every time it was sorted into 2nd tier, and one point every time it was sorted into 3rd tier, then dividing up that total by the number of employees that participated (nine, in this case.) In other words, if a key word was sorted into 1st tier by all of the participants, its overall score would be 3.</p><p>As seen, some obvious user experience key words are at the top. An e-commerce store most certainly should be easy to use and organized, and should perform fast to allow for the user to get the product they want as quickly as possible. Other, less technical terms also came up, which the design team felt was important to keep in mind, since users also want to feel certain ways about the overall store based on its aesthetics and user experience choices, such as being seamless and engaging. These also fit in with the PlayStation brand, as many modern video games are becoming more and more engaging, realistic, and seamless. Other design requirements are that the mobile website should include familiar mobile gesture like scrolling down, offer menus for specific navigations, offer an option use the full site, as well as keeping high-level, important functions visible at the top.</p><p>To remind ourselves of the keywords that we came up with throughout the design process, Wynn created a lovely wordle with the most important keywords having the most prominence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ixfu6q7XYbUWaXKQ.jpg" /><figcaption>Wordle displaying UX goals for the re-designed PlayStation Store. Prominent words are ones that were deemed to be of more importance by user testing.</figcaption></figure><p>Although I had not realized it at the time, this process was very similar to <a href="https://www.nngroup.com/articles/microsoft-desirability-toolkit/">Microsoft’s desirability toolkit</a>.</p><h4>Mobile Search Design</h4><p>After all the initial research done, I was tasked with specifically exploring mobile search design. I started out with sketches of ideas. The particular challenge in this case was how to display the results. The PlayStation Store has a variety of media content, mainly sorted in 3 types: Video Games, TV, or Movies. This presented unique requirements and constraints, as these sections are very distinct, so searches for these products was also likely to be distinct.</p><p>I first sketched out various wireframes for the pre-search screen, when the user first clicks the “search” function, or clicks the search field. I wanted to give them their history as many users search for products, but don’t end up buying it as they want to do more research on the game, and then come back to it. Also, I wanted to give users the ability to see what other people were searching and what was popular, as many users also wanted to see that. Based on user research, many users searching on the store are looking to get to an exact product in the fastest time possible. As such, I also created a “mid-search” screen that auto-searched in the middle of the user typing out their query. Sorted based on relevancy, this provides a fast way to get to potentially what they are looking for. The solutions I liked the most and created a wireframe for can be seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/302/0*8mhzJg1a5EnHGIg0.png" /><figcaption>Screen for when user starts the search (e.g. tapping the search field.) Suggestions for search appear.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/0*37Q982n5kBEydg0R.png" /><figcaption>Screen for when user is in mid-search. Results appear automatically as user types.</figcaption></figure><p>Once the user clicked the search or enter button on their keyboard, they would be taken to a more detailed results screen to browse, filter, and sort for the products they want. One unique requirement for this is that the search results have to show if the game has a special “PS+ Membership” price, on sale, or has some other unique promotion, all denoted with a small badge. In the final search result screen, I knew that I wanted to automatically presented the results sorted by each of the three content types offered by the PlayStation store (i.e. Games, Movies, TV Shows). This is because the categories are very distinct, so if users are looking for a TV show, their search result will definitely not be part of video games. With these requirements in mind, many alternatives were wireframed. The top two that were considered are seen below:</p><p>Alternative #1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/0*qpZnl0iggbqiv8ZS.png" /><figcaption>Results page with tabs for each content type and a focus on visuals for each result item.</figcaption></figure><p>In alternative #1, the search results split into four tabs, With this interaction, if they search for a term like “Batman” which has products in all 4 categories, they can easily switch to the type of product they’re looking for. Filters and sorting options are under each tab because they change depending on the type of content. The layout also displays only 4 products at a time, since each product has a relatively large image associated with it. This is to make the experience very immersive and engaging by providing large visuals of the media cover art, similar to how they would see it in a retail store.</p><p>Alternative #2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/0*UGlDEPg3fWmgmpc5.png" /><figcaption>Landing page for results. Top results (relevancy) per media type are all displayed at once.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/316/0*EHTVXzKgHX9FZNzl.png" /><figcaption>Results page within a specific category. Filtering and sorting options would be seen here.</figcaption></figure><p>In alternative #2, all three content categories are displayed at once, and the top three most relevant results per category are displayed in a list view. No thumbnails are displayed with the results so there is ample room to have the product title on one line and save vertical space in order to display as many results as possible. Clicking “see all” for any particular category will take users to a page that would display results with a small image and some product details in a list view to provide more visuals within a category. Breadcrumbs at the top keep the user reminded of where they are and allow for easy way to go back and see all.</p><h4>Analysis of Alternatives</h4><p>Alternative #1 is more engaging because it uses a grid view with larger images that also invoke the look of a physical video game or DVD case, but it is less organized since there is less room for information about the product. A list view would be easier to sort and compare as you can see more products at once, which is seen in alternative #2. This is important since a main purpose of the search function is to allow users to compare between options and find content easily based on their preferences. A main feature of alternative #1 that’s really great is sorting the results into different tabs, since it makes it easier to go between the different categories of results (minimizing information access cost), and each tab has an icon in addition to text to emphasize the type of content each tab contains. Another plus for alternative one is that it displays an “all” results initially. Since users use the PlayStation store primarily for games, displaying the most relevant movies and TV shows upfront, as alternative #2 does, doesn’t make efficient use of space.</p><h4>Recommendations</h4><p>From the comparison of the three search results alternatives, alternative #1 seems to be the best choice for potential implementation to improve overall user experience. However, both alternatives have elements in their design that help increase the overall usability. For example, alternative #2 has a list view that would allow for easier comparison of basic information between different products in the search results than the grid view in alternative #1. As such, a final design should incorporate both elements by offering a choice to the user for the view of the search results. This way, users can either have a more immersive, visual experience of browsing the search results with a grid view, or have a quicker overview of more products at once with a list view.</p><p>Usability testing should be done on the new design. Realistic scenarios and search tasks should be created and tested on to see how well users are able to complete them, and based on the results, the design should be iterated upon.</p><h4>Retrospective</h4><p>During initial analysis of the store, only a couple of design heuristics of the many that exist were used evaluate the usability of the store. A more in-depth analysis could have involved other usability heuristics. The UX goals card sorting exercise could have been done with more users, such as randomly recruited PSN members, in order to hear directly from the users and have a great variety in opinion. This is crucial in user experience design, as different users may have varying opinions on the usability of a product. For the mobile search design, I would’ve wanted to create even more iterations and variations. Also, because only basic wireframes were made and analyzed, some usability issues might have been overseen before deciding on a solution to move forward with for user testing. I also wished I had more varied content in the mock-ups to put a focus on content-first design for a content-heavy feature, to ensure we cover edge cases and let content more strongly inform design (e.g. visual hierarchy, placement, multi-language) Higher fidelity prototypes can be made for more thorough and accurate user testing.</p><h4>Remarks</h4><p>I would like to thank Jesse Wong for being a great mentor and supervisor, and Wynn Yau for being a wonderful fellow design co-op student to work with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_bwPfvB6lh149dRA.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a386e52962a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My time in the Manulife RED Lab]]></title>
            <link>https://medium.com/@yangchen/my-time-in-the-manulife-red-lab-b70797d3c552?source=rss-76d25fba7cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b70797d3c552</guid>
            <category><![CDATA[corporate-innovation]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Yang Chen]]></dc:creator>
            <pubDate>Sat, 03 Jan 2015 08:00:00 GMT</pubDate>
            <atom:updated>2017-12-08T07:15:38.919Z</atom:updated>
            <content:encoded><![CDATA[<p>Manulife | September 2014 — December 2014</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*4dbiE8klKIvlFtgT1eXdGw.png" /><figcaption>First iteration of the ZOOM Day Challenge schedule I created</figcaption></figure><p>Towards the end of my four months at the Manulife Research, Exploration, and Development (RED) Lab, our team helped run the <a href="http://www.bus-edpartnership.org/ZOOM-Career-Days.htm">ZOOM Day Challenge</a>- a program designed for local high school students to experience first-hand real-life work. We guided three high school students through a rapid prototyping challenge of making an app that would improve the banking experience. At the beginning, I wasn’t sure where they take our challenge, but in the end I was impressed. After going through a brainstorming exercise, many design iterations and customer interviews, they presented an interactive prototype to encourage saving. They had fun and came out in the end a little more knowledge about iterative mobile app design.</p><p>Upon reflection, their experience over the course of a day was almost like what I went through the four months of my co-op. Not knowing a lot at the beginning, but eager to learn, and coming out with a lot more knowledge and experience.</p><p>Overall, my time at the RED Lab was amazing. I got to be in an environment of fun, knowledgable, generally awesome techie people who could really appreciate a good start-up-related joke. (“That’s disruptive!”) I worked on projects focused mostly on user interaction innovation on web and iOS platforms. And even though before this work term I’ve never even owned a Mac before, it was a really cool opportunity to be able to learn Swift and Objective-C. Because of it, I was able to used those skills learned and actually <a href="http://hackthenorth.devpost.com/submissions/26989-judio">won the best iOS app prize</a> at my school’s hackathon! Our team also won the co-op innovation challenge for our facial-recognition idea for Manulife security, which was a fun side project.</p><p>I’ve learned a lot of technical skills this term, but perhaps the most important thing I will be taking away is the spirit of innovation and prototyping. It’s the combination of collaborative and individual work that drives this spirit, and I look forward to implementing this where needed wherever I go in the future.</p><p>Below are snapshots of one project I worked on, which was a re-invented online banking UI with dashboard-style widgets to give user the feel and look of full control over their bank accounts and data. Screenshots are cropped for non-disclosure purposes. Other projects are not available for display, again due to non-disclosure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*1-6iN7nQfL-aPOIZbFxPBQ.png" /><figcaption>Partial screenshot of one prototype developed as a tool to help Manulife banking customers.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*86yUrBsygYJnkU4gi9nMRw.png" /><figcaption>Partial screenshot of one prototype developed as a tool to help Manulife banking customers.</figcaption></figure><p>Tools used: HTML/CSS/JS/JQuery. Bootstrap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b70797d3c552" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>