<?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 Kajsa Westman on Medium]]></title>
        <description><![CDATA[Stories by Kajsa Westman on Medium]]></description>
        <link>https://medium.com/@kajs?source=rss-9e7b410f1e39------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*vD7oWJbeHr2XLO9YKJff7w.png</url>
            <title>Stories by Kajsa Westman on Medium</title>
            <link>https://medium.com/@kajs?source=rss-9e7b410f1e39------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:37:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kajs/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[Design research is only as good as the action it enables]]></title>
            <link>https://uxdesign.cc/design-research-is-only-as-good-as-the-action-it-enables-843e09fb7d84?source=rss-9e7b410f1e39------2</link>
            <guid isPermaLink="false">https://medium.com/p/843e09fb7d84</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[t]]></category>
            <dc:creator><![CDATA[Kajsa Westman]]></dc:creator>
            <pubDate>Mon, 06 Apr 2020 09:40:52 GMT</pubDate>
            <atom:updated>2020-04-29T12:14:24.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Sketch of researcher talking to woman on the street" src="https://cdn-images-1.medium.com/max/1024/1*imoXV5kMrudAt7wfv8WFAw.png" /></figure><p>When <a href="http://www.topp.se/">Topp’s</a> design teams engage users and test prototypes, we’ve got one ultimate goal: to enable our teams or our clients to take action. It’s common to start design projects with a research phase, but in our experience, the hand-over between research and design can be tenuous. Embedding user engagements in the design process instead, tends to lead to action.</p><p>There’s long been a debate in the design community about <a href="https://en.wikipedia.org/wiki/Quantitative_research">quantitative</a> vs <a href="https://en.wikipedia.org/wiki/Qualitative_research">qualitative</a> research, and which is though of as “better”. From our perspective, all the tools for user research — both quant and qual— can have value in the design process, as long as they’re geared toward action. So rather than judging one research method as “the best”, we acknowledge their strengths, weaknesses, and best uses of each. This article outlines 6 examples of research activities, both quant and qual methods, and when to use them to their strengths.</p><figure><img alt="illustration of high level steps in selecting a research methodology" src="https://cdn-images-1.medium.com/max/1024/1*2jWJi4bWlnekJmVCmfxBlA.png" /><figcaption>Research activity selection process, at a glance</figcaption></figure><p>The numbers and statistics produced by quantitative methods can signal the existence of a problem, but tell us little about its cause, or how to solve it. This is the main reason most design researchers use qualitative methods, exclusively or alongside quantitative ones. Qualitative research helps us empathise with users, to understand their needs and environment. This kind of empathy not only tells us why a problem exists in the first place, it also lets us build a narrative about a potential solution, that the design team can organize around. A narrative based on real user experiences helps us share intent and knowledge, between the stakeholders that assign budgets, the designers that propose the solution, developers that implement it, and the testers who test it.</p><p>The narrative is just as valuable a research outcome as data or insights.</p><p>User research can produce a wide range of outputs, and demand more or less effort, depending on how you’re engaging users. A few hours of covert observations can get some ideas going, and an A/B testing sprint can give you a backlog of problems to solve. A qualitative and quantitative combined study can result in a detailed report that drives the whole project, but might take months to complete. This is why we tend to use the term “user engagements” at Topp, which encompasses a wide range of formal and informal investigations, rather than “user research”, which implies something more academic.</p><h3>What are we trying to achieve with user engagements?</h3><p>As a design team, everything we do should get us closer to a solution. So every user engagement should have some impact on how we eventually execute the solution. This could mean nailing the project definition, isolating a research question or direction of inquiry, deciding on features, or crystallizing a design detail. From the design team’s perspective, the most valuable data or insight that comes from a user engagement enables design action. We know it’s valuable if it does one or more of the following:</p><ul><li>It helps us distinguish between wants and needs</li><li>It points out a new opportunity</li><li>It narrows down or changes the task at hand</li><li>It tells us what to avoid (and why it should be avoided)</li><li>It gives us empathy for the user’s context, in a way that changes how the product is designed</li><li>It clarifies what is required for the product to be valuable to users</li></ul><p>To extract these types of insights from user engagements, asking “why” becomes very important. What was the reasoning behind <em>this</em> reply, <em>this</em> choice?</p><p>For example, when users rate down a blinking blue light, is it really about the colour?</p><p>Or is it actually about something else? Perhaps the blinking pattern is too aggressive, or the bulb size is too big. Does the light need to be removed altogether? The “why” behind the “what” has an enormous impact on the action we eventually take.</p><figure><img alt="Two people taking" src="https://cdn-images-1.medium.com/max/1024/1*xOaA7nTwEgeGO1JUqJz1Yg.png" /></figure><h3>Qualitative Methods: Gather insights to get to action.</h3><p>There are myriad qualitative research methodologies out there, but we’ve focused on three specific ones, because they’re scalable, and they lead to action.</p><p>By scalable, we mean they can yield useful results after meeting 7–10 users, and can also be used at large enough scale that you’re essentially doing in-market testing. As a rule of thumb, when you surpass 10 users you start getting repetition in responses, resulting in a diminishing return of insights. When you get past 15–20 users, the engagement can take months, and the benefits of choosing a qualitative methodology diminishes.</p><p><strong>Observations</strong></p><p>Observation is a good way to find <em>inspiration</em> at the start of a project. Observations give you insights about behaviours: what people actually do, not what they say they do. The design actions that come out of observations are ideas to try, problems to address, and values to aim for. The effort you put into observations scales up well. It can yield insights when you spend a single session spent passively observing and taking notes for a few hours. It also yields insights when you visit multiple locations in multiple markets over several weeks with an interview protocol.</p><p><strong>Monitored Testing</strong></p><p>Monitored testing is a good way to <em>inform</em> how to iterate or <em>inspect</em> the execution of a design. It’s not enough to just imagine what would happen if you implemented a particular solution — the emotional aspects of most products demand that you actually experience them. Experimenting and making multiple prototypes is the key to evolving a design quickly. By monitoring a prototype in use, in combination with interviews, you’ll encounter both direct problems and new opportunities.</p><p>One misconception about testing is that it has to be done according to a protocol that you repeat strictly each time. But it also yields valuable results when performed iteratively, on prototypes that change with each iteration.</p><p><strong>Interviews</strong></p><p>Interviews can complement observation and testing; they can also stand alone. As a stand alone method, it’s good to start by finding inspiration and thoroughly understand a topic. As a complement to other methods, it’s a good way to understand motivations and fears (the “why”).</p><p><a href="https://www.youtube.com/watch?v=LX5SAw1gw7s"><em>Jon Kolko outlining the value of qualitative research</em></a></p><figure><img alt="Sketch of 3 digital devices" src="https://cdn-images-1.medium.com/max/1024/1*-7tfyWllGiAVOK60j9bx1g.png" /></figure><h3>Quantitative Methods: Gather data to get to decisions.</h3><p>User engagements that gather data points are often done to facilitate decisions on what to spend efforts on, before defining a final product. But it’s also a method for <em>inspection</em> and <em>iteration</em> of close-to finished products, that leads to design actions. These are three examples.</p><p><strong>Surveys</strong></p><p>Surveying is a rather limited method, as it mostly provides answers to the questions you know to ask. But it can be a low-effort tool to <em>inform</em> a position: confirm or debunk a prejudice, answer a question, or verify a proposition.</p><p><a href="https://www.surveymonkey.com/mp/quantitative-vs-qualitative-research/"><em>SurveyMonkeys guide to quant vs qual in surveys</em></a></p><p><strong>Smoke Tests</strong></p><p>A smoke test is a way of measuring the <em>desirability</em> of a digital experience idea, for example by creating a fictional ad campaign and website, then seeing how many people click through on it. When used to evaluate fictional solutions smoke tests sit in an ethical grey zone — they don’t cause any direct harm, but they can definitely be misleading — but have the advantage of delivering hard numbers based on the reactions of real world users.</p><p>You perform smoke tests in order to <em>inform</em> or <em>iterate</em>; to eliminate ideas from a large pool in order to focus your efforts. They’re much less useful, though, for generating new ideas or solving problems. Smoke tests only answer the question “is this more desirable than that?”, and tell you nothing about why. You need a large enough volume of smoke tests, with similar executions, in order to produce comparable results.</p><p><a href="https://en.wikipedia.org/wiki/Smoke_testing_(software)"><em>Smoke test in the context of software development is slightly different</em></a></p><p><strong>In-Market Testing</strong></p><p>In-market testing means releasing a (usually digital) product in a limited, monitored way. This can be a good way to <em>inspect</em> a nearly finished product, by gathering data on key indicators like performance, adoption, and discoverability. Depending on how the test is set up for monitoring, different types of outputs can be generated. Like smoke tests, in-market testing can be used to kill off ideas, but it can also be a way to find new problems. In-market testing requires a nearly finished product or feature to be valuable. The more complex the product, the more complex the testing.</p><p><a href="https://techcrunch.com/2019/11/14/spotify-confirms-its-testing-real-time-lyrics-synced-to-music/"><em>Spotify is one company known for their in-market testing</em></a><em>.</em></p><h3>It’s Always About Increased Confidence</h3><p>All types of user engagements should be designed to enable your team to act with more confidence. They should give stakeholders confidence that the product is desirable, give developers confidence that it’s stable, and make designers confident that they are solving the right problem.</p><p>User engagements are active. They create opportunities, and they let you iterate and execute versions of a product. Engagements that are done within the design process may take more or less time, and produce outcomes with higher or lower fidelity, but they should always propel the design forward. They should be performed by designers, together with small groups of users, preferably face to face. This allows multiple things to happen at once. Non-verbalised problems are often spotted in face-to-face settings, that would never appear in a phone interview or survey.</p><p>This is when the new behaviours and opportunities are found, because similar tendencies are observed across users. When users say one thing and do another, this is the moment when new ideas are born. More importantly, these moments offer clarity for designers, and bring us closer to action — the highest goal of any kind of engagement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=843e09fb7d84" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-research-is-only-as-good-as-the-action-it-enables-843e09fb7d84">Design research is only as good as the action it enables</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[The State Of Responsible UX]]></title>
            <link>https://medium.com/swlh/the-state-of-responsible-ux-e2c0277ee592?source=rss-9e7b410f1e39------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2c0277ee592</guid>
            <category><![CDATA[responsible-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Kajsa Westman]]></dc:creator>
            <pubDate>Mon, 27 Jan 2020 16:16:34 GMT</pubDate>
            <atom:updated>2020-02-05T21:52:37.667Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What’s considered “Responsible” in the context of User Experience Design has shifted from product execution, to how digital services (and the companies behind them) behave when you’re not directly interacting with them.</em></p><p>In 2016, a group of us at Topp published a piece called <a href="https://medium.com/the-conference/responsible-iot-3-essential-iot-design-features-504ce4c62e77">Responsible IoT</a> (“R.Iot”). Having worked for several years on IoT projects, we realized it was time to articulate some of the foundational questions designers need to ask when designing connected devices.</p><p>The article was born out of worry more than anything else. We’d seen IoT products end up in landfills less than a year after launch. We’d seen hardware designed to last for decades, running digital experiences that would be obsolete in months. We’d seen a lot of dishonest products, and cynical products of questionable value to the user. We’d also seen data privacy go from a fringe concern to something that was impacting everyone, with very few solutions in sight.</p><p>We could see even more problems on the horizon, and needed to articulate the arguments that would help our clients make better decisions about what IoT products to make, what to reconsider, and what to avoid.</p><blockquote>“Just because you can, doesn’t mean you should”<em> </em>— <em>we argued. Not always successfully.</em></blockquote><p>These days, it’s difficult to separate the design of an IoT product from any other digital product — it’s all some form of User Experience (UX). As UX design has matured as a discipline, the average UX designer has become more multifaceted. Designing responsibly is one of these facets.</p><p>Designing responsibly is such a common discussion topic at conferences and in forums that it’s taken on a life of its own. A Google search for “responsible design” gets 1.6 million hits. But what’s considered responsible UX today is less about how you implement a product interface, and more about the background actions of the company behind it: strategy, data management, service agreements, customer relationships, and so on.</p><p>So what has changed?</p><h3>1 — Ethical concerns are raised earlier.</h3><p>Conversations about the social implications, ethical concerns, and unintended consequences of a new product are more commonplace today than a few years ago, and they’re raised earlier in the project. We see clients raising their own concerns about product ideas, in structured and constructive ways, before we as the design team have a chance to point them out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*oBbxjcVN2wKMFIyCR9Wsyw.png" /></figure><h4><strong>Example: Parental Control</strong></h4><p>One example of how ethical concerns result in new products is the growing issue of how minors interact with them. This has given rise to a wide range of solutions: children’s accounts, <a href="https://www.youtubekids.com/">children’s versions</a> of products, and <a href="https://parents.nianticlabs.com/">parent portals</a> that give parents more control over their children’s digital life and data. We’re even looking now at the possibility of devices that can proactively <a href="https://niantic.helpshift.com/a/niantic-kids/?p=web&amp;s=troubleshooting&amp;f=i-m-an-adult-but-i-only-see-the-niantic-kids-login-method-when-trying-to-log-in&amp;l=en">detect if the user is a child</a>.</p><h3><strong>2 — Digital products are treated like continuous relationships, like a service.</strong></h3><p>One of the biggest changes in digital products in recent years is the shift from a single release to an ongoing service with continuous development. A product’s user experience is now intended to evolve over time, so it must be maintained and continuously improved upon by the provider, in alignment with their product strategy.</p><p>This means that users’ relationships with the companies behind digital products are also changing. It’s no longer a product that you’re convinced to pay for once; it’s a subscription that must continuously reaffirm its value. And ongoing relationships need ongoing maintenance.</p><h4>Design Skills Needed Throughout the Organisation</h4><p>This shift towards services has brought changes in how designers work day-to-day, especially as their formerly niche design skills make their way into departments throughout the company. Designers, and their inherent user-value perspective, are increasingly considered to be core team members from start to finish, while developing products &amp; strategy as well as working with innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*aW5qptOH8qZYiuXF5iyXfw.png" /></figure><h4><strong>Example: Smart Fridge</strong></h4><p>For one example of how digital products are treated like services, look at the screen interfaces on smart appliances. Previously, the screen and its GUI became outdated much faster than the appliance itself. As more companies push software updates over the air, the combined longevity of appliances + screen is improved. It might not be so easy to update the resolution of a screen, but at least its GUI is able to age more gracefully. This is making companies more aware of how quickly a “trendy” GUI can look dated, prompting them to look for designs that can withstand time.</p><p>Screens in home appliances probably aren’t going away anytime soon, but they could be superseded by screen-less interactions like voice controls.</p><h3><strong>3 — Live experiments are part of the development process.</strong></h3><p>Beyond just prototypes — which are now standard practice in pretty much any design effort — we’re also seeing a growing demand for early minimal-effort product experiments, as a way of facilitating decisions and informing long term product strategy. This is part of a bigger move towards opening up the digital product development process, by continuously running in-market and live experiments on smaller user groups (also called “user engagement”).</p><h4>More Focus on Experimentation and User Engagement</h4><p>This effort goes hand in hand with creating digital products that continuously evolve, as user engagement informs product desirability, and helps us determine which concepts are worth moving forward. This allows you to examine your expectations of how well a digital product will be received, and how feasible it is to build. This is a positive change towards a healthier UX practice with a better ability to execute more responsible UX design.</p><p>Increased user engagement also shines a light on what’s actually responsible practice. When you seek out users and engage them directly, this tends to become apparent quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*yY2h7EnOe7SJdmYo0pOZyQ.png" /></figure><h4>Example: Small Scale Testing</h4><p>A good example of the demand for (live) experiments is the common practice of companies sourcing testers amongst their employees and existing users to run early tests, before deciding on larger scale development. Tech sites report on the latest tests run by <a href="https://thenextweb.com/facebook/2019/11/15/facebook-is-quietly-testing-an-instagram-feed-like-feature/">Facebook</a> and <a href="https://techcrunch.com/2020/01/21/spotify-test-lets-influencers-post-stories-to-introduce-their-own-playlists/?guccounter=1&amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;guce_referrer_sig=AQAAALlE6rH3vtEuBtoq1tVBvplIwiUR890b-XtLNY4NVPpRSYAnLDHT4rVtQXEjzrk5edriEJXxifAONFp4qH2ehDNjK-yKqDRMBWr3wWkglCPnPAVO-_qADLO8TO-3zRcGUHT6zumwmfJNEcqewhH2IRj6KsjYjxwkyPOgE01jjLTT">Spotify</a>. Connected products like <a href="https://m.co/se/en-US/press/volvo-car-mobility-launches-m-the-smart-car-sharing-service-in-greater/">Volvo M</a> are also doing small-scale user testing while iterating a product.</p><h3><strong>4 — Privacy is explained, and a value proposition.</strong></h3><p>Products and services have become better at explaining their privacy policies, out of necessity. Most are keen on communicating that they can be trusted with your data. Legal text that was once completely impenetrable is increasingly summarised in natural language, and users are more often given the option to “opt-in” (rather than the presumptuous opt-out) when signing up for services. We’re also seeing installation guides and out-of-box experiences that provide recommendations on how to manage your privacy, and what considerations to make even after installing a smart home product.</p><h4>Explaining Data Privacy is Responsible</h4><p>Digital products have expanded far beyond the screen, and connected products have more autonomy than in the early days of IoT. As humans are removed from the transactions and replaced by machine-to-machine or AI-to-AI protocols, conversations emerge about what is reasonable for a user to control, or even understand?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*ho9cnJcb4oDKbN-6L6B4MQ.png" /></figure><h4>Example: Explaining Privacy</h4><p>For many companies, privacy concerns have moved out from legal documents and on to corporate sites in the form of <a href="https://nest.com/se/privacy/">policies and statements</a>. We also see this trend in product set-up flows, such as when <a href="https://youtu.be/WnM686Wi3bI?t=286">Google Nest</a> casually adds a reminder to consider that a guest’s interactions with the device are stored along with the user’s.</p><h3>5 — GDPR arrived.</h3><p>The roll-out of the General Data Protection Regulation (GDPR) was a wake-up call to many companies. Data privacy is now an early contract concern. While GDPR is only applied in the European Union, its existence has had global effects. Even suspicion that a new concept or feature is unable to adhere to GDPR can kill it while still in ideation.</p><p><em>We’re still waiting for broader adoption of more user-friendly data management control panels!</em></p><h3>So, what’s on the horizon?</h3><h4>Improved Digital Products and Services Through Science</h4><p>Studies on how digital products impact our lives will guide the development of better UX practices, improved interaction patterns, and more realistic priorities for their function. When studies showed that notifications cause micro-stress, it forced designers to re-evaluate best practices for how to use and display them.</p><h4>Trust Becomes (Even More) Central</h4><p>One way of summarizing the current state of responsible UX is to acknowledge that companies want to create more trust around their product. The link between trust and loyalty is undeniable. Companies increasingly want you to choose to trust them with your data, and in exchange, you get a more carefully designed digital product.</p><p>This helps explain why more companies are talking about social impact, policies, and actions for sustainability on their websites. We’re likely to see companies trying out a wide variety of ways to confirm to users that they are indeed worth trusting.</p><h4>More Contempt Towards “Immoral” Companies</h4><p>While designers are getting better at helping clients create more responsible digital products, the general public is also more likely to notice when products and companies don’t act responsibly. And unlike governments, consumers are concerned not just with legal adherence, but also moral and ethical behavior.</p><p>As companies strive to demonstrate their responsibility through better data transparency and privacy policies, how effective they’ll be depends heavily on users’ trust in their messaging. Do users trust a product to do no harm? The trust in a product is hinged on the ethics and actions of the company behind it. In 2018 and 2019 we saw several companies come under increasing scrutiny, and even saw some products boycotted, as their leaders and policy makers were dragged through the news. The <a href="https://www.wired.com/story/facebook-security-breach-50-million-accounts/">Facebook security breach</a> and <a href="https://www.businessinsider.com/uber-scandal-timeline-2017-5?r=US&amp;IR=T#it-hasnt-been-all-bad-though-ubers-diversity-report-was-better-than-expected-25">Uber’s string of scandals</a> come immediately to mind. Is it possible to retain trust for a company’s product when users start to have doubts about the company’s behaviour on the whole?</p><p>It’s not just designers and users who are reacting to companies’ actions around digital responsibility — expect legislators to force their hands too. They might soon be legally required to take more responsibility as well.</p><p>What “Responsible design” is, when that happens, is hard to know. But it will continue to change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2c0277ee592" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-state-of-responsible-ux-e2c0277ee592">The State Of Responsible UX</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>