<?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 KC Shiroma on Medium]]></title>
        <description><![CDATA[Stories by KC Shiroma on Medium]]></description>
        <link>https://medium.com/@kcshiroma?source=rss-ff3be77a49b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3GlydD1C2Nosy3Mv9dtANw.jpeg</url>
            <title>Stories by KC Shiroma on Medium</title>
            <link>https://medium.com/@kcshiroma?source=rss-ff3be77a49b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:43:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kcshiroma/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[Getting past the three research hurdles]]></title>
            <link>https://uxdesign.cc/getting-past-the-three-research-hurdles-f4a2c07b2e3d?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4a2c07b2e3d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Sun, 29 Aug 2021 15:55:56 GMT</pubDate>
            <atom:updated>2021-09-02T15:26:19.925Z</atom:updated>
            <content:encoded><![CDATA[<h4>UX Research — Surveys</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o2aDtY8GA3WFbt1c" /><figcaption>Photo by <a href="https://unsplash.com/@interactivesports?utm_source=medium&amp;utm_medium=referral">Interactive Sports</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Many businesses often have a lot of ideas on what products and services would be enticing to their clients. But without context and feedback from the end user (aka their clients), businesses may be blind to what their clients truly need. Surveys are one of the simplest ways to gather early and quick feedback. Even with its simplicity, it is sometimes difficult to do in the context of a bigger organization or with skeptical members of top management. In this article, I share three hurdles I faced when I conducted my research and some tips and resources that may become helpful to you.</p><h4><strong>Hurdle One: Handling Skepticism</strong></h4><p>There is a general skepticism about how valuable user research is. In my own experience as a UX Consultant, even in industries where top management is willing to pay for the service, there will be members of the team who are not convinced that it is worth the effort. Skepticism with regard to the value of user research is not a new topic. In fact, there are so many references you can look into on how to win stakeholders over.</p><ul><li>Christopher Nash from Dropbox Design wrote a Design Research <a href="https://dropbox.design/article/how-to-win-over-skeptics-with-qualitative-research">article</a> specifically on this topic.</li><li>This Quora thread has a good range of responses from people in the UX field. Read: <a href="https://www.quora.com/How-do-you-handle-it-when-people-are-sceptical-of-the-value-of-usability-research"><strong><em>How do you handle it when people are sceptical of the value of usability research?</em></strong></a></li></ul><p>I’d like to share my own experience. I vividly remember sitting in a room where one of the Department Heads was skeptical about the whole initiative. “It’s just a survey, why must we pay someone to do it? We’re deciding what to launch, why run a survey anyways?”</p><p>I explained that the survey was to gather feedback on the products they planned on offering. Since they had a variety of options to offer but were road-testing just a few to see how viable business is,<strong> it was worth getting early feedback to know if they were headed in the right direction.</strong></p><p>Despite the facts and statistics, the other members of the management team also wanted more assurance. They felt that they could not gather certain feedback or clarity because they did not have the time to conduct the research, thus they felt it best to hire someone who could.</p><p>The survey questions I prepared aimed to understand their profile, context and interest levels with the different products they had. I also offered my <strong>research as an opportunity for the business team to ask questions that they still have left unanswered. </strong>Upon giving them the chance, they shared what they wanted to know and that provided me an opportunity to share how we can make the insight gathered more robust if we try to learn more about their habits, understand other contexts that affect how they would eventually use the product/service.</p><p>People within the team became curious as to what sort of insights could be generated by the research. The hesitancy and skepticism faded because the planning stage was transparent, collaborative and open to <em>everyone’s</em> input. Because they gave their input on the questions, the ownership for the project became shared. I learned that sometimes, the skepticism is not just on the value of your research but on what your role is in relation to <em>their</em> job. It was no longer about an external consultant coming in and telling them that they were doing things wrong. It changed to an impression that someone else was coming in to help them learn more about their users.</p><h4><strong>Hurdle Two: Conducting the Survey</strong></h4><p>When surveys are well done, you can get a lot of valuable information. I have listed some great references to help you craft your survey:</p><ul><li>Nielsen Norman Group’s <a href="https://www.nngroup.com/articles/qualitative-surveys/"><em>28 tips for Creating Great Qualitative Surveys</em></a></li><li>UX Mastery’s tips on Creating Effective Surveys in their article <a href="https://uxmastery.com/better-user-research-through-surveys/"><em>Better User Research through Surveys</em></a></li><li>Sarah Doody shares a tip about using first person questions to get better survey insights in this <a href="https://www.invisionapp.com/inside-design/ux-user-research-surveys/"><em>article</em></a>.</li></ul><p>As suggested by NNg in the article above, it’s best to use a platform that’s already working. Most of these platforms (SurveyMonkey, Typeform etc.) allow you to set up logic for surveys. This helps you distill insights better and prevent clashing answers.</p><p>But there are other things that affect how people answer your survey. Literacy affects survey validity. In an instance when the business team explained that a lot of their potential users were not literate in English and not as tech-savvy, I decided to <strong>conduct the survey in a more approachable way</strong>.</p><p>Instead of an email link from someone they did not know, I asked for a coffee break with the respondents. I asked that a contact person from the business would make the introduction but at the venue, I took over. I introduced myself, told them who I was and explained that I was asking them to participate in a survey that should not take more than 15 minutes of their time. I gave assurance that the survey was not in any way going to affect their performance appraisals.</p><p>Instantly, some of the people in the room laughed. “We get so many feedback surveys that we just give the highest rating and finish it.” I thought so too. I handed printed surveys with translations to everyone and I asked them to let me know if they did not understand any of the terms presented and if any of the options in the survey did not make sense to them.</p><p><strong>Being smart with how you conduct research is not just with how you use your resources or plan your surveys. It is also about how empathetic you are to your respondents’ context</strong>. It is not just a matter of asking the right questions but also asking them in a format that your respondents can access. It is asking them in place where they feel safe, in words that they can understand and using tools that they can use with ease.</p><p><strong>Ensure that the words that you choose can be understood. More importantly, provide opportunity for comments or clarification.</strong> In the same project, it was helpful for me to be present during the data gathering because the respondents had a chance to clarify certain words that they hadn’t encountered before directly instead of guessing through their survey.</p><h4><strong>Hurdle Three: Sharing the Insights</strong></h4><p>Once you finish gathering your insights, you will have to share what you have learned. <strong>Sharing insight is part distilling and part visually communicating.</strong> Post data-gathering, you will have two types of insights: those that are directly related to the questions you asked and those that are indicative of other considerations affecting your users.</p><p><strong>Presenting the direct insights must be summarized in a way that is understandable by anyone who would look at your deck.</strong> Depending on the information you can summarize this into quotes, tables or data visualizations like pie-charts, bar graphs and word clouds.</p><p>Check out resources such as:</p><ul><li><a href="https://datavizproject.com/">DataViz Project</a></li><li><a href="https://www.youtube.com/watch?v=so9EJoQJc-0">Nancy Duarte</a>’s videos and books for inspiration.</li></ul><p>Equally or more important for people who will read your research, would be the insights unearthed that show relationships and factors affecting the end user’s context of use.</p><p>Do not filter this information even if you feel that some of them manifest stereotypes. <strong>As a researcher, it important to share what you find out and enable teams that will use this research to design experiences and products with these contexts in mind.</strong></p><p>As much as I can, I also create one-page summaries that can easily be attached in an email or printed to distribute in a meeting so that the insights can be shared.</p><p><strong>End note: </strong>Getting feedback from your end users is a worthwhile initiative. In my experience, I experienced a few hurdles but ultimately, the client was happy with the insights and saw the value of doing research. Some surveys may validate, others may change your course, while some present new opportunities. In my case, certain insights prompted my client to pivot their strategy because what they had assumed to be true about their users turned out to be false. They prioritized other ideas and have done well.</p><p>In fact, there are countless references about how UX Research is worth doing not just because of ROI but also because of cost-savings. See some references below:</p><ul><li>MarketPath’s<em> </em><a href="https://www.marketpath.com/blog/investing-in-ux-will-save-business-money-time"><em>Investing in UX will save business money and time</em></a></li><li>User Testing’s <a href="https://www.usertesting.com/blog/invest-in-ux"><em>3 Practical Reasons to Invest in UX Research and Design</em></a></li><li>Toptal’s <a href="https://www.toptal.com/designers/ux/roi-of-ux-redesign-case-studies"><em>The True ROI of UX Design: B2B Redesign Case Studies</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4a2c07b2e3d" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/getting-past-the-three-research-hurdles-f4a2c07b2e3d">Getting past the three research hurdles</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A quarter past redesign: learnings from 3 months working on a mobile app]]></title>
            <link>https://uxdesign.cc/a-quarter-past-redesign-learnings-from-3-months-working-on-a-mobile-app-d85376cf59a7?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d85376cf59a7</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[white-label]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 11:34:22 GMT</pubDate>
            <atom:updated>2020-10-20T14:27:37.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Knx2R1SOW1-l_xl5o2Un2Q.jpeg" /><figcaption>Actual photo of my work note book where I write my “End of Month Reflections”</figcaption></figure><h3><strong>A quarter past redesign: learnings from 3 months of working on a white-label mobile app</strong></h3><h4>The pandemic paved the way for a career pivot as a UX designer.</h4><h4>Starting point: a Career Pivot.</h4><p>When the pandemic broke out, I had no choice but to pivot my career. I was working as a UX Consultant with many discovery phase research work (service safaris, field research, contextual inquiries, etc). A lot of my projects and plans were affected due to the lack of mobility, the rigid quarantine measures, and the need to cut budgets. As difficult as it was to see so many potential projects and plans get put on the back burner, it was what it was and I had to move on.</p><p>Not long after, an offer to design for a white label mobile application came. While I enjoyed the design and prototype process, most of my past projects asked me to do more of the UX research work. This was a new and welcome challenge. It was time to put to further practice what I talked about.</p><p>I was lucky to come in at a phase when they were considering a redesign. More than 3 months into the role and just recently handing over my design to the developers, these are some things I’ve learned:</p><h3>1. Redesigns are every new designer&#39;s dream but also the development team’s nightmare.</h3><p>Fresh into my role, I was asked to redesign the check-out flow. Another one of my first tasks involved looking through all the current implementations of the application and see points of improvement to base the app redesign on. I wanted to make the fonts and colors consistent, I also wanted to change how the products were presented and I wanted an overhaul to the checkout. My manager and the CEO loved the ideas. I brought in fresh ideas and pointed out some things they didn’t notice since they’ve been with the app for too long. So things were approved. But! I headed back to the drawing board after presenting it to the development team. I soon realized that a number of my designs needed hard coding which meant longer development time than what was planned. While the majority of my designs were passed to development, there were a few parts of my design that we had to tweak in the interest of narrowing down to the essentials and lessening development time.</p><p><strong>This could have been avoided if we had included developers in the design process earlier. </strong>Instead of going through 2–3 iterations of the design and then running them by the developers at the end only to find out, it couldn’t work with the timeline. I had to work smarter and collaborate.</p><p>Since we had some outsourced developers, I had to make sure that my design followed the timelines they had agreed on. As this was something agreed upon before I joined the team, this meant I had to adjust to that timeline. There was no room for an entire process overhaul.</p><p>I was lucky that the problem was fixed very simply. <strong>In fact, it was a matter of opening communication lines for better coordination and collaboration.</strong> I was introduced to the developers and added to a Slack group. Whenever I came up with a concept, I’d easily ping the developer assigned for feedback before I presented it to my manager and CEO. This gave me a better understanding of what was feasible, what could be done but required a few more days, and what was difficult to integrate. This also helped my manager and CEO make executive decisions (a.k.a. spend more resources to develop a certain feature).</p><h3>2. Don&#39;t forget that you support and enable your clients in their work.</h3><p>As a white label application provider, you essentially give your clients tools to better their business operations.</p><blockquote>You have to keep in mind that you support and enable your clients to do their work faster and better.</blockquote><p>This doesn’t mean you give them an inflexible template. <strong>Context-specific considerations like related to business, politics, religion, etc. affect how certain parts of your application are designed. </strong>Even if something is white labeled there are some customizations that need to happen due to context.</p><p>In the past, I had to come up with a different set of banking icons for a finance client because they said that: <em>“Piggy banks were not the best image to use when the majority of their clients were Muslims. It felt rude and more reasonable to change the image to olive trees or money bags.”</em></p><p>Another time, we had to change how a cart computed the total cost at check-out because Country A had different laws on taxation from Country B.</p><p>Customizations can come in many forms: visual or structural. But my last (and favorite example), the customization that had to happen was more on improving the diversity of icons that were used in the application. (Read: <a href="https://blog.iconfinder.com/the-issue-of-diversity-in-icon-design-e48100e11943">The issue of diversity in icon design</a> by Monica Martei)</p><p>A team I was mentoring at that time, was designing an application focused on helping women save money. It was a B2B solution. How they branded it showed promise. In fact, a number of businesses employing mostly women had signed to include it as part of their employee benefits.</p><p>However, during testing, the icons that they used bothered their target users. The icons used were all male. When users selected their occupation, only “stay at home mom” and “nurse” used female icons. “Business owner”, “Teacher”, “Lawyer” all had male icons/avatars.</p><p>While this seems like a small detail to some, remember, this was an app that focused on financial solutions for women. The research that we conducted showed that it affected how they felt about using the application.</p><p>In fact, 92% of the respondents mentioned during the debriefing that “it would be better if the images were female”. There was even one individual who left a strongly worded comment that said <em>“You need to think of what subtle messages you make. This is an app for women, why are the professionals male?”</em></p><p>You also have to accept and understand that <strong>it is your responsibility to design and develop your application in a way that is compliant and inclusive to the social, political—and even, geographic— context.</strong> Otherwise, that would entail another level of tweaking on your client’s end that delay them from actually using your product!</p><h3>3. Simplicity and consistency—always.</h3><p>A white label application means that there are a number of components that will be rebranded and possibly even translated into a different language. You need to make sure that you don’t over complicate your design with wild colors or overly thin fonts that hinder accessibility. You also need to accommodate the possibility that a 2-line sentence in English might not be the same when it gets translated to another language. Keep visual and verbal components simple, concise, and consistent. (This applies to the tone and brevity of your interface&#39;s content.)</p><h3>4. Familiarity breeds comprehension.</h3><p>Applications use icons to help users understand what a button for. The icons that you use should help users understand what they’re for without having to exert so much effort in interpreting them. (Read: <a href="https://www.nngroup.com/articles/bad-icons/">Bad Icons</a> by Nielsen Norman Group)</p><p>As much as possible, use text labels with your icon. (Read: <a href="https://www.nngroup.com/articles/icon-usability/">Icon Usability</a> by Nielsen Norman Group)</p><p>When you do not use text labels, avoid unfamiliar images or icons. Go with what most people can understand otherwise you make it less usable. (Read: <a href="https://www.smashingmagazine.com/2016/10/icons-as-part-of-a-great-user-experience/">Icons as part of great user experience</a> by Smashing Magazine and <a href="https://uxdesign.cc/7-principles-of-icon-design-e7187539e4a2">7 Principles of Icon Design </a>by Helena Zhang on UX Collective)</p><h3>Endnote: Work in progress, still learning...</h3><p>It’s been quite a different experience designing for a B2B2C application. Even more different when you design for a company that is a white label provider to clients in various regions with brick and mortar stores. You have a lot more considerations when you build and you have to keep your mind open to context-specific scenarios.</p><p>Along the way, things can get confusing when you have a lot of input from a number of clients. But I can say that it&#39;s a good kind of chaos!</p><p>I’m still getting the hang of things but documenting discussions, communicating with the product team, and having a priority list for each build has helped me stay sane and on track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*V76tqQ-o3Cb9KkpJ" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d85376cf59a7" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-quarter-past-redesign-learnings-from-3-months-working-on-a-mobile-app-d85376cf59a7">A quarter past redesign: learnings from 3 months working on a mobile app</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on the emotional aspects of UX Research]]></title>
            <link>https://uxdesign.cc/the-emotional-aspects-of-research-f28d0329087e?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f28d0329087e</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Mon, 17 Feb 2020 02:56:54 GMT</pubDate>
            <atom:updated>2020-02-18T03:08:26.675Z</atom:updated>
            <content:encoded><![CDATA[<h4>2019 Last Quarter (Q4) UX Review</h4><p>It’s already February! Just when I thought I’d have time to properly reflect on the last quarter of the year, January became a lot busier than I expected. I’ll keep this last review for 2019 less about processes and more about the emotional aspects that affect research findings — irrationality, biases, and labels.</p><p>These three factors affect products, services, opinions and the dynamics within a team creating it. They affect the “truths” that you have to accept as you design products and services.</p><h4>#1. People, despite how logical we believe ourselves to be, are irrational.</h4><p>There are enough books to tell you that we decide largely by emotions than with facts or figures. In fact, a lot of things we do are irrational and habitual. (I would recommend reading <a href="http://danariely.com/books/predictably-irrational/"><em>Predictably Irrational</em></a><em> </em>if you would want to know more on the topic).</p><p>You need to recognize the disconnect between what makes sense and the fact that we humans are ‘predictably irrational’. This is a reality that you have to accept in life and be aware of as you do user research.</p><p>You will sometimes want to pull your hair out trying to get to a logical answer. “But why?!”</p><p>You have to stop trying to box people into logical conclusions because oftentimes, the answer you are looking for will not be the answer you get.</p><figure><img alt="An illustration of two paths. A path of reason which is straight and a path led by the heart with more turns and stops." src="https://cdn-images-1.medium.com/max/1024/1*zQMAAkWYa0tbCo_1SKjcaw.png" /><figcaption><strong>While getting to point B from A may seem to be straightforward, what happens, in reality, isn’t like that. </strong><em>Illustration by </em><a href="https://dribbble.com/kcshiroma"><em>KC Shiroma</em></a></figcaption></figure><p>People do not feel the need to justify their choices with statistics, scientific research. People will justify their choices with emotions. Emotions that may not always be parallel to what they say or the values that you know they hold. <strong>It is hard to understand but this irony is a part of reality.</strong></p><p>For instance, a financial app interviewed successful women about their financial behaviors. They assumed that given their background and the fact that their product was about investments and savings, these women were the right target to be early adopters. They found out that they did not have better financial habits than women who were earning less. Furthermore, there was hardly any difference between the percentage saved by women in less educated demographics. The icing on the cake? Aside from not investing, these women were also not saving money.</p><p>They ran the same interviews with a different group and the results in their interviews were no different. And yet, the team was hell-bent to find the reason why. <em>(Note the confirmation bias here, big research no-no!)</em></p><figure><img alt="Illustration of mother hugging her daughter with quote “My top priority is not my but her well-being.”" src="https://cdn-images-1.medium.com/max/1024/1*dvZAbynuVmcPDpbgRbTLeQ.png" /><figcaption><strong>While logic would say they should put themselves first, Mothers will be mothers. They put themselves last. </strong>Illustration by <a href="https://dribbble.com/kcshiroma">KC Shiroma</a></figcaption></figure><p>The reality was that despite their expertise, knowledge, and education, these women had one thing in common that trumped all logic. The fact that they were MOTHERS. When it comes to mothers, children come first. Regardless of race, social status, income, educational level — women would put themselves last and as a result, rarely have the resources to practice healthy financial behaviors (saving, investing etc.).</p><h4>#2. Bias is everywhere if you only recognized it.</h4><p>Even as researchers, there are biases that you have that will influence how you accept information.</p><blockquote>In the example above, the researcher on the team questioned the data multiple times because “it <strong>doesn’t make sense </strong>how top tier executives in financial companies would not practice smart financial habits.”</blockquote><p>This reflected her world view as clear-cut: IF X is then Y. IF you work in finance then you will know what you have to do to be financially smart.</p><p>This confirmation bias misled her because that was simply not the case. Culture, socioeconomic reality, gender roles, family roles, priorities can override everything someone has been taught. There are also societal biases that also affect behaviors.</p><p>In fact, just look at the parallels and you’ll notice that a simple difference in gender can generate a different opinion. (This <a href="https://www.youtube.com/watch?v=luLkfXixBpM">Pantene commercial</a> illustrates this example so well.) A dad working at home is ‘dedicated’. A mom working long hours was shown as ‘selfish’. Same context, different gender, different feedback. Why? Biases!</p><p>There are roles people expect you to fulfill. The mother should be caring for her child and leaving work. The double standards leave a bitter taste, but! It’s there…</p><p>From a purely logical point of view, you think the considerations are black and white. That the variables already preempt the conclusion. Yet, you have women leading financial companies without savings of their own. We have a tendency to act based on emotions, vulnerabilities, fears, feelings, societal roles, aspirations.</p><p><strong>Recognize the vulnerabilities that shape these biases and you will have more context into the decisions people make.</strong></p><figure><img alt="An illustration of a scale—one basket holds emotional symbols the other logic. The emotional basket weighs down the scale." src="https://cdn-images-1.medium.com/max/1024/1*_plU5OURDCjz_drgRlZoRQ.png" /><figcaption><strong>How much weight do emotions, wants, vulnerabilities and responsibilities have on a person’s decision?</strong> Illustration by <a href="https://dribbble.com/kcshiroma">KC Shiroma</a></figcaption></figure><p>Working moms don’t want to be seen as “successful in career but a failure as a parent” and they would rather “keep everyone happy” even if that means failing to make themselves financially secure by spending for everyone else.</p><p>They feel a strong need to do good by everyone almost as if these were “stakeholders”. In fact, for a number of working moms, their “stakeholders” are not just at work but the parents, in-laws, spouse, children, co-parents that they appease in one way or another. Some of those things they spent on included: trips for in-laws, gifts, and gadgets for their family. <strong>At the core of what seems to be “pure stupidity” is a “self-less vulnerability”.</strong></p><p>When you lead with your head, you will often find yourself going in the same direction as you planned. When you follow your heart, expect circles and a detour. Recognize that vulnerability and see how it dramatically shifts decisions. These shifts can also influence why users use or don’t use your products.</p><p>They LOVE the concept of investing and saving made easy — but they never converted into users…because they decided to give that money to a child’s new gadget, an upcoming family trip etc.</p><figure><img alt="Illustration of a girl with a colorful hair style. One side shows judgement of others and the other side her true reality." src="https://cdn-images-1.medium.com/max/1024/1*ItJv2GlHZ_0X350Tf8wefQ.png" /><figcaption><strong><em>We know that there is truth beyond labels—but, do we remember not to judge a book by its cover? </em></strong><em>Illustration by </em><a href="https://dribbble.com/shots/10107896-A-Hairy-Situation-Style-Expression-and-Reality?utm_source=Clipboard_Shot&amp;utm_campaign=kcshiroma&amp;utm_content=A%20Hairy%20Situation%3A%20Style%20Expression%20and%20Reality&amp;utm_medium=Social_Share"><em>KC Shiroma</em></a></figcaption></figure><h4>#3. LASTLY, Labels.</h4><p>Labels are how people try to make sense of the world. They attach words to things and create meaning. They are just that — an attempt to define something so everyone else knows what it is. But labels are not always cohesive and complete.</p><blockquote><strong>In fact, labels can be incredibly limiting or incredibly empowering.</strong></blockquote><p>Whenever I do user research, I come across a number of demographics. It became more apparent to me how differences in the modern world are more visible with the interconnectedness of people and social media. When your family isn’t cookie-cutter it’s known.</p><p>An example — Single parents respondents. There are a lot of societies that still put some form of stigma with single parents. That some of my single-parent respondents in the past felt that they “failed” as a parent because they are single parents. The effect of having that <em>one</em> word before “parent” that causes so much discomfort and opens them to a lot of judgment.</p><p>When you would ask some single parents to describe themselves. The tone they would use to describe themselves as single-parent carries a more hushed tone than when they speak of their age, their children and their occupation.</p><p>One instance, a lovely woman said in one of my interviews “Well, I’m a single parent. (Shifts gaze away) I think I have to say that since this is some form of study on insurance and you know they ask about beneficiaries…”</p><p>I said: “Okay, but could you tell me something else about YOU?” She looked at me as if she was confirming if I had passed judgment. Then she sat for a moment and thought. Her posture shifted then she said:</p><blockquote>“I am the breadwinner of my family (Says it proudly). I actually raised three girls on my own and I am a two-time cancer survivor.”</blockquote><p>The tone and mood of the interview changed. I became more aware of the effect of how refocusing on something other than a label would lead to a more open interview in the interviews after. Labels, affect not only how you perceive the world but also how people present themselves to you.</p><p>This happened a few more times during my research phase. The more I shifted the questions <em>away </em>from their civil status, the more information I was able to learn about them — their achievements, life stories, and some quirky anecdotes.</p><p><strong>Research is as much analyzing what goes on in one’s head (mental models, thought process) as it is the heart (fears, aspirations, hopes.).</strong></p><p>When finding your insight remember to be human and that being human means recognizing and being empathetic that people are influenced by factors beyond the mind.</p><p>No matter how advanced and complex societies become, people are people. Aim for a more complex understanding of why people do the things they do and what shapes their decisions because this unpredictability is what makes us human — vulnerable, connected and emotional.</p><p><em>I wrote these quarterly reviews during a year of me trying to make sense of the things and insights I gathered. It was also a year of me presenting information as logically as I could to companies. In the process of doing discovery phase research for companies, I also shared what I learned here on Medium. In the blip of time that was 2019, thank you for taking the time to read my thoughts.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f28d0329087e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-emotional-aspects-of-research-f28d0329087e">Reflections on the emotional aspects of UX Research</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Management, Metrics, and Methods.]]></title>
            <link>https://uxdesign.cc/2019-third-quarter-q3-ux-review-management-metrics-and-methods-670527d4ff75?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/670527d4ff75</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Sun, 03 Nov 2019 05:31:27 GMT</pubDate>
            <atom:updated>2020-02-18T03:18:21.592Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XXoKVS3CXEKHk03hG6LxjA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>2019 Third Quarter (Q3) UX Review</h4><h3>Management, Metrics, and Methods for your UX Projects.</h3><p>Time has flown by. Q3 has passed and soon, this decade will be over.<em> </em>(<em>If you haven’t figured, 2019 is the end of </em><strong><em>this</em></strong><em> decade! </em>😁)</p><p>I have to share that this quarter has been much more challenging and also more fulfilling than the previous two quarters. (In case you’re interested to read my past stories, you can find my Q1 UX Review <a href="https://medium.com/@kcshiroma/2019-first-quarter-q1-ux-review-11b10626bb3a">here</a> and my Q2 UX review <a href="https://medium.com/@kcshiroma/2019-second-quarter-q2-ux-review-6d5f3800a719">here</a>.)</p><p><em>How was it more challenging? </em>It was my first time to do research independent of an organization and also my first time to be responsible for all business aspects.</p><h4>That said, hands down to how freelancers hustle 🙌🏼</h4><p>I can joke that I matured faster in the past quarter than I have the past 3 years. The maturity that you get when you become independent is true. There is no safety net when you operate on your own. You will have to bootstrap, manage finances, manage time and resources while building your portfolio. I have to give it to people have worked as Consultants or Freelancers — especially those who have worked as such for years — <strong>they know how to hustle</strong>.</p><p>Honestly, I know I have had it easier because I have a partner who complements my skill set, EQ and industry knowledge. Those who work completely independently have to hustle for their network, knowledge, and resources. It’s no joke and I have mad respect for those who do great work remotely and independently.</p><p>That said, I would like to move forward with this story and share three (3) key learnings I’ve had this past quarter.</p><h4>#1. Management buy-in in a UX Project is about so much more than project approval. 🙊</h4><p>It is a common challenge to get management support/executive buy-in for UX projects. Even in<a href="http://info.userzoom.com/UX-Enterprise-Survey-2019.html"> UserZoom’s State of UX in the Enterprise 2019</a> report, this is still one of the most challenging parts of the UX research process. Executive-level support is critical to getting the project going but remember that your UX endeavor should be as valuable to those executive-level managers.</p><p>One of the conversations I would never forget was with a past C-level executive whom I worked with for multiple projects over several months. All the UX research activities were inputs not just to validate product concepts but to push a bigger strategy to move the corporation into even greater performance metrics. UX Research should not just be reports and recommendations but valuable and useful inputs to the business. Having a wider view of UX for the business influences your research design and the lifetime purpose it fulfills — will it be a set of recommendations to apply for the next sprint or will this be strategic inputs for the business in the years to come?</p><h4>#2. Know the metrics they’re looking for — and make sure they’re useful. 📊</h4><p>I’ve seen this mistake made by start-ups I mentor and also past projects I’ve worked on. Before you focus on a certain metric, understand what exactly you are trying to measure. Output and value of that output are much more important than checking off a type of measurement from a list.</p><p>I gave these three tips to a start-up I’ve mentored a few weeks back:</p><ul><li><strong>Gauge objectives and create metrics based on them. </strong>—<em> The Father of Modern Managemen</em>t,<a href="https://www.business.com/articles/management-theory-of-peter-drucker/"> Peter Drucker</a>, is famous for saying<em> </em>that<em> </em><strong><em>“What gets measured gets managed</em>.”</strong> If you can’t measure it, you can’t improve it. If you don’t know know what you’re trying to measure, then there’s no way of achieving “it”. You have to be clear on what you’re trying to achieve if you want to get anywhere with your project.</li></ul><p><em>I suppose, I should provide more context to this advice.</em> The team that asked for a consultation wanted to improve their process turnover and also achieve better reviews. However, they did not have benchmarks on what their current performance was, what the ideal number was and furthermore, they did not have a way to measure the reviews they would use for improvements. They had a desire to improve but neither method nor metric for actually improving.</p><ul><li><strong>Don’t forget the qualitative story — understand the underlying need/s </strong>— Your numbers are quantitative information but remember that your metrics are influenced by factors other than logic. Make sure that certain aspects of your measurement tool helps give you context to the different metrics you are trying to measure.</li></ul><p>Top management will often ask “Why is that the case?”, “Why do you think that happened?”. These are individuals very sharp with patterns when they see numbers. Having questions that give context to the why gives more dimension and value to your research.</p><ul><li><strong>Keep metrics sound and justified.</strong> — Applied research may not be as strict as academic research that will demand you to hire a statistician to compute for the validity, margin of error and soundness of your research design. There is more leniency by way of having a smaller sample but this does not give you a free pass to be arbitrary with your research numbers. Look into past research design and remember bare minimums when it comes to certain methods. Also, <strong>be fair when you present your metrics. </strong>One of my past NGO bosses reminded me to prioritize integrity not impressiveness when presenting metrics and data. If sample sizes are small, don’t mislead with percentages. If research design veers away from usual frameworks make sure that this has been agreed upon by everyone involved.</li></ul><p>On that note, the last learning I would like to share from this quarter is:</p><h4>#3. Best case practices will not always be good for you/your organization/your product. Be careful when using them as references for your project method/s. They’re nice — but nice is different than good [for <em>your</em> project]. 🔍</h4><p>This is something to remember when you follow methods for research and/or product design. Instead of being very strict with methods, keep in mind the organizational structure, the research objectives and the strategies affect how you plan your research or design your product.</p><p>Take it from how researchers would use conceptual frameworks to map out actions required in the study. It helps in the process of discovery, setting scope and limitations as well as groundwork for future research. It helps with analysis. It also helps you adapt future research to answer questions not answered in this scope of research. The beauty of applied research is that you get to take context, industry, and business resources into a research design without having to go through lengthy literature reviews. So keep your organization in mind. Keep in mind that best case practices may not be the best case for you.</p><p><em>Thank you for reading!</em></p><p><em>If you liked the article, please leave a clap 👏🏼(you can clap more than once, by the way!). You can go ahead and share it with people who’d be interested. </em>😁 <em>If you have any questions feel free to leave a comment or email at ux.kazumi@gmail.com ✉️</em></p><p><em>If this is your first time to read one of my stories — Why, Hello! 👋🏼 I’m KC, I’m a UX Consultant and I write about my experiences and learnings from the UX industry each quarter.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=670527d4ff75" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/2019-third-quarter-q3-ux-review-management-metrics-and-methods-670527d4ff75">Management, Metrics, and Methods.</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s be honest: not everyone is a designer — and that’s okay]]></title>
            <link>https://uxdesign.cc/lets-be-honest-not-everyone-is-a-designer-and-that-s-okay-318159e6c742?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/318159e6c742</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 03:31:01 GMT</pubDate>
            <atom:updated>2019-07-17T23:33:43.085Z</atom:updated>
            <content:encoded><![CDATA[<h3>Let’s be honest: not everyone is a designer — and that’s okay</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RtBwzt0zaTmrC4Mx" /><figcaption>Photo by <a href="https://unsplash.com/@stayandroam?utm_source=medium&amp;utm_medium=referral">Gemma Evans</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Anyone can be but not everyone is. I disagree with the idea that everyone is a designer. Let’s be clear on how we <strong>define</strong> design and do reality checks on the <strong>value</strong> of the work that we do and <em>how</em> we do it.</p><p>I’ve noticed more and more content and workshops that happily tell you something along the lines of:</p><blockquote><em>“You’re a designer! Don’t believe me? Well, did you make a decision that helped you solve a problem? No? Hmm… You probably decided to schedule your day so that you will be able to finish what you need to do.</em></blockquote><blockquote><em>You made a decision with a </em><strong><em>purpose</em></strong><em>. You designed your day. That means, you’re a designer. All of us are designers.”</em></blockquote><p>💥Stop! 💥</p><p>While it’s encouraging to hear that <em>everyone</em> is a designer. I find it unrealistic and somewhat shallow to say <em>everyone</em> is a designer. Are we happy to hear that we are a designer? Are we happy because we felt we could not be one before because we are not artistically inclined? Is this new definition of design so much better because it’s more “inclusive”? Is that why we <em>celebrate </em>it?</p><h3>Let’s take a step back, what do we mean when we say “design”?</h3><p>By definition, design means to do or plan something with a specific purpose in mind. Design is not being able to make a pretty drawing or be able to choose the best colour for your &lt;insert output here&gt;. Design is more <strong>purposeful</strong>.</p><blockquote><em>D</em><strong><em>esign</em></strong></blockquote><blockquote><em>• do or plan (something) with a specific purpose in mind: [with object and infinitive] : the tax changes were designed to stimulate economic growth.</em></blockquote><p>So going back, if we follow that definition, then <em>yes, </em>someone creating a schedule can be “designing. But if we’re honest with ourselves we know what we mean when we say ‘designers’.</p><p>We know that it is not just anyone with decision making capacity. It’s also more than just someone who can make something look “pretty”.</p><p>This is a strong opinion that may seem contrary to the very encouraging tone that a lot of UX or Design Thinking workshops have. But, here’s the reality, <strong>not everyone is a designer</strong>.</p><h3>Reality Check: Not everyone can ‘design’ in the first place.</h3><p>Let’s be clear on what we mean by ‘design’. Design, in my opinion, requires intentionality <strong>and</strong> impact. There is a type of designer that we refer to when we think of ‘designing’ for products or services.</p><p>When we say we want ‘designers’, we want <em>product</em> designers not just people who feel empowered to be creative problem solvers. <strong>We want people who can take insights from users and translate that into an output — someone who can use insight to intentionally create solutions with impact in mind.</strong></p><h3>🏁Let’s define ‘Design’ Better.🏁</h3><p>That said, let’s respect the word ‘Design’ and use it to mean something with depth <strong>and</strong> purpose. My favourite definition of design is Jared Spool’s.</p><blockquote><strong><em>“Design is the rendering of intent.” — Jared Spool</em></strong></blockquote><p>Designing the user’s experience entails more than just knowing the definitions of design or being able to encourage people. How you <em>design </em>something <em>influences</em> lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jh7xfEUrpJXlqQxV.png" /><figcaption>There are so many quotes that define “Design’. This is my favourite. <a href="https://twitter.com/jmspool/status/992412455807614976?lang=en">https://twitter.com/jmspool/status/992412455807614976?lang=en</a></figcaption></figure><p>Design influences lives because we can design an experience to be less frustrating. We can make life easier to live — by <strong><em>designing</em></strong> it. 😉</p><h3>Reality Check: Design as an exercise is different from designing an experience.</h3><p>Anyone can draw a stick figure. You can involve anyone in a creative exercise (ideation, design sprints) but not everyone can <strong><em>create</em></strong> something. Furthermore, not a lot of people can create something that is valuable, usable, desirable and beautiful.</p><p>If it need be said, facilitating a workshop does not make you a designer unless you know how to translate those ideas into strategy and actionable items outside the workshop. With each distinct phase of the product design process — we sharpen the definition and expectation of what a designer is (and is not).</p><p>Which brings me to my next point:</p><h3>Reality Check: It’s easily to mistake encouragement for subject matter expertise.</h3><p>With the boom of Design Thinking, HCD and UX, being “the problem solving type of designer” is the new shiny new toy. It is fantastic to say you “solve real problems” — but be careful with the encouragement you give/receive. It doesn’t place you a cut above the rest just because you have a different perspective of design.</p><p>Encouragement is great, fun HCD workshops refresh you from your usual work day too — but one workshop does not make you a designer. Neither does feeling empowered.<strong> Let creativity and capacity to craft experiences go hand-in-hand when we refer to a “designer”.</strong></p><p>You are what you can create.</p><h3>Reality Check: Not everyone has to be a designer to be involved in the creation process.</h3><p>Sometimes it’s not even the design or the definition that’s the problem. It’s how we craft our understanding of who needs to be part of the creation process.</p><ul><li>Who do we isolate when we work? Why?</li><li>Who do we isolate when we work with other teams? On what basis?</li></ul><p>If your reason is because they have a mindset different from your new “refined and impactful” perspective of design, then you’re a bottleneck.</p><p>If I were to give a candid response to that, I’d say that is a useless superiority complex. It is a cliquish behaviour that will prevent you from knowing how to work with different people and how to be strategic with the different people you involve. Do <strong>not</strong> be that type of person.</p><h3>Reality check: There are limits to what you can do and that’s okay. In reality, you *have* to work with a variety of individuals.</h3><p>Part of being a designer also involves knowing what you are good at and who you need to talk to. Knowing how to get stakeholder briefs and client briefs are just as important to your design process. It is important to know who you design for and the business goals that frame how you will proceed with your insights and ideas.</p><p><strong>Furthermore, you do not need everyone to be designers.</strong></p><p>In fact, you need people who are not designers. The critical stakeholders to your product have domain, industry and product expertise that you may not know of. They probably do not know the methods that you know but they keep the business alive as you design. Do not isolate someone who does not fall into your definition of design. Be mature and critical. Outside of people as inspired to design as you, <strong>who knows the product and industry better?</strong></p><h3>Summary: Not everyone is a designer but anyone can be.</h3><p>I’d like to clarify that I’m not saying Design is an exclusive circle that only a chosen few can be part of. Anyone can be a designer — I’ve met a variety of people in this field from different backgrounds and there is no course or personality that is best suited for UX/DT/HCD. There is however, a distinct difference between ‘everyone’ and ‘anyone’.</p><p>Anyone can be a designer with the right understanding of the workflow, the principles, business skills, and empathy (x10,000!). A designer, who by (proper) definition, has the capacity to create something intended for impact.</p><blockquote><em>There is no average GPA or IQ for designers but </em><strong><em>there is a certain level of intellect needed to gather and analyse insight then render intent</em></strong><em> so that the product or process created has value and impact.</em></blockquote><p>We can all be encouraging but unless we translate empathy into actionable insight and use those insights to create something with the intention to improve or impact a life, then all that encouragement is more of a gimmick than a value adding way to generate better collaboration and output.</p><p>Lastly, design is not a one-time thing. There are iterations and while it’s easy to encourage people to be iterative. It is not for the faint of heart.Designers can take insights from something that failed and make it better. The process of understanding and creating is not one that ends with a decision. Design involves deliberate practice of delivering valuable work. It is a cycle of understanding, creating, sharing and refining. Do not be misled to thinking it is something everyone can do.</p><p><strong>❗️I am not telling you to box yourself out of being a designer. To clarify, I am asking you to be aware of your strengths and know the value you offer.</strong></p><ul><li>You may be a designer but at what stage in the process?</li><li>Are you a facilitator? Are you a subject matter expert?</li></ul><p>I would rather have a conversation going on how to bridge strengths than to push everyone to be a new type of designer. Of the many things that a you can be, don’t just be a “new definition”. Value over job titles, value over trendy team roles—let’s focus on delivering value!</p><p><em>Hi there! 🙋🏻‍♀️Thanks for reading. If you liked the article, please leave a clap 👏🏼(you can clap more than once, by the way!). You can go ahead and share it with people who’d be interested. </em>😁 <em>If you have any questions feel free to leave a comment or email at ux.kazumi@gmail.com ✉️</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=318159e6c742" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/lets-be-honest-not-everyone-is-a-designer-and-that-s-okay-318159e6c742">Let’s be honest: not everyone is a designer — and that’s okay</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019 Second Quarter (Q2) UX Review]]></title>
            <link>https://blog.prototypr.io/2019-second-quarter-q2-ux-review-6d5f3800a719?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d5f3800a719</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 14:31:26 GMT</pubDate>
            <atom:updated>2020-02-18T03:22:40.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jaUasy5jePJKbHWJ" /><figcaption>Photo by <a href="https://unsplash.com/@thoughtcatalog?utm_source=medium&amp;utm_medium=referral">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>UX Organizational Maturity, Value, and Sources of Insight</h3><p>Half the year has gone by and it’s time for me to reflect on what I’ve learned from the past three months.</p><h3><strong>1. Understand the different levels of maturity of the organizations you work with to better assess needs and deliver value.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HXCHoiy5FYm0ZZlS" /><figcaption>Photo by <a href="https://unsplash.com/@chuttersnap?utm_source=medium&amp;utm_medium=referral">chuttersnap</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Where I’m from, there is still a high-level skepticism with UX. Why? Because the recognition of UX as a field of work is either still very new or unfamiliar. Many organizations are more reactive than proactive when it comes to UX (a.k.a. “Let’s UX this because we need to know what’s wrong.”).</p><p>It may seem like those who are still “new to UX” are not worth your time because you have to convince them and then prove the value. I spoke to someone heading a digital team who said that the different methods take time and investment but the bigger challenge is the skepticism that you encounter. This forces you to have a very “What’s the value? Let me show you!” mindset when working with skeptics.</p><p>It is true that UX mature organizations are more willing to invest in UX but <strong>just because there are barriers to their understanding (and perhaps “appreciating”) UX, doesn’t mean they’re not worth reaching out to.</strong></p><p>In fact, this can be their first UX encounter that can be the foundation of a long-term relationship. Also, there are a number of times that the organizations that are most skeptical of “UX” think of it as a gimmicky thing without realizing that it might be something they need.</p><h4><strong>It is still worth engaging them and figuring out how to best work together.</strong></h4><p>It could be training. Or perhaps something more evaluative method like a usability test or a heuristic analysis?</p><blockquote>There are various levels of engagement, types of methods and work scope that you can have. The key here is to understand where they’re at, what you can offer and what’s feasible given timelines and budget.</blockquote><p>There are multiple sources of information that discuss the different levels of maturity of organizations with regard to User Experience. In the past, we used this as a guide to creating our own <strong>UX value ladder</strong> that we used as a basis when profiling our clients.</p><p>It was created to help us pinpoint “where they are” so that we could identify tactics that can help us show them what options they have and how these options are of value to them. It helped align the operations, sales, and marketing team approach to potential clients.</p><p>There are many, many UX maturity ladders you can refer to that’s available online. Here are three that I personally refer to when I assess my clients so that I can “tweak” my approach accordingly.</p><ul><li>Nielsen Norman Group’s “<a href="https://www.nngroup.com/articles/ux-maturity-stages-1-4/">Corporate UX Maturity</a>”</li><li>Testing TIme’s “<a href="https://www.testingtime.com/en/blog/6-degrees-ux-maturity-scale/">The 6 degrees of the UX maturity scale — How UX-ready is your company?</a>”</li><li>UX Magazine’s “<a href="https://uxmag.com/articles/how-mature-is-your-organization-when-it-comes-to-ux">How Mature is Your Organization when it Comes to UX?</a>”</li></ul><p>I hope you find the one that is most applicable to you and your organization’s needs.</p><h3><strong>2. Expect that you may find pain and opportunity points outside of your product — know that a critical pain point to your experience can be offline.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3YypF3Q5OOg-qYZ6" /><figcaption>Photo by <a href="https://unsplash.com/@hudsonhintze?utm_source=medium&amp;utm_medium=referral">Hudson Hintze</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sometimes, we (clients and UX professionals alike) may start a project with a general assumption of what’s wrong with the product. That’s alright, it’s only part of one’s trail of thought but make sure you don’t keep a short-sighted view. Your client may hold their assumptions but as a UX professional, you should not.</p><h4>When your research data surface pain points different from your assumptions do not get defensive,<strong> listen.</strong></h4><p>Listen because your customers have the information you need to improve their experiences. Before you question research design or review the recordings, listen to what they’re saying. Maybe they have already told you the critical problem but you just haven’t “heard” them. 👀</p><ul><li>Maybe the reason for poor turn-over is not the app but the <strong>touchpoint before purchase</strong>.</li><li>Maybe the reason for poor activity within your dashboard isn’t that they don’t understand it but that your users <strong>don’t see</strong> transactional features on it — that’s <em>why </em>there is no activity. They view the information and think that’s all there is to it.</li><li>Maybe, just maybe, the “totally cool feature” you applied based on a competitor<strong> just doesn’t work for your customers</strong> even if your products belong to the same industry.</li></ul><p><strong>Be comfortable knowing that you have unearthed insights</strong>, that’s great! Don’t beat yourself up for finding information that you did not expect to get — these are great insights. They also help you see things from the perspective of a user. Do not disregard them.</p><h4>❗️BONUS ITEM: Managing Client Reactions</h4><p>When your clients feel a little disgruntled with the unexpected pain points you’ve presented, don’t be quick to be defensive. You can defend your research without being hostile. Some clients might say “We did not expect negative data on [insert touch point] because we get great feedback on the layout of the store!” Do not start a debate, go back to the pain point. Show the data, show the journey. It will be your storytelling, not your argumentative skills that will help the client see what you see.</p><blockquote>It will be your storytelling not your argumentative skills that will help the client see what you see.</blockquote><h3><strong>3. Garbage in, garbage out. Do not compromise your work’s integrity or value.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sYoCTKJ7lj_9rpnA" /><figcaption>Photo by <a href="https://unsplash.com/@shanerounce?utm_source=medium&amp;utm_medium=referral">Shane Rounce</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are a lot of tag-lines on making something beautiful out of a challenging situation. With a human-centered design, it is incredibly common to invest time and effort in making sure you’re ‘solving the right problem’ that it’s almost second nature for many of us to make sense of the complexity, find solutions and iterate.</p><h4><strong>Be strict with the inputs to your work.</strong></h4><p>There are limits to investing time and effort into finding a solution— especially when the project was set-up in such a way that limits your chances of succeeding. You have to understand that no matter what you do or how capable you are, if your objectives, definitions and key results were never clear to start with, you’ll risk missing the mark and wasting your efforts.</p><p>Recently, I was asked by a client to help create personas. I was to present this to a top-level management team so that they could align on who their customers are. The personas will then kick-start discussions into customer journeys and product and service solutions to help them strategize for their business priorities.</p><p>The team knew that they needed to be customer-centric and that they knew that instead of an excel sheet with demographic data, the client knew that a visual representation <em>(*cough* persona *cough*) </em>would be of more value. This was a great initiative. I was excited.</p><p>Soon enough, I came across the first hurdle with my project. I was provided with very limited and poorly collected information. I voiced my concern that this was an insufficient basis for data and actual data was something that could be collected through proper research design and on-ground activities (as they had a lot of in-store touchpoints).</p><p>I got this as a reply: <em>“You’re great at what you do, surely you can make something out of these? There won’t be enough time for full-scale research. Anyways, garbage in, gorgeous out, right?”</em></p><p>Don’t fall into the trap of being threatened and agreeing. You are good at what you do and it’s important to draw the line.</p><p>If you are asked whether you can come up with something, the answer is yes, you can make something out of limited data. But what would you fill the gaps in information with? Best guesses are still assumptions. You cannot use assumptions because assumptions need to be validated.</p><h4>Concrete business strategies cannot be built upon assumptions.</h4><p>Personas are valuable with the proper research to validate assumptions and to know behavioral information from your actual users.</p><p>Businesses lose money by not knowing their customers — this is something we already know. This is just as true with businesses that take shortcuts.</p><h4>Businesses are set to waste money when they know that they have to gather data customers and take shortcuts with assumptive data instead.</h4><p>It’s easy to make money off personas but what value have you provided? You should never take on something you would be ashamed to be associated with. Would you be proud to say you worked on x for y — if you aren’t, reflect on why so? Those indicate red flags.</p><h4>You need to communicate the value of what you do and also protect the integrity of what you do.</h4><p>I was lucky that the person who had incorporated me into that engagement shared the same viewpoint. “There is no such thing as garbage in, gorgeous out. We need to ensure that we don’t let you act on assumptions no matter how “great” you think assumptive personas are because they might not capture your niche market correctly.” <strong>Garbage in, garbage out. Do not compromise your work’s integrity or value.</strong></p><p>This was an incredibly lengthy post. If you have read all the way to this point, thank you. I hope you learned something. I know people rarely comment on posts but I’d love to hear about your learnings in UX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d5f3800a719" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/2019-second-quarter-q2-ux-review-6d5f3800a719">2019 Second Quarter (Q2) UX Review</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX on the Job: Documenting your UX Projects]]></title>
            <link>https://blog.prototypr.io/documenting-your-ux-projects-8b236b9a345d?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b236b9a345d</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Mon, 13 May 2019 07:36:51 GMT</pubDate>
            <atom:updated>2019-11-14T01:27:33.731Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX on the Job — Documenting your Client Projects</h3><h4>Project documentation is paramount as it can be the basis for the current state and future state analyses. But how do we get there?</h4><h4>It started with a comment</h4><p>I summarized my <a href="https://medium.com/@kcshiroma/2019-first-quarter-q1-ux-review-11b10626bb3a">Q1 UX Review</a>’s three key points on my LinkedIn account. <em>See top 3 insights below:</em></p><ol><li>Ensuring that everyone is informed is key to any project. <strong>Make sure you have a way to document your projects.</strong></li><li><strong>Streamlined processes breed consistency in your project delivery.</strong> Do not underestimate the impact of inconsistent processes and work outputs on your organization.</li><li><strong>Ask objective-based questions</strong> to understand your users and their contexts better.</li></ol><p>Within an hour of posting this I received a comment from asking me:</p><p><strong>“How did you end up documenting? What medium? Thanks!”</strong></p><p>I had to explain that it depends on the clients I’ve worked with. It was here where it dawned to me that with the intention of documenting everything related to the UX project, we end up forgetting to make it easy to see what you and your clients need to find. We forget to “UX” ourselves.</p><blockquote>“It dawned to me that with the intention of documenting everything related to the UX project, we end up forgetting to make it easy…”</blockquote><p>Some clients will expect you to work within their current processes and programs(Slack + GDrive, Workplace, BaseCamp, Jira). While others will set-up a Viber group and post announcements there. There’s a method in the madness once you establish what the channels are for.</p><p>Project documentation is paramount as it can be the basis for the current state and future state analyses. People need to know where to find what they need to know and as a UX Manager, you can do this by ensuring two things:</p><h4>#1 Document Projects by Creating Detailed Alignment Email/s with Call Recording Time Stamps</h4><p>I’ve had some clients who record the entire meeting via Zoom or Skype recordings because they have off-shore team leads. This video recording also gets forwarded to us.</p><p>But the thing is, <strong>Who has 1–1.5 hours to spare looking through footage of someone they don’t know? Who would listen attentively?</strong></p><p>This is where time stamps come in handy. If you were part of that meeting you can approximate at which part you discussed key things, find the timestamps and then include that in your alignment email. This makes it easier for them to get updated without taking so much of their time.</p><p>These conversations are client interactions have to be saved and documented for future reference. This makes it easier for both the client and I to recall the discussion. This can be done through a simple email:</p><blockquote>“Hi team!</blockquote><blockquote>Thanks for the meeting. We’ve summarized the 1.5 hours into these ___ points. For reference, refer to time stamps beside each key point.”</blockquote><p>I have a more detailed example for you in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MXI6zIQU8WgdWetS_ubWw.jpeg" /><figcaption>Disclaimer: This is a mock email based on the ones I usually send. Note that ALL details, email, and deadlines are fictional.</figcaption></figure><p>I shared that the frequent way of documenting in my case is influenced by who I work with. My second tip on documenting UX projects rely on understanding the different platforms that work best for the people involved in the project. You have to understand that sometimes the platforms or tools you use — no matter how “cool” — may not be something your clients would like to adapt. That said, you must:</p><h4>#2 Understand the Context and Tools that Work Best for the Project and the People involved in that project.</h4><p>That said, regardless of how “cool” your tools are, do not force your tools to a client. Especially when they have their own processes and tools in place, they will most likely refuse. Be strategic with how you spend your time. Be flexible.</p><p>Recently, most my clients have been financial institutions so strict firewall restrict us to email as our primary way of documenting.As a way to ensure we get to coordinate and send information, <strong>we decided on 3 channels to communicate and document </strong>which you can refer to below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uN3pJsSgaCo-DE7pmNEPuQ.jpeg" /><figcaption>Distinct and defined communication channels would help you in the long-run. Having a well-organized and well-categorized folders and files in your cloud will also.</figcaption></figure><ol><li><strong>ALIGNMENT EMAILS</strong> — We send alignment emails summarizing meetings whenever important decisions related to the project are made. This is a standard practice that’s a better alternative to meeting transcriptions.</li><li><strong>ONE MAIN MESSAGING APP </strong>— We decided on having only one main messaging app for quick discussions. We chose to use the app that they were all using because it was the only one their firewall allowed.</li><li><strong>ONE MAIN CLOUD SHARING PLATFORM </strong>— Lastly, we made sure to have a well organized Google Drive for file sharing and documenting everything related to the project. (Each stage is a folder.)</li></ol><p>It’s most likely that your organization may use a different platform or a different tool but what’s key about documenting UX projects is that you <strong>document consistently and ensure that qualitative</strong> (what are the causes of delay) <strong>aspects are highlighted just as much as your quantitative </strong>(percentage achieved, jobs to be done, etc.)<strong>.</strong></p><p>More importantly, if you’re working with a client, it’s important to be flexible and understand your client’s processes before you insist on your own.</p><p>Hope this helps! :)</p><p>Best of luck with your projects!</p><p><em>Thank you for reading!</em></p><p><em>If you liked the article, please leave a clap 👏🏼(you can clap more than once, by the way!). You can go ahead and share it with people who’d be interested. </em>😁 <em>If you have any questions feel free to leave a comment or email at ux.kazumi@gmail.com ✉️</em></p><p><em>If this is your first time to read one of my stories — Why, Hello! 👋🏼 I’m KC, I’m a UX Consultant and I write about my experiences and learnings from the UX industry each quarter.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b236b9a345d" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/documenting-your-ux-projects-8b236b9a345d">UX on the Job: Documenting your UX Projects</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Sandpaper situation: Finding the balance between guiding your team and letting them go]]></title>
            <link>https://medium.com/@kcshiroma/ux-sandpaper-situation-finding-the-balance-between-guiding-your-team-and-letting-them-go-e308a0b67ed3?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e308a0b67ed3</guid>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 15:49:01 GMT</pubDate>
            <atom:updated>2019-04-20T01:30:20.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FgDbuCiqo2WRdP-D" /><figcaption>Photo by <a href="https://unsplash.com/@fancycrave?utm_source=medium&amp;utm_medium=referral">Fancycrave</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>My personal reflections on the necessary “friction” that enables growth and encourages learning for junior UX research team members.</h4><h4>How are you supposed to handle daunting UX projects, pesky clients and your team member’s growth?</h4><p>Two months ago, I posted a conversation I had with my Junior UX researcher on <a href="https://www.linkedin.com/feed/update/urn:li:activity:6504226621841608704">LinkedIn</a>. The context of that conversation was about how in our line of work, <em>our roles expect us to do both the client facing work and implementing the research project. </em>I told her that I recognize that is an incredibly daunting situation to be in especially that it was her first job.</p><p>It <em>is </em>a lot of responsibility demanded of her all in a fast-paced learning environment. There’s no doubt on that. The very nature of the work entails us to know methods but apply them depending on the users, the context and client goals. All this factored in, I told her that it gave her no reason to be afraid of taking more responsibility. She had so much potential. In fact, embracing the challenge would be a stepping stone for her further growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gRMRBJcFVt9pHwm6" /><figcaption>Photo by <a href="https://unsplash.com/@epicantus?utm_source=medium&amp;utm_medium=referral">Daria Nepriakhina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Reflections on my UX Leadership style: Hone skills with hands-on experience</strong></h4><p>I took time to reflect after giving her that advice. Looking at our process flows, there are so many steps within each stage of the process. We were usually on our feet as we scoped projects, finalized work scopes and research plans, applied the chosen UX research method/s, analyze and presented the data findings. What was good about these processes, was that it was mapped out with my team based on their experiences on what worked and didn’t work.</p><p>I wanted them to be challenged further. Their initial job descriptions were “Research Assistants” with data logging as their main job responsibility. I found that to be too limiting. Along with their 6-month evaluation, I set expectations that their roles were not task-based but strategic and operational as Junior UX Researchers.</p><p>Despite the increase in “difficulty level” of their job role, I also made it clear I will not wait for them to “feel ready”. As a leader, I do not wait for individual “maturity dates”. I am a firm believer that experience is the best teacher. I believe that knowing the methods without context to implement them in renders an incomplete experience.</p><blockquote>I believe that UX competence is developed with having a base knowledge of the UX methods, an ability to think critically and contextualize it into the current project.</blockquote><p>I want to develop their competence with a mix of foundational knowledge with a real context to apply it to. I make sure to give guides for project work and then leave them space to figure things out as they manage a project. This hones their skills within a context of an industry, a product/service and actual timelines with real clients. They hone their skills while they handle<strong><em> actual </em></strong>work.</p><h4>Balancing the hands-on experience with alignment meetings to assess and reflect</h4><p>I have to place a disclaimer that it’s not a completely “hands-off” approach. We have set days of the week where we align to assess the work that has been done, the progress and why. When there are aspects of the project that they need advice on, they can flag it any time during the week or discuss in detail in a sit-down meeting. To me, I believe that these will train them to be capable of handling projects much more than written assessments and formal training sessions. It also allows us to reflect on why certain things happened.</p><h4>Final Reflections: What does this all mean?!</h4><p>Two months after that post, my Junior UX Researcher is in the final leg of her project. I look back and still feel strongly that more than business goals we have achieved, it’s also the opportunities that we give and support each other in that make it a challenging but enriching experience for people in our team. This is also a crucial aspect in our field. It’s a fast-paced job that’s why, to me, it’s important that the work experience has to also be positive for them on a personal level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NO5EZHrP5-mRYHZ8" /><figcaption>Photo by <a href="https://unsplash.com/@alecuffia?utm_source=medium&amp;utm_medium=referral">José Alejandro Cuffia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a team lead, I often find myself being worried whenever red flags pop-up in a client project. I’m wary that this may be a lot for someone in their first role. I try to manage this by checking up on them as consistently as I can.</p><blockquote>I’m also a big believer in the tough love that lets people in your organization see how strong and analytical they can be when they don’t let their doubts gas light challenges they face at work.</blockquote><p>UX research projects as consultants mean bigger responsibilities than an entry-level role, yes. I do not deny this. As a team lead, I understand the pressure and high expectations you go through. I joke that it’s baptism by fire, 100% assured! Joking aside, it feels good to see people in your team grow.</p><blockquote>I realized that as a lead, it is rare for me to give compliments but feedback both good and back is critical. Your own team members will not know how much they grew. Their growth makes more sense to them in retrospect than it does while it’s happening. However, this is something that you, as a manager, can observe and give praise/feedback on.</blockquote><h4>UX Sandpaper situation…?</h4><p>Whenever this junior UX researcher begins doubting her abilities, I tell her to think of it as a sandpaper situation. Angry clients, frustrated clients are really people trying to do the best at their job but are tensed given work-related pressures. When you’re client-facing, it’s not rare to find yourself in high-stress situations. Coordinating client work may make you face situations with deal with less-than-kind comments or demanding clients. In high-pressure situations, <strong>do not doubt your ability</strong>.</p><p>Regardless of what experiences these are, I would encourage you to think of it as sandpaper. Those situation will hurt <strong>at that moment</strong>. But a few months later, it won’t. They won’t remember what they were so anxious about.</p><p>What they get from that experience is refinement necessary to help them with becoming more polished in their job.</p><blockquote>Just like sandpaper, they get polished by challenging experiences—whether it’s assessing data or handling a disgruntled client.</blockquote><h4>Final Notes</h4><p><strong>I’m not advocating that you throw your juniors under the bus.</strong> What I’m saying is that as a manager I’m aware that I have to find the tricky balance between enabling people’s growth by giving the necessary learning tools and experience but also knowing when to be hands off. In short, when to let them deal with the project-related problems on their own.</p><blockquote>By no means am I saying that it’s easy. In fact, as a manager, it’s you who understands that the job demands so much given fast-paced projects and lean teams. However, investing in your people and their skills is so crucial to overall organizational success. Don’t be too quick to get their workload or help them out at the first signs of discomfort or confusion—let them handle the challenges. As tempting as it is to tell people what to do, Let them go. Let them grow.</blockquote><blockquote><strong>Let them go. Let them grow.</strong></blockquote><p>When people in your team grow their skills, are trained to be capable of more things and become efficient, it affects how they do their work and the variety and depth of what they are able to contribute. Ultimately, it ripples into your organizational performance. I’d say it’s pretty clear cut that investing in your team is worth the effort. As a manager, it’s important to let your team have space to grow. Do not throw them off the bus but train them to know what to do and also prepare them to be “polished”. 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e308a0b67ed3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019 First Quarter (Q1) UX Review]]></title>
            <link>https://medium.com/@kcshiroma/2019-first-quarter-q1-ux-review-11b10626bb3a?source=rss-ff3be77a49b------2</link>
            <guid isPermaLink="false">https://medium.com/p/11b10626bb3a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-management]]></category>
            <dc:creator><![CDATA[KC Shiroma]]></dc:creator>
            <pubDate>Tue, 02 Apr 2019 11:59:41 GMT</pubDate>
            <atom:updated>2020-02-18T03:27:16.341Z</atom:updated>
            <content:encoded><![CDATA[<h3>Communication, Consistency and Creating a flow based on research objectives</h3><p>The first quarter of 2019 has just ended. I looked back to the first three months of the year and came up with three key learnings I gathered as I worked on UX client projects while building my own UX team.</p><p><strong>Lesson #1. Make sure key project stakeholders are informed and aligned.</strong></p><p>This sounds so cliche but time and time again, I’ve come to realize that the most common source of frustration (for both me and my client) when it comes to UX projects are oftentimes more about the coordination and communication with regard to the project than the results of the methods.</p><blockquote>This is best summarized with the George Bernard Shaw quote that said:</blockquote><blockquote><strong>The single biggest problem in communication is the illusion that it has taken place.</strong></blockquote><p>As someone who works as a consultant for various businesses from different industries, I’ve come to notice that more and more UX projects have multiple teams involved. Theoretically, multiple stakeholders from different departments is a great thing because it allows cross-function coordination. However, not all organizations have someone overseeing the coordination across departments. Not all organizations have someone who is in charge of ensuring that one team is informed of the changes in the project or verifying if the inputs provided to someone from another team involved is the updated build.</p><p>You’re often caught between a rock and a hard place in these situations. But the best way to manage this is by <strong>ensuring you have documentation</strong> whenever critical decisions or changes to the project have been made.</p><p>I gave this tip to someone else working in the industry and that person pointed out that it comes off as lacking trust when one has to document.</p><p>My argument is that, as someone who is often caught in the middle, you <strong>need</strong> proof that the actions you’ve taken had sign-off from someone in the organization. Having a form of documentation whether it’s an alignment email or a message to your work channel, also enables you to have a conversation going. The people cc:-ed in the email, can revert if there’s something missing or unclear. <strong>You need to keep that communication line open to keep people informed and aligned</strong>.</p><p>If the project is stretched through a long time period, check-points per phase might be helpful to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KPKWRm99P5LI4IMaKouBQg.jpeg" /><figcaption>UX Tip for Lesson 1: Have a way to track work to ensure your project’s stakeholders are aligned and informed. <strong>Note that the cell contents presented here are examples not actual info from my NDA projects.</strong></figcaption></figure><p>Having a way to track work that’s been completed, what work will be completed, any upcoming challenges, key people responsible, action steps needed, deadline and status. (See image above.) I’ve found it easier to use spreadsheets but please work with whatever works best for you and your team.</p><p><strong>Lesson #2. Make sure you aim for a level of consistency when delivering projects to clients</strong>.</p><p>We are a young team and as an output-based organization, our business has not been strict on branding guidelines or presentation formats. But that was before… We have had multiple projects with one client happening at one time. The lack of consistency between outputs become more pronounced.</p><p>This experience taught me that internal alignment is very important as it feeds back into consistency in delivering output outside of our own organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dRfaisbhko1GFtLRGVhuhA.jpeg" /><figcaption>UX Tip for Lesson 2. Have a <strong>process</strong> to ensure consistency in the content and delivery of the outputs.</figcaption></figure><p>How did we take a step towards becoming more consistent? Through understanding that consistency is achieved by having internal processes formalized and templates created. The table below summarizes the two approaches I did as we worked towards achieving consistency.</p><ol><li>Identifying the current gaps in the process. (Internal and external processes)</li><li>Identifying the elements that are still missing across the different presentations.</li><li>Tweaking the current deck while also establishing the different steps in the process of presenting to clients.</li><li>Starting to come up with aesthetics. (Font, color, borders, chart elements and overall styles are all included here.)</li><li>Reviewing the presentation flow and ensure that it meets the project objectives and the flow of the discussion guide. (Which is our basis for presenting information to clients: ex. Macro details to micro…)</li></ol><p><strong>Lesson #3. Asking the right questions is important — but knowing how to ask questions is much, much more important.</strong></p><p>It dawned on me pretty late that even the best of the best may feel lost when they’re made to ask questions. In the first place, how can you find answers when you find it hard to ask questions? This happens especially when it’s towards someone they’ve never met. It’s easy to be inquisitive to people we know but it’s difficult to know how to best ask questions to someone who you’ve met only for the sake of the study.</p><p>As a UX Researcher and Strategist, a huge chunk of the insights I deliver are rooted in understanding their objectives so that I can ask questions that will profile the correct respondents but also provide the insights to help my client make data-driven decisions to improve their product. It took me so long before I realized that not everyone may know how to create an interview flow reflective of your research objectives.</p><p>Asking questions is crucial when you want to gather business requirements, understand user motivation or create clearer user scenarios. The questions that you ask can help you in your user research and design process. It’s important to have a flow that’s rooted in your learning objectives and builds up to finding insight by starting from introductions to general questions to follow up and deep dive before doing a recap of their answers. (See flow below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdhqAKb10rmIj-Q5lRLLSw.jpeg" /><figcaption>Lesson 3. Ask questions. When in doubt or having difficulty figuring out what to ask, create a flow based on learning objectives and then build the flow of your interview, step by step.</figcaption></figure><p><strong>OTHER TIPS:</strong></p><p>When in doubt, look at all your questions and see if they answer your learning objectives.</p><blockquote>When something seems to be missing, ask yourself “What is it?”. When you answer “what”, then you can phrase that missing insight into a question.</blockquote><p>So let’s say you realize that in your research scope information about when they do their errands is missing. Then you are able to turn that into a question asking when and how often.</p><p><em>Ex. How often do you go to the &lt;place&gt; to do &lt;task&gt;? Is there a set day or time?</em></p><p>It’s so important to be comfortable with having to review your interview flow and getting feedback so that you get stakeholder involvement as well as feedback and alignment even before you conduct the interviews. You want to be as thorough as possible!</p><p>Do not be afraid to get feedback from stakeholders early on.</p><p>That’s all for my 2019 Q1 UX Review. I hope you’ve picked up something along the way.</p><p>If you have thoughts or want to share your own Q1 learnings, please leave comments. I’d love to read them and learn from you too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11b10626bb3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>