<?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 Ukasyah Qodratillah Ananda Putra on Medium]]></title>
        <description><![CDATA[Stories by Ukasyah Qodratillah Ananda Putra on Medium]]></description>
        <link>https://medium.com/@UkaQAP?source=rss-2d9f37899427------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fiCi_gvIyA59wjksMEAYfA.jpeg</url>
            <title>Stories by Ukasyah Qodratillah Ananda Putra on Medium</title>
            <link>https://medium.com/@UkaQAP?source=rss-2d9f37899427------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 08:11:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@UkaQAP/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[Eid Reflection: The Sense of Agency, Designers’ Hidden Gift]]></title>
            <link>https://medium.com/somiacx/eid-reflection-the-sense-of-agency-designers-hidden-gift-5ae77ca54793?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae77ca54793</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[uncertainty]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 06:02:04 GMT</pubDate>
            <atom:updated>2025-04-14T06:02:04.720Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FIq2hpyDDUlaHk_R" /><figcaption>Photo by <a href="https://unsplash.com/@earl_plannerzone?utm_source=medium&amp;utm_medium=referral">Earl Wilcox</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We just had Eid Al-Fitri break in Indonesia and got back to work. Not sure whether it’s due to meeting a lot of families, Eid breaks is also the time for people to be in reflective mode, including me. Thankfully I found my reflection in a more hopeful way and helped me move forward. I’m writing more as a reminder for myself and if this can help any of you navigate this uncertain times, I am grateful.</p><p>Let’s face it, this Eid break was a bit bleak. There is a lot of negative news surrounding an event that’s supposed to be a celebration time. Whether it is an international one (never-ending-war in multiple areas in the world, global trade wars) to our own country that makes us anxious (RUU TNI, budget efficiency, concerning foreign sovereign fund).</p><p>In this troubled times, I am really thankful that I have a design background. Not because of its’ drawing skill (to be honest, I am really sucked at drawing), not because of the problem solving mindset (though it somewhat helps). One crucial aspect of design background that really helps me going through this uncertain time is:<strong><em> the sense of agency</em></strong>.</p><p>If you are a designer, either by education or by profession, your work always start with a brief and you’re supposed <em>to do something about it. </em>You need to come up with something by your own hand. The brief would not magically turn into a design work <em>(at least not until recently, now with the time AI I know it is possible). </em>I’ve been exposed to this dynamic over my professional career and I now just realized I can apply this as well in navigating this uncertainty. Design process teaches me there is always something I can do within my own power to respond to life, <em>the brief.</em></p><p>I’m no saint. People close enough to me know that within me there is always a little version of myself that is in panic mode. Sometimes this little me got a little too big and fill out my entire self. At the end of last year it got a little out of control, it consumed me completely. In this moment again I found design offers me a tool for me to have some sense of agency. I encountered a book titled <a href="https://dschool.stanford.edu/shop/drawing-on-courage">Drawing on Courage</a>. <em>(Thanks for Jakarta Book Party and Periplus for the free book!</em>) The book told us how we can leverage the design process to untangle our own worry and fear. Here is one quote from the book:</p><blockquote>The feelings we don’t express leak out. If you don’t express it, you lose the ability to control how you express it”</blockquote><p>It suggests to make our feeling visible: by sketching it out, by making it into a paragraph, by turning it into this world’s artifacts; just like when we are designing something. It makes our worry tangible so we can address it more objectively. This helped me regain the sense of agency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nG8oYkAOluBq8Uf2QEBruA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxZMz2ET62Ew6JdXLiXIRw.png" /><figcaption>The cute illustration in the book really helps to illustrate (HA!) the design tools we can use to address our emotion. <em>I’d suggest to read the whole book, it’s really helpful!</em></figcaption></figure><p>I know in life there will always be thing beyond our control and power. For that I just have to enjoy the ride and hope that it will turn out okay. But now I believe, even in those moments, there are things that I can do to respond to what life throws at me. Even if life puts us down and make us fail, just like in our design, we can learn from it, iterate, and try again.</p><p>I’m really thankful for my Eid Al-Fitri break and the reflection time it gave me. I am writing this as a reminder for myself, that in our limited self, there is always something we can do. I hope this can help you as well navigating this uncertain time.</p><p>Uka is a Lead Design Consultant at <a href="http://www.somiacx.com/">Somia CX</a>. In his spare time, he can be found trying out new coffee beans he ordered from his favorite roastery or trying to establish two-way communication with the neighborhood felines.</p><p>You can find out more about his writing <a href="https://medium.com/@UkaQAP">here</a> or visit his <a href="https://www.linkedin.com/in/ukasyahqap/">LinkedIn page</a> to learn more and connect with him.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae77ca54793" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/eid-reflection-the-sense-of-agency-designers-hidden-gift-5ae77ca54793">Eid Reflection: The Sense of Agency, Designers’ Hidden Gift</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Are A Man & Woman on A Mission]]></title>
            <link>https://medium.com/somiacx/we-are-a-man-woman-on-a-mission-8b5a2a8fb688?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b5a2a8fb688</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-research]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Tue, 04 Mar 2025 10:26:37 GMT</pubDate>
            <atom:updated>2025-07-08T08:26:33.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*PLlrCRlcrZhX3puuZw143g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mischievous_penguins?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Casey Horner</a> on <a href="https://unsplash.com/photos/star-photography-265UjRsLgd8?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>I’ve been wondering about our profession as UX practitioners for quite a while, why in general it seems we are losing our charm. Throw back a couple of years ago, the profession is really hot. Every company needs help in building their next big digital platform, or how the more mature one started to build the team to tie together all their offerings to make it a cohesive experience for their customers. Everyone suddenly wants to become UX Designers or UX Researchers.</p><p>Recently, all we heard is about downsizing and how business switches back to their old setup, and usually the UX team is the one that let go. From ones that still have the team, we heard “My team couldn’t produce an outcome that is valued by the stakeholders.” What’s happening? Aren’t User Experience supposed to be grounded on evidence and that what helps us to have a seat at the table? Why are we suddenly considered not contributing anymore? Four experiences makes me think about our own mindset as an industry in doing our profession.</p><p><strong>A. Jumping the bandwagon without understanding the process</strong></p><p>During my experience interviewing candidates, I noticed a lot of people are switching careers to this industry due to the popularity and the enticing salary that it can offer. Many of them were enrolled in a bootcamp that helped them familiarize with the Human Centered Design process, a backbone approach for UX. But for some reason, many of the candidates are doing the approach for the sake of ticking the checkbox without actually understanding what they would get by doing it. It makes the work feel ‘broken’, there is no continuity between the problems we are trying to solve, their approach, data gathered, the analysis and the actual solutions produced.</p><p><strong>B. An Approach becomes just a template</strong></p><p>In the corporate world, I noticed that Human Centered Design (HCD) or Design Thinking (DT) sometimes are learned by using a series of templates (e.g empathy canvas, persona, pain and gain creators) but again losing why do we need to use it in the first place. HCD is reduced to templates to be filled without knowing the value we can get out of the approach. Worse, I encountered where HCD is reduced to be perceived as team bonding activity due to the ‘fun’ in interviewing respondents, role playing in prototyping and final presentation.</p><p><strong>C. No room to actually practice and get grounded feedback</strong></p><p>In talking to more senior practitioners I also noticed that how many years of experience they have doesn’t directly contribute to a better practitioners. If they are not within environments where there is room for them to actually apply and learn from the process all those years of experience becomes rather pointless. I personally encountered practitioners that have less experience can be sharper and produce greater output if they are in an environment where they constantly can practice and get grounded feedback from their stakeholders. Grounded as in understanding why certain actions could or couldn’t be done considering the company capabilities and limitations and the impact of it. Compared to more seasoned practitioners that has no space to apply the process and can only follow direct orders, they don’t have the space to learn to differentiate from good or bad actions. They don’t know which approach would be suitable within certain conditions. Or simply, they couldn’t back their decision properly. This is every practitioners’ job to make sure the environment they can control can be set up to facilitate constant learning.</p><p><strong>D. We forget why we are here</strong></p><p>One last thing that I observed, although I think is the most crucial, we sometimes forget that businesses create UX teams or employ UX services not out of charity. They hire us to serve their business goals. Everything we do is to serve those goals: by understanding what the business are trying to accomplish, by selecting appropriate approach that would get us closer to achieve the goals, by understanding our customers, internal flows and staff, the limitations and constraints, by analyzing the data and coming up with relevant solutions for those goals. Every opportunity that we encounter to achieve the business goals, regardless in which process, we should grab it whenever we have the chance.</p><ul><li>Noticed a different stakeholders that might contribute deeper understanding of the problem we are tackling but it’s not directly related? Talk to them!</li><li>Found a new way to get data that help you understand the problems better? Try it!</li><li>Found an interesting story within our participant session that you think is related with our business goals but outside of our predetermined questions? Ask it!</li><li>Found a new idea in the middle of the session that we think it’d solve the business goals? Explore it!</li><li>You feel that the initial approach you set up is no longer relevant and you think it’d be more beneficial to pivot? Do it!</li></ul><p>What we are doing is not simply following UX processes. We do what we do to achieve the shared goal within the business. We need to make sure at the end of our project or milestone, we are answering or at least getting closer to that business goal.</p><p>We are not simply UX practitioners.<br>We are A Man &amp; Woman on A Mission.</p><p>Uka is a Lead Design Consultant at <a href="http://www.somiacx.com/">Somia CX</a>. In his spare time, he can be found trying out new coffee beans he ordered from his favorite roastery or trying to establish two-way communication with the neighborhood felines.</p><p>You can find out more about his writing <a href="https://medium.com/@UkaQAP">here</a> or visit his <a href="https://www.linkedin.com/in/ukasyahqap/">LinkedIn page</a> to learn more and connect with him.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b5a2a8fb688" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/we-are-a-man-woman-on-a-mission-8b5a2a8fb688">We Are A Man &amp; Woman on A Mission</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing The Invisible Interaction of Museum Collections]]></title>
            <link>https://medium.com/somiacx/designing-the-invisible-interaction-of-museum-collections-984709a13de7?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/984709a13de7</guid>
            <category><![CDATA[heritage]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[visitor-experience]]></category>
            <category><![CDATA[museums]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Wed, 13 Mar 2024 08:12:14 GMT</pubDate>
            <atom:updated>2024-03-13T08:12:14.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R70cqO77oblfQe8AOQlx9g.jpeg" /></figure><p>User experience designers usually design for something tangible or something we can see. We design digital interactions for websites and mobile applications. We also deal with services when we design bank services. The interaction we design can also involve physical objects, like the design button interface for a TV monitor. But last year, we, <a href="http://www.somiacx.com/">Somia Customer Experience</a> got to experience designing something invisible: the interaction between visitors and the museum collections. I’ll explain further why I said the interaction is invisible.</p><p>For context, The Indonesia Heritage Agency engaged us to create visitor experience guidelines for <a href="https://www.museumnasional.or.id/">Museum Nasional</a>. As part of the project, we observed and interviewed the museum’s current visitors and non-visitors (particularly those who are into museums other than Museum Nasional) to see how they navigate and interact with the collections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0L9ZsHZFENgjXO6L1lyXaQ.jpeg" /><figcaption>Intercepting Museum Nasional’s visitor to understand their perception &amp; interaction with the museum collections.</figcaption></figure><h3>Interacting beyond the collection</h3><p>From the sessions with the museum visitors, we understood one thing: They are not interacting with the actual objects of the collection. The collections are only used as a medium to interact with the stories that they represent. Interestingly, there are different invisible aspects of the collection&#39;s stories that we need to consider if we want to design a relevant experience for the visitors.</p><h4>Designing for the Invisible Past Life</h4><p>Visitors use the collections as a gate to understand how people in the past used to live, not simply about the collection details. The materials, dates, and locations found become secondary to knowing how exactly the people used the collection and the life surrounding it. For example, when they see the piggy bank from the Majapahit era, they want to know what kind of money people in the past used, who saved money in the piggy bank, for what purposes people saved in the past, and did they have the same motivation as us in the modern day. The collections become like time machines that throw people back in time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1REQa4PY8Zp3F2Y1xGkZw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*x5kHctLe2JX0wW2NSXqaTw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dRUEAxVPChp_3f4p4FVOsw.jpeg" /><figcaption>Piggy bank collection from the Majapahit era. Source: Somia Customer Experience’s documentation.</figcaption></figure><p>Visitors are trying to see the connection between past and present. So when we design interaction for these collections, we need to understand which past life we need to bring to life and not simply display the collections as is. This connection between past and present is critical when we want to design interaction with collections that are distant from the modern day. For example, when we talked with visitors interacting with the Kedukan Bukit collection, they struggled to see why the stone was in the museum in the first place, even though the artifact was the first proof of the Sriwijaya Kingdom. The visitors were missing that writing in stone at that particular time could only be done by an established authority, so the stone acts like a ‘birth certificate.’ Only by explaining the relevancy of the stone in the modern day can visitors understand its importance.</p><figure><img alt="Kedukan Bukit collection, a written proof of The Kingdom of Sriwijaya, from front." src="https://cdn-images-1.medium.com/max/1024/1*I5G-3lVmfQ4iQXLCdD91mQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tVpCGNE25Oo7LPXD5TblCw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rj3ZMxQj8Xb0I24SzWJh4w.jpeg" /><figcaption>Kedukan Bukit, one of the written proofs of the Kingdom of Sriwijaya. Source: Somia Customer Experience’s documentation.</figcaption></figure><h4>Designing for the Invisible Historical Significance</h4><p>Collections in the museum each have their own stories and values. Some of them have a bigger historical significance than the others. The collection could be a personal belonging of an important historical figure, regalia of a past kingdom, or, just like previously mentioned, as proof of existence. The historical significance, however, is sometimes not directly represented by the collection&#39;s visual appearance. Historically significant collections may not always be visually interesting. It could be due to the collection&#39;s condition, size, or generic shape.</p><figure><img alt="The saddle of Pangeran Diponegoro" src="https://cdn-images-1.medium.com/max/696/0*KuFLTHy-bRlA4qyf.jpg" /><figcaption>The Saddle of Pangeran Diponegoro. Source: <a href="https://www.museumnasional.or.id/spear-and-saddle-302">Museum Nasional</a>.</figcaption></figure><p>Look at Pangeran Diponegoro&#39;s saddle, which was his belonging during his fight against the Dutch between 1825 and 1830. Pangeran Diponegoro wore the saddle while running from the Dutch pursuit. In terms of visuals, although it looks slightly more luxurious than a regular saddle, it is still only a saddle. The collection alone could not tell the visitors the important figure of Pangeran Diponegoro. When designing visitor interactions with museum collections that hold significant historical value, it is crucial to create an experience that allows visitors to comprehend the importance of the artifacts, in this case, the Pangeran Diponegoro and story of pursuit. This can be achieved through various means, such as the way we display the collections, the lighting we use, their placement, and, of course, by visualizing the stories alongside the collection.</p><h4>Designing for the Invisible Connection Between Collections</h4><p>How many of us feel tired or overwhelmed after exploring a heritage-based museum? Aside from the actual physical activity of moving from different areas of the museum, it is probably because we are absorbing a large amount of new information from the collections. A museum usually has a large number of collections to show. Each collection has many stories for visitors to learn. Meanwhile, humans have a limited capacity to absorb new information within a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*9gCQ5Njls3Woc8PvVT627Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5X_fGnCGbh_eOvqdeecLow.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klShoB1gP-vhhQZWGY7P-w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbR_DZiUoV5VLZcomuweSQ.jpeg" /><figcaption>Prototyping the interaction of collections. We highlighted some of the important stories of some collections and evaluated the visitor’s reception of it. Source: Somia Customer Experience’s documentation.</figcaption></figure><p>From our observations and prototyping activity, we learned that visitors usually can only remember one particular piece of information from one collection, even if they are presented with many. We also learned that after they finished exploring, they tried to connect one collection to another to make sense of what they learned. Museums usually already have a certain exhibition theme and pick collections according to the narration they want to tell. However, with the visitor’s limited capacity, we need to be aware of which information we want the visitors to learn from each collection and the connection between one to another. This is to ensure that the narration we want to convey in the exhibition can be understood, reducing the misinterpretation of the set of collections.</p><figure><img alt="Diagram of narration breakdown. Start with overall big theme narration, to the sub-theme, then to individual collection information. All need to be connected." src="https://cdn-images-1.medium.com/max/734/1*q_XExSjoXH1JirFQjbhvoA.png" /><figcaption>Each collection’s information should only have one focal point that is tied to the overall narration of the exhibition. Source: Somia Customer Experience’s documentation.</figcaption></figure><p>This limited capacity of visitors to process information creates an untapped opportunity for the museum. Since one collection could have many stories that we only need to pick one, from time to time, we can create different exhibitions from the same set of collections with different focal point narration for each collection. This can create a perception of novelty that may attract visitors to revisit the museum for new exhibitions.</p><p>The next time we get to design interaction for a heritage-based museum’s collections, remember that what we design for stories that the physical object represents. The object is only a gate for visitors to understand the past life and its historical significance. Let’s make sure we plan all the connections between each collection in one exhibition so visitors can easily grasp what we are trying to say.</p><p>Uka is a Lead Design Consultant at <a href="http://www.somiacx.com/">Somia CX</a>. In his spare time, he can be found trying out new coffee beans he ordered from his favorite roastery or trying to establish two-way communication with the neighborhood felines.</p><p>You can find out more about his writing <a href="https://medium.com/@UkaQAP">here</a> or visit his <a href="https://www.linkedin.com/in/ukasyahqap/">LinkedIn page</a> to learn more and connect with him.</p><p>In the past, Somia CX also did an independent exploration project about museums. You can read the article <a href="https://medium.com/somiacx/understanding-peoples-behaviour-and-needs-towards-museum-an-independent-project-2ffbfd876c18">here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=984709a13de7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/designing-the-invisible-interaction-of-museum-collections-984709a13de7">Designing The Invisible Interaction of Museum Collections</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HCD Project is Not All About The Meat, Sometimes It’s About The Table Manners]]></title>
            <link>https://medium.com/somiacx/hcd-project-is-not-all-about-the-meat-sometimes-its-about-the-table-manners-b0d8e195242a?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0d8e195242a</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Fri, 26 Jan 2024 02:36:11 GMT</pubDate>
            <atom:updated>2024-01-26T02:36:11.106Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4UKOtxdIk12ASwb8" /><figcaption>Photo by <a href="https://unsplash.com/@thegordeev?utm_source=medium&amp;utm_medium=referral">Egor Gordeev</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When we talk about how to run a successful human-centered design or UX project, practitioners usually focus on the content-related aspect: the methodology, the way we conduct the research, and how from the research we can come up with the relevant solutions for the problem we are currently solving. The Meat. But actually, many other things could affect the trajectory of our projects. One of the things that I think is crucial is stakeholder management: mapping who is involved and how we communicate with them, The Table Manner of a project.</p><h4>Mapping stakeholder involved</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT4uQF7h39mlsF5czK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fanimation-tech-motion-graphics-xT4uQF7h39mlsF5czK&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExNGZya2thNDdzbjRjMGwwZ3hraG9vMTlzZTM0eWJnaTByc2I4YTQ5NCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FxT4uQF7h39mlsF5czK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/8de8e2c62ba6cd2f5e1ad1766dfe5a01/href">https://medium.com/media/8de8e2c62ba6cd2f5e1ad1766dfe5a01/href</a></iframe><p>We need to know who within the company we need to engage. This is not just so we know which divisions we need to talk to build content awareness, but also to create buy-in. This is important for two things: easier navigation within a project, but also to make sure the result of the research can be followed up to implementation.</p><p><strong><em>Who has the biggest influence?<br></em></strong>Consider who would have the biggest influence, either the one that is supporting the project, or the one who is skeptical or against it. Involve them regularly, so we can hear their feedback or concerns. Sometimes, these people give hard feedback not because they have concerns, but simply because they can. Some people want to exercise the power they have. By engaging them from time to time, we can understand their concern and address them along the way, reducing the chance of them dropping bombs at the very end of the project.</p><p>For example, in a company that has a top-down approach usually if we can get someone from the higher-ups who believes in the initiative to speak in the kick-off meeting, it would make the communication to these related divisions much easier.</p><p><strong><em>Who will be impacted the most?<br></em></strong>The other party we need to consider is the one that might have been the most impacted or do the hard work to implement the initiative. Try to understand what they have been doing so far and what are their blockers. Explain how our project might impact or solve it. They might have already spent months doing another related initiative and see our project as a threat. See how we can collaborate or use what the team has been doing so far. By doing this, we are reducing the risk of the result of our project being not implemented due to the related stakeholders not feeling valued by us.</p><p>In a project where we created a visitor experience strategy for a heritage museum, we involved divisions that are directly related to visitors: curators, exhibition, education, and public services. However, at the beginning of the project, we did not realize that there were two different teams of curators handling the artifacts, the more senior in terms of hierarchy. Having realized that later on in the project, we set a dedicated session to run through the progress of the project and all the findings we had so far. When they learned about our findings, they felt a bit devastated. Based on our findings, it felt that they were not doing their job properly, but it was only because they had some limitations that made them unable to do it properly. When sharing with the higher stakeholders, we made sure to not only share the findings but also the team’s challenges so they could have what it takes to implement the result later on.</p><h4>Communicating with the stakeholders</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYuvgZISsj8j3a%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fnatgeochannel-blue-sound-YuvgZISsj8j3a&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExdHlzM3lxNWV6eDNwenR1djh3Y25kNG5tcDh6OGx1aWdscjR0MWYxbyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FYuvgZISsj8j3a%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/d41401e4d6ba2ffb11a74557dfc7f2bd/href">https://medium.com/media/d41401e4d6ba2ffb11a74557dfc7f2bd/href</a></iframe><p>When sharing case studies in public, I often heard questions “Oh, my stakeholders don’t care about our users, they only care about the numbers. Do you know how we can make them care?”. In terms of content delivery, there are a couple of ways to make it more engaging, mainly focusing on how to make the insight ‘alive’, which can be using videos or quotes from our customers. But what I want to highlight is, the way we present the project is also a crucial part of it. Here are several learnings I got in talking with the stakeholders:</p><p><strong><em>What’s in it for them?<br></em></strong>When we talk about human-centered initiatives, often we only focus on the customer’s perspective, but forget that our internal stakeholders are also human. They have their KPIs they need to achieve as well, they have their problems to solve. When we talk to different divisions, try to think about how our project might be beneficial to them so they are interested in engaging with us.</p><p><strong><em>Avoiding lost in translation<br></em></strong>Let’s be honest, practitioners use a lot of jargon. Persona, Stimuli, Prototype, Discussion Guide, IDI, to name a few. These jargons are not common or they might have different meanings outside of HCD or UX knowledge. Try to use more publicly known terms to make what we are conveying easier to understand. For example, instead of saying <em>Discussion Guide</em> we can use a <em>list of questions for the interview, </em>instead of <em>Stimuli</em> we can use <em>initial concepts.</em></p><p>Another thing to consider is to learn the stakeholders’ ‘language’. Sometimes they have a specific terminology that they use to explain a certain business process. Familiarize ourselves with the terms so at the very least we understand what they are saying to us, better if we can convey what we want to say using their ‘language’. We could miscommunicate just because we are not on the same page. By doing these, we are reducing the gaps between us and them.</p><p><strong><em>Establishing authority<br></em></strong>Not all people know or already believe in the human-centered design or even the qualitative approach. Even if we already have the right methodology, the right research activities, picking the right participant samples, all would be thrown out of the window if they don’t believe in the overall approach to begin with. Try to understand these beforehand. If we think they are not in the same boat as us, it will be a good idea to present case studies that demonstrate successful stories of the approach, to make them onboard.</p><p>Sometimes the question of authority is not about the approach, but about us personally. They may doubt whether we can deliver the project, especially if the project is quite complex. We can combat this by inserting some of our previous track record when we explain the methodology or activities we will carry out to convince them.</p><p>We are visual creatures. We judge based on what we see. Sometimes, the way we present ourselves could heavily affect the reception of the content we are sharing with the stakeholders. The way we dress, the way we stand, and the way we engage with stakeholders could contribute to whether they believe in what we say or not. One story I heard from my acquaintance in handling a government project was that they got underestimated because their stakeholders felt the project was handled by a team of ‘students’, as they are wearing business casual outfits and backpacks when meeting with them. So we need to adapt a little bit to make sure we are ‘presentable’ according to our stakeholders’ standards.</p><p>The next time we are navigating a HCD or UX project, let’s not focus only on the content level of it, a.k.a The Meat, but also on how we deliver the project to the related stakeholders, The Table Manner. Map the relevant stakeholders: understand who supports or is against the project and who would be impacted the most. Adjust the way we communicate to the stakeholders by finding aligned interests, avoiding miscommunication, and establishing our authority in the subject. These are to ensure the meticulously cooked dishes we prepare are palatable and can be enjoyed, thus leaving a good impression on them.</p><p>Uka is a Lead Design Consultant at <a href="http://www.somiacx.com/">Somia CX</a>, In his spare time you can find him trying out new coffee beans he ordered from his favorite roastery, or trying to establish two-way communication with the neighborhood felines.</p><p>You can find more on his writing <a href="https://medium.com/@UkaQAP">here</a> or visit his <a href="https://www.linkedin.com/in/ukasyahqap/">LinkedIn</a> to learn more and connect with him.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0d8e195242a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/hcd-project-is-not-all-about-the-meat-sometimes-its-about-the-table-manners-b0d8e195242a">HCD Project is Not All About The Meat, Sometimes It’s About The Table Manners</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learnings from Strategic UX Roundtable Discussion]]></title>
            <link>https://medium.com/somiacx/learnings-from-strategic-ux-roundtable-discussion-75aee78c28bc?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/75aee78c28bc</guid>
            <category><![CDATA[strategic-ux]]></category>
            <category><![CDATA[takeaways]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[roundtable]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Tue, 15 Aug 2023 01:07:14 GMT</pubDate>
            <atom:updated>2023-08-15T01:07:14.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_KosFEgoUjs7UtoWziOyHw.png" /></figure><p>On 1st of August, Somia CX held a roundtable discussion with 3 panelists to discuss the recent buzzword in the industry: Strategic UX. The 3 panelists were: Yoel Sumitro, Senior Director of Delivery Hero; Larissa Rena, Global Senior Inclusive Design Researcher at IKEA; and our own Ketut Sulistyawati, the Director of Somia Customer Experience. Me myself was moderating the session. For approximately 2 hours we discussed many things, from debunking what exactly Strategic UX is, to how to be ‘strategic’ as UX practitioners in this uncertain time. Here are several takeaways from the discussion:</p><h4><strong>All research in UX by nature is supposed to be strategic. Foundational / exploratory and tactical research tackle different problems at hand, but both are equally important for the business.</strong></h4><ul><li>Strategic research usually covers the realm of the “unknown unknown” — exploring new topics such as safety for drivers or exploring white space for new business opportunities. While tactical research seeks to find the answer of the “known unknown” such as usability or product usage.</li><li>Both types of research are equally important. Whatever kind of research we do, what matters is whether our research can contribute to the objective and help with the problem context faced at hand.</li><li>What’s more important is to know what is needed by the team / business / organization and the capability to formulate and execute the right approach to answer it.</li></ul><h4><strong>International research vs research in Indonesia</strong></h4><ul><li>There is no significant difference in the researchers’ quality or the methods used. But researchers who have done international research usually have more experience in the logistics of running cross-country research (eg., translation) and how to run research in different cultures.</li><li>In international organization, decisions need to be made whether insights that come from a few countries can be implemented for products for the worldwide market, or whether certain customization is needed at country or local level.</li></ul><h4><strong>On the value of research</strong></h4><ul><li>Research is a way to minimize risk, eg. to help companies avoid launching a wrong product to the market.</li><li>Understanding the business goals is crucial so researchers can relate how research can contribute to those goals. For example, avoiding cost of lawsuits, increasing revenue, or reducing cost.</li><li>Knowing the business numbers or working with other experts who can come up with them can help make the research case more tangible for the business.</li><li>But the minimum value of research is at least it should help the stakeholders make an informed decision based on the result of the research.</li></ul><h4><strong>Other than from delivering good deep insight, foundational or exploratory research needs to be actionable to be valuable for the organization</strong></h4><ul><li>To be actionable and valuable, research insights need to be delivered to the right stakeholders, at the right time, to make the right decisions.</li><li>Unfortunately, many good insights are lost in translations, not understood, and then sitting on a shelf because the “users” of the research don’t know what to do with it. Researchers might be needed to translate the insights into the language that the stakeholders understand and facilitate discussions to guide them exploring the possibilities and implications based on the insights.</li><li>Another way is through collaborative engagement with stakeholders during the research process, rather than working in silo and only delivering the insights when the research is completed.</li></ul><h4><strong>To deliver utmost value to what we do, we as UX practitioners not only need to master UX related activities, but also how to navigate within the system of our organization.</strong></h4><ul><li>Just like we do research to get to know our customers, we researchers need to understand our stakeholders as well to make sure the research result is fruitful</li><li>Understanding the business or business acumen is needed, to make sure that we understand what actually the organization needs.</li><li>Stakeholders management is crucial to make sure the result of our work can be understood by the stakeholders and implemented.</li><li>Try to communicate the value of the UX in terms of what benefit or loss the business would get by doing it, speaking the result more on their ‘language’.</li></ul><p>Apart from the discussion covered in the session, we also learned several things to be improve on how we run the session, nothing is perfect:</p><h4><strong>Biggest learning: managing expectations</strong></h4><p>From the start we intended the session to be a panel talk / round table discussion. Initially we would like to carry out the session to be more structured with clear blocks of topics to be covered. During the coordination with the panelists, we felt that the audience would benefit more from a dynamic conversation since our field is constantly growing. But it seems the intent was not properly conveyed.</p><ul><li>The publication did not clearly say that the session would be a fireside chat with multiple points of views and more fluid discussions from the panelist, that we would have a rich debate rather than speakers explaining their own slides.</li><li>As a result, the session attracted mixed audiences with mixed expectations. The free flow of conversation was confusing for those expected to learn about the topic in a more structured manner. The open debate was unsettling for those who are hoping to get conclusive answers.</li></ul><h4><strong>Really thankful with backstage team in supporting me as moderator</strong></h4><p>In order to create engaging conversation, we had a backstage team to monitor our Slido &amp; Zoom chat to find interesting questions, since from the registration we expected there would be hundreds of people joining the event. To be honest, some of the comments we got were rather hurtful, so I am really thankful for the team that has to bear it so I could focus on moderating the session. We also learn we can not satisfy everybody, we have to accept that we can not make everybody happy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*HThkGHoOI5R9rlkpaJA7tg.jpeg" /><figcaption>Thank you for joining the session all!</figcaption></figure><p>We hope you all can learn something from the panel discussion, thank you for your support and the feedback! Feel free to reach out to us if you would like to discuss more about the topic.</p><p>See you in our next events!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75aee78c28bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/learnings-from-strategic-ux-roundtable-discussion-75aee78c28bc">Learnings from Strategic UX Roundtable Discussion</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Takeaways from My First Human-Centered Indonesian Public Sector Project]]></title>
            <link>https://medium.com/somiacx/takeaways-from-my-first-human-centered-indonesian-public-sector-project-3d6d154c567b?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d6d154c567b</guid>
            <category><![CDATA[indonesia]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[hcd]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[design-research]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Mon, 12 Jul 2021 13:14:38 GMT</pubDate>
            <atom:updated>2021-07-12T13:14:38.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*0Zdj_V1Ib7YFqXomFE4bvw.png" /><figcaption>Pic Source: <a href="https://unsplash.com/photos/bZT3YDRjacc">Unsplash</a></figcaption></figure><p>Whenever I read a case study of Human Centered Design (HCD) in public sector from foreign countries, I’m always in awed with how the agency or the team can improve many peoples lives with their project, and honestly a bit jealous too. I used to wonder “When will Indonesian government use this approach when designing policy? I bet it’d make the policy better”.</p><p>Recent years I feel my hope was heard when I learned many public sector project started to apply the approach, usually ones that are backed by International NGO. Then I started to wonder “How would it feel ya to work in public sectors using the HCD approach?”. 3 Months ago I got the very chance to answer my own wonder when I was assigned to work on one with one of my colleague.</p><p>Here are my several takeaways.</p><p><em>(Side note: careful what you wish for, it might get answered rather quickly)</em></p><h4>Quickly familiarise your self with all the abbreviation and terminology</h4><p>Yes, Indonesian public sector really like to abbreviate every single thing they have, from activities, departments, objects, and many more. For example, most adult individual in Indonesia would know things like KTP, SIM, NPWP, BPJS Kesehatan . Or in this pandemic era we even have two abbreviations for social curfew, PSBB and PPKM . As someone who rarely or even sometimes avoiding interaction with government unless it is really needed, all of these abbreviation and terminology could easily make me overwhelmed, especially we were not only going to be exposed at front stage, but also the back stage interaction <em>(read:more abbreviations).</em></p><blockquote>KTP = Kartu Tanda Penduduk / Citizen ID Card<br>SIM = Surat Izin Mengemudi / Drivers Licence<br>NPWP = Nomor Pokok Wajib Pajak / Tax Identification Number<br>BPJS Kesehatan = Badan Penyelenggara Jaminan Sosial Kesehatan / Health Social Security Agency<br>PSBB = Pembatasan Sosial Berskala Besar / Wide Scale Social Restrictions<br>PPKM = Pemberlakuan Pembatasan Kegiatan Masyarakat / Community Activities Restrictions Enforcement</blockquote><p>Therefore early in the beginning of the project, my project partner and I had several sessions with subject matter expert in order for us to get familiarise with all of the abbreviation and terminology being used. We also asked around within our network that willingly share their experience interacting with the topic being covered. By doing this, we built the basic understanding of the topics therefore we could discuss more important things with the client not wasting much time asking obvious questions to the respondents we invited. The communication between the team will become easier when we understand and speak their lingo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/0*VtF7W-PXzbBiwwP0" /><figcaption>Me, early in the project trying to understand and remember all of abbreviation and terminology. Source: <a href="https://media.giphy.com/media/4JVTF9zR9BicshFAb7/source.gif">Giphy</a></figcaption></figure><h4>Clarify things you don’t understand right away</h4><p>As far as we learned by ourself, there was always something we did not understand or simply missed. Therefore whenever we encountered unfamiliar topics during our project, we would discuss this with the client to make sure we got the concept right, otherwise we might carry false understanding and could become fatal when we were designing the solution.</p><p>We also setup a zoom relay within our remote interview sessions ,so many of clients team members from different departments could observe the session without making the respondent uncomfortable. After a session ended, we invited them to a debrief session where we could discuss the findings, clarification, or get understanding what was happening backstage directly from the related departments.</p><p><em>(Even with all of this, there was still time when we perceived wrongly about a concept, fortunately it was still early in the project)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ZFLDJNnPzJ5rkgG3Sw9EQ.png" /><figcaption>Remote Interview Setup to enable many observer without making respondent uncomfortable. Respondent will only see one observer account on the session while it is being relayed to another account where many team members can observe the session</figcaption></figure><h4>Include higher stakeholders during the projects, not just at the very end</h4><p>Let’s be honest, we all must have experience the long bureaucracy that is happening in Indonesian public sector. And when you were working in the backstage with them, you needed to follow this as well. With this bureaucracy environment, there is tendency for the client’s team to need confirmation from the higher up before making their decision. Fortunately, the project already setup a steering committee meeting every two weeks where we informed the current progress and what we would do next.</p><p>By doing this steering committee meeting, when the higher management heard the progress and had some concern, they could directly express it and we then could discuss and find solution right away in the same occasion. We then could confidently move forward, the higher management would always be informed and could give their feedback along the way, therefore creating a better buy-in for the project.</p><p>The session with higher management is also a good place for us to raise concerns, unsolved issues, or things that need attention quickly. Sometimes there were something that were stuck in one the bureaucracy chain that only by the nudge of the higher stakeholders that we could get it on time <em>(or at the very least, actually get it).</em></p><h4>Use plain language and avoid jargons</h4><p>If in the beginning we touched a bit regarding the use of lots of abbreviation and terminology in public sector, HCD practitioners are not without fault either. We are sometimes trapped and confused by our jargons as well, like Stimuli, Persona, Synthesis, Co-Design, Future State Journey. Throw all that words to a party who just recently exposed with HCD , misunderstanding are bound to happen.</p><p>Focus on what we trying to solve and what we need to do will break us out from the meaningless jargons. Use plain language if we can, to explain about the activities or things we are about to produce. If it is not doable, have a separate session to explain about the activities so every one has the same understanding what will happen and what they need to prepare. Because at the very end, insights uncovered from the research and the solution we propose are all that matter.</p><p><em>(There was one time in the project where we all got confused due to different perception between us and the client on what Persona is)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*saiA4aC0z9S9TRuB" /><figcaption>GIF Source: <a href="https://media.giphy.com/media/1oJLpejP9jEvWQlZj4/giphy.gif">Giphy</a></figcaption></figure><h4><strong>Guiding based on objective</strong></h4><p>During the project i noticed sometimes my client would give feedback or direction that initially seems to be unusual or even counterproductive with the objective we were trying to achieve. But turned out it was just because HCD approach was so different with they used to. When this happens, ask them why did they give that particular feedback or direction, try to understand their motivation, then suggest alternative direction that suits with the objective. They might give inputs based on what they are familiar with, we just need to ask why then guide them along to the right direction.</p><p>That are my several take aways from my first public sector HCD project, hope it will help you on yours!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d6d154c567b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/takeaways-from-my-first-human-centered-indonesian-public-sector-project-3d6d154c567b">Takeaways from My First Human-Centered Indonesian Public Sector Project</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips to Sharpen Your Research]]></title>
            <link>https://medium.com/somiacx/tips-to-sharpen-your-research-c11894f337d0?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/c11894f337d0</guid>
            <category><![CDATA[qualitative-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Sat, 06 Jun 2020 02:32:12 GMT</pubDate>
            <atom:updated>2020-06-06T02:32:12.110Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V75lA1969h6sRoLnYsYGxg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@maltewingen?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Malte Wingen</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Product development teams already know the importance of doing research, either an evaluative research like usability testing, a generative one like defining new product features, or an exploratory one where we try to enter new market for our product. Despite all the insight and opportunities to improve our product we will get from it, research takes time, manpower, and resources to do it. Here are some tips to make sure our effort doesn’t go to waste.</p><h4>1. Sit and Have Coffee with The Stakeholders</h4><p>In <a href="http://www.somiacx.com/">Somia CX</a> we believe our clients are the subject matter experts. They do their business every day and know in detail how they are running their business. That’s why in every project we setup multiple sessions with related stakeholders to give us induction about the product being covered, relevant past research, and the area in generals. Ask what they want to understand from the research and why it is important for the product, the business, and the company. Ask them to explain what has been done before and the learning from it.</p><p>Sometimes we might feel overwhelmed by the seer amount of new information we get, or we might feel lost since our questions only leads to another questions. Note everything down and clarify things that we still don’t quite understand. If there are unanswered questions that we think are quite important we then can include that into one of our research questions. Don’t be afraid to look like a fool and ask too many questions. Only by downloading and grasping the understanding the current situation we can dig deeper and avoid our research only scratch the surface level of the topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nzNaMlB-LBRGo0X7OgrBPg.jpeg" /><figcaption>One of merchant we visited during our research.</figcaption></figure><p>For example, in one of our research about understanding merchants’ selling behaviour, we learned from the client that they had significantly different products and pricing strategy for each geographic zoning. Knowing this information, we picked our research location and tweaked the discussion guide to match geographic zoning.</p><h4>2. There’s Nothing New Under the Same Sun</h4><p>After we grasped the current situation and objective of the research, we might want to look around for secondary research that has been done before. The objective is not only to understand the subject matter better, but also to seek inspiration and get fresh perspective. The research might not be entirely the same with our’s, it could be the same topic but in another country, or you could even seek analogues inspiration in other topic with similar activities.</p><p>Reading the previous research will also teach us about important element we might want to focus on our current research. For example, by reading similar research in Africa about financial innovation, we learned that people might use other channel rather than bank to save their money that might be informal but easier to access. Similarly we also found many people in Indonesia saved their money in ‘Arisan’ or ‘Jula-Jula’. ‘Arisan’ is a social gathering where all of the members need to put certain amount of money and can get the accumulated money by taking turn to draw their names in lottery. With this similarities, we can take inspiration that worked in other country and create new solution that more suitable in our context. This is one of the insight that led us to developed <a href="http://www.somiacx.com/thought/save-cash-and-bank-it-what-ive-learnt-from-service-prototyping/">Save Cash &amp; Bank It.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2SS4yPOuVx7KRngyXzc1Q.jpeg" /><figcaption>Typical Arisan setup (Photo source: <a href="https://pa-panyabungan.go.id/images/arisanibuksri1.jpg">https://pa-panyabungan.go.id/images/arisanibuksri1.jpg</a>)</figcaption></figure><h4>3. Captain, prepare to take off!</h4><p>Understanding from the subject matter expert and the previous should lead us to better research scope and approach. After we prepare the research questions and all stimuli needed, we might want to pilot the session first. Pilot session is trying out the research with someone from our contact who resembles the characteristic with our target respondents. The closer the these pilot respondents resembles real ones the more useful the feedback will be for our research. The objective of doing pilot is to improve the research approach (questions, flow, stimuli) by trying it in a session. After the session ends we can evaluate whether the question flow makes sense, whether it is within the allocated time, or any particular section difficult to explain, then we can adjust accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jZz1WKIwy8owIpoqYsThww.png" /><figcaption>Note taking + discussion guide document used in the research, we used post it to write the data then pasted it on the section being discussed on the document.</figcaption></figure><p>Pilot session also help us to see the technical issue that might rise during the session and address it before we go to with real participants. In one of our research where its’ setup requires us to moderate the session and take notes at the same time while moving around multiple rooms, initially we thought it was enough just to combine discussion guide and note taking template into one document. But after the pilot session we realised we still had difficulties to take notes. The document space was not enough for us to write the necessary insight from the respondents, while making the space bigger will make the document hard to navigate. So we tweaked the methods by attaching multiple stacks of post it to accommodate the amount of information needed to be noted.</p><h4>4. Have A Time Out and Adjust Your Material</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8u84z1cOL-4N5jrDXH9gSg.png" /><figcaption>Illustration by<a href="http://www.somiacx.com/"> Somia CX</a></figcaption></figure><p>Plan the research to at least have one break in the middle of the research will help the research a lot. Break in between session is important not only to give time to tidy up the documentation and avoid burn out but also to a good chance to learn from the interview findings and adjust our discussion guide and stimuli for the next ones. After several interviews, we will start hearing similar things and form patterns. From here on, the additional learning we get from additional interviews is diminishing in return. The couples of last interviews we will hear mostly the same thing and we waste our time. With a break, we can have time to reflect what we have learnt so far, and identify new questions that we need to answer from this insights. We then can adjust our discussion guide and stimuli to dig further on this extension set of questions. As such, we can gather more and deeper insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OCZXtFwWtYlOH1Ncf1AcFw.png" /><figcaption>One of the sessions in bot-assisted-medical-app research.</figcaption></figure><p>In one of Somia’s research around bot-assisted-medical-app for doctors, the initial the focus area of the research is to learn how the app can help doctors to take note of medical record within the app so they don’t have to do it manually. During our first part of the research (before the break) we found out doctors usually have a really tight schedule so they ask their nurses to help with the note taking. There is also a strict rules from the hospital that medical record can only be recorded using hospital-approved platform, making it hard for the app to be widely used. We also found new usage opportunities for the app: doctors often need to search medical information quickly to help with their diagnosis, but they need to filter information on google as they are not all come from medically trusted sources. We then tweaked the discussion guide to dig deeper around information search and create several stimuli to test concepts around quick search, group chats with medical colleagues, quick way to save information from various sources, and access to medical journals. Because of these changes, we managed to identify more relevant features for the app, pivot and test the new product direction within the same research.</p><p>Those are the tips, hopefully it can help your next research!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c11894f337d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/tips-to-sharpen-your-research-c11894f337d0">Tips to Sharpen Your Research</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hardware vs Software Product Testing]]></title>
            <link>https://medium.com/somiacx/hardware-vs-software-product-testing-7c61fb083ddf?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c61fb083ddf</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 03:43:27 GMT</pubDate>
            <atom:updated>2019-06-12T22:28:41.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ylsQfedi5Z89IWXyYPKDIw.jpeg" /></figure><p>As you might already know, Somia CX is a client based consultancy, therefore it’s natural for us to get various type of projects. It’s true not only for the scope of the projects, from just evaluating existing product until foundational research, but also from the industry and its product types. In this year quarter alone I’ve personally done 3 different scopes and products: Validating new food-related-type of service, Foundational research in music industry, and the most recent and for me personally the most interesting one: evaluating real functioning prototype in sanitaryware.</p><p>The last project is a follow up from series of researches in the last 3 years we’ve done with the client, from exploratory one where we ventured into multiple directions in the same area until real 1:1 functioning prototype where people can actually use the product. I realised there are ways where doing hardware related projects, especially sanitary one, are different. Here are two big findings that we found.</p><h3><strong>1. Preparing The Prototypes: Not Just Making It Clickable</strong></h3><p>In software based project, we usually use clickable prototypes where we can simulate real working product, by just using prototyping tools such as Invision or directly from the software creation tools such as Adobe XD or Figma. Depending on the complexity we can create the clickable in 1–3 days. We then let the participants to try the product using scenarios and get their feedbacks.</p><p>Just like in software based one, our goal is to evaluate and gather feedback from people who <em>actually try the product</em>. Since the sanitary product we test have water related function, we need to make the prototype to be connected to some water line, easy right? That is also what we initially thought.</p><ul><li><strong>Turning house into testing lab<br></strong>The first thing we need to do is finding the place where we can install the prototypes, that need to be mounted on the wall, this turns out to be a bit problematic. Since we don’t have a permanent space for hardware setup, we need to find one. It turns out there are limited place where you can install 8 different sanitary product setups without having your cash sucked up by the renovation budget. The solution: using fake walls to mount the prototypes so we don’t have to spend too much money on fixing the actual wall.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*XA5HWIe1JyRBdNLBbc-u7A.png" /><figcaption>Left: Fake walls used to mount prototypes. Right: On ground team preparing the fake walls</figcaption></figure><ul><li><strong>Not just about the prototypes</strong><br>When you do hardware related testing, there are aspect that could go wrong not from the prototypes itself <em>(well, there are, but more on that later) </em>but from the installation. So you better have on ground team that can help you right away to solve any problems rising. We had a team that help us from installing the prototypes until making sure the test goes smoothly from technical aspects. This team solved many issues that normally we won’t have in a controlled lab or simple clickable prototypes: unstable water pressure, water leaking, water tank sensor not working, water pipe suddenly undone, and many other technical problems. Just like our lovely printer, they can be naughty in the most important time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCeVR2ObU8p0v5IcBWoOWA.jpeg" /><figcaption>On ground team going up to water torrent in the roof to replace faulty water sensor</figcaption></figure><h3>2. Hardware Prototypes = Mechanical Bug</h3><p>We can set boundaries or limitation in software based product so we can focus the evaluation on certain features or journeys. It’s easy to do it via prototyping tools, just create hotspot and link all the page together. You can even simulates micro interaction like hanging navigation or some animation effects. You don’t have to actually code it to make it look ‘real’.</p><p>Just like the software based one, the prototype in hardware product also need to look ‘real’ so we can have a proper feedback from the participants, visually &amp; functionally. If by tapping a button water will come out, then prototype need to also do it. But then what set apart the prototypes from real launched product is the internal mechanism of it. Launched product usually has already considered the durability, reliability, maintenance, and assembly process. Meanwhile prototypes is usually still ‘hacked’ together to recreate the functionality, either by creating certain parts with cheaper material, using parts from other products, taping certain parts to hold it in place, or any other means to create the prototype so it can later be iterated efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MeyI7_KXxEHjXzgL2e8-vA.jpeg" /><figcaption>‘Behind the scene’ of the prototypes: hacked installation to recreate real functionality, one part of it went abruptly leaking just hours before the testing, forcing us to cut one prototype out from the water supply.</figcaption></figure><p>This ‘hacked’ together situation means sometimes during the evaluation time, it could fail<em>. </em>During our evaluation time, 3 out of 8 prototypes were faulty. One prototype had problem with its’ water supply part, it leaked everywhere so we had to cut it from the water line. One had problem with its mechanical trigger control since the trigger was taken from another product. One had problem with sensor trigger control. All of this happened the night before the evaluation days. A dedicated engineer from the client tried and managed to save only one with the sensor. It had to be reset using magnet after every time participant use it. With all participants had been booked for the next five days we adapted the the flow of the evaluation to make sure we still can get feedback for the rest of faulty prototypes. We covered those two and only uncover it after participants had tried other prototypes. We used it as a probing tools.</p><h3>Summary</h3><p>Testing hardware needs a different sets of preparation and longer time, since it has different complexity. We need to make sure we have all things considered when we do hardware related projects: suitable space, prepared technical aspect of the space &amp; good technical team. And last but not least, an alternate plan when things go south.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c61fb083ddf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/hardware-vs-software-product-testing-7c61fb083ddf">Hardware vs Software Product Testing</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learnings from working on digital financial solution in Indonesia]]></title>
            <link>https://medium.com/somiacx/learnings-from-working-on-digital-financial-solution-in-indonesia-e20892e0cfb5?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/e20892e0cfb5</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[financial]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Thu, 01 Feb 2018 10:01:01 GMT</pubDate>
            <atom:updated>2018-02-01T10:01:01.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNOqd1O4iGnPR7K56zzUfg.jpeg" /></figure><p>The first project related to finance that we did was 4 years ago, coming from an established bank. Ever since, we’ve been working on numerous projects in financial sector, both with banking institutions as well as non-banking players such as telecommunication, tech infrastructure, financing startup, transportation, and social crowdfunding.</p><p>It is fascinating to see wide variety of companies competing to offer financial solutions for the diverse target customers in Indonesia, especially in digital area. Even though each financial solution will be affected by different factors (organizational structure, technology, target market, etc.), we found there are a couple key things to consider:</p><ol><li><strong>First trial matters, words travel fast</strong></li></ol><p>Financial activity is a sensitive issue. Many people are reluctant to try new products in finance. People who are usually really open minded with new things could become conservative when it comes to money matter. Though mobile penetration in Indonesia is high, it doesn’t automatically translate to high penetration of financial services delivered through the digital platform. They could have made Youtube as their primary media source yet still go to the neighbourhood warung to buy phone balance.</p><p>Testing the solution as early as possible, as often as possible may help uncover people’s concerns on a new financial solution. We can explore whether the flow makes sense and whether the visual leads users to actions that they want to accomplish. Testing the concept before launching publicly is key because it allows potential users to try it without risking actual money. Further along the line, we need to make sure the system has no apparent bug that may impact the value of user’s money. The design of the system should also support undesired condition, e.g. slow and unreliable Internet connection, and provide fall-back mechanism if that happens.</p><p>Financial being a sensitive area, we can not emphasize more the importance of assuring smooth experience for people who try the actual product for the first time. Indonesian people are very social, giving high marks for influential factor through social circle. If users find their first time experience not pleasant, they are not only going to abandon the product, but also tell their peers not to use it, with full-blown emotion.</p><p>The chain of word of mouth in Indonesian society is remarkable. For example, in one of our research we met someone who moved all of her saving from her old bank to a new one simply because one neighbour told her that the long relative of this neighbour knew someone who lost his money in her old bank. And she passes on the story to others, even though she never experienced it herself. In some worse condition, the bad experience becomes ‘myth’ that is attached to the product which makes it really hard to recover the image.</p><p><strong>2. Dance between simplicity and security</strong></p><p>In most cases, people already have some ways to do whatever financial activity that is being offered by the new digital financial solution. If this new solution is answering the untapped needs that people only have a workaround to do it, then they will see it as an already much better alternative, as long as there is no fundamentally flawed flow. But things can get more complex if the target of the product already has a solid yet conventional methods of doing it. The new solution should be dramatically improving the process for users in order to convert. For example, let us take a look at the rising solution of digital payment that try to replace cash in day to day transaction.</p><p>Cash money as we know it has been around for quite a long time and it can handle much variety of transaction amount within its system. Paper and coin with different printed value are designed to do just that. Even though there are few drawback of the system such as crumpled and torn money or lack of small value for change, the overall system is simple to use.</p><p>Many digital payment solution promise to be faster and more reliable than cash, either through digital money in plastic cards or smartphone apps. This is true when all the payment are automatic or have a fixed amount like Commuter Line ticket and TransJakarta. But when it comes to dynamic small amount payment, things that often happen in day to day transaction, cash is still much faster and easier to use.</p><p>Imagine this scenario, you are in convenient store to buy a snack. Which one do you consider faster: take our wallet from our pocket and pay it in cash or wake up our phone, open the app, do whatever necessary to trigger the payment interface (could be OTP, QR code scanner or else), input the value and confirm the transaction? Or if you are using digital money in card, notice the extra steps the merchant needs to do to trigger the payment within their own POS system to be able to accommodate the card. Suddenly you already have several people behind because you are holding up the queue.</p><p>From our previous research this usually happens because of technology limitation and security purpose. Some new payment methods are not well integrated to the POS used by merchants and require them to perform extra steps to be able to accommodate the new methods. Throw some extra steps to make sure the system is robust and could not be tempered, and you have this complicated flow unbearable to use, either for the users or the merchants.</p><p>Limitation and security measure are always to be found, and it’s not something to be avoided. In fact, we should embrace these. Sit down with all the stakeholders involved and find ways to make it simpler. Then test it out the system through roleplay, enact the flow from both user and merchant side, see where the flow breaks down, find workaround, test it again and repeat until you find a good balance between the requirement (technology and security) and the ease of use. Only by actually trying the system you will know how good or bad the system is.</p><p><strong>3. Improve users’ daily life continuously</strong></p><p>Many digital financial solutions set aside certain amount of money to give people boosters to try their products. Usually these boosters come in form of discount, cash back, or gifts. Until certain degrees, people will react positively to these boosters, but then usually it fades.</p><p>Although it is a good in the beginning, booster alone is not enough to make people constantly use the new solutions. We need to have deep understanding of our potential users. See how they do their daily life. Learn how they do certain part of their day that are close to the product offering. Search the most relevant area where the products could show its features and at the same time improve the users’ life. So when the booster is gone, people already experience an improvement in their daily activities when using the products, and it is hard to justify coming back to life before the improvement.</p><p>For example, people will get a discounted ride when using Go-Pay within Go-Jek. But what they get is not only a price cut, but also eliminating the problem with drivers who don’t have small change, and saving some time if the drivers are kind enough to exchange their money with local vendor, or avoiding to grump to the drivers if users are forced to let go their change. Being able to skip that on a daily basis is huge. So even when the discounted price right know is actually on par with other online ojek platforms, many people stick with Go-Jek and using Go-Pay.</p><p><strong>Things to remember</strong></p><p>Financial activity is a sensitive issue for most people. It is a complex area that sometimes temps us to bypass the process and jump to what we consider a good solution for our users, while ignoring what users actually need. Understanding the behaviour of our target users is key and testing our product as early and often as possible is a must. Because if we do not handle this complexity early on, our users will. Don’t wait until users associate our product with bad experience to get us moving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e20892e0cfb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/learnings-from-working-on-digital-financial-solution-in-indonesia-e20892e0cfb5">Learnings from working on digital financial solution in Indonesia</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Indonesia UX Profession Report 2017 is Out!]]></title>
            <link>https://medium.com/somiacx/indonesia-ux-profession-report-2017-is-out-e61fbffebac6?source=rss-2d9f37899427------2</link>
            <guid isPermaLink="false">https://medium.com/p/e61fbffebac6</guid>
            <category><![CDATA[profession]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[indonesia]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[2017]]></category>
            <dc:creator><![CDATA[Ukasyah Qodratillah Ananda Putra]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 03:01:40 GMT</pubDate>
            <atom:updated>2017-10-11T03:01:40.051Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uIAIJLFqAizbmiwwHf0YXA.png" /></figure><p>Hi guys, I know it’s been a couple months since <a href="https://medium.com/u/42a2a3aedc3c">Somia Customer Experience</a> gathered your input regarding UX profession in Indonesia. We’re sorry we’ve been very busy and just got the time to finish the report for you all! We presented what we found in 7 chapters: Demographic, UX Maturity, UX in Organization, UX in Daily Life, Students, Hiring, and Love, Hate, &amp; The Future.</p><p><strong>Couple of highlights about the report:</strong></p><ul><li>Indonesia UX Industry are driven by Millennials, They are 79.1% of the UX practitioners!</li><li>Technical skills such as wireframing and prototyping are not among top 3 skills that considered important in the industry.</li><li>There is an increase in proportion in female UX practitioners, even though the industry is still male dominated.</li><li>Companies that put high importance in UX are shifting towards bigger UX team.</li><li>If you are looking about the salary standard, there is interesting distribution we found in the industry.</li></ul><p>For further details, jump directly to the report via Slideshare below or with PDF files that you can download in our <a href="http://goo.gl/6GLbZm"><strong>Gdrive folder</strong></a>. You can also find our previour reports from last year in that folder.</p><p><strong>Happy reading!</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F3EC3swJuh0ci4c&amp;url=https%3A%2F%2Fwww.slideshare.net%2Fsomiacx%2Fthe-state-of-ux-profession-in-indonesia-2017-80676055&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fthestateofuxprofessioninindonesia2017-171011024257-thumbnail-4.jpg%3Fcb%3D1507690054&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2d4797bd7ecc9bc5c17392ae180755a/href">https://medium.com/media/c2d4797bd7ecc9bc5c17392ae180755a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e61fbffebac6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/somiacx/indonesia-ux-profession-report-2017-is-out-e61fbffebac6">Indonesia UX Profession Report 2017 is Out!</a> was originally published in <a href="https://medium.com/somiacx">Somia CX Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>