<?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 Dheavira Hadina Putri on Medium]]></title>
        <description><![CDATA[Stories by Dheavira Hadina Putri on Medium]]></description>
        <link>https://medium.com/@dheavirahp?source=rss-705a7a592311------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*30YhYN_8iRTO7uSM.jpg</url>
            <title>Stories by Dheavira Hadina Putri on Medium</title>
            <link>https://medium.com/@dheavirahp?source=rss-705a7a592311------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:40:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dheavirahp/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[Explore KRL Access 2021 - UX Case Study]]></title>
            <link>https://dheavirahp.medium.com/explore-krl-access-2021-ux-case-study-6451ac8feae0?source=rss-705a7a592311------2</link>
            <guid isPermaLink="false">https://medium.com/p/6451ac8feae0</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Dheavira Hadina Putri]]></dc:creator>
            <pubDate>Thu, 27 May 2021 08:55:53 GMT</pubDate>
            <atom:updated>2021-05-27T08:59:03.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iCFzOT99l_3sIL2HCWMIPA.png" /></figure><blockquote>Disclaimer: The purpose of this case study is a improvement of the my UX Skill and some my problem when I used KRL Access application. I did this project individually around 10 days covering the end-to-end process from conducting initial research until prototyping.</blockquote><h3>Problem Brief</h3><p>Almost everyone in Jakarta knows, Commuter Line is one of the most widely used public transportation because of the route coverage for the Jabodetabek area. Data from the Media Indonesia said that until March 2021, the number of passengers each day reached more than <strong>300 thousand</strong>. Under company PT. Kereta Commuter Indonesia, KRL Access is an application made to guide passengers when traveling with Commuter Line. With train scheduling as the main features in this application which is very helpful for passenger.</p><p>In 2021, KRL Access has just released the latest version with total changes and the addition of several features such as checking balances via nfc. But from this new application, many users complained about KRL Access in the Google play store review.</p><p>This was the main notion of the challenge, s<em>o how can we minimize those gaps?</em></p><h3>Design Process</h3><p>In making this case study, we need an outline of the design process to solve the problem. First, I conducted self exploration and user review to dig and get deeper information about the existing problem. Then, I started to define the problem and synthesizeit into some key insights to be focused on. Finally, the prototype is based on the results of the research that has been done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SV1yQe6A8kRhjtDuoxTabg.png" /><figcaption>Design Process Overview</figcaption></figure><h3>Stage 1 - Emphatize</h3><p>First, I tried to define the problem by trying to <strong>self explore</strong> the application. To validate this problem, I ended up looking for <strong>user reviews</strong> of this application on Google Play Store because they are potential users who can provide information about problems in the application. For Information, KRL Access is a #7 Top Free in Maps &amp; Navigation Apps in Google Play Store. Update in 27 April 2021, and now it has a rating 3.5 of 5.0. Here are some review from the KRL Access user’s answer that I got from Google Playstore:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gt3KRPoNbqIIe9rzy8Ds7g.png" /><figcaption>User review in Google Playstore</figcaption></figure><p>Then I also wanted to dig deeper information about their motivations &amp; pain points that users experience from using a mobile app to guide their way when using the Commuter Line. Therefore, I conducted <strong>user interview</strong> (online) with <strong>5 participans. </strong>The criteria for participants are:</p><ul><li>🧑‍🤝‍🧑Who: <strong>Users who use KRL Access or similar direction guidance applications</strong></li><li>⌚When: <strong>Within the last 3 months</strong></li><li>📍Where: <strong>Live in Jabodetabek area</strong></li></ul><p>Research Questions:</p><ul><li>What are the<strong> user’s biggest problem</strong> when traveling with Commuter Line using a mobile app?</li><li>What are the <strong>user’s motivations </strong>when traveling with Commuter Line using a mobile app?</li></ul><p>Based on the interview that I got, I found that 3 most dominant problems. Here are some quotes from the participant’s answer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-QlqrSoWoEVeEh4MgZXow.png" /></figure><p>From the all of research and interview result, I feel that I know more about the scope and core of the problems that exist in this application.</p><h3>Stage 2 - Define</h3><p>Based on the empathize stage, I classify and also group the problems using an affinity diagram. The problems are classified according to their similarity. Problems are classified based on similarity in context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7s0EfR6JTVdQV_R_JiHzw.png" /></figure><h4><strong>Pain Points</strong></h4><p>I conclude some pain points related to the pattern of problems that have been grouped in the affinity diagram.</p><ol><li><strong>Worried of getting wrong information</strong> when using a train</li><li><strong>Innacurate information and schedulling</strong> of train</li><li><strong>Need to top-up </strong>and checking balance multitrip card on app</li></ol><h4>Persona</h4><p>Based on the research and the pain points, I try to make persona can be concluded to present passenger who feel confused when using KRL Access. I made 2 user personas<strong>, Regular </strong>and <strong>occasional</strong> user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*mp5m_E15qtow5jTcIasAyA.png" /><figcaption>Persona 1 - Regular Us</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*3XfjO-iNgyIl2ci7ZPnuTg.png" /><figcaption>Persona 2 - Occasional User</figcaption></figure><h3>Stage 3 - Ideate</h3><h4>How Might We</h4><p>Based on the define stage, I used How Might We to defining insights then capture an idea the solution possible based on the pain points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDNs8VWcJd4AH8I6gt8w5A.png" /><figcaption>How Might We</figcaption></figure><h4>Information Architecture</h4><p>Information architecture is created as a visual representation of the infrastructure, features, and hierarchies that outline the product so that users can understand it easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eW8SzJTWtvCbTxNiph72eg.png" /><figcaption>Information Architecture</figcaption></figure><h4>Mood Board</h4><p>Explore the design inspirations in the context of user interfaces, typography, layout, color, etc with Mood boards. It helps to visualize the concept and trigger creativity before the prototype stage.</p><p>Keyword: <strong>Minimalist</strong>, <strong>Clean</strong>, and <strong>Red</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aThgMkFdRNtqLfN72KF4Sw.png" /><figcaption>Mood Board from Dribbble✨</figcaption></figure><h3>Stage 4 - Prototype</h3><h4>Wireframe</h4><p>Before continue to develop through the redesign of KRL Access, I try to make wireframe based on the ideate stage to see the overall flows in app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*TSrXeZqmUTIdqWBGNVaV0w.png" /><figcaption>Wireframe</figcaption></figure><h4>Design System</h4><p>I tried to make a design system for making high-fidelity to redesign KRL Access. For the color palette, the color is similar to the original KRL Access version, but the dominant color has been changed to white to make it cleaner than the current version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O6H6ePZ_z1mIBwzhTYabSg.png" /><figcaption>Design System</figcaption></figure><h4>High - Fidelity Design</h4><p>Based on the proposed solutions, I tried to crafting all component into high-fidelity design, then create interaction and interactive prototyping using <strong>Figma</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFMNXTNby3TVd3NeBZR6_g.png" /><figcaption>High - Fidelity Design (Comparison with Existing Design)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UPKxTDt9-mdWlINgft6DwQ.png" /><figcaption>High - Fidelity Design (New Features)</figcaption></figure><h4><strong>Final Prototype</strong></h4><p>You can check the prototype <a href="https://www.figma.com/proto/k56D74jSxrNwFXeZuZ3kHD/Portfolio-21?page-id=116%3A1164&amp;node-id=116%3A1165&amp;viewport=537%2C255%2C0.050673168152570724&amp;scaling=scale-down"><strong>here</strong></a><em>.</em></p><h4><strong>Conclusion</strong></h4><p>Here are a few keypoint that I learn about sprint design and doing research and process it in less than 5 days based on my experience doing in KRL access:</p><ul><li><strong>Enable additional devices on the smartphone properly</strong>, such as NFC and GPS that are already embedded in the application. should be used by making application features that are more helpful to users.</li><li><strong>Do some research and interviews with users</strong> to make sure that you distinguish between features that are really needed, then supporting features and features that are not needed. Then create the most accessible flow for the main features that users will frequently use.</li></ul><p>Thank you for reading my UX Case Study. Feel free to give your claps 👏🏻 or leave your comment 💬 if you enjoyed read this. I’m also open for further discussion😉</p><p><a href="https://www.linkedin.com/in/dheaviraputri/"><strong>Linkedin </strong></a>| <a href="https://dribbble.com/dheavirahp"><strong>Dribbble</strong></a><br>📧Email: <a href="http://dheavirahadinaputri@gmail.com/"><strong>dheavirahadinaputri@gmail.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6451ac8feae0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding an UX Research Flow: How transform traditional business into digital]]></title>
            <link>https://dheavirahp.medium.com/understanding-an-ux-research-flow-how-transform-traditional-business-into-digital-4c1bee0ef915?source=rss-705a7a592311------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c1bee0ef915</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[assessment]]></category>
            <dc:creator><![CDATA[Dheavira Hadina Putri]]></dc:creator>
            <pubDate>Wed, 16 Sep 2020 15:00:04 GMT</pubDate>
            <atom:updated>2021-05-27T08:49:17.427Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>UX Research Flow: How transform traditional business into digital</strong></h3><p>“As an UX Researcher, you’re not a user” — That sentence became my principle when I saw the YouTube banner from the NNgroup channel after watching one of their videos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*15PA2710aqJi9JcCInqf3A.png" /><figcaption>NNgroup’s Youtube Channel Banner</figcaption></figure><h3><strong>Challenge</strong></h3><p>Imagine that I became an UX Researcher and working at an enterprise company that the company has decided to focus on working professionals (WP). An enterprise company has many branches of business which are integrated in a structured information system.</p><blockquote><strong>Goal: improve the current traditional business process to digital transformation.</strong></blockquote><p>Below are activities I undertake an effort to design a user-centered process while creating a UX research workflow and how my engineering background and my design penchant for visualizing information helped me create a effective workflow process.</p><h3><strong>Methodology: Start design thinking</strong></h3><h4><strong>Define your stakeholder</strong></h4><figure><img alt="Find out who are the company’s business stakeholders" src="https://cdn-images-1.medium.com/max/1024/1*sTOriJcW4CcQVfnBbl5SMQ.png" /><figcaption><a href="https://stories.freepik.com/amico"><em>Illustration by Amico on Stories Freepik</em></a></figcaption></figure><p>At the beginning, I <strong>determine</strong> who the stakeholders in this research. In a company has a workflow starting from receiving customer requests until serving their needs, and also within the company there are many division and role that have tasks in the workflow. Most established companies need to remake their purpose and it’s hard to change without a clear view of what that future business might look like after digital tranformation. From this description, it can be seen that enterprise company-level has components: <strong>purpose</strong>, <strong>vision</strong>, <strong>values</strong>, and <strong>assets</strong>. These are the components that I need to understand what the company needs when driving any form of digital transformation.</p><h4>Interview your stakeholder</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nt5gErxQJHPt51feDCiH9Q.png" /><figcaption><a href="https://stories.freepik.com/amico"><em>Illustration by Amico on Stories Freepik</em></a></figcaption></figure><p>When we have decision who our stakeholders are, of course we have to know everything about them. To get all of information, we can apply the interview method. Prepare questions and number of people before starting the interview. I <strong>interviewed</strong> 5 customers and 9 employees from all division (3 people in one division).</p><blockquote>You can determine the number of people you will interview according to your needs, it is <strong>recommended that the number of people is odd and not more than 5 because it will provide repeated insights</strong>.</blockquote><p>For customers, I wanted to know how they communicate their problem with this company: what works and doesn’t work, what is complaining, how they keep track of what happened to their problem, etc. For Employees, I wanted to understand their workflow: how they approach the customer problem, how they manage the team, what they will prioritize for their business, etc.</p><h4><strong>Finding problem with method</strong></h4><p>After we collect all the problems from stakeholders, we can grouping and see the direction of the problem. We can use method <strong>Affinity Diagram</strong> to organize then highlight important problem from stakeholders and users and <strong>How Might We</strong> to assume and develop scenarios and use cases that describe how the eventual solution might be used.</p><p><strong>What’s most important?</strong></p><p>1. Following the needs of users turning to digitization</p><p>2. Changing the habits of employees from traditional to digital system</p><p>3. Rearranging the workflow to be more efficient with technology support</p><h4><strong>Ideate and testing designs</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QaCjIXVkmZYxSFDlaQ-Wtg.png" /><figcaption><a href="https://stories.freepik.com/amico"><em>Illustration by Amico on Stories Freepik</em></a></figcaption></figure><p>Don’t underestimate how important these problem are, or how powerful method can be when done well. When the team understand their core problem and put the empathize to solve the problem is much better than using silver bullet method to speed up a problem solving.</p><p>Use <strong>flowchart</strong> to help visualize and concept for the workflow’s logic, put together their task and we will see how the workflow of this company. We can starting on paper and create sketch then develop <strong>user journey </strong>to understand the point of view of the user experience when interacting with the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6C9X3Wf0E01-B6E2SjQSsQ.png" /><figcaption><a href="https://stories.freepik.com/amico"><em>Illustration by Amico on Stories Freepik</em></a></figcaption></figure><p>Conceptualize an idea into a prototype that can be discussed with other division employees to do <strong>usability testing</strong>. This method is used to see how employees achieve their goals to complete their work, whether their workflows are becoming more efficient or not. To bring up innovative ideas or better insights, we can use <strong>A/B testing</strong> or <strong>Crazy Eight</strong> so that the results obtained are more conceptual.</p><h3><strong>Results</strong></h3><p>Technology development is very fast and supports all aspects of life, from network systems, banking, until daily needs. To balance the needs of users, a businessman should follow it step by step to maintain the quality of their service to their users.</p><p>Currently we are understand from the study and over all the process are:</p><p>1. From the interview method I <strong>can understand the needs of stakeholders</strong>: how the business model and vision and mission of the company, how does the company workflow so that it can serve customers, etc.</p><p>2. Existing problems can be processed with <strong>the right design thinking method and put a sense of empathy</strong> so as to create an idea that can solve these problems</p><p>3. Companies can <strong>start their digitization by prioritize</strong> what things can be turn to digitalization — e.g. moving all of their data to a single network or cloud storage so that it can be used together at the same time.</p><p>4. Provide a good experience to customers by <strong>creating user-friendly experiences</strong> digital services</p><p>5. <strong>Conceptualize workflow</strong> for employees with technology support. So that employees can serve users quickly and effectively.</p><p>But, we also know that the transformation from traditional to digital is not easy to do quickly. By focusing on these five factors, it will help the company embrace the new digital landscape, exceed customer expectations, and improve the overall aspects of doing business. Therefore it is necessary to make adjustments by conceptualizing technology that facilitates interaction between stakeholders and users.</p><p>Thank you for the nice references:</p><p><a href="https://www.superoffice.com/blog/digital-transformation/">https://www.superoffice.com/blog/digital-transformation/</a></p><p><a href="https://uxplanet.org/user-experience-and-digital-transformation-the-why-what-and-how-567b18510e69">https://uxplanet.org/user-experience-and-digital-transformation-the-why-what-and-how-567b18510e69</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c1bee0ef915" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>