<?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 Ananda Vickry Pratama on Medium]]></title>
        <description><![CDATA[Stories by Ananda Vickry Pratama on Medium]]></description>
        <link>https://medium.com/@anandatama?source=rss-b1428b66532f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4DpcshK-BpbzHdubIh_j3Q.jpeg</url>
            <title>Stories by Ananda Vickry Pratama on Medium</title>
            <link>https://medium.com/@anandatama?source=rss-b1428b66532f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:45:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anandatama/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[ANQOT — a UX case study]]></title>
            <link>https://uxdesign.cc/anqot-a-ux-case-study-d5e4c36520f1?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5e4c36520f1</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 04:22:27 GMT</pubDate>
            <atom:updated>2018-09-16T13:31:57.664Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKShx9UaLVGwEp08u73fIw@2x.jpeg" /></figure><p>The purpose of this UX case study is to participate in the TBIG CreatiON 2018 competition, as the TamiTama team (Me, Nadia, and Devika).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*ipmeDrkSVDuF6aCPXmlwTQ.jpeg" /><figcaption>ANQOT Logo</figcaption></figure><p>ANQOT is an app that helps angkot drivers in getting passengers without having to ‘ngetem’ (which means, stop to get passengers), so it also makes it easier for passengers to ride angkot more safely. This app also allows the existence of special angkot stops so that the driver does not feel carelessly to ngetem.</p><h3>Background</h3><p>Community life is influenced by transportation. With the existence of transportation, all day-to-day community life can run well. As a means of transportation, public transportation (in Bahasa called angkot) is expected to be an effective mass transportation mode to reduce disruptions traffic. Unfortunately, nowdays angkot is less attractive because people prefer to use personal vehicles such as motorbikes and cars.</p><p>Personal vehicles offer convenience and flexibility, and are currently positioned as a symbol of prosperity but also threaten the existence of angkot. Based on data from the Mabes Polri, the number of personal vehicles registered as of January 1, 2018 reaches more than 111 million. Motorbikes have the largest contribution of 82%, followed by Personal Cars. The remaining contributions are from Bus Cars, Freight Cars and Special Vehicles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*yD584XX8axQ9EshjK8f19Q.png" /></figure><p>In addition to personal vehicles, the presence of app-based transportation (online) is increasingly dimming the existence of angkot.</p><p>In 2015, data from the Ministry of Transportation showed that the number of angkot in Jabodetabek reached 24 thousand units. Depok City with 4.2 thousand units and Bekasi with 4 thousand units. For the DKI Jakarta area, it reaches 2.9 thousand units. While the City and Regency of Bogor each reached 3.4 thousand and 1.9 thousand units.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*zniQxqdJ7jkU6WDuRhKcsA.png" /></figure><p>Even so, angkot is still chosen by the community even though it is not as rich as before until now. Some of the problems faced were the lack of angkot passengers, while the driver had to pursue a deposit that had been set by the angkot owner. Not to mention other costs such as gasoline costs, driver’s meals and vehicle maintenance.</p><p>Some strategies carried out by angkot drivers to maximize their income include starting early and stopping at the side of the road waiting for passengers or the term is usually called <strong><em>‘ngetem’</em></strong>. This angkot habit is detrimental to the passengers and other vehicles in the vicinity.</p><p>Based on the results of an online questionnaire distributed by us which was filled by more than 160 respondents, 90.7% of respondents, namely angkot passengers, had experienced arbitrary ngetem and 80% of respondents felt uncomfortable with the angkot habit. Angkot which is ngetem in any place causes saturation of passengers who wait too long, delay in arriving at their destination, buskers enter, and become one of the causes of traffic distruption. The Regional Government (Pemda) is expected to be able to cooperate with angkot owners and the community to bring out innovations for the survival of angkot and regulate the transportation of their regions.</p><h3><strong>SOLUTION</strong></h3><p><strong>Objectives and Results of ANQOT</strong></p><p>Based on the context described above, we created an app called ANQOT that can be used by a passenger and angkot driver. The advantage for angkot drivers is that there is no need to stop or take too long on the side of the road to wait for passengers who do not necessarily exist or not. In this way the driver can save time and optimize money per day. This application also makes it possible to have a special stops for angkot. While on the passenger side, one of the benefits is that it can minimize the time needed by passengers to wait for angkot and increase of comfortable.</p><h4>Process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgmiJ50Ku31kM3BEbCwuVw@2x.jpeg" /></figure><h4><strong>PHASE 1: STRATEGIZE</strong></h4><p><strong>Defining the problem</strong></p><p>Talking about densely populated cities, of course it cannot be separated from congestion problems, for example in the capital city of Jakarta. According to BPS data in 2018 (Source: Detik.com), there are 18 million motorized vehicles circulating on the streets of Jakarta. The Jakarta city government also hopes that there will be a massive policy to move people to angkot. Unfortunately, the quality of angkot service at this time is not close to the word ‘comfortable’.</p><p>As people who live in urban areas, we also feel that angkot still has many problems. One of the problems that must be resolved immediately is the habit of angkot that is ngetem in any place. These habits are considered to be one of the causes of traffic congestion and disrupt passenger comfort. But in the perspective of the angkot driver, the habit must be done because of the demands of the chase deposit. Then, we wondered:</p><blockquote>“How do we help angkot drivers to get passengers without having to ngetem carelessly?”</blockquote><p>Therefore, the idea of ​​making this ANQOT app was born.</p><p><strong>Product Strategy</strong></p><p><strong>Understand the market and opportunities for success</strong></p><p>The problem solving process is based on the principle of User Centered Design in the hope of providing a good of User Experience (UX). The principle of approach to UX enables the manufacture of products by paying attention to the business, user, and technological constraints. This method makes technology solutions that produce the greatest value for users and therefore can maximize the Return of Investment (ROI) for the intended business side.</p><ul><li>Is this a common problem among target users? (“Is this a real problem” or “Does it have a market?).</li><li>If so, what are the chances of success of this application? (or “What is the market demand and what size is it?”).</li><li>Are there similar products out there and where are their current positions? (or “What is the landscape of competition on the market?”).</li><li>What core values ​​can this product provide to users and who is the target user? (or “What is the proportion of the value and target market for this product?”).</li><li>How to measure success? (or “What is business metrics and data infrastructure”).</li><li>What should be the key feature of Minimal Viable Product (MVP)?</li></ul><p>To answer the questions above, we do several things, namely:</p><ol><li>Surveys, to understand market demand, identify and target users, and identify problems.</li><li>Conduct one on one interview to get further insights about the needs, desires, and problems of the user’s target.</li></ol><p><strong>Business Strategy</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*uzdn-z1AdPp_FEbdLyn8Jw.png" /><figcaption>Business Strategy of ANQOT</figcaption></figure><p>ANQOT is planned to be a mobile app that can be downloaded for free by users. Unlike other transportation booking app, ANQOT presence is focused on increasing the value of existing vehicles which in this case are angkot. In accordance with our mission to reduce congestion and public uncomfort while using angkot, ANQOT must be part of the user’s daily life.</p><p>During the initial launch period, ANQOT main focus was to gain user trust and satisfaction while using the application. Key Performance Indicators (KPI) that measure the success of this stage include:</p><ol><li>Number of application downloads.</li><li>Number of active users.</li><li>Time used (per user).</li><li>Churn and retention rate.</li></ol><p>After penetration is sufficient, we will proceed to the next steps such as advertising, collaboration with the local government or related parties, and so on.</p><p>The strategies and sources of income that have been described above are only limited to the initial description and still need some additions that will be discussed in the future.</p><h4>PHASE 2: EMPATHIZE</h4><p><strong>Online survey</strong></p><p>We conducted a survey with Google Form on August 2–11 with 162 responses. The scope of the survey about angkot and also the ngetem habits. Our goal is to find out the purpose, motivation, needs, and frustration of angkot passengers.</p><p>We collect useful information such as the reason for choosing angkot, how important the problem of ngetem should be solved and what the reasons are, what solutions they want, and whether they need an app to solve this problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*H93SBHa3n9zFsRvXJiBI2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*GEu3vWwVFFWCLiJoX5vLsg.png" /></figure><p><strong>User Interview</strong></p><p>After conducting an online survey to identify angkot passengers, we also conducted user interviews with 3 angkot drivers around Ramayana Ciputat, Tangerang Selatan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*ayEUNHsXTEZeKkhwvvVLkw.png" /></figure><ol><li>How long have you worked as an angkot driver?</li><li>Have you ever had trouble finding passengers?</li><li>Do you often to ngetem?</li><li>How much time do you spend about that?</li><li>Can your passengers reach the maximum amount by ngetem?</li><li>Do you think that the current public transport system is effective?</li><li>Do you agree with the existence of a mobile application-based system to make it easier for angkot drivers to find passengers?</li></ol><p><strong>Persona</strong></p><p>Information obtained from surveys and interviews gives us an overview of the target users in the form of persona. This is to know that the ANQOT application (product) can be in accordance with the background, attitude, goals, motivation, and frustration of the user. We have 2 target users, namely passengers and angkot drivers.</p><p>First, lets to meet Siti, the angkot passenger!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*zMlTeOXnxlGvslPia1y2Zw@2x.jpeg" /></figure><p>Second, lets to meet Asep, the angkot driver!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*D4RkQhfRkQpaIHpjiAbmaA@2x.jpeg" /><figcaption>Persona 2</figcaption></figure><p><strong>Use cases</strong></p><p>To better understand the motivation of users to deepen our knowledge of the value provided by ANQOT, we use Jobs to Be the Done framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*8egeK_2XMS4KvTqe63BcIQ@2x.jpeg" /></figure><p><strong>Understand the goals and needs of users</strong></p><p>At this point, we dedicate time to understanding the needs and objectives of the user. We also try to understand the value elements associated with these two things, as the biggest outcome of ROI generally comes from the perceived value of the product to the target user. These values can later be measured by Net Promoter Score (NPS), which is a metric that is widely used for customer loyalty and advocacy and is highly correlated with the company’s revenue growth later.</p><p><em>Categorize value elements and illustrate what users take by a design perspective.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*5XLlKJeAFsjZm4IXZ0E-Bw@2x.jpeg" /><figcaption>Design Value of ANQOT</figcaption></figure><p><strong>The problem</strong></p><p>The main problem of us is a sense of trust. Users which is angkot drivers and passengers, must trust each other that their needs and desires can be met by ANQOT. To realize this is certainly not easy.</p><p>In this case, on the one hand, the results of surveys and interviews indicate that the user has the same meeting point. Referring to the persona that has been made, if the first experience provided when using the ANQOT application can be well received by users, a sense of trust both fellow users and developers can be established</p><p>This key problem identification makes us choose an approach to user-centered design in the development of ANQOT to provide a good user experience. This approach focuses us on users. With this method, we can design a product (ANQOT) according to the needs, desires, habits and capabilities of users.</p><p>In the end, mutual trust can be shared. On the business side, this will have a positive impact on key business metrics; especially KPI in revenue growth, such as user involvement, adoption rate, user retention rates, etc.</p><h4><strong>PHASE 3: IDEATION</strong></h4><p><strong>Main design features</strong></p><p>Based on our learning from the steps above, we brainstormed to determine what features will be in the ANQOT application as a solution to the problem, and the results are as follows:</p><ol><li>Verify user identity and user detail pages.</li><li>The choice determines the destination path in accordance with the angkot majors in the user’s city.</li><li>See special stops of angkot along the destination.</li><li>Look the position of angkot and passengers in the range radius.</li><li>Give ratings and reviews to angkot drivers that can be read by drivers, angkot owners, and local governments.</li></ol><p><strong>Information Architecture</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hv3s7i7eq58mKdUku8ilUg.jpeg" /><figcaption>IA of ANQOT</figcaption></figure><p><strong>Task Flow</strong></p><ol><li>How to order angkot.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*AdSH4Krol7DqjibWJ47VYg.jpeg" /><figcaption>Task Flow 1</figcaption></figure><p>2. How to check the nearest angkot stop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*aKjyu7tXLR_Tk09Wg4lJkQ.jpeg" /><figcaption>Task Flow 2</figcaption></figure><p><strong>Sketches</strong></p><p>We brainstorm to determine design solution ideas that are in accordance with the things above. We do the sketching process with paper sketching to make it faster and easier to change the rough sketch of ANQOT design if there is something missing or want to add.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*z_TEtvHXwWZjPg36n13Rcw.png" /><figcaption>Paper Sketches</figcaption></figure><p><strong>PHASE 4: PROTOTYPE</strong></p><p><strong>Wireframe</strong></p><p>After sketching, we also digitized the results of sketch to get a clearer picture of the ANQOT application. We make wireframes digitally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eaqgQp1EiMMBmT9p900vqg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FGx0IdaCiZA3d6lWxJEyGg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3lFQswzRR2B_bksvai8D9g@2x.jpeg" /></figure><p><strong>Visual Design</strong></p><p>Because at the TBIG Creation 2018 competition the prototype was made when the participants passed to become finalists, then we did not visualize all the wireframes that had been created. We only display a brief overview of the ANQOT application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bq7KBMdFdL22cJxYpNJLaQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zsYMibumQJJApGbv915fyg@2x.jpeg" /></figure><h3>What’s Next?</h3><p><strong>PHASE 5: VALIDATION</strong></p><p><strong>Usability Testing</strong></p><p>When the prototype design is complete, the next step is to test the target user directly to validate the design solution to the problem that we want to solved. Testing were carried out to test the usability of this ANQOT. The method that can be used is guerrilla usability testing or contextual inquiry by giving the some of task and questions to respondent.</p><p><strong>Reflecting and reiterating</strong></p><p>The design solution with all the features that we offer to target users is an early stage solution. This is certainly still a lot of shortcomings. Therefore, after usability testing for users, we synthesize the data obtained to then repeat again from the ideation stage again until we find a design or feature solution that suits the user’s target. This must be done with the hope that this ANQOT will truly be a solution that can be accepted by users.</p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this case study or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5e4c36520f1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/anqot-a-ux-case-study-d5e4c36520f1">ANQOT — a UX case study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Competitive analysis of online bookstore — a UX case study]]></title>
            <link>https://uxdesign.cc/ux-case-study-competitive-analysis-of-online-bookstore-10a2cf6e0a1f?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/10a2cf6e0a1f</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Sat, 04 Aug 2018 14:44:49 GMT</pubDate>
            <atom:updated>2018-08-08T11:38:12.555Z</atom:updated>
            <content:encoded><![CDATA[<p>The purpose of this study is to develop and improve my UX research skill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tg8Qm6Cgz6zM5TedSo7Q_g@2x.jpeg" /></figure><h3>Background</h3><p>I love books. Recently it occurred to me to design an online bookstore. To get an idea of what my site will be like, I start the step by exploring what is happening in the market by conducted competitive analysis against the main page of each competitor’s site. How do sites sell books? What do users’ feel when they go to the main page? What features are offered? What information is on the main page?</p><h3>Problem</h3><p>Explore features and information on the competitors’ main page in order to know the scope of the design and problem.</p><h3>Process</h3><p>I conducted observation to every main page of the competitor’s site. I tried to identify what each did well, and what each could still be improve. I can act as a user as much as possible to feel what’s really happening.</p><p>A competitor’s</p><ul><li><a href="https://www.gramedia.com/">Gramedia</a></li><li><a href="http://www.bukukita.com/">Bukukita</a></li><li><a href="http://www.bukabuku.com/">Bukabuku</a></li></ul><h3>Competitive Analysis</h3><ol><li><strong>Firstly</strong>, I analyze what features and information are contained on the main page based on the general layout of the webpage: header, navigation, main content, sidebar (left and / right), and footer. This purpose is to gathering the scope of main page design.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enlVFaDd_TGjJq-tCS7zeg.jpeg" /><figcaption>General webpage layout</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*68e9h8hEG3tsnIyZrgv-8g.png" /><figcaption>Competitive analysis of general webpage layout</figcaption></figure><p>2. <strong>Secondly</strong>, I started using this site as a user. The purpose is to gathering what’s problem was occurred that can to be a benefit for my rough picture strategy decision later.</p><p><strong>Gramedia</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*c0_WLLMy2ExTz-L9ZFR2Wg@2x.jpeg" /></figure><ul><li>Not all products offered on the main page have discounted prices. This is maybe because Gramedia is not only focusing on book products.</li><li>There is no buy button in the product list section. If there is a buy button, it will certainly make it easier for users to make purchases.</li><li>Categorization of book offers on the main page is divided into “Most Popular Books”, “Most Wanted Islamic Books”, “Invite Your Child to Read”, “Selected Comics”, and “Come on, Learn Economics”. The title of the categorization is quite persuasive. But it becomes unattractive because the category is not common preferences.</li><li>When viewing a product, the site gives a recommendation book.</li><li>There is a search filter based on stock, price, and category. This feature allows users to filter search according to their preferences.</li><li>Only use 1 shipping method that not much option can choose.</li><li>Payment method is using via banks (transfer or credit card). Those who do not have a bank account can use Go-pay.</li><li>Personal assistant feature is very helpful for users to using the Gramedia site because it’s fast respond to conversations.</li></ul><p><strong>Bukukita</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*H2w198Hv1hbQ3R2s9kERcg@2x.jpeg" /></figure><ul><li>Information on the product list section is complete. The purchase button and how much the original price difference with discount prices make users more interested in desire buying.</li><li>Categorization of book offers on the main page is divided into recommendation books, best seller books, latest books, and promotional books. This division helps users who want to find out what’s happening in the book market.</li><li>There are feature point rewards and lottery every month for users who have successfully made a purchase. This feature is great for increasing user retention.</li><li>The search feature has no filters. Users will have difficulty choosing books that have general keywords such as ‘Food’, because they cannot set up search filters.</li><li>When viewing a product, the site also displays the other books from writer, publisher, and similar.</li><li>Has 4 shipping methods that can be selected according to user needs.</li><li>Limited payment methods for banks (transfer or credit card). Users who do not have a bank account may feel difficulties to purchasing.</li><li>There are testimonial features that are useful to provide a sense of security and trust for new users that wanna to use this site.</li></ul><p><strong>Bukabuku</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ov7HDI5zVzHtt-DEip8SZg@2x.jpeg" /></figure><ul><li>Every hour the top 20 books this week will be updated. Sorting into these 20 lists can make it easier for users to find out what books are popular in the order.</li><li>Categorization of book offers on the main page is divided into staff picks, latest, and pre-order books. This site is more dominant in showing staff picks categories which is containing 50 books list.</li><li>For users who want to make money, Bukabuku provides a dropship or reseller program. The feature is useful for Bukabuku to increase they customers.</li><li>Almost the same as dropship or reseller, affiliate programs also have the advantage of adding consumers and also helping users who want to make money with Bukabuku.</li><li>Author corner feature makes it easy for users to find out more about their favorite authors.</li><li>There is no buy button in the product list section. If there is a buy button, it will certainly make it easier for users to make purchases.</li><li>The search feature has a complete filter, based on from keywords, categories, formats, languages, until sorting list.</li><li>When viewing a product, the site also displays other book from authors and the similar.</li><li>There are testimonial features that are useful to provide a sense of security and trust for new users that wanna to use this site.</li><li>Payment methods can be via bank (transfer or credit card). If you don’t have a bank account you can go through Western Union and even COD (Cash On Delivery).</li><li>Has 4 shipping methods that can be selected according to user needs.</li></ul><h3>My Online Bookstore</h3><p>After conducted a competitive analysis against competitors, I was thinking of taking advantage and disadvantages of each competitor to be used as an rough strategy for my online bookstore that hopefully can closed gap between of two that things.</p><ul><li>Only displaying the discounted products in main page.</li><li>In product list section, information about book must be there are: cover, tittle, author, original price, discounted price, price after discount, stock availability, bonus, and don’t forget about purchase icon or button.</li><li>Categorization of book offers on the main page is divided into recommendation, latest, promotional and pre-order books.</li><li>The search feature must have a complete filter, based on from keywords, categories, formats, languages, price, until sorting list.</li><li>Point reward and lottery every month which make this differ is 1 point = 2 Rupiah (Note: On Bukukita, 1 point = 1 Rupiah).</li><li>Open to dropship or reseller and affiliate programs, but that make this differ is affiliate program can be use a social media. (Note: In Bukabuku, affiliate program only on blog)</li><li>Add author corner feature. Additionally, I think to decided to add publisher corner that can help user to know more about their favorites publisher.</li><li>When viewing a product, the site also displays other book from author, publisher, and similar.</li><li>Payment methods can be via banks (transfer or credit card). If you those who don’t have a bank account you can go through Western Union, Go-Pay, Indomaret or Alfamart (minimarket), even COD (Cash On Delivery).</li><li>Has more 5 shipping methods that can be selected according to user needs. (Note: Adding online riding services such a Go-jek or Grab).</li><li>There are testimonial features that are useful to provide a sense of security and trust for new users that wanna to use this site.</li></ul><h3>Conclusion</h3><p>I have found a rough picture strategy of how my site will compete in the market by trying to provide better features and information than competitors.</p><h3><strong>What’s next?</strong></h3><p>The next step is to conducting a user research by using contextual inquiry method. The goal is to find the needs, wants, and pain points from a real users in order to make the main page design (and others) better than competitors. Based on competitive analysis on general webpage layout design of competitor mainpage, you can do same as well for your layout design.</p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this case study or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10a2cf6e0a1f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-case-study-competitive-analysis-of-online-bookstore-10a2cf6e0a1f">Competitive analysis of online bookstore — a UX case study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Researching UX: User Research — Book Summary]]></title>
            <link>https://medium.com/@anandatama/researching-ux-user-research-book-summary-a894f1b58c4c?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a894f1b58c4c</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 05:10:19 GMT</pubDate>
            <atom:updated>2018-07-26T12:42:54.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NKyrYaZjK3eSGzDKnXCXDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*yO02glvbE8k2qJBo2fqGdA.jpeg" /></figure><p>This book is a practical guide — it will show you step-by-step how to conduct of user research. If you’re a young researcher at the outset of career or those who haven’t been anywhere near UX before, this book have many benefit and very valuable to encourage you to start a user research. From this book, Lang and Howell have contributed to the qualitative knowledge in a meaningful way; especially in conducting a depth-interview, user testing, guerrilla research, and contextual research. That’s a qualitative research skill you can achive after finish reading this book. Sound interesting, right?</p><p>The structure of the book follows the sequence of a research project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*9_Zbzu9t5xs8XXWKQe7bpw.png" /><figcaption>The research cycle</figcaption></figure><p><strong>DESIGN</strong></p><p><strong>Chapter 1</strong> shows how to scope and kick off your project, involving stakeholders to ensure you’re working to the right objectives.</p><p><strong>Chapter 2</strong> walks through the process of choosing a methodology, and the different considerations which play a part in your decision.</p><p><strong>SETUP</strong></p><p><strong>Chapter 3 </strong>covers the different methods for recruiting people to take part in your research, and how to ensure you get the right participants.</p><p><strong>Chapter 4 </strong>outlines the role of a discussion guide (aka session plan, aka script) and shows you how to piece it together part-by part.</p><p><strong>Chapter 5 </strong>looks at the runup to your research sessions, and the preparation involved with lab-based, remote and contextual studies.</p><p><strong>FIELDWORK</strong></p><p><strong>Chapter 6</strong> shows you how to manage a research session, and how to be successful in the roles of observer, note-taker or moderator.</p><p><strong>Chapter 7 </strong>focuses on the detail of interviewing, exploring the anatomy of questions and the role of observation.</p><p><strong>ANALYSIS</strong></p><p><strong>Chapter 8</strong> lays out a system of analysis, describing each of the main phases and showing you which activities to deploy to achieve your specific purpose.</p><p><strong>IMPACT</strong></p><p><strong>Chapter 9 </strong>shows how to bring the project to a successful conclusion, using deliverables and engagement techniques to maximise the impact of your work</p><p><strong>The Gist of the Book</strong></p><ul><li>Research is a team sport.</li><li>When you’re making decisions about your project, think about the end point and work backwards.</li><li>Successful research is about driving design decisions through engagement, not delivering documents.</li><li>Do as much research as you need to, and then stop.</li><li>Analysis starts at the beginning.</li><li>Research is about consent.</li></ul><p>These are the summary per chapter in “Researching UX: User Research”:</p><h3><strong>CHAPTER 1 — Begin the Project</strong></h3><p>To make sure you’re making a good start, it’s helpful to refer to the checklist below, and tick off the things you need. It’s also a good way to structure your activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*Ni_uhnr3ItP01ifghGFfvw.png" /></figure><p><strong>GET STARTED</strong></p><ol><li><strong>Define Your Research</strong> — Business objectives are the end goal of the project. Research objectives are the learning goals of the project. Overt objectives’ are the ones talked about openly, while ‘covert objectives’ are kept quiet (but are no less important).</li><li><strong>Define Hypotheses</strong> — Formal hypotheses are statements which can be tested against the data to determine if they’re supported or not. Rolling hypotheses are early-stage theories or explanations that evolve throughout the project.</li><li><strong>Timeline &amp; Resources</strong></li><li><strong>Engage Stakeholders</strong></li><li><strong>Identify Risks</strong> — It’s important to face up to these possibilities and plan for them, rather than just hope for the best.</li></ol><p><strong>Tools You Can Use</strong></p><p><strong>Use Desk Research to Generate Hypotheses</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*EnCi_qpTktKg8bIH4vYOhA.png" /><figcaption>How to generate hypotheses</figcaption></figure><p><strong>Hold a Kickoff Workshop</strong></p><p><strong>Kickoff workshops follow a standard agenda</strong>:</p><ul><li><strong>Introductions</strong>: name, their role, and their relationship to the project.</li><li><strong>Provide background</strong>: provide an introduction covering the reasons why the project needs to happen, the business, and the context.</li><li><strong>Agree objectives</strong>: ask all of the participants in the workshop to write their objectives for the research on Post-It notes.</li><li><strong>Generate hypotheses</strong>: ask the participants to propose their hypotheses, written on Post-It notes.</li><li><strong>Define resources</strong>: any sources of potential participants, RASCI to define roles, any existing data sources or reports, something to test: a prototype, concept boards or existing product, time and budget.</li><li><strong>Define roles</strong>:</li></ul><p>First, create a RASCI. This is a document which captures the people’s different relationships to the project: R stands for Responsible. A stands for Accountable. S stands for Supporters. S stands for Supporters. S stands for Supporters.</p><p>Next, write all the different jobs that will need to be done on Post-It notes.</p><ul><li><strong>Define the approach</strong>: the team may have some initial preferences or expectations for the approach.</li><li><strong>Define the sample</strong>: hear the team’s suggestions about the kinds of people you should be approaching to interview.</li><li><strong>Arrange stakeholder interviews</strong>: define the other stakeholders you should be speaking to, and arranging times to interview them.</li><li><strong>Define communications approach</strong>: Agree the format, frequency and communications tools you’ll use to catch up and review work.</li><li><strong>Pre-mortem</strong>: ask the team to project their thoughts forward to the end of the project, and assume it hasn’t gone well.</li><li><strong>Personal objectives</strong>: challenge yourself to include something new.</li></ul><p><strong>Talk to Your Stakeholder</strong> — Stakeholders could include the Head of Marketing, Copywriter, User Experience Designer, Lead Developer and Commercial Director.</p><p><strong>Create a Research Canvas</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*NhbohOlnXImrJEOpieiZoA.png" /><figcaption>An example research canvas</figcaption></figure><p><strong>Project Plan</strong> — A project plan is essentially a timeline, showing what will happen when, and enabling you to make sure you’ve got enough to complete each activity before your deadlines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*Up5iehsZk-2DgNiIeH0eQA.png" /><figcaption>A more detailed look at the research cycle</figcaption></figure><p><strong>Make a Plan to Engage People</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*ti2EBTO7omlR5cjOBUuC5A.png" /><figcaption>Engagement planning</figcaption></figure><ul><li>Who you need to get buy-in from.</li><li>Identify what each of these audiences are interested in.</li><li>Identify the key messages.</li><li>Identify the moments.</li><li>Identify the communication methods.</li></ul><p><strong>Tactics for Engagement</strong></p><ul><li>Stakeholder interviews.</li><li>Project space.</li><li>Show &amp; tell.</li><li>Topline findings.</li><li>Project blog / website.</li></ul><p><strong>Work Through Risks to the Project</strong> — A risk register is a list of the potential pitfalls that might affect your project, and your team’s planned response to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*2OZzVWKI34SsbzhB9hSrjQ.png" /><figcaption>A risk register</figcaption></figure><h3><strong>CHAPTER 2 — Choose an Approach</strong></h3><p>Once you’ve conducted your kickoff session, stakeholder interviews and desk research, you’re ready to design your research methodology.</p><p><strong>What is Data?</strong> — In particular, we’ll be showing you how to transform raw data into usable insight, evidence and ideas.</p><p><strong>Qualitative vs. Quantitative</strong> — Qualitative questions are concerned with impressions, explanations and feelings, and they tend to begin with why, how or what. Quantitative questions are concerned with numbers.</p><p><strong>Discovery vs. Validation</strong> — If you’re right at the beginning (in the ‘discovery’ phase), you’ll be needing to answer fundamental questions. If you’re at the validation stage, you have a solution in mind and you need to test it.</p><p><strong>Insight, Evidence and Ideas</strong> — Understand users’ needs in the discovery phase — need insight. Need research to persuade other people — need is evidence. To generate new ideas — rigorous research.</p><p><strong>Validity</strong> — Validity can take several forms. When you design a research project, ask yourself whether your approach is:</p><ul><li><strong>Representative</strong>: Is your sample a cross-section of the group you’re interested in?</li><li><strong>Realistic: </strong>If you’re asking people to complete a task, is it a fair reflection of what they’d do normally?</li><li><strong>Knowable: </strong>Sometimes people don’t know why they do things. If that’s the case, it’s not valid to ask them!</li><li><strong>Memorable: </strong>Small details are hard to remember.</li><li><strong>In the moment: </strong>If your question isn’t knowable or memorable, it’s still possible to tackle it ‘in the moment’.</li></ul><p><strong>Multi-Method Approaches</strong> — And your research projects will always be better if you can combine both, because they counteract each other’s blind spots.</p><p><strong>In-The-Moment Research</strong> — In-the-moment research, then, gives a more realistic view of events than asking people afterwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*Ym9jEdVlige0vPtfSPs-ng.png" /><figcaption>In-the moment research</figcaption></figure><p><strong>Research Methods</strong></p><ul><li><strong>Depth Interviews</strong> — Asking questions in a relatively unstructured conversation. Normally one-to-one.</li><li><strong>User Testing</strong> — Observing users while they complete a series of tasks with the product being tested. Also includes elements of qualitative interviewing.</li><li><strong>Guerrilla Interviews</strong> — Stopping people in a public place to conduct short (5–15 minute) interviews or tests.</li><li><strong>Contextual Research </strong>— Stopping people in a public place to conduct short (5–15 minute) interviews or tests.</li><li><strong>Web Analytics</strong> — Exploring, monitoring and testing hypotheses using a tool such as Google Analytics.</li><li><strong>Co-design</strong> — Bringing together a group of stakeholders and users to work on creative group exercises, to both define a problem and explore solutions.</li><li><strong>Card Sorting </strong>— Types of content are written on cards, which are then sorted into groupings based on their conceptual similarity. Can be done online or in-person.</li><li><strong>Tree Testing </strong>— Users are asked to find particular items of content within a tree structure, eg, “Which aisle are the bread rolls in?” Mainly done online but sometimes in-person.</li><li><strong>Surveys</strong> — Large numbers of users are asked to fill in a structured set of questions, usually online.</li><li><strong>A/B testing</strong> — The behaviour of test and control groups are compared on a live product, to see which scores best against a specific metric.</li><li><strong>Eyetracking</strong> — Like a user test, but participants’ eye movements are monitored to see where their gaze is moving across a web page, picture or room.</li><li><strong>Diary Studies </strong>— Participants keep a record of their behaviour, thoughts or feelings over a period of time, typically a few days to a couple of weeks.</li><li><strong>Focus Groups</strong> — A group of customers are gathered to answer questions about aparticular subject. Similar to co-design, but with more emphasis on talking rather than activities.</li></ul><h3><strong>CHAPTER 3 — Finding Participants</strong></h3><p>Once you’ve started your research project, planned the logistics of how you will run your fieldwork, and decided on your approach to your analysis and outputs, you need to find your participants: the people who you’ll be interviewing, observing, or asking to try your product.</p><p><strong>Who To Recruit</strong></p><p><strong>Defining Your Sample</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*AU3hprqe-Ju8CVp_AGFZNg.png" /><figcaption>Sample planning session</figcaption></figure><p><strong>Creating a Recruitment Brief</strong> — A recruitment brief is a document specifying the details you need to complete recruitment successfully.</p><ul><li><strong>The sample definition</strong>. Here, you’ll list the variables, definitions and values you created in the exercise above as recruitment criteria.</li><li><strong>The logistics</strong>. Dates, times and locations of research sessions.</li><li><strong>Details of the incentive payment for participants</strong>. If you’re planning to outsource the recruitment, then some background on the project is also helpful.</li></ul><p><strong>Defining Criteria</strong> — Once you’ve dealt with your primary variables, you’ll need to specify your other criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*dlJjtVx3BtIlkdvOcM6VXA.png" /><figcaption>Example primary variables</figcaption></figure><p><strong>Getting The Right People</strong></p><ul><li>Evaluating against the recruitment brief.</li><li>Using a screener.</li></ul><p><strong>Creating a Screener</strong> — A screener is a set of questions that are asked to potential participants, based on the sample criteria you defined in your recruitment brief.</p><p><strong>Methods of Accessing People</strong></p><ul><li><strong>Recruitment agencies</strong> — Professional recruiters will find you high-quality participants, and will be able to give you advice and guidance along the way.</li><li><strong>Guerrilla </strong>— We’ve already mentioned that the recruitment brief and screener you use for guerrilla recruitment will be short, compared with the version you use for pre-arranged interviews.</li><li><strong>DIY </strong>— Doing recruitment yourself can be a poor use of resource, and will almost always cost you more than using a recruiter, once you’ve taken your own time into account.</li><li><strong>Gatekeepers</strong> — Sometimes a client or someone within your organization will play the role of a ‘gatekeeper’ to a group of individuals. The gatekeeper will usually have access to a list of potential participants and their contact details.</li></ul><p><strong>Persuading People to Take Part</strong> — Sometimes, people choose to take part in research purely because it’s a subject they care about. Mostly, though, you’ll need to provide them with an incentive of some sort.</p><p><strong>Arranging Sessions</strong> — Now you know who you want to talk to, you need to plan the times and dates be doing your research. For guerrilla research, this will be straight away. Exactly where you found the fieldwork in the lab, home or in workplaces, you will need to book them in.</p><p><strong>Informed Consent</strong> — As a researcher, you have an ethical duty to make sure that potential participants are able to make an informed decision about whether or not they want to take part in your research.</p><h3><strong>CHAPTER 4 — Writing a Discussion Guide</strong></h3><p>You do this by imaginatively playing through what might happen, plotting out how to achieve your aims, and weighing up different questions and activities you might use. Most of this planning takes place in your head, but it also has a physical product, which goes by the name of the discussion guide.</p><ul><li><strong>Introducing the session</strong> (5 minutes of a 60-minute session) — In this first section, you’re going to lay the ground rules for the participant, explaining what you need from them in the session, and answering any questions they may have. This is also the moment at which you’d give the participant a consent form to read and sign.</li><li><strong>Participant introduction</strong> (5–10 minutes) — The purpose of this section is to get the participant talking and feeling comfortable with the interview setting. It also provides you with some background information about their life and habits, which you can refer to later on.</li><li><strong>Setup for the main task or topic</strong> (3–5 minutes) — Before you go into the main task, you need to lay the groundwork correctly.</li><li><strong>Main task or topic</strong> (5–20 minutes) — If your research is about testing an e-commerce journey, then you would get your participant to complete the journey now. If your research is about getting reactions to a new concept, then this is when you would do the big reveal, etc.</li><li><strong>Exploring the detail</strong> (10–20 minutes) — Tasks or activities to use. These are different ways to get your participant to explore the topic or product, especially the parts that they might not otherwise have discovered.</li><li><strong>New versions or comparisons with competitors </strong>(0–10 minutes) — Towards the end you’re in a position to show some new variations.</li><li><strong>Summing up </strong>(5 minutes) — In this section, you’re asking the participant to summarise their experiences and reactions.</li></ul><p><strong>Questions, Tasks, and Activities</strong></p><p><strong>Tasks</strong> — Tasks are the tool we use to be able to observe users’ behaviour. <strong>Questions</strong> — At this point, it’s just worth mentioning that your bigger research questions and hypotheses should definitely be included in your discussion guide. <strong>Activities </strong>— Activities are another way to get an insight into participants’ decision-making and behaviour.</p><p><strong>How to Write a Discussion Guide</strong></p><p>Before you starting writing the detail, plan out your approach at a high level:</p><ul><li>Write out your main research questions or rolling hypotheses.</li><li>Check how long you’ve got, and divide up your time into rough sections using the approach described earlier in this chapter.</li><li>Identify your main task, activity or topic.</li><li>Think about your secondary activities and areas to cover.</li><li>Otherwise, create a list of competitors or other products you’d like to compare.</li><li>Think about the context that will be useful to understand about the participant and their relationship to the product.</li></ul><h3><strong>CHAPTER 5 — Set Up Your Sessions</strong></h3><p>If you want your research sessions to run smoothly, you will want to take some time in the days beforehand to prepare. That way, you can be sure that everything you need is ready, the project team know their roles, and you’ve got time to fix any problems that come up.</p><p><strong>Getting Prepared for Research in the Lab</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*194im7VrcZ3Vtq8qc_uIgw.png" /><figcaption>Overview of the testing week</figcaption></figure><p><strong>Monday: Three Days Before Your Session</strong></p><p>On the Monday, allow two to three hours for setup activities.</p><ul><li><strong>Run a Pilot Session</strong> — it’s a chance for you to test out your guide with a pretend participant.</li><li><strong>Check Your Test Venue</strong> — Get some photos and you can plan how you’ll use the space.</li><li><strong>Labs and Two-Way Mirrors </strong>— The minimum that you need is a quiet room and some equipment or materials to test with.</li></ul><p><strong>Tuesday: Two Days before your session</strong></p><p><strong>Agree Roles</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*6WPK61_RC_wbB04n7-YvIA.png" /><figcaption>Agreeing roles for team members</figcaption></figure><p><strong>Agree a Checklist </strong>— A really worthwhile activity at this stage is to write out a checklist of all the things you need to prepare for your test session.</p><p><strong>Wednesday: The Day Before Your Session</strong></p><p><strong>Mark Up Your Guide </strong>— So we recommend making a condensed version of your discussion guide.</p><p><strong>Set Up the Research Room</strong> — You will want to make sure that the testing and viewing rooms are tidy, clean and set up appropriately for your research.</p><p><strong>Remind Participants </strong>— Once your participants are confirmed, you can print out the details to refer to in the session.</p><p><strong>Thursday: The Day of Your Session</strong></p><p>The key checks for the morning are:</p><ul><li>Double checking that your equipment is working, charged and has enough disk space.</li><li>Make sure you have back up equipment (spare laptop/tablet).</li><li>Checking your emails for any last minute participant cancellations.</li><li>Checking your research and observation rooms are ready.</li><li>Check that your prototype (or whatever you are testing) is working</li></ul><p>If you are doing the interviewing, we really recommend allowing yourself time alone to go over the discussion guide. Find a quiet spot to do this where you won’t be interrupted.</p><p><strong>Getting Prepared for Research in the Field</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*OjxbNGyXZZQUMpihlTp6GA.png" /><figcaption>Example week for guerrilla testing</figcaption></figure><p><strong>Getting Prepared For Remote Research</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*6ZvqHy0eHydWY1KjjtJHXA.png" /><figcaption>Remote testing week</figcaption></figure><h3><strong>CHAPTER 6 — Running Your Sessions</strong></h3><p><strong>Roles</strong></p><p>The four key roles on the day of research are:</p><ul><li><strong>Interviewer.</strong> This person is responsible for talking to the users and running the test sessions.</li><li><strong>Host </strong>(of the observation room). This person is responsible for looking after the people watching the research in the observation room. They will facilitate discussions and make sure observers know how to get the most out of watching the research.</li><li><strong>Note-taker </strong>This person is in charge of capturing the information from the test session, such as positive moments, pain points, quotes or suggestions.</li><li><strong>Observer</strong> This person has come along to watch the testing but is encouraged to get involved and take notes.</li></ul><p><strong>Taking Notes</strong></p><ul><li>We use <strong>pink Post-It notes </strong>to make notes about pain points that come up during the session.</li><li><strong>Green Post-It notes </strong>are for positive comments or interactions.</li><li>We use <strong>yellow Post-It note</strong>s for suggestions or more general observations.</li></ul><p>Our rules of recording on Post-It notes are:</p><ul><li>One comment or observation per Post-It.</li><li>Make sure the participant number is on the Post-It note.</li><li>Include the time on any key moments.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*bHiTDFvz0LO7wXNyw5FcPw.png" /><figcaption>Using Post-It notes</figcaption></figure><p><strong>Tools For Recording</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*tUQXrZ9ZYf-BgAPKHj4amA.png" /></figure><h3><strong>CHAPTER 7 — Interviewing</strong></h3><p>We’ll cover interviewing techniques, managing tasks, and how to deal with tricky situations that can throw you off balance.</p><p><strong>Show Participants How to Help You</strong></p><ul><li>By clearly communicating the rules, process and expectations of the session, you can show them how to help you.</li><li>If you want a session to run smoothly, the first thing you can do is be clear about what you need.</li><li>Tell them what will happen. Make it a conversation, not a speech</li><li>At transition points in the session, remind them.</li><li>If the participant is doing something you don’t want, say so. Be firm (but pleasant and polite) in your moderating.</li></ul><p><strong>Dressing for Your Interview</strong> — Use your clothing to make your participants feel at ease, and to set the tone of the session.</p><p><strong>Observing vs. Asking</strong></p><ul><li>Your observations of the participant as they complete tasks and activities.</li><li>Nonverbal communication: body language, gestures and the like. Does it echo what’s been said, or contradict it?</li><li>The participant’s tone of voice, energy, mood, cadence, and how these are changing over time.</li><li>If there’s more than one participant, the dynamic and interaction between them.</li></ul><p><strong>Paying Deep Attention</strong> — Actually, the core skill is simple: stop worrying about your next question, and instead pay attention to the participant. You’ll find your next question comes naturally from what they say or do.</p><p><strong>Starting the Session</strong> — We introduce ourself and thank them for taking the time to come in and help us out. We explain what we’re doing and what they can expect from the session, and give them a chance to ask any questions.</p><p><strong>Make Sure You Get Consent</strong> — You need to explain your consent form to your participants and be ready to answer their questions.</p><p><strong>How to Ask a Question</strong></p><p>In this section we’re going to look at how questions work:</p><ul><li>Individually, questions have their own syntax.</li><li>In sets, questions have a combined power</li><li>Good questioning relies on timing</li></ul><p>Here are 10 pointers to making you a better interviewer. Try to focus on one or two of these each time you run a session, and ask your colleagues for feedback on how you did.</p><ol><li>Clearly State the Subject and the Query.</li><li>Don’t Use Leading Questions: Establish Relevance Instead.</li><li>Keep Your Question As Short As It Can Be.</li><li>Closed Questions and Open Questions Have Complementary Strengths and Weaknesses.</li><li>Look Out For ‘Value Words’.</li><li>Listen For Contradictions and Gaps.</li><li>Use Question Chains.</li><li>Prompt, But Don’t Lead.</li><li>Choose The Right Moment.</li><li>Be Quiet.</li></ol><h3><strong>CHAPTER 8 — Analyzing Your Data</strong></h3><p>Analysis is the core of the research process. It’s where you transform your raw data (in other words, your observations about what users did or said) into insight and ideas.</p><p><strong>Phases of Analysis</strong></p><p>The first three phases are non-negotiable. You’ll have to do these to some extent, even if your project is very short. Phases 4 and 5 are optional, depending on the outputs you need from the project.</p><ol><li><strong>Make a plan</strong>. You’ll do this right at the start of your project, and return to it when you get into fieldwork.</li><li><strong>Absorb the data</strong>. After fieldwork, you’ll need to tidy up the data you’ve collected into a usable shape. This phase focuses on organizing and digesting the evidence.</li><li><strong>Find patterns</strong>. Sift the data to uncover common themes and explanations. This phase focuses on generating the insights.</li><li><strong>Use patterns</strong>. Reconfigure the patterns you’ve uncovered to generate new ideas. This phase focuses on producing ideas.</li><li><strong>Create your narrative</strong>. Rework the insights and evidence as a communication. This phase is about creating a story.</li></ol><p><strong>Phase 1: Make a Plan</strong></p><p>The purpose of this phase is to make sure you’re getting maximum benefit out of the rest of the project. You’ll make sure that you’re recording the data in a format that makes it easy to work with, and you’ll make best use of the time you’ve got for analysis afterwards.</p><ul><li><strong>Who’s involved</strong>: the core project team, including designers and researchers.</li><li><strong>How long</strong>: 5 minutes for a small, simple project, to two hours for a more complex discovery project.</li><li><strong>Where to do it</strong>: in the project space, or a meeting area with a large wall or whiteboard.</li></ul><p><strong>Phase 2: Absorb the Data</strong></p><p>The purpose of this phase is to re-absorb the detail of the data, and to get it into a format that’s easy to work with for the following phases.</p><ul><li><strong>Who’s involved</strong>: the people who conducted the research, working individually</li><li><strong>How long</strong>: extremely variable, from hours to weeks</li><li><strong>Where to do it</strong>: somewhere quiet, where you’re less likely to be disturbed</li></ul><p><strong>Create a Space</strong> — To create your project space, begin by building a stimulus wall, using a selection of the different printed resources available to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*57n7ukD-WvyigsSQ9ZJb4Q.png" /><figcaption>Example project space</figcaption></figure><p><strong>Collate Sources</strong> — Even in the simplest project, you’re likely to have data in several different sources orlocations. Gather it together</p><p><strong>Reformat</strong> — Sadly, the format you found convenient for capturing data is probably not the most convenient format to work with in the analysis.</p><p><strong>Rejecting Bad Data</strong> — It feels somehow wrong to throw away data, but now’s the time to be ruthless.</p><p><strong>Prioritize</strong> — another way to prioritize is to sort your sessions into three groups: Clear and helpful, Confusing or complicated, and Clear and unhelpful.</p><p><strong>Review Recordings</strong> — take yourself back to the moment and take yourself back to the moment.</p><p>I<strong>mproving Your Technique</strong> — Listening back to your own interviewing is the single best way you can get better at it.</p><p><strong>Transcribe</strong> — To generate ideas for the following phase of the analysis process.</p><p><strong>Phase 3: Finding Patterns</strong></p><p>The purpose of this phase is to go from individual observations (what your individual participants did or said) to patterns and rules (the general conclusions you can draw based on your data).</p><ul><li><strong>Who’s involved</strong>: the core project team. Later on, you may chose to involve other people, such as stakeholders and/or service users.</li><li><strong>How long</strong>: half a day to two days.</li><li><strong>Where to do it</strong>: in a room with plenty of space to move around and stick things onto walls. Ideally, you’ll already have set up a project space in the previous phase.</li></ul><p><strong>Review Objectives or rolling Hypotheses</strong></p><p><strong>Brain Dump</strong></p><p><strong>Don’t:</strong></p><ul><li>Worry about keeping to the data. It’s fine to digress into your own feelings about the research, conclusions you’ve drawn, or related topics.</li><li>Try to take structured notes. Let the conversation flow.</li></ul><p><strong>Do:</strong></p><ul><li>Keep strictly to the time. This is really a warm-up activity. 30 minutes is plenty.</li><li>Let everyone speak. The person who’s managing the timing should also act as moderator, if one or two people are dominating the discussion.</li><li>Pay attention to the topics and concepts that are emerging from the discussion. These will be useful later.</li><li>Capture the highlights. While written notes get in the way, there may be an interesting point raised in the course of the conversation</li></ul><p><strong>Who Were the People?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*NcF5FC-HpxKEXVx5fNen1w.png" /></figure><p><strong>Conceptual Diagrams</strong> — Through your earlier activities and hypotheses, you’ll have started to get a sense of themes emerging. Let’s attempt to visualize those patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*i5z59hFWqonm05L89Xs5Eg.png" /><figcaption>Roughly drawn</figcaption></figure><p><strong>Maps &amp; Sketches </strong>— As well as abstract conceptual diagrams, it can also be useful to draw maps and sketches.</p><p><strong>Tablecloth</strong> — To create the tablecloth, add a column for each participant (or group of participants if you’ve got a larger sample). In the rows, add the variables you’re interested in.</p><p><strong>Using a Spreadhsheet</strong> — Bonus feature: if you opt for a spreadsheet for your tablecloth, you can use conditional formatting to help highlight patterns, creating a ‘rainbow tablecloth’.</p><p><strong>Affinity Sort </strong>— Affinity sorting is one of the most popular methods for making sense of data from qualitative research.</p><p><strong>Theory to Help You Understand the Data </strong>— If you take this approach, remember that any theory is there to help you, not get in the way. Don’t worry about using a pick-and-mix approach (the technical term is ‘bricolage’).</p><p><strong>Avoid Getting Heavy With Theory When Presenting Your Findings</strong></p><p><strong>Check Your Biases</strong></p><ul><li>Consider your cultural biases.</li><li>Watch out for your cognitive biases.</li><li>Create and test deductive statements.</li></ul><p><strong>Phase 4: Working With Patterns</strong></p><p>The purpose of this phase is to expand your understanding of your users’ needs through creative activities.</p><ul><li><strong>Who’s involved</strong>: the same group who were involved in phase 3.</li><li><strong>How long:</strong> half a day to a day.</li><li><strong>Where to do it</strong>: in the project area</li></ul><p><strong>Thought Experiments </strong>— Thought experiments are a game-like approach to understanding your users’ needs better. The idea here is to achieve insights by manipulating some aspect of your themes, by asking a lot of “what if?” questions</p><p><strong>Extension</strong> — A variation on thought experiments, extension involves taking one attribute of your product or experience and greatly exaggerating it or eliminating it.</p><p><strong>Think By Making</strong> — The idea of prototyping needs no introduction, but it’s a great way to extend the ideas you’ve developed already and begin to ‘think by making’.</p><p><strong>Metaphor</strong> — A strong, unfamiliar metaphor can be a powerful design tool. At this stage in the analysis process, you’re in a position to try out some new ways of describing users’ relationship to the product.</p><p><strong>Phase 5: Creating a Narrative</strong></p><p>The key to doing this effectively is to have a clear, logical core narrative that you can use in different media to tell your story.</p><ul><li><strong>Who’s involved</strong>: the whole team.</li><li><strong>How long</strong>: 30 minutes to a day.</li><li><strong>Where to do it</strong>: in the same area you used for phases 3 and 4.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*QsUsmFy8woU7WLPR5kKq4w.png" /><figcaption>A pyramid of findings</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*ulNoCD4Tgxk49IrWPkqaGQ.png" /></figure><h3><strong>Chapter 9 — Turning Research Into Action</strong></h3><p>It’s common to associate the end of a research project with some kind of debrief session or report, where the person who did the research tells everyone else what the answer is.</p><p><strong>Engaging Stakeholders Throughout the Project</strong> — There are a number of ways you can involve your colleagues and stakeholders throughout the project. This isn’t a complete list — use it as a starting point to add your own ideas to.</p><p><strong>Attending Research Session</strong>s — It might sound obvious, but one of the best ways to get your colleagues thinking about the research is to persuade them to attend some of the interview sessions.</p><p><strong>Topline Findings </strong>— Once your research sessions have begun, it’s a good idea to share a regular update of your findings.</p><p><strong>Project Blog / Websites</strong> — Taking the idea of topline reporting a step further, it’s worth considering a project blog, website or intranet page.</p><p><strong>Documenting What You’ve Learned</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*y89wT7oQFhelzzTtVOhHZg.png" /></figure><p><strong>Report Deck</strong> — The classic format for documenting research projects is a slide deck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*lKvXdpf5SpHGxZXDGPznlQ.png" /><figcaption>An annotated screeengrab</figcaption></figure><p><strong>List Reporting</strong> — In contrast to report decks, list reporting dispenses with the frills and gets straight to work listing the problems and recommendations.</p><p><strong>Journey Map </strong>— Journey maps show the steps taken by a user to complete a specific task. Journey maps are an excellent way to record users goals and expectations, and the problems that they encounter in completing them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*dtR-Zv3DUI4jBwrGcPIrdA.png" /><figcaption>An example journey map</figcaption></figure><p><strong>Experience Map</strong> — An experience map is like a journey map on a grander scale. Instead of focusing on a specific journey, it takes in the entire customer experience for a particular product or service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*dEEdW-yFeZKPYop-0YupFA.png" /><figcaption>Example experience map</figcaption></figure><p><strong>Personas </strong>— A persona is an abstracted set of user needs, normally presented in the form of an imaginary person.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*mq-ZwEOUtF4umZEObWmDWQ.png" /><figcaption>Example persona</figcaption></figure><p><strong>Showreel </strong>— Showreels are compilations of video clips. They’re great for providing your audience with direct exposure to your users, and it highlights their experiences like no other format can.</p><p><strong>Debrief Session</strong></p><p>In most research projects, you’ll want to mark the end of the cycle with a face-to-face debrief session.</p><p><strong>Presenting Findings</strong> — Firstly, present back the findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*57L8GJ4lYF7FPYXmyvO9Yg.png" /><figcaption>Feedback model</figcaption></figure><p><strong>Agreeing Actions</strong> — The best way to do this is by continually engaging and making the research relevant to your stakeholders.</p><p><strong>Empathy Mapping</strong> — Complete a different empathy map for each set of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*8aFeWLR4jdiBaFDy9HrLDQ.png" /><figcaption>Empathy map example</figcaption></figure><p><strong>Prioritization Grid</strong> — Create a 2x2 framework like the one below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*jBdbyjGPj5K5jL-MQFll0w.png" /><figcaption>A prioritization grid</figcaption></figure><p><strong>Agree Backlog</strong> — If you’re already managing a backlog of product changes, you can add the actions from the research onto your existing list. If you’re starting from scratch, then work as a group to create recommendations in a list report.</p><p><strong>Roadmapping</strong> — This is a particularly good activity if you’ve created an experience map. Looking at the experience map, identify user problems you could address with new initiatives and add them as Post-It notes in a different color.</p><p><strong>Top Priorities </strong>— Ask each participant to complete Post-It notes capturing recommendations for action during your presentation, or generate them in small groups afterwards.</p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this summary or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a894f1b58c4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Just Enough Research — Book Summary]]></title>
            <link>https://medium.com/@anandatama/just-enough-research-book-summary-8bde7053c48a?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bde7053c48a</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 05:16:56 GMT</pubDate>
            <atom:updated>2018-07-26T05:11:08.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKKmqrFYWO21KxaLaucSaA.jpeg" /></figure><p>Back in 2013, Erika Hall, founder of Mule Design, wrote “Enough Research”. This book consists of 9 chapters which is distills her experience into a brief cookbook of research method. Although this book is not so thick (only have 163 page), you’ll find research reasons, the basics, research processes and research methods that can help you to be a good researcher.</p><p>The list of chapters in this book:</p><ul><li><strong>CHAPTER 1</strong> — Enough is Enough</li><li><strong>CHAPTER 2</strong> — The Basics</li><li><strong>CHAPTER 3</strong> — The Process</li><li><strong>CHAPTER 4</strong> — Organizational Research</li><li><strong>CHAPTER 5</strong> — User Research</li><li><strong>CHAPTER 6</strong> — Competitive Research</li><li><strong>CHAPTER 7</strong> — Evaluative Research</li><li><strong>CHAPTER 8</strong> — Analysis and Models</li><li><strong>CHAPTER 9</strong> — Quantitative Research</li><li><strong>CONCLUSION</strong></li></ul><p>And now, these are the summary per chapter in “Just Enough Research”:</p><h3>CHAPTER 1 — Enough is Enough</h3><p><strong>What research is</strong></p><ul><li>Research is <strong>simply systematic inquiry.</strong></li><li><strong>Personal research</strong>​ — Finding information for yourself (Google searches).</li><li><strong>Pure research </strong>— Is carried out to create new human knowledge based on observation or experimentation.</li><li><strong>Applied research</strong> — Borrows ideas and techniques from pure research to serve a specific real-world goal.</li><li><strong>Design research</strong> — Studying about design itself or the end users.</li></ul><p><strong>What research is not</strong></p><ul><li>Not asking people what they like (or hate).</li><li>Not a politcial tool.</li><li>Applied research is not science.</li></ul><h3>CHAPTER 2 — The Basics</h3><p><strong>Who should do research? Everyone!</strong></p><p><strong>Find your purpose</strong></p><ul><li>Generative or exploratory research: “What’s up with…?”</li><li>Descriptive or explanatory: “What and how?”</li><li>Evaluative research: “Are we getting close?”</li><li>Casual research: “Why is this happening?”</li></ul><p><strong>Roles</strong></p><ul><li>Author.</li><li>Interviewer/Moderator.</li><li>Coordinator/Scheduler.</li><li>Notetaker/Recorder.</li><li>Recruiter.</li><li>Analyst.</li><li>Documenter.</li><li>Observer.</li></ul><p><strong>The research processes</strong></p><p><strong>Overcoming objections</strong></p><ol><li><strong>The objections you will hear</strong></li></ol><ul><li>We don’t have time.</li><li>We don’t have the expertise or budget.</li><li>The CEO decides what we do anyway.</li><li>One methodology is better (quant or qual).</li><li>You need to be a scientist You need infrastructure (equipment and a special room).</li><li>It will take too long.</li><li>You can find our everything you need once we launch the beta.</li><li>We know everything already.</li><li>Research will change the scope.</li><li>Research will impede innovation.</li></ul><p>2. <strong>Actual reasons behind the objections</strong></p><ul><li>I don’t want to bother.</li><li>I’m afraid of being wrong.</li><li>I’m uncomfortable talking to people.</li></ul><p><strong>Research in any situation</strong></p><blockquote>“Poor user experiences inevitably come from poorly informed<br>design teams.” — <strong><em>Jared M. Spool</em></strong><em>, founder of user Interface Engineering</em></blockquote><p>Contexts and situations where you might be doing research:</p><ul><li>Freelance.</li><li>Client services agency.</li><li>In-house at a big company.</li><li>In-house at a startup.</li><li>Working with an agile development team.</li></ul><p><strong>Just enough rigor</strong></p><ol><li><strong>Cover your bias</strong></li></ol><ul><li><strong>Design bias​ </strong>— The design of your study has inherent biases so be sure to compensate for them.</li><li><strong>Sampling bias</strong>​ — Be mindful of who you select to participate.</li><li><strong>Interviewer bias</strong>​ — It’s hard to be neutral.</li><li><strong>Sponsor bias</strong>​ — Who’s paying for everything?</li><li><strong>Social desirability bias</strong>​ — Everyone wants to look their best.</li><li><strong>The Hawthorne effect​ </strong>— The behavior of the people you are studying might change just because you are there.</li></ul><p>2<strong>. The ethics of user research</strong></p><ul><li><strong>The project as a whole​</strong> — Is it ethical?</li><li><strong>The goals or methods</strong>​ — Are you tricking your participants?</li><li><strong>Consent and transparency​</strong> — Informed consent is the rule.</li><li><strong>Safety and privacy</strong>​ — Don’t do telephone interviews with someone who is driving.</li></ul><p><strong>3. Be skeptic</strong>: Ask a lot of questions! Get comfortable with knowing and working with your own limits.</p><p><strong>4. Best practices</strong></p><ul><li>Phrase questions clearly.</li><li>Set realistic expectations.</li><li>Be prepared.</li><li>Allow sufficient time for analysis.</li><li>Take dictation.</li></ul><p><strong>5. How much research is enough?</strong></p><ul><li>Avoiding unnecessary research</li><li>That satisfying click — There is no answer to the question of enough.</li></ul><h3>CHAPTER 3 — The Process</h3><ol><li><strong>Define the problem</strong> — A useful research study depends on a clear problem statement. Base your statement on a verb that indicates an outcome, such as “describe,” “evaluate,” or “identify.”</li><li><strong>Select the approach</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*9pLUhTqIEscXKc5BOI8kKw.png" /><figcaption>The topic and nature of your questions will guide your choice of research activities.</figcaption></figure><p><strong>3. Plan and prepare for the research</strong></p><p>Identify the point person who will keep track of everything. Sketch out a plan in terms of time, money, people involved and their roles, necessary materials, etc. You don’t have to get it 100% correct but it helps to have it all laid out.</p><p><strong>Recruiting</strong> — Recruiting is simply locating, attracting, screening, and acquiring research participants. There’s no draft, so you have to recruit.</p><p>A good research participant:</p><ul><li>Shares the concerns and goals of your target users.</li><li>Embodies key characteristics of your target users, such as age or role.</li><li>Can articulate their thoughts clearly.</li><li>Is as familiar with the relevant technology as your target user</li></ul><p>Recruiting isn’t fun but it gets easier with practice.</p><ul><li>Use the web to your advantage to cast a wide net.</li><li>Use a screener to make sure that you’re recruiting the right<br>people.</li></ul><p>Elements of a screener:</p><ul><li>What are all of the specific behaviors you’re looking for?</li><li>What level of tool knowledge and access do participants need?</li><li>What level of knowledge about the topic (domain knowledge) do they need?</li></ul><p><strong>Collect the data</strong> — Find your research subjects. Conduct your interviews. Do your feld observation. Run your usability tests.</p><ul><li>Materials and tools — Use what you already have frst, and go for familiar tools.</li><li>Interviewing — A simple interview remains the most eﬀective way to get inside another person’s head and see the world as they do.</li><li>Usability testing — The goal is to determine to what extent the product or service as designed is usable.</li></ul><p><strong>Analyze the data</strong> — Once you have collected the data, gather it all together and look for meaningful patterns. Turn the patterns into observations, and from those, recommendations will emerge.</p><ul><li>Get everyone involved.</li><li>Structuring an analysis session.</li></ul><p><strong>Report the results</strong></p><p><strong>And repeat</strong></p><h3><strong>CHAPTER 4 — </strong>Organizational Research</h3><p>Researching an organization is very similar to traditional user research and can be incredibly helpful to interactive design and development projects.</p><p><strong>Who are stakeholders?</strong></p><ul><li>Defined as “those groups without whose support the organization would cease to exist.”</li><li>Executives, managers, subject matter experts, staff in various roles, investors and board members.</li></ul><p><strong>Interviewing stakeholders</strong></p><blockquote>“Interviews with project stakeholders oﬀer a rich source of insights into the collective mind of an organization. They can help you uncover areas of misalignment between a company’s documented strategy and the attitudes and day-to-day decision-making of stakeholders. They can also highlight issues that deserve special consideration due to their strategic importance to a business.” — <strong><em>Steve Baty</em></strong><em>, “conducting successful Interviews with Project stakeholders”</em></blockquote><p><strong>What interviewing stakeholders is for:</strong></p><ul><li>Neutralizing politics.</li><li>Better requirements gathering.</li><li>Understanding organizational priorities.</li><li>Tailoring the design process.</li><li>Getting buy-in from said stakeholders.</li><li>Understanding how your work affects the organization.</li><li>Understanding workflow.</li></ul><p><strong>Types of interviews:</strong></p><ul><li>Individual interviews.</li><li>Group interviews.</li><li>Email interviews.</li></ul><ol><li><strong>Interview structure</strong></li></ol><ul><li>Introduce yourself.</li><li>Explain the purpose of the meeting.</li><li>Explain how the interview data will be shared.</li><li>Be sure that people can speak freely.</li></ul><p>2. <strong>Dealing with hostile witnesses</strong></p><ul><li>Do your research ahead of time to predict if a stakeholder might be combative.</li><li>Remain calm and confident (practice with members of your team beforehand).</li></ul><p><strong>3. Documenting interviews.</strong></p><p><strong>What to do with stakeholder analysis</strong></p><p>What you should include in this documentation:</p><ul><li>Problem statement and assumptions.</li><li>Goals.</li><li>Success metrics.</li><li>Completion criteria.</li><li>Scope.</li><li>Risks, concerns, and contingency plans.</li><li>Verbatim quotes — Very valuable but try to anonymize them.</li><li>Workflow diagrams (see graphic).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*fePTgva0Ekg74cn3I_d2Jw.png" /><figcaption>A workflow diagram can describe the current situation or illustrate your recommendation based on you’ve learned about the organization</figcaption></figure><h3>CHAPTER 5 — User Research</h3><p>When we talk about user research as distinguished from usability testing, we’re talking about ethnography, the study of humans in their culture. We want to learn about our target users as people existing in a cultural context. We want to understand how they behave and why.</p><p><strong>Everything that factors into context</strong></p><ul><li>Physical environment</li><li>Mental model</li><li>Habits</li><li>Relationships</li></ul><p><strong>Assumptions are insults</strong></p><p><strong>Getting good data from imperfect sources</strong></p><p><strong>What is ethnography?</strong></p><p>The fundamental question of ethnography is, “What do people do and why do they do it?” In the case of user research, we tack on the rider “…and what are the implications for the success of what I am designing?</p><p><strong>The four Ds of design ethnography</strong></p><ul><li><strong>Deep dive </strong>— Get to know a small but sufficient number of representative users very well</li><li><strong>Daily life</strong> — It’s of limited utility to learn how people behave in your conference room so go to where they live and work.</li><li><strong>Data analysis</strong> — Systematic analysis is the difference between actual ethnography and just meeting interesting new people at a networking event.</li><li><strong>Drama! </strong>— Lively narratives help everyone on your team rally around and act on the same understanding of user behavior</li></ul><p><strong>Interviewing humans</strong></p><ol><li><strong>Preparation</strong></li><li><strong>Interview structure</strong>: Three boxes, loosely joined</li></ol><ul><li>Introduction: Say hello, express gratitude, talk about why you’re there,<br>review demographic information</li><li>Body: Ask open-ended questions, follow up or probe as necessary, allow<br>pauses and silences.</li><li>Conclusion: Express gratitude again, ask if they have questions, talk about<br>next steps.</li></ul><p><strong>3. Conducting the interview</strong></p><ul><li>Don’t forget to breathe</li><li>Practice active listening (Nod and say “mm-hmm” but pay close attention)</li><li>Keep an ear out for vague answers</li><li>Avoid talking about yourself</li></ul><p><strong>Contextual inquiry</strong></p><p>Contextual inquiry is a deeper form of ethnographic interview and observation. It is particularly useful for developing accurate scenarios, the stories of how users might interact with potential features.</p><p>Things to keep in mind</p><ul><li><strong>Travel</strong>​ — Allow plenty of time to get to the site and set up.</li><li><strong>Get situated</strong>​ — Find a comfortable spot that allows you to talk to the participant without interrupting their normal routine.</li><li><strong>Interview​ </strong>— Establish trust and learn about what you will be observing. Find out when it will be least disruptive to interrupt and ask questions.</li><li><strong>Observe</strong>​ — It’s a show. You’re watching. Note everything in as much detail as possible. The relevance will be apparent later. Pause to ask questions. Stay out of the way.</li><li><strong>Summarize</strong>​ — Conclude by summarizing what you learned and asking the participant to verify whether your observations were correct.</li></ul><p><strong>Focus group</strong> — Focus groups are the antithesis of ethnography.</p><h3>CHAPTER 6 — Competitive Research</h3><p>You need to know not only who your competitors are from the perspective of the business (that’s generally obvious) but who competes for attention in the minds of your target users.</p><p><strong>SWOT analysis</strong> — Plotting out strengths, weaknesses, opportunities, and threats</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*qztStG1y54CwIrZFUonAnQ.png" /><figcaption>A SWOT analysis organized in a simple grid can help you grasp your competition position.</figcaption></figure><p><strong>Competitive audit</strong> — Once you have identifed a set of competitors and a set of brand attributes, conduct an audit to see how you stack up.</p><p><strong>Brand audit</strong> — Your brand is simply your reputation and those things that signify your identity and reputation to your current and potential customer.</p><p>Here are the questions you need to ask about your brand:</p><ul><li>Attributes</li><li>Value proposition​</li><li>Customer perspective</li></ul><p><strong>Name</strong> — The name is the single most important aspect of a brand.</p><p><strong>Logo </strong>— The logo is simply the illustrative manifestation of your brand, which can take several forms: wordmark, bug, app icon, favicon, etc.</p><p><strong>Usability-testing the competition</strong> — Just what it sounds like. Take those usability testing skills and apply them to someone else’s product or service.</p><h3>CHAPTER 7 — Evaluative Research</h3><p>Evaluation is assessing the merit of your design. It’s the research you never stop doing. There are several ways to go about it, depending on where you are in the project.</p><p><strong>Heuristic analysis</strong> — “Heuristic” in English simply means “based on experience”; a heuristic is a qualitative guideline, an accepted principle of usability. The method is very simple: evaluators (at least two or three, ideally) individually go through a site or application with a checklist of principles in hand and score the site for each one. <a href="http://bkaprt.com/jer/17/">Nielsen’s ten heuristics</a>.</p><p><strong>Usability testing</strong> — Usability is the absolute minimum standard for anything designed to be used by humans. If a design thwarts the intended users who attempt the intended use, that design is a failure from the standpoint of user-centered design. Usability is a quality attribute defned by five components by <a href="http://bkaprt.com/jer/18/">Nielsen</a>.</p><p>Do the cheap tests first and the expensive ones later:</p><ul><li>Start with paper prototypes and sketches</li><li>Look at and test competitor’s products</li><li>Test at every stage (as much as time will allow)</li></ul><ol><li><strong>Preaparing for usability testing</strong></li></ol><p>What you need:</p><ul><li>A plan (What are the tasks that you need to cover? Include the tasks as part of a larger scenario so the user can understand the context.)</li><li>A prototype or sketch.</li><li>Four to eight participants of each target user type based on personas (ideally) or marketing segments.</li><li>A facilitator.</li><li>An observer.</li><li>One or more methods of documentation.</li><li>A timer or watch</li></ul><p><strong>Recruiting</strong> — Recruiting for usability testing is substantively the same as for ethnographic interviews.</p><p><strong>Facilitating </strong>— A good facilitator is personable and patient.</p><p><strong>Observing and documenting </strong>— Even if you are set up to record, it’s very important to have a second person observing the tests and taking notes.</p><p><strong>Eye-tracking </strong>— Eye-tracking measures where someone is looking, how long, and in what direction.</p><p><strong>2. Analyzing and presenting test data</strong></p><p>The aim of usability testing is to identify specific significant problems in order to fix them. The outcome is essentially a ranked punch list with a rationale.</p><h3>CHAPTER 8 — Analysis and Models</h3><p>Analysis involves a few simple steps:</p><ul><li>Closely review the notes.</li><li>Look for interesting behaviors, emotions, actions, and ver- batim quotes.</li><li>Write what you observed on a sticky note (coded to the source, the actual user, so you can trace it back).</li><li>Group the notes on the whiteboard.</li><li>Watch the patterns emerge.</li><li>Rearrange the notes as you continue to assess the patterns</li></ul><p><strong>Affinity diagram</strong> — Clusters of related observations. Each cluster then lets you extract insights and make recommendations.</p><p>Steps:</p><ul><li>Write down observations</li><li>Create groups, noting all stated and implicit goals</li><li>Identify next steps</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*2JyTrqnYWqX81429tr3raA.png" /><figcaption>An affinity diagram helps turn research into evidance-based recommendations</figcaption></figure><p><strong>Creating personas</strong> — A persona is a fictional user archetype — a composite model you create from the data you’ve gathered by talking to real people — that represents a group of needs and behaviors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*FaVnyWRvjpnlaHoKz_J5NA.png" /><figcaption>A persona document should feel like the profile of a real individual while capturing the characteristics and behaviors most relevant to your design decisions</figcaption></figure><p><strong>Mental Models</strong> — A mental model is an internal representation of something in the real world — the sum total of what a person believes about the situation or object at hand, how it functions, and how it’s organized.</p><p>Creating a mental model</p><ul><li>Do user research.</li><li>Make an affinity diagram.</li><li>Place affinity clusters in stacks representing the user’s cognitive space to<br>create the model. These groups will include actions, beliefs, and feelings.</li><li>Group the stacks around the tasks or goals they relate to.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*B_gDQWLk1Jk54p4rfQufRg.png" /><figcaption>Mental model diagram illustrate your user’s thought processes in detail.</figcaption></figure><p><strong>Task Analysis/Workflow</strong> — Task analysis is simply breaking one particular task into the discrete steps required to accomplish it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*KWKvjrTdYbyF1C_qBQkVVQ.png" /><figcaption>This task path for ticket purchase can help identify areas where the user needs specific content and functionality to meet her goal.</figcaption></figure><h3>CHAPTER 9 — Quantitative Research</h3><p>Qualitative research methods such as ethnography and usability testing can get you far, but you still won’t get everything right. Once your web site or application is live, then you have quantitative data to work with.</p><p>Optimizing a design is the chief aim of quantitative research and analysis</p><p><strong>Conversions</strong> — A user is said to convert any time they take a measurable action you’ve defined as a goal of the site. Measuring the conversion rate for each of these will indicate the success of that particular path, but not how each type of conversion matters to the success of the organization itself. That is a business decision.</p><p><strong>Analytics</strong> — Analytics refers to the collection and analysis of data on the actual usage of a website or application to understand how people are using it. Over half of the world’s websites have Google Analytics installed.</p><p>Some of the basic stats to look at include:</p><ul><li>Total number of visits.</li><li>Total number of pageviews.</li><li>Average number of pages per visit.</li><li>Bounce rate (the percentage of people who leave after viewing one page).</li><li>Average time on site.</li><li>Percentage of new visitors</li></ul><p><strong>Split Testing (a.k.a. A/B Testing)</strong> — This method is called split testing because you split your trafic programmatically and randomly serve diﬀerent variations of a page or element on your site to your users.</p><p>How to do it:</p><ul><li>Select your goal.</li><li>Create variations.</li><li>Choose an appropriate start date.</li><li>Run the experiment until you’ve reached a ninety-five percent confidence level.</li><li>Review the data.</li><li>Decide what to do next: stick with the control, switch to the variation, or run more tests</li></ul><h3><strong>Conclusion</strong></h3><p>Form questions. Gather data. Analyze. One sequence, many approaches. Get started (right now!) and encourage you to develop a research habit wherever and however you work.</p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this summary or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bde7053c48a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing UIN Jakarta Academic Information System (AIS) Website with Cognitive Walkthrough…]]></title>
            <link>https://medium.com/@anandatama/usability-testing-uin-jakarta-academic-information-system-ais-website-with-cognitive-walkthrough-e6412100b6da?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6412100b6da</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Sat, 21 Jul 2018 12:13:39 GMT</pubDate>
            <atom:updated>2018-07-26T04:06:29.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I8sjlAwMHRVNqqz4NITP8Q.jpeg" /></figure><h3>Usability Testing UIN Jakarta Academic Information System (AIS) Website with Cognitive Walkthrough Method on Assessment of Lecturers</h3><h3>Abstract</h3><p>An academic information system in the form of a website requires usability as the key to success as well as user requirements for the existence of the website. The purpose of this study is to identify and analyze the problems faced by users and also provide recommendations for improvements to the development of the website to be more user-friendly. In this research, we conducted usability test to UIN Syarif Hidayatullah Jakarta Academic Information System (AIS) website using cognitive walkthrough method on assessment of lecturers menu. The cognitive walkthrough method is a method to test usability where the respondent performs a set of task scenarios to achieve they goal. This usability test includes the components of effectiveness and efficiency. The results of this test show that the completion rate of the task scenario is 100%.</p><p>The average time for the respondent to complete all tasks is 319.5 seconds. Problems faced by users when using AIS is the 2 times button menu loading, the text and icon menu is too small, bullet point is too small, scroll bar is not full moving, pop up save and close the assessment of lecture that disturb, and AIS website view is unresponsive in device mobile. Increase required AIS is once menu loading, text and menu icon enlarged, can open menu through click menu name, scroll bar charging be more responsive, no pop up when save and close the assessment, and reconstruction display for mobile device.</p><p>For full version about this research, you can click the link: <a href="https://tinyurl.com/ycozg9x4"><strong>https://tinyurl.com/ycozg9x4</strong></a></p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this research or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6412100b6da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Info KRL: a Guerrilla UX Case Study]]></title>
            <link>https://uxdesign.cc/info-krl-a-guerrilla-ux-case-study-8a5344cc6cfa?source=rss-b1428b66532f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a5344cc6cfa</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Ananda Vickry Pratama]]></dc:creator>
            <pubDate>Mon, 02 Jul 2018 13:07:01 GMT</pubDate>
            <atom:updated>2018-08-28T11:04:33.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_IStmb5gUo9Hd3KHhraSQ.jpeg" /></figure><p>The purpose of this study is to develop and improve my UX research skill.</p><p>KRL commuter line transportation mode has its own appeal so much in demand people in Indonesia. Even in 2017 reaches <a href="http://www.tribunnews.com/metropolitan/2018/01/04/jumlah-penumpang-krl-sepanjang-2017-melampaui-target">315.811.848</a> passengers. However, for you and me as passengers, sometimes we don’t know the KRL schedule and often times the schedule is not in accordance with Gapeka aka Travel Traffic Chart for some reasons.</p><p>App Info KRL comes as a solution to that problem. I am using Info KRL to help my trip about what’s time the train arrival and where those is being actually (which is a realtime position).</p><p><strong>Objectives</strong></p><ul><li>Discover how passenger use Info KRL to help their trip.</li><li>Find pain point in the user experience.</li><li>Give solutions to solve those pain points.</li></ul><p><strong>Process</strong></p><p>In this case study process, I followed IDEO model for human-centered-design. This process help me to be more directed, structured, and solid in order to achieve goals based on the findings obtained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*wU4m4-nJxU27cL1AR5S-wA.png" /><figcaption>Design Process</figcaption></figure><h3><strong>1. Empathizing with the User</strong></h3><p><strong>Provisional Persona</strong></p><p>The purpose of this section is to create temporary persona from related research about KRL transportation that already exists. This way makes it easier for me to do guerrila usability testing because it already has a rough picture about who’s the user. Based on <a href="http://academicjournal.yarsi.ac.id/index.php/jeba/article/view/379/255">this research</a> in 2017, the most common general characteristics of KRL passengers are: <strong>age 20–30 years, employee</strong>, and <strong>need to work.</strong></p><p><strong>Guerrilla Usability Testing</strong></p><p>By paying attention to the provisional persona, I conduct guerrilla usability testing to identify the pain point of the Info KRL users. In this test, I asked 5 people to do some few task on Info KRL, while I recorded whatever they said, did, even their thought or feel during this usability test.</p><blockquote>Guerrilla usability testing is a rapid, low-cost method of quickly capturing user feedback that involves a User Experience (UX) consultant asking questions about specific areas of a site or application. — <a href="https://www.boxuk.com/insight/blog-posts/unboxing-guerrilla-usability-testing">boxuk</a></blockquote><p>Why only need to with 5 users? It’s about <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/"><strong>iterative design</strong></a><strong> </strong>which that the main reason is be better to distribute budget for user testing across many small test.</p><p>Task:</p><ul><li>Select a travel route.</li><li>Monitoring schedule in real time.</li><li>Create a travel itinerary on the calendar.</li><li>Reply to a message in discussion.</li></ul><p><strong>User Interview Process</strong></p><p>My approach was straightforward to prove the hypothesis. I have the hypothesis that there are still many KRL passengers who do not use any application to help their trip. Then I created a simple script to guide the interviewee to experience about task and give me idea from their behavior.</p><p>Behavior information from interviewee that I gained are:</p><ul><li>4/5 users still knowing the KRL schedule from officer announcement.</li><li>2/5 users ride the KRL to meet friends and the others is go to work.</li></ul><p><strong>Updated Personas</strong></p><p>After gather the information from user interviews, I also to update my provisional personas so that more weight and valid.</p><p>The first is Faisal, who is ride KRL to meet him friends. He use KRL because it’s cheap and fast. However, he still knowing KRL schedule from officer announcement even though he want to quickly reach the destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-yKppgQO6BZsOU1BMDEDg.png" /><figcaption>Provisional Persona 1: Faisal</figcaption></figure><p>The second is Putri, who is ride KRL to go to work because it’s near the workplace. Same as Faisal, she knowing KRL schedule from officer announcement even though she need to get the KRL as soon as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3gJLzArl66Kg0uCa1TLXYQ.png" /><figcaption>Provisional Persona 2: Putri</figcaption></figure><h3><strong>2. Defining the Problem</strong></h3><p><strong>User Research Assimilation</strong></p><p>This section collects the main points of the findings obtained from my user interviews. Then group them into three parts:</p><p>1. What the user <strong>said.</strong></p><p>2. What the user <strong>did.</strong></p><p>3. What the user <strong>thought</strong> or <strong>felt</strong> (non-verbal cues).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XGNXMU1TCixhYLe6_hdQlw.jpeg" /><figcaption>Categorizing Research Insights</figcaption></figure><p><strong>Affinity Mapping</strong></p><p>The main points of insight gained from each user are then sorted by order of affinity by grouping into pain point buckets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8oZSD1mb9tCE60NDeOrA5g.jpeg" /><figcaption>Affinity Mapping</figcaption></figure><p>During this process, I prioritize groups of pain points based on frequency with at least 3 to 5 of users, putting the other on hold for later validation.</p><p>I have <strong>4 pain points </strong>with the following frequency sequence:</p><ul><li><strong>The order of the function menu is less user friendly</strong>: 5 users.</li><li><strong>Did not find the message reply button</strong>: 5 users.</li><li><strong>The station name short code is confused</strong>: 4 users.</li><li><strong>Difficulty changing stations in route selection</strong>: 3 users.</li></ul><h3><strong>3. Ideating and Prototyping</strong></h3><p>The next part is the process of getting deeper into the pain points that have been obtained and ideation to give a solution with prototype.</p><p><strong>Pain point 1: The order of the function menu is less user friendly.</strong></p><p>All users complained about the function menu order. When they open the app, the menu that appears directly is a realtime monitoring. Some users expect the menu that first appears is the search route so they are not confused. In addition, in the search route menu was also realtime monitoring of appropriate the destination station.</p><p><strong>Solution:</strong></p><p>The route search menu is changed to be the first to replace the realtime monitoring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgC-qwkX66AQyXQWud8yOQ.png" /><figcaption>Solution for Pain Point 1</figcaption></figure><p><strong>Pain point 2: Did not find the message reply button.</strong></p><p>All users get frustrated looking for a reply message button in the discussion menu. In the end, they can only try by random clicking, because there is no reply button message.</p><p><strong>Solution:</strong></p><p>Create a reply button in the other person’s message section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*La7MSDjQz12Np4LlRBrrbg.png" /><figcaption>Solution for Pain Poin 2</figcaption></figure><p><strong>Pain point 3: The station name short code are confused.</strong></p><p>4/5 user exhibited very clear frustration and must guessing when faced with KRL schedule information containing station name short codes.</p><p><strong>Solution:</strong></p><p>Create new section function to give additional information about list of KRL station short codes with their full names.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olm4eyphROmCeYxe8r04bA.png" /><figcaption>Solution for Pain Point 3</figcaption></figure><p><strong>Pain point 4: Difficulty changing stations in route selection.</strong></p><p>The three users still have to scroll to select the station even though it’s easier with writing name of the station.</p><p><strong>Solution:</strong></p><p>Replace text ‘search station’ to ‘type station name’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ATkl7UjdrhOD7ZH6HC5Vuw.png" /><figcaption>Solution for Pain Point 4</figcaption></figure><h3>What’s Next?</h3><p>After creating the prototype, the next step is testing and validating a solutions above using the same usability test questions and few task. The target is also similar people background to my initial users.</p><h3>Takeaways</h3><p>This UX case study has been a challenging and rewarding experience for me because for the first time I was conducting a guerrilla research. Not only did I get to exercise my UX skills, I was hoping this case study can useful for reader especially for KRL passengers that also Info KRL app users.</p><p><strong><em>Thank you for reading!</em></strong><em> If you enjoyed this case study or have any feedback, I’d love to hear from you. You can give your response on below this post or email me at anandapratama170199@gmail.com</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a5344cc6cfa" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/info-krl-a-guerrilla-ux-case-study-8a5344cc6cfa">Info KRL: a Guerrilla UX Case Study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>