<?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 Adinda Dyandra on Medium]]></title>
        <description><![CDATA[Stories by Adinda Dyandra on Medium]]></description>
        <link>https://medium.com/@adindadyandra?source=rss-c5dfd346f735------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9Y_-_S01Ae9RdQ4KtF3u7g@2x.jpeg</url>
            <title>Stories by Adinda Dyandra on Medium</title>
            <link>https://medium.com/@adindadyandra?source=rss-c5dfd346f735------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:09:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adindadyandra/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[UX Case Study: Changing User Behaviour Immensely Through Product]]></title>
            <link>https://medium.com/@adindadyandra/ux-case-study-changing-user-behaviour-immensely-through-product-db29cf41c798?source=rss-c5dfd346f735------2</link>
            <guid isPermaLink="false">https://medium.com/p/db29cf41c798</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Adinda Dyandra]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 04:56:00 GMT</pubDate>
            <atom:updated>2020-07-12T04:56:00.538Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTm_p-fjteaMCmd5dSlrlQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@andrewtneel">Andrew Neel</a> on <a href="https://unsplash.com/photos/cckf4TsHAuw">Unsplash</a></figcaption></figure><h3>How a product can change +4500 employee work behaviour.</h3><h4>Background &amp; Objective</h4><p>Tokopedia is an Indonesian technology company, employing over 4,500 people, with a large e-commerce platform. Currently, Tokopedia is currently creating more flexible remote work arrangements, as such we need to create a product to monitor and evaluate the overall remote performance of Nakama.</p><p>The objective of the assignment was to create a product to change Tokopedia’s employees and leaders’ current remote work behaviours in order to drive them to be more organised in their end-to-end remote working journey.</p><h4>Who are the users?</h4><ol><li>Tokopedia’s employees — Nakama</li><li>Leaders</li></ol><h4>What were the challenges?</h4><ol><li>Changing the +4500 employees behaviour and mental model in remote work through a product that will be used as the main force in the transition process.</li><li>Creating a system and boundaries for the product that would later be used as part of regulations in the remote policy as the related parties haven’t constructed any regulations or details for the new policy.</li></ol><h3>So, how did we do it?</h3><figure><img alt="Affinity Diagrams helped us to empathise the steps." src="https://cdn-images-1.medium.com/max/1024/1*wC1QwfkkpTsQkOryR8stzw.jpeg" /><figcaption>Affinity Diagrams helped us to empathise the steps.</figcaption></figure><h3>Research</h3><p>After understanding the stakeholders’ needs, we began the design process with research to gather insights from users.</p><h4>In-Depth Interview</h4><p>Our respondents were divided into two segments:<br>1. Employees who have a monthly remote work quota.<br>2. Employees who don’t have a monthly remote work quota</p><p>We wanted to know their thoughts, pain points, and expectations on both previous and new remote work policies. We also asked them what they wished to have in order to help them with this behaviour and policy transitioning.</p><h3>Empathise</h3><h4>Defining problems</h4><p>To understand their needs we first needed to empathise with their pain points and expectations, and put ourselves in their shoes. Then, we studied the use cases we found from the research. Afterwards, we found the gap between their pain points and expectations.</p><p>The point of finding the gap is to reveal the actual problems, to help us find more suitable solutions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohA2HCJ6DhspSsVtS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohA2HCJ6DhspSsVtS%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3ohA2HCJ6DhspSsVtS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="297" frameborder="0" scrolling="no"><a href="https://medium.com/media/82632202ea9fac967dd728ca5bff4bdd/href">https://medium.com/media/82632202ea9fac967dd728ca5bff4bdd/href</a></iframe><h4>Formulating problem statement</h4><p>After defining the problems, we formed a problem statement based on the following formula:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rqYkDLSyVNJGfWxrJ5iVdg.png" /></figure><h4>And here was the problem statement:</h4><blockquote>“<strong>Employees need</strong> assistance to adapt to the new remote working behavior <strong>because</strong> the new remote policy has several restrictions and regulations that greatly affect the company’s behaviour and culture.”</blockquote><h3>Ideation</h3><h4>Started with a design principle</h4><p>The design principle is used as the basis of fundamentals of the design. It can help us to “keep on the path”, meaning that whatever design ideas that we would later sort or execute will still be abiding by this basic principle.</p><h4>Spitballing the ideas</h4><p>Personally, for me, this was the most fun part of all! We were spitballing every that we had based on each use case and problems defined. To help us in the ideation process, we use some methods, such as:</p><ol><li><strong>How Might We<br></strong> We used this to help us to imagine what kind of actions or interactions should exist. We changed the problems into question form by using HMW at the front of the sentence.</li><li><strong>Affinity Diagrams<br></strong>We explored many ideas about each product section or flow using the affinity diagram. It helped us to group and sort the ideas exhaustively.</li><li><strong>Competitive analysis</strong><br>Unfortunately, we didn’t really find similar products with similar journeys, so we tried to break down the competitive analysis into per product sections. We searched for products with a similar journey/flow to the flow of each product section.</li><li><strong>Concept model<br></strong>We used the concept model to combine all the concepts that we want to include in the product. It is basically a depiction of what the product will be like, what the user can do with it, among others.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*-ZLhm31F0tixVw2COG54iA.png" /></figure><h3>What we came up with</h3><p>We came up with several product sections for employees’ interface, consisting of flows and features. Here are some of our product ideas:</p><h4>Product Boundaries for Submissions</h4><p>Since the full regulations to this policy hasn’t been rolled out until the design is delivered, we created something that can be seen as a regulation but what we prefer to call as product boundaries. This product was created to instill a sense of protection and safety between the two different user sections, but also to push for behavioral change.</p><h4>Remote Request Field</h4><ol><li><strong>Calendar with Google Calendar API<br></strong>To drive users to put their meeting schedules into considerations when requesting for remote working, we integrated the calendar to a scheduling app such as, Google Calendar.</li><li><strong>Task Field </strong><br>Since remote work pushes for more clarity between employees, we created a task form to help increase their work transparency.<br>to help increase their work transparency.<br>We designed the request field using the mental model for a task field in project management applications, such as Trello and Asana. We used the mental model to create familiarity in the field fillings, decrease the learning curve, and basically to drive them to fill all of these mandatory fields.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*Gq-yunfUUOAIkgpQCI3X2A.png" /><figcaption>Calendar &amp; Task Field</figcaption></figure><h4>Bulk Request</h4><p>This is designed for employees who consecutively submit a request for remote working for more than one day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*BtPohRFZb9AudeYKh_jIxA.png" /><figcaption>Bulk Request — Calendar</figcaption></figure><h4>Information Page</h4><p>We created an Information Page for both employees and leaders, consisting of the how-to of the product, tooltips, remote regulations, and what to do if they encounter any errors to make this product more intuitive and to decrease the learning curve for the users.</p><h4>Onboarding Page</h4><p>The function is similar to the Information Page. The onboarding will only give first-time users a bigger picture of the whole product journey to help to build their expectations of the end-to-end user journey.</p><h4>Reminders &amp; Warnings</h4><p>It is used as a quick guide or tooltips to help build user’s expectations and/or to inform users what kind of actions they or other users (leaders) would need to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*lOXvzapZJgt-Yqh_KrVOfQ.png" /><figcaption>Warnings &amp; Reminders</figcaption></figure><h4><strong>Notifications</strong></h4><p>Notifications aim to create in-product reminders and warnings, and to inform users what kind of actions are expected from them or have been done by other users (leaders). However, this reminder will be shared in the form of a Push Notification.</p><h3>Iterations</h3><h4>Remote Request Field</h4><p>Since employees’ task lists can be broken down into steps or checklists,. <strong>Some of their tasks actually only require a description box, while some will be requiring both features</strong>. As such, we create a button for the checklist, so they can either add it as they wish, use only a descriptions box instead, or use both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*i47KfV-DHFXFqmz3UXfP5Q.png" /><figcaption>Request Remote Field</figcaption></figure><h4>Bulk Request</h4><p>Users found the calendar, which is integrated with Google Calendar, to be helpful for selecting which date to request remote work. They said it helped remind them about their schedules, so they can estimate whether remote work is a viable option for that date.</p><p><strong>However, </strong>on the calendar page, <strong>they found it’s rather difficult to see their daily schedules by scrolling all the way down</strong>. It was also harder for them to differentiate the schedules per date.</p><p>Hence, we changed the design to look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vp_f61MlKM13SPKotfJmWg.png" /><figcaption>Bulk Request — Calendar (After iterations)</figcaption></figure><p>They can just click on each chip to see the schedules they have on that particular date.</p><h4>Key Takeaways</h4><p>I learned a lot of things from this project, which include:</p><ol><li>Taking time to understand and dig deeper until you discover the <strong>actual problems</strong> is really important. Users might not always know what they actually need until they are served with more varying solutions.</li><li>The design principle is really helpful to maintain <strong>consistency </strong>of the design you’re creating. It helps to keep every idea, flow, or feature on the same path.</li><li>Test, make iterations, repeat. There will always be <strong>room for improvement</strong> in any design. But it’s okay, that’s why it’s better to iterate instead of using the waterfall method.</li></ol><h4>Aaand that’s it. Thank you for reading! 🎉</h4><p>Let me know if you have any inputs, I would really love to hear it.<br>Let’s talk and collaborate! Hit me up on: adindashvdyandra@gmail.com 🤩</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db29cf41c798" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>