<?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 Azie Melasari on Medium]]></title>
        <description><![CDATA[Stories by Azie Melasari on Medium]]></description>
        <link>https://medium.com/@aziemelasari?source=rss-e7bb8a4465e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AjYoQnbnpgM3RnItQVHuPg.png</url>
            <title>Stories by Azie Melasari on Medium</title>
            <link>https://medium.com/@aziemelasari?source=rss-e7bb8a4465e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:35:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aziemelasari/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[UI/UX Case Study: A POS Restaurant App for Efficient Order Management]]></title>
            <link>https://medium.com/@aziemelasari/ui-ux-case-study-a-pos-restaurant-app-for-efficient-order-management-2044b5151926?source=rss-e7bb8a4465e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2044b5151926</guid>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[pos-app]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Azie Melasari]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 07:08:14 GMT</pubDate>
            <atom:updated>2024-01-24T07:08:14.102Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kep-kBaIyPNjJALqHcAirQ.png" /></figure><p>Hey Folks! 👋</p><p>I’m thrilled to share my latest UI/UX design case study, a culmination of my work during the Dibimbing Batch 21 UI/UX Design program. In this project, I’ll be introducing Geena, a POS WebApp designed to revolutionize order management in the restaurant industry.</p><h3>Overview</h3><p>The food and beverage industry has seen a notable move towards digital order management solutions in recent years. With the growing need for efficient restaurant operations, there is a demand for a user-friendly Point of Sale (POS) Restaurant App. Hence, I intend to develop a platform called Geena POS. This case study seeks to delve into the UI/UX aspects of such an app to improve order management processes in restaurants.</p><blockquote>Project: Geena POS<br>Timeline: 3 Weeks<br>Tools: Figma<br>Role: UI/UX Designer</blockquote><h3>The Process</h3><p>When creating products, it is essential to have a framework in place. For this particular case, I will be utilizing the design thinking framework which includes empathy, define, ideation, prototype, and test.</p><h3>Empathize</h3><p>At this stage, I’ll undertake 3 primary tasks: Planning the Research, Establishing Research guidelines, and Conducting the Research. This initial process is aimed at identifying the issues with the POS App.</p><h4>1. Planning the research</h4><h4>Objective</h4><p>I aim to investigate and comprehend the cashier’s behavior when creating orders in a restaurant to develop effective strategies for order management. I am conducting an in-depth analysis to identify the root causes of any challenges faced in this process. The research objectives are as follows:</p><ol><li>Understand the behavior of cashier/restaurant owner when generating orders.</li><li>Develop a user-friendly digital product that is beneficial for restaurant owners.</li><li>Gain insights into the needs and challenges encountered by cashiers/restaurant owners while using the POS Restaurant App.</li></ol><h4>Methodology</h4><p>Qualitative (Desk Research): Desk research aims to enhance comprehension of creating a digital product capable of efficiently managing restaurant orders.</p><p>Qualitative (In-depth Interview): This method is employed to gather insights into user behavior, needs, challenges, and expectations while utilizing the application.</p><h4>Sample Specification</h4><ul><li>Having experience as a cashier</li><li>Business Owners</li><li>Nationwide</li><li>Women/Men</li><li>Aged 18–60 years</li></ul><h4>Key Information Areas</h4><p>Key information areas are essential topics that we aim to investigate in this research. These key information areas will serve as the foundation for generating a list of questions:</p><ol><li>User Profile<br>2. General behavior of cashier staff when using the POS Restaurant App</li></ol><h4>2. Making Research guideline</h4><p>Upon finalizing the research plan, I have crafted a comprehensive research guide for executing both Desk Research and Surveys. This guide encompasses an introduction, clearly outlines the survey’s purpose for participants, presents a series of questions aligned with key information areas, and concludes the survey process.</p><h4>3. Conducting the Research</h4><p>During this stage, I am delving into user sentiments regarding the utilization of the POS App. The research process is conducted online through Google Meet.</p><h3>Define</h3><h4>Research Findings</h4><p>Following the completion of interviews with all respondents, the insights gathered were analyzed using the thematic method, employing affinity diagrams. This approach, commonly used in qualitative research, allows for the identification of patterns and themes within the collected data, facilitating a comprehensive understanding of the information obtained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlAr-T8M3ORSMtI5n_cC2w.png" /></figure><h4>User Persona</h4><p>A user persona is a fictional character crafted to embody the characteristics and behaviors of the target users of a product. These personas serve as a tool to concentrate on recognizing and addressing the problems encountered by users, fostering a more user-centric approach in product development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hM2UcJhdC3swudUA353UNQ.png" /></figure><h4>Customer Journey Map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fIH6YyJzHBt8J6aX_rR67Q.png" /></figure><h4>Problems</h4><p>Based on the results of the analysis using affinity diagrams and customer journey maps, it was found 3 main problems faced by users.</p><ol><li><strong>Outdated Application Appearance:<br></strong>The visual design of the application lacks a modern and aesthetically pleasing look. This deficiency may impact user engagement and perception, as a contemporary and visually appealing interface is often associated with user-friendly and up-to-date technology.</li><li><strong>Manual Table Availability Check:<br></strong>Users are required to manually check the availability of tables. This process consumes a significant amount of time and effort, resulting in inefficiency. Implementing an automated system for table availability could streamline this task.</li><li><strong>Limited Payment Methods:<br></strong>The application offers only a few payment methods, limiting user choices. There is a lack of alternative options such as Ovo, QRIS, and others, which may restrict user convenience and satisfaction. Exploring additional payment options could enhance the overall user experience.</li></ol><h3>Ideation</h3><h4>User Flow</h4><p>User flow is used to describe the overall flow of users using the product. The following is the user flow of the activities Login, Book Table, Choose Menu, Payment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F0iWksj6vEC4vjKKa8ed5g.png" /></figure><h4>Information Architecture</h4><p>Information Architecture is a method used to arrange all flow, content, and design requirements in an application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lku-Jdajefrgxst4T75KSw.png" /></figure><h4>Prioritization Matrix</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VH9c6Z3xtpjEnr27icmQzg.png" /></figure><h4>Wireframe</h4><p>Before I created a detailed design, I made a simple outline called a wireframe. It helped me plan the basic structure and layout of the design before adding more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRESLtR7zVvqnLYY2R0ACA.png" /></figure><h4>Design System</h4><p>Following the creation of the wireframe, I began developing a style guide. This guide helps identify elements such as typography, color scheme, buttons, and other design components, ensuring a consistent and cohesive visual appearance throughout the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EJfTe1lOZbLEPLjIoB0liw.png" /></figure><h4>Mockup All Screen</h4><p>After completing the wireframe, I moved on to the next step, where I created a high-fidelity design. The following is the outcome of the UI design that I’ve developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*38fFx6el6MnV-vVyU_HwQQ.png" /></figure><h4>Prototype</h4><p>Following the completion of the empathize, define, and ideate stages, I proceeded to create a Figma prototype. This prototype comprises 16 screens, illustrating the interactive and visual aspects of the design concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QH6Za0_V3s-ctEiPHqzawA.png" /></figure><h3>Test</h3><h4>Usability Testing</h4><p>The final stage involves conducting usability testing. The primary objective of this User Testing (UT) is to gather valuable insights into user behavior while placing orders through the Geena POS WebApp. This study is designed to comprehensively understand user types, their behaviors, and the specific needs and challenges they encounter when interacting with the Geena POS WebApp.</p><p>Enclosed are the outcomes of the Usability Testing I conducted, with the hope that they prove beneficial. For access to the full Usability Testing report, please follow this link: [<a href="https://www.canva.com/design/DAF5rbBWZA4/EzanKxbBhKfnbNmPpdYoyA/edit?utm_content=DAF5rbBWZA4&amp;utm_campaign=designshare&amp;utm_medium=link2&amp;utm_source=sharebutton">Link to Usability Testing Results</a>].</p><h4>Summary Insight + Recommendation</h4><ol><li><strong>Font Size for Table Numbers on the Order Menu Page:<br></strong>The font size for table numbers on the Order Menu page is too small, making it difficult for users to be aware of their table numbers.</li><li><strong>Absence of Cancel Button on the Payment Page:<br></strong>There is no cancel button on the Payment page, which could assist users in canceling or exiting the payment process.</li></ol><h4>Result after feedback</h4><p>After doing the UT process, I made design improvements based on the recommendations for each task.</p><ol><li>Font Size for Table Numbers on the Order Menu Page</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-oytG6xW6PLh_hCFy8EmA.png" /></figure><p>2. Absence of Cancel Button on the Payment Page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ua8eH-DkByRE4SmXW1Idaw.png" /></figure><h3>Conclusion</h3><p>By completing this research, I have acquired valuable insights into the intricacies of effective research planning, the functionality of qualitative research methods, strategies for recruiting respondents, and the significance of active listening during interviews. Your engagement in reading is highly appreciated!</p><p>Thank you for dedicating time to review this case study. Your comments are welcomed, and I trust that the findings shared here will be valuable for anyone interested in the realm of UI/UX design.</p><h3>Appendix</h3><ul><li><a href="https://www.figma.com/file/Ht27dIOILxNywScpeEIlRh/Final-Project_UX?type=whiteboard&amp;node-id=0%3A1&amp;t=qUBUQGdKgfYHxnHn-1">Conduct Research</a></li><li><a href="https://www.canva.com/design/DAF5rbBWZA4/EzanKxbBhKfnbNmPpdYoyA/edit?utm_content=DAF5rbBWZA4&amp;utm_campaign=designshare&amp;utm_medium=link2&amp;utm_source=sharebutton">Usability Testing</a></li><li><a href="https://www.figma.com/file/33NXa6hLzk6qeShiTvU5b0/Final-Project_UI?type=design&amp;node-id=3%3A23856&amp;mode=design&amp;t=cOPsSsGoglqaPpaZ-1">Wireframe &amp; HIFI</a></li><li><a href="https://www.figma.com/proto/uBxW3x7I6y8209Mh8btGx1/Final-Project_Prototype?page-id=0%3A1&amp;type=design&amp;node-id=101-4663&amp;viewport=567%2C-353%2C0.08&amp;t=OKMqv7n1YJXJI9o0-1&amp;scaling=min-zoom&amp;starting-point-node-id=101%3A4663&amp;mode=design">Prototype</a></li></ul><p>Let’s connect with me on <a href="https://www.instagram.com/aziemelasari/"><em>Instagram</em></a><em> </em><a href="https://dribbble.com/aziemelasari"><em>Dribbble</em></a><em> </em>👀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2044b5151926" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI/UX Case Study — Understand user behavior in using the Grab feature in OVO]]></title>
            <link>https://medium.com/@aziemelasari/ui-ux-case-study-understand-user-behavior-in-using-the-grab-feature-in-ovo-386fe5c72722?source=rss-e7bb8a4465e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/386fe5c72722</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ovo]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Azie Melasari]]></dc:creator>
            <pubDate>Sat, 11 Nov 2023 12:03:11 GMT</pubDate>
            <atom:updated>2023-11-23T11:42:48.476Z</atom:updated>
            <content:encoded><![CDATA[<h3>UI/UX Case Study — Understand user behavior in using the Grab feature in OVO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5p00vhAghJcpZ4IkNjIfyg.png" /></figure><p>Greetings, Everyone! 👋</p><p>Excited to present my upcoming UI/UX Design case study. This represents a unique opportunity for me to share the knowledge and insights I’ve gained during my studies at Dibimbing Batch 21 UI/UX Design. My goal is that this case study becomes a source of valuable insights and inspiration for everyone out there.</p><h3>Overview</h3><p>OVO is a payment system service application that facilitates cashless transactions and provides access to various digital financial products and services through collaborations with selected partners.</p><p>Recently, OVO introduced a new feature, the Grab feature. This feature serves the same function as the standalone Grab application, with the distinction that users are still required to open the Grab app separately and cannot access it directly within the OVO app. We will explore the efficiency of the Grab feature within the OVO application from a user perspective.</p><blockquote>Project: OVO Mobile App<br>Timeline: 3 Weeks<br>Tools: Figma<br>Role: UI/UX Designer</blockquote><h3>The Process</h3><p>When creating products, it is essential to employ a structured framework to develop suitable and effective solutions. In this case study, I will be utilizing the design thinking framework, which comprises empathy, definition, ideation, prototyping, and testing, to guide the product development process.</p><h3>Empathize</h3><p>In this phase, we will undertake three key tasks: planning the research, creating research guidelines, and conducting the actual research. This initial process serves as the stage for identifying issues with the Grab feature in the OVO Mobile App.</p><h4>1. Planning the research</h4><h4>Objective</h4><p>Our objective is to investigate and explore the motivations, habits, pain points, and barriers associated with using the Grab feature within the OVO App. We aim to conduct a thorough analysis of the problem to uncover its root causes. The research objectives are as follows:</p><ul><li>Understand the types (segments) of users who utilize the Grab feature in the OVO application.</li><li>Examine user behavior when engaging with the Grab feature.</li><li>Identify user needs and challenges encountered while using the Grab feature.</li></ul><h4>Methodology</h4><p>In this research, I employed the Qualitative Method (In-depth Interviews).</p><h4>Sample Specification</h4><ul><li>Active OVO user (has engaged in Grab features within the OVO app at least 3 times in the last month).</li><li>Nationwide scope.</li><li>Female/male.</li><li>Age range: 18–54 years old.</li></ul><h4>Key Information Areas</h4><p>Key information areas represent the primary subjects we aim to investigate in this research. These areas will serve as the foundation for generating a list of questions. They include:</p><ul><li>User Profile</li><li>General behavior when utilizing the Grab feature within the OVO application</li></ul><h4>2. Making Research guideline</h4><p>Following the completion of the research plan, I developed a comprehensive research guideline for conducting In-depth Interviews (IDI). This guide encompasses an introduction, clarifies the purpose of the interview for the participants, provides a set of questions aligned with key information areas, and concludes the interview process.</p><h4>3. Conducting the Research</h4><p>During this phase, I investigate insights into the user’s perspectives regarding the use of the OVO application. The research is conducted online through Google Meet.</p><h3>Define</h3><h4>Research Findings</h4><p>Following the completion of all respondent interviews, the insights gathered underwent analysis using a thematic approach, employing affinity diagrams. The thematic method serves as a valuable technique for scrutinizing data derived from qualitative research, facilitating the identification of patterns and the extraction of themes from the collected information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-zgrbIH5pVcGMEqXtF4DA.png" /></figure><h4>User Persona</h4><p>A user persona is a fictional character that embodies the characteristics and behaviors of the target user for a product. Utilizing user personas assists us in concentrating on recognizing and addressing the challenges faced by users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WO1JsPt7Ir83mzUZhkBFQ.png" /></figure><h4>Customer Journey Map</h4><p>A user persona is a fictional character that embodies the characteristics of the target user for a product. These personas serve as valuable tools, guiding our efforts in pinpointing and addressing the challenges encountered by users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SsUMduaBX4QR7Fag_aWn_A.png" /></figure><h4>Problems</h4><p>Through the analysis employing affinity diagrams and customer journey maps, three primary issues were identified, impacting users’ experiences.</p><ol><li><strong>The appearance of the application is not modern<br></strong>The visual design of the application lacks a contemporary and aesthetically pleasing look. This may impact user engagement and perception, as a modern and visually appealing interface is often associated with user-friendly and up-to-date technology.</li><li><strong>Unclear or hidden placement of the Grab feature may cause confusion.<br></strong>Users may face confusion if the Grab feature is not easily accessible or its location is not intuitively placed within the application. The clarity in feature placement is crucial for a seamless user experience, ensuring that users can quickly locate and use the desired functionality without unnecessary effort or guesswork.</li><li><strong>Opening two apps may cause inconvenience and confusion.<br></strong>The requirement to open two separate applications introduces inconvenience and potential confusion for users. Juggling between apps can disrupt the user flow and lead to frustration. Streamlining processes within a single app can significantly enhance user convenience and contribute to a more efficient and enjoyable experience.</li></ol><h3>Ideation</h3><h4>User Flow</h4><p>The user flow illustrates the sequence of actions users take while interacting with the product. The following outlines the user flow for the activities of Registration, accessing the GrabBike feature, navigating the Promo Page, and booking a driver.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZP9UOgTexY0ic2LB57m6kg.png" /></figure><h4>Information Architecture</h4><p>Information Architecture is a methodology employed to organize the flow, content, and design requirements within an application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghL8LAPWcgxnMoMQU0_X-g.png" /></figure><h4>Wireframe</h4><p>Prior to creating a mockup, I crafted a wireframe to establish the fundamental structure and design concept that I would be implementing. Below is the wireframe representing the redesigned GrabBike feature within the OVO mobile application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UFXTbazPFyrxPKRoj0dXA.png" /></figure><h4>Design System</h4><p>Following the wireframing phase, we initiated the development of a style guide to define the typography and color palette, ensuring a visual consistency that mirrors the aesthetics of the OVO application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VozfI_2ECR6_GCr7tWksA.png" /></figure><h4>Mockup</h4><p>A mock-up serves as a top-level depiction of a product design, incorporating various elements such as styles, typography, colors, and more. Following multiple stages of research and ideation, we present a mockup design for the GrabBike feature within the OVO mobile application.</p><p>Here’s a visual comparison of the Grab feature in OVO, emphasizing changes made to both the Home Page and the GrabBike Page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xG_OywtNTZE1z6Yd6JJ6Rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2z8BoDrcgplZ0ujXp-xJZA.png" /></figure><h4>Mockup All Screen</h4><p>In the previous step, I crafted a wireframe, and subsequently, I proceeded to develop a high-fidelity design. Presented below are the outcomes of the UI design that I’ve generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqXstu9_sakNo7u1x9XNmw.png" /></figure><h4>Prototype</h4><p>Following the completion of the empathize, define, and ideate stages, I developed a Figma prototype consisting of 14 screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCBJlMfe1BOYJWTs6hXarg.png" /><figcaption>Note: The prototype link is in the Appendix</figcaption></figure><h3>Test</h3><h4>Usability Testing (UT)</h4><p>The last step is usability testing. The purpose of this Usability Testing (UT) is to gain insights into user behavior regarding the Grab feature in the OVO application. This study aims to understand the types of users, their behavior, and their needs and challenges when engaging with the Grab feature.</p><h4>Task given</h4><p>I asked the user to perform the following tasks. I do this by giving them scenarios, such as “Imagine that you are going to use grab feature in OVO app, what would you do in the app to access the grab feature?</p><ol><li>Initiate a Grab transaction and complete the payment process.</li><li>Navigate through the Grab feature to explore available options and settings.</li><li>Respond to a simulated challenge or issue while using the Grab feature.</li></ol><h4>Summary Insight + Recommendation</h4><ol><li>Pop-up for Grab x OVO are unnecessary as the GrabBike menu already features a NEW label. <strong>(Medium)</strong></li><li>Simplify payment methods on GrabBike by exclusively using OVO; additional options are unnecessary as GrabBike is integrated into OVO. <strong>(Medium)</strong></li><li>Improve the GrabBike search experience by incorporating a countdown to prompt users to wait until a specified time. <strong>(Important)</strong></li></ol><h4>Result after feedback</h4><p>After doing the UT process, I made design improvements based on the recommendations for each task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fK5C1gobxilqX8Qe8Ju0Q.png" /><figcaption>Pop-up for Grab x OVO are unnecessary as the GrabBike menu already features a NEW label</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7a3oxuNrrFkL7DDAhyPjA.png" /><figcaption>Simplify payment methods on GrabBike by exclusively using OVO, additional options are unnecessary as GrabBike is integrated into OVO</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bgY8chZP2QyWH3_jvEvOgQ.png" /><figcaption>Improve the GrabBike search experience by incorporating a countdown to prompt users to wait until a specified time.(Important)</figcaption></figure><h3>Conclusion</h3><p>Through the completion of this research, I gained valuable insights into effective research planning, the functionality of qualitative research methods, respondent recruitment strategies, and the importance of attentive listening during interviews. Your engagement in reading is appreciated!</p><p>Thank you for taking the time to read this case study. Your comments are welcome, and I hope that the findings presented here prove beneficial for everyone interested in UI/UX design and the integration of the GrabBike feature into the OVO mobile app.</p><h3>Appendix</h3><ul><li><a href="https://www.figma.com/file/wSGFwN4sqZpTiHfxXfZttJ/User-Flow?type=whiteboard&amp;node-id=0%3A1&amp;t=pQYp7GqH0mZ9OntX-1">User Flow</a></li><li><a href="https://www.figma.com/file/SVN5BIgerHZ42jz8oeUVjs/Conduct-Research?type=whiteboard&amp;node-id=0%3A1&amp;t=1B0rrnCqHNwZZN2W-1">Conduct Research</a></li><li><a href="https://www.figma.com/proto/zfMvcKCRThjX7Sb8HOjRYK/Azie-Melasari_Day22_UIUX21?page-id=2%3A10&amp;type=design&amp;node-id=2-440&amp;viewport=1046%2C321%2C0.18&amp;t=C4fxPYA7W7YdvssF-1&amp;scaling=scale-down&amp;starting-point-node-id=2%3A440&amp;mode=design">Prototype</a></li></ul><p>Let’s connect with me on <a href="https://www.instagram.com/aziemelasari/"><em>Instagram</em></a><em> </em><a href="https://dribbble.com/aziemelasari"><em>Dribbble</em></a><em> </em>👀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=386fe5c72722" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Writing Case Study — Copy Writing Improvement in KAI Access Mobile App]]></title>
            <link>https://medium.com/@aziemelasari/ux-writing-case-study-copy-writing-improvement-in-kai-access-mobile-app-23da1b00cbd3?source=rss-e7bb8a4465e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/23da1b00cbd3</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Azie Melasari]]></dc:creator>
            <pubDate>Fri, 27 Oct 2023 18:36:51 GMT</pubDate>
            <atom:updated>2023-10-27T18:53:18.990Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Writing Case Study — Copy Writing Improvement in KAI Access Mobile App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LPgVqdbk43FpK2F39e44pw.png" /></figure><p>Hello everyone! 👋</p><p>I’m Azie Melasari, and I’m thrilled to present my inaugural UX Writing case study. This marks a fantastic chance to share the expertise and insights I’ve gained during my time at <a href="https://dibimbing.id/">dibimbing.id</a> Bootcamp Batch 21 UI/UX Design. My aspiration is that these case studies will offer valuable insights and serve as an inspiration for UX writers and all those intrigued by the world of UX writing. Let’s encourage more research and data-driven decision-making in our field.</p><blockquote>Project Name: KAI Acess Mobile App<br>Date: October 2023<br>Role: UX Writer</blockquote><h4>Introduction</h4><p>KAI Access Mobile App, meticulously crafted for a seamless journey through the Indonesian railway system, ensures your travels are smooth and convenient. It simplifies planning your train trips, booking tickets, and accessing critical information such as schedules and platform details — all easily accessible at your fingertips. It’s your ideal companion for a worry-free train adventure in Indonesia.</p><p>Incidentally, I’ve taken up a UX Copy Improvement assignment as part of my <a href="https://dibimbing.id/">dibimbing.id</a> bootcamp coursework, where I’ve chosen to refine the copy for the KAI Access mobile app. Before diving into the details, allow me to provide a brief insight into the brand voice of the KAI Access mobile app.</p><h4>Brand Voice</h4><p>The brand voice of the KAI Access Mobile App is designed around three essential characteristics: formality, informativeness, and trustworthiness. These elements work together to create a reliable and professional image that provides valuable information to our users as they navigate their railway journeys in Indonesia. Let’s explore how each category contributes to our communication.</p><ul><li><strong>Formal</strong>: The formal tone is used when we want to show respect and professionalism in our communication. It’s employed in official announcements, legal information, and customer service interactions to build trust and credibility.</li><li><strong>Informative</strong>: We are committed to being informative. Our content is clear and concise, ensuring users have the information they need about train schedules, booking, and travel guidelines.</li><li><strong>Trusted</strong>: The trusted category reflects our dedication to reliability and credibility. We want users to have faith in the accuracy of our information and services. This is achieved through transparency and dependability, ensuring we consistently meet user expectations.</li></ul><h4>Problem</h4><p>During my initial exploration of this app, I sensed a need for improvement, particularly in the realm of copywriting. Upon reaching the Account Screen, Face Recognition Screen, and Error/No Internet Screen, it became evident that several pieces of copy lacked clarity and warranted revision. This prompted me to shift my attention towards a detailed examination and deconstruction of the copy found on these three screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2HIB4Z2Tciuo-cQ4cGvYQ.png" /></figure><h4>Research Objectives</h4><p>Enhancing user experiences, boosting engagement, and driving desired actions — all achievable through the power of effective copy. By focusing on clarity, consistency, persuasiveness, and relevance, well-crafted copy becomes a valuable asset for conveying messages and accomplishing your business objectives.</p><h4>Research Method</h4><p>In this case study, my primary focus will be on UX Writing within three distinct screens: the “Account Screen,” “Face Recognition Screen,” and the “Error/No Internet Screen” of the KAI Access Mobile App. To gather valuable insights, I have employed a qualitative research method, specifically conducting in-depth interviews.</p><p><strong>Qualitative—In—depth Interviews</strong>: This research approach allows us to delve into the intricacies of user behavior, their needs, challenges, and expectations while using the application. Additionally, we aim to assess and refine the innovations we plan to introduce and gain a deeper understanding of user behavior and requirements as they interact with the KAI Access Mobile App.</p><h4>Respondent Requirements</h4><p>The requirements of the 5 respondents for this research are:</p><ul><li>Nationwide</li><li>Women/Man</li><li>18–60 year old</li><li>Have experienced use the KAI Acess Mobile App</li></ul><h4>Main Findings</h4><p>We delve into user needs to enhance their experience and refine our copywriting by gaining insights into their perceptions and expectations.</p><h4>Insight Gathered</h4><p>Based on the insights gathered, several pain points have been identified:</p><ul><li><strong>Forced and Intimidating Language</strong>: The use of language comes across as too forced and aggressive, creating an unwelcoming tone.</li><li><strong>Lack of Friendliness:</strong> The language used is excessively stern, lacking the friendly and approachable tone desired.</li><li><strong>Excessive Wordiness</strong>: The copy is unnecessarily long and verbose, especially when providing Face Recognition details.</li><li><strong>Clumsy and Unclear Messaging</strong>: The copy is convoluted and unclear, leading to confusion among users.</li></ul><h4>Solution</h4><p>The solution lies in crafting copy that is not only easier to comprehend but also more efficient and user-friendly. This can be achieved by closely considering the context for clarity and consistency on the Account Screen, Face Recognition Screen, and Error/No Internet Screen.</p><h4>Results</h4><p>Here’s a before-and-after visualization of the KAI Access Mobile App, focusing on the Account Screen, Face Recognition Screen, and Error/No Internet Screen, highlighting the improvements made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O0PIpRevHhhaguhiHcrQQg.png" /><figcaption>Account Screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVh8BabyrOueuk1PUD0jVw.png" /><figcaption>Face Recognition</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0drz2xUSdOgFSTEDSlfLw.png" /><figcaption>Error/No Internet</figcaption></figure><h4>After Improvement</h4><p>By implementing these copywriting changes, the application will create a more user-friendly and approachable impression. It adopts a casual tone while maintaining its user-friendliness.</p><h4>Conclusion</h4><p>And that wraps up this article! Throughout my research, I’ve had an incredible learning journey. I’ve discovered the significance of copy for a brand and the art of critically assessing it. What’s even more fascinating is realizing that copy isn’t just about “writing”; it’s about creating an experience. It’s about making it effortless for users to navigate our application by engaging with the words we choose.</p><p>So, that’s all from me. This article may not be flawless, but I’d greatly appreciate your feedback.<br>Thank you!👋</p><p>Let’s connect with me on <a href="https://www.instagram.com/aziemelasari/"><em>Instagram</em></a><em> </em><a href="https://dribbble.com/aziemelasari"><em>Dribbble</em></a><em> </em>👀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23da1b00cbd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>