<?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 Nastia Naumets on Medium]]></title>
        <description><![CDATA[Stories by Nastia Naumets on Medium]]></description>
        <link>https://medium.com/@anastasiia.naumets?source=rss-e139132ebc4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PBcIGrA9A9ffSgrlEDUxjQ.jpeg</url>
            <title>Stories by Nastia Naumets on Medium</title>
            <link>https://medium.com/@anastasiia.naumets?source=rss-e139132ebc4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:58:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anastasiia.naumets/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[Leveraging web analytics for data-informed project discovery]]></title>
            <link>https://medium.com/design-bootcamp/leveraging-web-analytics-for-data-informed-project-discovery-6e2d22ce140a?source=rss-e139132ebc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e2d22ce140a</guid>
            <category><![CDATA[discovery]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nastia Naumets]]></dc:creator>
            <pubDate>Tue, 30 Aug 2022 06:00:03 GMT</pubDate>
            <atom:updated>2022-08-30T06:00:03.592Z</atom:updated>
            <content:encoded><![CDATA[<h4>Data yields a new perspective.² Pamela Pavliscak</h4><h4>What you’ll learn here</h4><p>In this article you will read about the practical application of web analytics data in order to reveal user insights and guide project discovery. You will first learn the benefits of using analytics data as a part of UX research. Then I’ll briefly outline the project’s goals, constrains and plan of actions. Finally we’ll drill down into the details of our measurement plan and data analysis process.</p><p>I’d like to warn you that you wont become an expert analyst after reading about this specific project experience. Although I hope you’ll find it exiting to learn more and eventually use analytics data on your projects.</p><h4><em>Benefits of using analytics data</em></h4><p>As Erika Hall simply described it: <em>“Analytics refers to the collection and analysis of data on the actual usage of a website... Based on data from analytics, you can identify areas where your website is not as effective as you’d like it to be”.</em>³ When combined with other research methods, analytics lets you observe a full picture of user’s behavior and helps fully understand the issues you’re trying to solve. Besides, we found that leveraging web analytics in the design process brings other benefits. Let’s take a look on them:</p><ol><li>Web analytics is an empowering tool that promotes a <strong>data-informed perspective</strong> and contributes to <strong>decision-making process</strong>. A wonderful book <em>Designing with Data</em> describes “data-informed perspective” as a more critical way to think about the problem. When the team is informed by data and is using it as one of many inputs into decision-making process, they are therefore enabled to learn about the problem in a more creative and iterative manner.¹</li><li>Analytics data can help you build <strong>empathy with the users</strong>. By continuously exploring the data insights you’ll sharpen your understanding of how people behave, and therefore how to design the best experiences for them.</li><li>Finally, collecting and comparing analytics data will help you <strong>measure the effect of your design</strong> on the users, and therefore on business. Hence you can clearly articulate the value that design brings to the business.</li></ol><p>Let’s check one of my recent projects where analytics data helped us to reveal key insights about user behavior, reinforce our assumptions and prioritize further steps.</p><h4>Project goals &amp; c<strong>onstraints</strong></h4><p>We were working with our client, the leading body wear<strong> </strong>retailer in Europe, for few years now. They’ve recently discovered that many users of their e-commerce website abandon checkout. Therefore our discovery team was tasked with an investigation of possible reasons and solution seeking to reduce the drop-off rate and to fix any usability issues we would find along the way.</p><p>While shaping our discovery plan, we’ve made sure to account for project constraints. Firstly, the time for completion was rather limited, which meant that the tools and methods we could use for research was narrowed down. Secondly, the client provided us with their previous research artifacts which later yielded an important data and framed our further steps. Lastly, we anticipated that our vision could be challenged by some of the stakeholders, therefore we needed to offer bulletproof arguments to get all of them onboard and to expedite the decision-making process.</p><h4>Our plan of actions</h4><p>As the focus of this article is the analytics data and the benefits it brings for the project discovery, I’ll shortly describe our plan of actions and then will zoom in on analytics.</p><p>Keeping in mind our goals &amp; constrains, we embarked on examining discovery activities and picking the ones that would suit our needs. On the one hand, we needed to explore the problem (users leaving the site during checkout) and “generate” a deep understanding of the users unmet needs &amp; pain points. On the other hand, we needed to assess existing solution and collect data that would help us to improve it. Therefore we’ve combined the generative and evaluative research methods⁴ and sketched out our discovery plan.</p><figure><img alt="Diagram with discovery process visualization" src="https://cdn-images-1.medium.com/max/1024/1*uYgUdYugLgiYKC8s4mG5tQ.png" /><figcaption>Discovery process visualization</figcaption></figure><p>Activities that we planned were the following:</p><ul><li><strong>Stakeholder interview</strong>, as a part of the standard requirements-gathering process, but also to get better understanding of stakeholders’ assumptions about root causes and expectations for the end results.</li><li><strong>Client documentation review, </strong>where we could find information about customer feedback and complaints.</li><li><strong>Competitor analysis. </strong>As a generative study, it would help us to explore common trends and identify innovative solutions. As an evaluative method, it would be useful for evaluation of existing patterns and functionalities.</li><li><strong>Analytics data analysis,</strong> was meant to bring insights about user behavior on the site. Besides it would help us to evaluate the performance and find the dead ends in the checkout process.</li><li><strong>UX evaluation. </strong>Finally, once we’ve gathered all the data and identified possible issues with the checkout flow, we were planning to evaluate them against basic usability principles.</li></ul><p>At the end, diversity of our sources of data allowed us to create a holistic picture of the problem and brought us closer to possible solutions.</p><h4><strong>Zooming in on analytics data analysis</strong></h4><p>Without further ado, let’s dive deeper into the analytics study that we conducted within this project.</p><blockquote>Just because something is measurable doesn’t make it meaningful.³ Erika Hall</blockquote><p>In order to understand what exactly to measure and obtain actionable insights, we’ve started to set up a <strong>measurement plan</strong> and iterate on it as we go. As Jen Cardello suggests in her article⁶, our measurement plan included:</p><ul><li>Macro conversions — big picture actions</li><li>Micro conversions — desirable actions to support the meeting of the goals</li><li>Metrics, that indicate whether these desirable actions occur</li></ul><p>Our first and foremost macro conversion was the following — completed checkout flow that led to a purchase. Additionally we wanted to know if users tended to meet any obstacles or confusion. So we asked ourselves: How can the best user experience on checkout be ensured? What is important to our users when they go through this process? After thorough consideration, we formulated the other “big picture goal”: the checkout structure and flow should match users’ needs, while any distractions should be avoided.</p><p>As for the micro conversions, we determined the behavioral cues⁵, that would indicate whether the goal has been reached. For us it was a <strong>successful passing through checkout funnel, </strong>while high <strong>drop-off rate</strong> on any of checkout steps would indicate that this step should be examined more closely.</p><blockquote>Only once this big-picture goal is defined should you look for concrete metrics that relate to that goal.⁵ Aurora Harley</blockquote><p>Therefore we’ve decided to examine the <strong>checkout behavior report </strong>as a starting point.<strong> </strong>It would tell us what percentage of users drop-off on every step of checkout and signal where to dig deeper. We would also examine the most popular delivery and payment methods. This information will later guide our assessment of their placement and convenience on the page.</p><h4>Ready, set, analyze!</h4><p>Once we’ve collected the data of every checkout step (shopping cart -&gt; login -&gt; details -&gt; delivery -&gt; payment -&gt; confirmation), <strong>high drop-off rate</strong> was spotted after the shopping cart (74.8%) and payment step (22.1%).</p><figure><img alt="Chart with a drop-off rate on every step of checkout" src="https://cdn-images-1.medium.com/max/1024/1*mmoc115_DLtxICy00Azvfg.png" /><figcaption>Drop-off rate on every step of checkout</figcaption></figure><p>As we know from the<strong> </strong>Baymard Institute study, the average shopping cart abandonment rate is 69.99%⁷. Based on this statement we’ve considered our drop-off rate to be high. As for the payment step, in comparison to the drop-off rate of other checkout pages, which varied from 4% to 8%, it raised questions. Therefore we focused on shopping cart and payment step.</p><p>To understand why users might be leaving shopping cart we first checked the <strong>average page load time</strong> — 5.1 seconds. As the “good” page load time is considered to be around 3 seconds⁸, we’ve added this metric to our plan for further investigation. Next, we examined the <strong>average time on page</strong>, which was 39 seconds. It can mean that users are staying on the page because they’re interacting with it, but it can also mean that they are lost and cannot find what they need. So to compliment this finding, we looked on <strong>page views &amp; unique page views</strong>, which were the following: page views — 3,993,987; unique page views — 1,136,082. These numbers indicate that, most likely, users tend to open shopping cart page several times in a single visit. Based on this finding, during UX evaluation we will pay a close attention to any elements on the page that can distract users from the purchase.</p><figure><img alt="Bar chart that shows Page Views VS Unique Page Views" src="https://cdn-images-1.medium.com/max/1024/1*qcsF3wZwMy6LXgCiAvVmDQ.png" /><figcaption>Page Views VS Unique Page Views</figcaption></figure><p>Then we proceeded to the delivery and payments methods. The data collected from the checkout behavior report showed us that the most popular delivery method is DHL home delivery (59.6%), and the the most popular payment method is Klarna (49.8%). Having this info we can later make sure the respective elements on the checkout pages have high exposure, visual importance and ease of use.</p><figure><img alt="Pie charts with delivery and payment methods visualization" src="https://cdn-images-1.medium.com/max/1024/1*o2KqNWgGIuj5trYlHMiKSQ.png" /><figcaption>Delivery and payment methods visualization</figcaption></figure><p>Finally, the high drop-off rate on the payment step served as an indication to investigate further. We suggested to asses if there are issues or delays with payment processors, if users need any additional payment options, if the CTA is findable and clear. If our time and budget allowed, ideal case scenario would be to reinforce this data with the heat maps and user session recordings to see what exactly is happening on this page.</p><h4>What’s next?</h4><p>Once the analytics data was collected, analyzed and presented, our next move was to add other sources of input (customer feedback, competitive data, UX evaluation results) on top, make a summary of our findings for the client and proceed to the next phase of the project — requirements elicitation.</p><p>To sum up, analytics data has greatly contributed into meeting the goals of our project discovery. Not only we identified the weak spots of the checkout flow and learned key behavioral insights of the users, but by doing that we also created a solid base for facilitation of decision-making process.</p><p>I hope this article gave you a basic understanding of how you can use the analytics data for your project discovery and combine it with other sources of input for your UX research process.</p><p>Thank you for reading! If you have any questions or suggestions, feel free to write them in comments, or <a href="https://www.linkedin.com/in/anastasiia-naumets-4aa056ba/">contact me</a> directly.</p><h4>References</h4><p>[1]: Rochelle King, Elizabeth F Churchill, Caitlin Tan, <em>Designing with Data </em>(2017) <a href="https://learning.oreilly.com/library/view/designing-with-data/9781449334925/">https://learning.oreilly.com/library/view/designing-with-data/9781449334925/</a></p><p>[2]: Pamela Pavliscak, <em>Data-Informed Product Design</em> (2015)<em> </em><a href="https://learning.oreilly.com/library/view/data-informed-product-design/9781492048688/">https://learning.oreilly.com/library/view/data-informed-product-design/9781492048688/</a></p><p>[3]: Erika Hall, <em>Just Enough Research, 2nd Edition </em>(2019) <a href="https://learning.oreilly.com/library/view/just-enough-research/9781492018032/">https://learning.oreilly.com/library/view/just-enough-research/9781492018032/</a></p><p>[4]: The Ultimate Guide to UX Research by Maze, <em>Generative Research: Definition, Methods, and Examples </em><a href="https://maze.co/guides/ux-research/generative/">https://maze.co/guides/ux-research/generative/</a></p><p>[5]: Aurora Harley from NNG, <em>Translating UX Goals into Analytics Measurement Plans </em>(2017) <a href="https://www.nngroup.com/articles/ux-goals-analytics/?lm=analytics-what-do-numbers-really-mean&amp;pt=youtubevideo">https://www.nngroup.com/articles/ux-goals-analytics/?lm=analytics-what-do-numbers-really-mean&amp;pt=youtubevideo</a></p><p>[6]: Jen Cardello from NNG, <em>Three Uses for Analytics in User-Experience Practice </em>(2013) <a href="https://www.nngroup.com/articles/analytics-user-experience/?lm=analytics-what-do-numbers-really-mean&amp;pt=youtubevideo">https://www.nngroup.com/articles/analytics-user-experience/?lm=analytics-what-do-numbers-really-mean&amp;pt=youtubevideo</a></p><p>[7]: Baymard Institute, <em>48 Cart Abandonment Rate Statistics</em> (2022) <a href="https://baymard.com/lists/cart-abandonment-rate">https://baymard.com/lists/cart-abandonment-rate</a></p><p>[8]: Kathryn Whitenton from NNG, <em>The Need for Speed, 23 Years Later</em> (2020) <a href="https://www.nngroup.com/articles/the-need-for-speed/">https://www.nngroup.com/articles/the-need-for-speed/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e2d22ce140a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/leveraging-web-analytics-for-data-informed-project-discovery-6e2d22ce140a">Leveraging web analytics for data-informed project discovery</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The business value of UX]]></title>
            <link>https://uxdesign.cc/business-value-of-ux-design-35a8039b4817?source=rss-e139132ebc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/35a8039b4817</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-value]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Nastia Naumets]]></dc:creator>
            <pubDate>Fri, 13 May 2022 11:45:28 GMT</pubDate>
            <atom:updated>2022-05-14T11:28:17.499Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>What is the ROI of UX design? How to explain the business value of UX design to the client? How to measure the impact of UX design?</em></h4><p>If you’re eager to know the answers to these questions, continue reading.</p><figure><img alt="“The ROI of UX Design” scheme which shows that return of investment in UX design is $100 for every $1 invested." src="https://cdn-images-1.medium.com/max/1024/1*JWz6BZUnnq0oXVmJlTX-2A.png" /><figcaption>The ROI of UX Design, source: <a href="https://s3.amazonaws.com/coach-courses-us/public/theuxschool/uploads/The_Trillion_Dollar_UX_Problem.pdf">https://s3.amazonaws.com/coach-courses-us/public/theuxschool/uploads/The_Trillion_Dollar_UX_Problem.pdf</a></figcaption></figure><p>Lately, I’ve been reading many reports about the value of UX research and design for software development and also reflecting on its impact on my past projects.</p><p>I’ve been working as a UX designer for more than 4 years in the outsourcing companies with clients of a different caliber. Very often the clients challenge us to prove the value of different UX activities during the discovery and definition phases claiming that “UX research consumes a lot of time and resources and postpones the start of development” which translates into “spending a lot of money with no tangible results”. I strongly believe that it is our responsibility to educate clients about the value of what we do and make a case for investing in UX design.</p><h3>1. Show what happens when UX design is neglected</h3><p>So first, let’s go through negative outcomes for the company if UX design is neglected during product development lifecycle:</p><p><strong>Disappointed customers</strong><br>Failing to understand users’ drivers and needs during discovery will result in creating irrelevant product that does not meet customers’ needs and expectations. In addition ignoring usability principles may lead to error-prone, inconsistent interfaces that are hard to use.</p><blockquote>The value of UX is not wasting time and money developing the wrong solution. Jeff Humble</blockquote><p><strong>Lower sales<br></strong>Disappointed customers lead to lower engagement, adoption and retention and at the end provoke decreased conversion rates and reduced sales.</p><blockquote>88% of online consumers are less likely to return to a site after a bad experience. (stats by <a href="https://www.invisionapp.com/inside-design/statistics-on-user-experience/">Invision</a>)</blockquote><p><strong>Increased time for development<br></strong>I’ve met many clients having an erroneous belief that time spent on deeper analysis of user’s behavior, the same as working through all the possible user flows and edge cases is simply waste of time that can be used to speed up the development. In most cases it’s the exact opposite. User research on the early stage of the project sheds the light on the most important parts of the experience, uncovers possible issues and dead ends of the flows. Thus it allows a clear prioritization of the features and facilitates further decision making and release planning. High fidelity prototyping, on the other hand, helps the team to reveal development issues and dependencies that lie deep down below the surface. As mentioned by Dr Susan Weinschenk in “<a href="https://www.youtube.com/watch?v=O94kYyzqvTc">The ROI of User Experience</a>”:</p><blockquote>The cost of fixing an error after development is 100x that of fixing it before development.</blockquote><p><strong>Bad reputation of the brand<br></strong>Unhappy customers start spreading the word about their bad experience very quickly. Soon the nasty reviews and poor rating will flood the feedback spaces that are viewed by thousands of people every day. The brand perception will be altered in a blink of an eye.</p><p><strong>Decreased motivation of company employees<br></strong>Bad user experience affects not only the customers but employees and partners as well. Declined brand reputation will demotivate employees and may even cause people quitting their jobs.</p><h3>2. Present the ROI of UX Design</h3><p>After we’ve scared the client with all the dreadful consequences of taking UX design for granted, we need to switch to the more pleasant topic that every stakeholder loves to discuss, return on investment. The business value of UX design can be represented by following benefits:</p><ol><li>Increased sales by boosting engagement and conversion</li><li>Increased customer satisfaction and loyalty</li><li>Reduced development time and cost</li><li>Increased employee satisfaction, lower turnover, reduces time for training</li><li>Fewer support calls, reduced spendings of customer support</li><li>Lower risk of implementing the wrong solution</li></ol><h3>3. Use data to support your statements</h3><p>Now let’s throw some numbers:</p><ul><li>According to “<a href="http://2016.futureof.design/">The Future of Design in Start-Ups</a>” (2016) survey results, 87% of design-mature companies believe that design leads to higher sales, 60% of companies claim that design brings higher customer retention, 83% — higher customer engagement and 60% — faster product cycle.</li></ul><figure><img alt="“Future of Design” survey charts that show the impact of design" src="https://cdn-images-1.medium.com/max/1024/1*jgCf51sjNwkxmmZgiVaUUQ.png" /><figcaption>“Future of Design” survey charts that show the impact of design</figcaption></figure><ul><li><a href="https://blog.red-website-design.co.uk/wp-content/uploads/2018/07/80-Web-Design-Stats-to-Guide-Your-2018-2019-Website-Strategy.jpg">48% of consumers</a> consider design to be a key factor when determining a company’s credibility.</li><li>According to <a href="https://baymard.com/lists/cart-abandonment-rate">Baymard Institute studies</a>, e-commerce site conversion rate can be improved by 35% through better checkout design. As Abby Covert, the author of “<a href="http://www.howtomakesenseofanymess.com/">How to make sense of any mess</a>”, says:</li></ul><blockquote>The impact of UX is crystal clear: the more satisfied your users are, the more likely they are to do whatever it is you are encouraging.</blockquote><ul><li>Clothing retailer, Anthropologie, increased sales by 24% with a UX redesign that made its checkout process easier (<a href="https://uxmag.com/articles/designing-superior-shopping-experiences">source</a>).</li><li>Staples e-commerce site redesign brought an 80% increase in the number of visitors, a 45% reduction in drop-off rates, and a 67% increase in repeat customers (<a href="https://humanfactors.com/case-studies-staples.aspx">case study</a> by HFI).</li><li>As mentioned by <a href="https://www.experiencedynamics.com/blog/2014/07/making-strong-business-case-roi-ux-infographic">Experience Dynamics</a>, UX design saves 50% of development rework time by defining all the requirements upfront. Moreover, it reduces overall development time by 33–50% by improving decision-making process and task prioritization.</li></ul><h3>4. Identify KPIs of UX design</h3><p>Close the deal by presenting an overview of goals and metrics that can be used to measure the impact of UX design. Here is the list suggested by Frank Spillers in his “<a href="https://www.experiencedynamics.com/blog/2014/07/making-strong-business-case-roi-ux-infographic">Making a Strong Business case for the ROI of UX</a>” (slightly adjusted by me):</p><figure><img alt="The table with goals and metrics that can be used to measure the impact of UX design" src="https://cdn-images-1.medium.com/max/754/1*FeXMswmfdeQGe6U_En6_-A.png" /><figcaption>The table with goals and metrics that can be used to measure the impact of UX design</figcaption></figure><h3>Conclusion</h3><p>So now you’re armed with a plan of making a case about the ROI of UX design for your clients. Follow these simple steps to educate the stakeholders and show the business value of what you do:</p><ol><li>Show what happens when UX design is neglected</li><li>Present the ROI of UX Design</li><li>Use data to support your statements</li><li>Identify KPIs of UX design</li></ol><p>If you have any comments or questions, feel free to post your feedback here or <a href="https://www.linkedin.com/in/anastasiia-naumets-4aa056ba/">contact me</a> directly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35a8039b4817" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/business-value-of-ux-design-35a8039b4817">The business value of UX</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[Book review: “Strategic Writing for UX” by Torrey Podmajersky]]></title>
            <link>https://medium.com/design-bootcamp/book-review-strategic-writing-for-ux-by-torrey-podmajersky-ceaeccfef5fc?source=rss-e139132ebc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ceaeccfef5fc</guid>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Nastia Naumets]]></dc:creator>
            <pubDate>Sun, 21 Nov 2021 11:10:02 GMT</pubDate>
            <atom:updated>2021-11-21T11:10:02.698Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello guys, just sharing some highlights and thoughts on “<a href="https://learning.oreilly.com/library/view/strategic-writing-for/9781492049388/">Strategic Writing for UX</a>” by Torrey Podmajersky.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rXejhcKLorK7JiXnQH-tg.jpeg" /></figure><p>I opened this book to get to know how to write good error messages. What I learned from it though is so much more than just “good ux copy”. The book offers lots of insights on establishing ux content strategy in your organisation.</p><figure><img alt="Cover of “Strategic Writing for UX” book" src="https://cdn-images-1.medium.com/max/204/1*TmC3itCzuJx3hZQKX6-NkA.png" /><figcaption>Cover of “Strategic Writing for UX” book</figcaption></figure><p>First few chapters give a perfect overview of the notion and purpose of ux writing. Frameworks, methods, tools, practices and as a cherry on top, detailed guides on how to deal with different ux patterns (titles, buttons, labels, etc).</p><p>Besides that the author describes what we can do to achieve continuous improvement of our ux writing, such as content auditing, measurements and various user research methods.</p><p>Since my role as a ux designer encompasses not only ux writing, the most valuable chapters for me were the last ones<strong>. </strong>Chapter 8 describes the workflow of ux content strategist that may be applied in any other field. A well-considered plan on how to introduce ux content strategy into an organisation and set a foundation for future growth and improvement.</p><p>Basically the author shares their tips&amp;tricks about the following:</p><ul><li>Stakeholder interviews for understanding business goals</li><li>Divergent/convergent thinking while gathering information</li><li>Establishing new collaboration processes</li><li>Creating working relationships and building trust with the team</li><li>Milestones and progress indicators</li><li>Setting a foundation for future growth</li></ul><p>My favourite quote of the book:</p><blockquote><em>“For a writer, the simple act of listening uncovers a gold mine.”</em></blockquote><p>Not so simple though 🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ceaeccfef5fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/book-review-strategic-writing-for-ux-by-torrey-podmajersky-ceaeccfef5fc">Book review: “Strategic Writing for UX” by Torrey Podmajersky</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get the most out of contextual inquiry]]></title>
            <link>https://uxdesign.cc/how-to-get-the-most-out-of-contextual-inquiry-c762760e5e05?source=rss-e139132ebc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c762760e5e05</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[contextual-inquiry]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nastia Naumets]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 23:34:06 GMT</pubDate>
            <atom:updated>2019-10-28T23:34:06.276Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Short guide on conducting contextual inquiry and few ideas on how to unleash its potential.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*_tp9eZAtH0G-Qtlv02WBrA.png" /></figure><p>Contextual inquiry is based on observing users in their own environments. It’s one of the most effective research method on discovery stage especially when combined with other techniques.</p><p>Spending the whole week onsite and conducting contextual inquiries helped our team discover user activities, needs, challenges and concerns. At the end of the week we had enough data to shape organisation processes and identify opportunities for future development.</p><p>So where to start?</p><h4>1. Set a goal</h4><p>…and stick to it. I think everybody has this thought once in a while: “So what exactly we wanted to achieve? 🤔 ” Sometimes we focus so much on the process that we forget to make one step back and think about primary goal. Any research has to be aligned with business and user needs. So before going onsite define a goal of the research and stick to it during the process.</p><p>For example our purpose was to understand how organisation operates within their current solutions and find opportunities for improvement. We were guided by:</p><ol><li>Business need “save resources by automating processes”</li></ol><p>2. User need “eliminate manual operations and make work more pleasant <em>”</em></p><h4>2. Prior research</h4><p>You will seem more credible if you approach the client with knowledge of the company industry, technology they use and basic understanding of what users do during the day.</p><p>Before our travel we created a project in <a href="https://www.notion.so/product">Notion</a> and shared it with the team. It contained information about the client company and departments, investors, management, competitor overview and tools users currently use.</p><h4>3. Preparation</h4><p>Before starting interviews there are few things that need to be planed:</p><ul><li>Prepare an interview script. It shouldn’t be very detailed as your questions will be based on user context. Talk about routines, time consuming tasks, issues that arise.</li><li>Explain who you are, what you will do and why.</li><li>Make sure to ask permission to record sessions.</li><li>Make recordings (video/photo/audio), make notes.</li><li>Distribute activities between team members: Patrick will record and take pictures, Gary will make notes and Karen will interview users.</li></ul><h4>4. Shadowing</h4><p>Ready, set, go! Start with asking user to perform their usual tasks. Observe how they interact with tools, pay attention to details. For example instead of setting up reminder in the app, they use stickies and put them all over the screen. Stickies also partly serve as knowledge base and contact list. This could indicate that the current app does not provide convenient ways to complete these tasks.</p><p>By watching users work we’ve gained insights into behaviour and context of use of different user groups, e.g.:</p><figure><img alt="Photo of a man in" src="https://cdn-images-1.medium.com/max/403/1*AYgl2wq_v576yGi19VZmxA.png" /></figure><ul><li>Group 1: use multiple screens and mobile phone for different windows and apps; print excel tables on paper to check numbers more accurately; keep track of multiple projects at the same time.</li><li>Group 2: due to lack of apps integration, spend 50% of time transferring data between apps manually; feel pressure because of great responsibility and error-prone manual tasks.</li><li>Group 3: use current app on tablet; work inside and outside (possible bad weather conditions); document all their actions; use technical equipment in their work, wear uniform to hold it.</li></ul><h4>5. Interview</h4><p>Guided by our goal to improve user processes, we decided to use JTBD approach to interviewing users. JTBD made a good fit as it focuses on exploring user motivation and unmet needs (jobs). As Alan Klement says in his book “<a href="http://www.whencoffeeandkalecompete.com/">When coffee and kale compete</a>”:</p><blockquote>Your guiding star in understanding your customers’ JTBD is their motivation to better their lives. Focus on that. Focusing on functionality will distract you.</blockquote><p>So during interviews our questions concerned not only current solutions but also what users consider as alternatives and what they used in the past:</p><ul><li>What did you do before current solutions?</li><li>What you did and didn’t like about previous solutions?</li><li>What do you see as alternative to current solution?</li><li>What do you like about it?</li><li>If you couldn’t use current solution, what would you do instead?</li></ul><p>Knowledge that we gained helped us to understand what user expects from a new product and how to prioritise features.</p><h4>6. Data analysis</h4><p>To make sure you get enough data from your users and to process it afterwards, it’s better to dedicate at list a day per group. We spent whole day with representatives of each user group. Every day we started with inquiries, then we collected and processed our findings, next we shared results with interviewed users and discussed unclear matters.</p><p>What to do with research findings? We used <a href="https://www.nngroup.com/articles/affinity-diagram/">affinity diagram method</a> to organise data into groups and identify relationships. After first interview we gathered all notes and captured one action/process per sticky note. We also mentioned channels and system statuses where needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*KM92y1RwUF2Jd0JCL_0tAQ.png" /></figure><p>The processes in our system are framed by teams and projects, therefore we grouped notes by user groups (by colour) and by project stages. At the end of each day we invited users to go through stickies and confirm if we understood them correctly. Sticky notes on the wall provided a basis for further work on <a href="https://www.nngroup.com/articles/service-blueprints-definition/">service blueprint</a> (which is another great topic to write about).</p><h4>In conclusion</h4><p>Conducting contextual inquiry is a great experience both for the project and for the team. On the one hand, real-world contexts reveal behaviours for which you might not be aware. On the other hand, working onsite brings the team together and contributes into common understanding.</p><p><em>Special thanks to </em><a href="https://www.nngroup.com/"><em>NN/g</em></a><em> blog that is the source of truth in any UX related question.</em></p><p><em>Special thanks to </em><a href="https://www.apollo-design.center/"><em>Apollo Design Center</em></a><em> that greatly contributes into design culture in Ukraine.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c762760e5e05" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-get-the-most-out-of-contextual-inquiry-c762760e5e05">How to get the most out of contextual inquiry</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[App Design & Development Conference 2018]]></title>
            <link>https://medium.com/@anastasiia.naumets/app-design-development-conference-2018-60425af8bce?source=rss-e139132ebc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/60425af8bce</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Nastia Naumets]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 13:39:39 GMT</pubDate>
            <atom:updated>2018-07-10T13:39:39.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c45P6GXTu96dGi6ImWRKJw.png" /></figure><p>Hello. My name is Anastasiia 💁‍. I’m a UI/UX designer at <a href="https://eleken.co/">Eleken</a> company in Kyiv, Ukraine. I started my career path 6 months ago and since then I keep my mind wide open to every opportunity that may help me to become better as a designer and as a person.</p><p>I was inspired to write this review by <a href="https://www.linkedin.com/in/tracyosborn/">Tracy’s Osborn</a> talk on <a href="https://addconf.com/2018/">ADDC</a> conference in Barcelona 🙌👩. Tracy is a designer, developer and author (Toronto, Canada). She shared some good practices in marketing for a new app promoting.</p><p>Some words about me: traveling is my passion. Meeting new people with different culture, mentality, background, experience and mindset is vital for me. A week ago I’ve attended <strong>App Design and Development Conference</strong> in Barcelona, Spain. That was my first conference experience abroad and it was super awesome 🔥. I’ve enjoyed beautiful city, gorgeous cuisine, delightful people and of course fascinating talks of high-level professional designers and developers from world top companies.</p><p>Tribute to organisers: organisation level 👍, venue 🏰, food 🤤, staff 🤘, guests 👩‍🎤👨‍🎤, attendees 🤪.</p><p>During the conference speakers have covered many topics:</p><ul><li><em>designer and developer collaboration</em></li><li><em>AR &amp; VR</em></li><li><em>chatbots</em></li><li><em>prototyping</em></li><li><em>depth sensing technology</em></li><li><em>gaming experience for UX</em></li><li><em>design for emerging markets</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ksJUGQ9aCh6SmJfGgFH_yA.png" /><figcaption>Eli Ganim, Engineering Manager, Facebook</figcaption></figure><p>The first one and maybe the most significant talk for me was about apps designed for <a href="https://en.wikipedia.org/wiki/Emerging_markets#Commonly_listed">emerging markets</a> from <a href="https://www.linkedin.com/in/eli-ganim-b1901825/">Eli Ganim</a> 👨‍🔧. Eli is an Engineering Manager at <strong>Facebook</strong>. He revealed the importance of building apps for users from such countries as China, India, Russia, Brazil as emerging markets will account for over 90% of new mobile subscribers globally by 2020. We all should absolutely keep this in mind while working on our own projects.</p><p><a href="https://www.linkedin.com/in/dori-adar-48532b55/">Dori Adar</a>, the founder of <strong>Hands on Games</strong> and UX specialist, provided important takeaways from the gaming world to apply in almost every digital product design. During his talk we could observe real time experiment on how <em>“Compelling Goal”</em> influences frequency and eagerness of user experience, find out good patterns of teaching users how to use a product, learn the importance of <em>random</em> reward and storytelling in user experience.</p><p><a href="https://www.linkedin.com/in/cristinasantamarina/">Cristina Santamarina</a>, the technology consultant and founder of the <strong>Neon project</strong>, shared the most important language challenges she faced when designing conversational interfaces (bots). During her talk Cristina proposed techniques how to deal with such problems as typos, slang, trolls, technological illiteracy and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n2nSTjKAVMotLNniJYnxeQ.png" /><figcaption>Sara Cambridge, UX Resercher, Google</figcaption></figure><p>Cherry on the cake 🍒 <a href="https://www.linkedin.com/in/saracambridge">Sara Cambridge</a>, User Experience researcher from <strong>Google</strong>. Sara presented her research that is focused on understanding of designer/developer collaboration. She has interviewed tones of designers and developers and shared her insights into what works and what does not for the teams. The most important lesson that I’ve learnt from this speech is that we should communicate a lot. Discuss, ask, advise, share, support each other on every stage of product development. Bring out issues and ideas, suggest solutions, be open to different perspectives.</p><p>The other thing that I find crucial especially for designers (devs) who just started their careers is the feeling of psychological unsafety. 👶 designer may have something to say, that can be helpful and will eventually improve the process, but he/she does not because he/she thinks that it’s stupid, it’s not worth to be mentioned, other colleagues will start laughing at him/her.</p><blockquote>According to Sara we should think of our work as of a perpetual learning process. Making mistakes is not the end of the world and they even should be made while learning. That’s why we need to speak up as much as possible. Only in this way psychological unsafety will be gradually gone.</blockquote><p>Besides learning and discovering new things, I’ve met wonderful people that made my stay even better. Thank you <a href="https://www.instagram.com/mert_kahraman/">Mert</a>, <a href="https://www.instagram.com/drewb_is_home/">Andrew</a>, <a href="https://www.instagram.com/anivma/?hl=ru">Antonia</a>, <a href="https://www.instagram.com/robertotim/">Rob</a> for sharing this experience with me ❤️.</p><p>Thanks to the dedicated organisers of the conference for your contribution in our professional and social lives 🙏.</p><p><strong>Conclusion:</strong></p><p>Go to conferences abroad 🛫.</p><p>Make people know your company and your country 🤝.</p><p>Share your vision 🙆‍.</p><p>Dance on bumping boat 💃.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9mzXNHo_DDWI5t6xyNmxQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60425af8bce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>