<?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 Bettina D&#39;ávila on Medium]]></title>
        <description><![CDATA[Stories by Bettina D&#39;ávila on Medium]]></description>
        <link>https://medium.com/@medinous?source=rss-f30b3154f62c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kokBQ_DxWFmAWbTd.</url>
            <title>Stories by Bettina D&amp;#39;ávila on Medium</title>
            <link>https://medium.com/@medinous?source=rss-f30b3154f62c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:48:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@medinous/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[Why AI (desperately) needs designers]]></title>
            <link>https://uxdesign.cc/why-ai-desperately-needs-designers-06c30e2601b8?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/06c30e2601b8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 22:38:00 GMT</pubDate>
            <atom:updated>2025-02-12T10:03:16.803Z</atom:updated>
            <content:encoded><![CDATA[<h4>Artificial Intelligence, despite its benefits, presents designers with unprecedented challenges that demand our action.</h4><p>The responsibility of us designers to protect user interest and value has never been so important. Not only we’re living in a trendy era with the rise of ChatGPT and many other AI tools, but we’re also experiencing how these systems shifts control away from the user. Whether it’s automating tasks, discovering hidden patterns, enhancing user experiences, generating new content, or optimising decisions, AI’s existence is driven by its ability to learn from data and improve over time without explicit programming. Currently, the speed and the way these super powerful technologies are being rolled out, we cannot follow as society, which causes great impact on the economy, on mental health, on culture and on society as whole.</p><blockquote>“We, designers, have to own up to our role in this emerging predictive world because we have our invisible hand meddling with the controls”— Helen Armstrong</blockquote><p>This quote is from the wonderful book <a href="https://helenarmstrong.info/big-data-big-design/">“Big Data, Big Design: Why Designers Should Care About Artificial Intelligence”</a> authored by Helen Armstrong, which explores the intersection of design and artificial intelligence, emphasising the role of designers in shaping AI-driven experiences. In a predictive digital world, we play a crucial role in ensuring that AI solutions are ethical, transparent, and aligned with human values. We must consider the potential biases in data, the impact on user privacy, and the societal implications of our creations. By prioritising responsibility and accountability, designers can help build a future where AI technologies enhance human capabilities and improve quality of life.</p><p>The book explores these issues in depth, featuring contributions from various designers, educators, and researchers who work at the intersection of artificial intelligence and design. It serves as my primary reference for the questions and discussions raised in this article, but I have drawn from numerous other sources to provide a comprehensive perspective, all of which are listed at the end of this article.</p><figure><img alt="An image of the book cover of “Big Data, Big Design” from Helen Armstrong" src="https://cdn-images-1.medium.com/max/1024/1*uJRzRn7_H-HVx0x4DKDM-Q.png" /><figcaption><a href="https://helenarmstrong.info/big-data-big-design/">https://helenarmstrong.info/big-data-big-design/</a></figcaption></figure><p>The central theme of the book — and of this article — is to emphasize the responsibility of designers in the ethical development of AI products and services. Our discipline is fundamentally human-centric, focusing on understanding and addressing human needs and desires within the broader societal context. The psychology, research, and strategy we employ in designing our products have a profound impact on the physical, mental, and emotional well-being of people worldwide.</p><h3>AI is human-centric…?</h3><p>Human-centric design, like inclusive and participatory approaches, ensures fairness in data models, mitigates bias, and promotes inclusivity. It is widely recognised that human-centric design has been the guiding principle of all design frameworks and processes over the past decade, and this should be no different when working with AI. These perspectives have been valuable because they inform decision-makers about potential human impacts and help anticipate unintended consequences. Initiatives, such as Stanford University’s Human-Centered AI Institute and MIT’s substantial investment in AI education, exemplify the global effort to prioritise a human-centric approach. According to <a href="https://medium.com/@sarahtan.twh/the-problem-with-ai-development-today-designers-need-to-step-up-3d00aab146c8">this article</a> by Sarah Tan, by exploring AI’s human impact through various Human-Centered Design (HCD) approaches, design aligns values between humans and machines, integrating ethics at the project’s core.</p><figure><img alt="A visual schema similar to a solar system, showing “Humans” as a bubble in the center of the schema while multiple “Algorithm &amp; AI” bubbles orbit around “Humans”" src="https://cdn-images-1.medium.com/max/1024/1*vyun57MPFR4tdOYv8wM8Eg.png" /><figcaption><em>Putting humans at the center of AI systems — Human-Centered Artificial Intelligence: Three Fresh Ideas. Shneiderman B. (2020)</em></figcaption></figure><p>Advocating for user needs, design research has the power to examine AI implications in real-world contexts — addressing socio-economic dynamics too. However, this isn’t easy. We, as designers working in the industry, often feel pressured to quickly adopt the latest trends without time for reflection. We are frequently required to use behavioural research to influence user choices, sometimes at the expense of their well-being. Additionally, we must operate in fast-paced environments, adopting to the ‘move fast and break things’ mentality popularised by early Facebook culture. This approach can make it harder for us to design thoughtfully and ethically</p><p>But how to stand up for people in the face of such forces?</p><h3>AI capabilities all designers should know</h3><p>Here’s what I aim to achieve with this article: to inspire designers to get more involved in creating AI systems, so we can make the process more ethical and human-centered. This means using design thinking as our guide to reduce the negative impacts of AI on society by developing human-centered AI systems and guidelines.</p><p>How we can achieve this is still being figured out, and we are all part of this process! To help, I want to highlight the main capabilities discussed in Armstrong’s book, where we designers should be actively involved. We need to advocate for design decisions that meet user needs and respect the socio-economic context in an ethical way. It won’t be easy, but we can start paving the way with these elements.</p><h4>1. Designing to power up predictions</h4><p>Prediction is a central capability of machine learning (a subset of AI that involves training algorithms on data to make predictions or decisions without being explicitly programmed). In the context of predictive modelling, the goal of machine learning is to forecast future events or outcomes and anticipate behaviours based on patterns found in historical data.</p><p>For instance, we can think of Gmail’s feature that autocompletes sentences based on your past behaviour. Over time, the system learns an individual’s style so well that it can finish sentences and even suggest appropriate tones or sentiments.</p><figure><img alt="A screenshot of the Gmail email composition screen, showcasing Gmail’s predictive text feature. The model suggests completing the sentence based on the initial input: “Let’s talk tomorrow. What”. Gmail suggests “Let’s talk tomorrow. What time works for you?”" src="https://cdn-images-1.medium.com/max/662/1*lDmgP2_ciE-GkFu-cyiARQ.png" /><figcaption>Screen capture from my personal Gmail</figcaption></figure><p>Or we can think of the numerous applications across various industries, such as stock price forecasting, inventory and supply chain optimisation, healthcare predictions (such as disease outbreak forecasting), targeted marketing campaigns, and other personalised user experiences.</p><p>While these AI-driven predictions aren’t always 100% accurate, they offer significant benefits to businesses. The advantage is that by anticipating future demands, trends, and needs, companies can better prepare for opportunities and gain a competitive edge. For that end, designers are required to plan for a shifting experiential landscape when working with intelligent technology in their projects.</p><p>On the other hand, designers cannot blindly apply AI technology without the risk of subjecting humans to discrimination, surveillance, and/or manipulation, not just individually but at scale. Predictive models can sometimes reinforce existing biases or lead to unintended consequences.</p><figure><img alt="Four people wearing weird masks with different shapes" src="https://cdn-images-1.medium.com/max/1024/1*bJLmwqWWT6dABBCbLgCIuA.png" /><figcaption>“Face Cages are a dramatisation of the abstract violence of the biometric diagram”. More on: <a href="https://zachblas.info/works/face-cages/">https://zachblas.info/works/face-cages/</a></figcaption></figure><p>Designers have a responsibility to foresee these potential issues and take steps to mitigate them, ensuring that their designs are ethical and inclusive. As Kate Crawford, <a href="https://ainowinstitute.org/">AI Now Institute</a> founder, puts it:</p><blockquote>Understanding the politics within AI systems matters more than ever, as they are quickly moving into the architecture of social institutions: deciding whom to interview for a job, which students are paying attention in class, which suspects to arrest, and much else.</blockquote><h4>2. Designing to anticipate future scenarios</h4><p>In her book, Helen Armstrong explores the concept of anticipation, showing how designers can use AI to predict and meet user needs proactively. This involves leveraging data-driven insights to stay one step ahead of users, reducing friction and enhancing the overall user experience.</p><p>One advantage of anticipatory design is that it reduces decision fatigue by minimising the cognitive load on users through predictive systems. These systems offer relevant choices or take actions on behalf of users. For example, companies like Netflix and Amazon use predictive analytics to recommend products or content. However, there are ethical implications, as such systems might infringe on user autonomy or privacy. As Armstrong rightfully states on page 210:</p><blockquote>The promise of anticipatory design lies in its potential to craft experiences that feel intuitive and personalised. Yet, with this power comes the duty to wield it responsibly, ensuring that the human element remains at the heart of every design decision.</blockquote><p>Fortunately, there is a forward-thinking approach that allows us to create products and services that are resilient to change and can evolve with user expectations. Designers can use AI to simulate and model potential future scenarios, anticipating various user needs, environmental factors, and societal changes. This ensures that our designs remain relevant and adaptable.</p><figure><img alt="Screenshot of Flock’s mobile application screen, explaining which factors influece the user’s quota, such as wind speed and chance of rain." src="https://cdn-images-1.medium.com/max/856/1*B5Sc7UItSOcZT9q5eXDBUg.png" /><figcaption><em>Flock defines flight risk to make insurance for drone operations simple: the insurance company worked with studio IF to create an interface that help clients understand how automated decisions were made around insurance rates.</em></figcaption></figure><h4>3. Designing to create personal experiences</h4><p>Personalisation in user experience design involves tailoring interfaces, content, and interactions to meet the specific needs, preferences, and contexts of individual users. When we talk about personalisation in the context of AI, it often means leveraging predictive technologies and data analysis to deliver experiences that are more relevant and valuable to users at any given moment. Personalisation ensures that the information or actions presented to the user are useful, usable, and desirable, inspired by the popular quote from design researcher Liz Sanders.</p><p>AI can enhance personalisation by analysing vast amounts of user data to identify patterns and preferences, using predictive models to anticipate what a user might need or want next — this can involve considering the user’s current context, such as location or time of day, to provide more relevant suggestions. However, personalisation also raises ethical concerns, including privacy, bias, and transparency. This is why we, designers, play a crucial role in ensuring that personalisation is implemented effectively and ethically. We must understand user needs and preferences through research and testing, and continuously gather feedback to refine personalisation features.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDybczED-GKE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDybczED-GKE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDybczED-GKE%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6cf6ef6eec5b59e000dc098865a8e440/href">https://medium.com/media/6cf6ef6eec5b59e000dc098865a8e440/href</a></iframe><p>We can say that personalisation is a powerful tool in a designer’s toolkit, but as Armstrong emphasises, the success of personalised experiences hinges on the thoughtful and ethical application of AI insights. It is crucial to always prioritise the user’s best interests, ensuring that personalisation efforts are not only effective but also respectful and beneficial to the individual.</p><h4>4. Using AI as a Design Material</h4><p>Designing for AI is challenging because the technology is invisible and abstract. As designers, if we can’t ‘sketch’ a solution, it feels like losing a crucial ability. As interaction design professor Philip Van Allen puts it, ‘it’s like our arm is cut off.’ To address this, he created a no-code programming environment for his students, providing easy access to machine learning. The tool is called <a href="https://philvanallen.com/portfolio/delft-ai-toolkit/">Delft AI Toolkit</a> and it simulates an AI system in 3D, allowing designers to observe and manipulate the system’s behaviour and data sources in a virtual space before investing time and expertise into model training and building a physical robot.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBjsFq0DOrgQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBjsFq0DOrgQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBjsFq0DOrgQ%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7554deb21a70eb4fc12cd2a0689fdd80/href">https://medium.com/media/7554deb21a70eb4fc12cd2a0689fdd80/href</a></iframe><p>Another approach to working with AI as a design material comes from John Zimmerman, a professor at Carnegie Mellon University. He developed a method that focuses on the AI system capabilities rather than the underlying technology. Zimmerman observes that many of his design students are uncertain of what’s possible when working with AI technologies, so he uses a “match-making” system which helps them grasp the AI system’s potential. For example, he presents a two-class text classifier and asks, ‘What could you do with this, and for whom?’. This method helps designers identify existing capabilities and apply them in innovative ways. As with any design tool, the more we experiment with it, the more comfortable we become, and the more examples and abstractions of AI capabilities we will generate.</p><figure><img alt="Photography of numerous candy hearts with different colors and with different words inside, representing how algorithms can get these words combinations wrong, such as “Flying Whale” or “Crap”" src="https://cdn-images-1.medium.com/max/1024/1*CtuMa294Ag1Pdx1Kj3gXHw.jpeg" /><figcaption><em>Janelle Shane’s experiments with DALL-E 3 playfully tease out all the ways algorithms can “get things wrong”. Here, she jumps into the algorithmic training process to generate candy heart messages. More on: </em><a href="https://www.aiweirdness.com/dall-e3-generates-candy-hearts/">https://www.aiweirdness.com/dall-e3-generates-candy-hearts/</a></figcaption></figure><p>A third approach, which I find particularly effective, is using the <a href="https://www.ooux.com/">Object-Oriented UX (OOUX)</a> methodology. OOUX focuses on ‘objects’ before ‘actions,’ aligning with how users perceive the real world. It borrows concepts from object-oriented programming but applies them to user experience design. This approach works well with AI workflows by organising data and interactions around objects, making complex AI systems more intuitive for non-developers by matching their mental models. <a href="https://www.ooux.com/">Sophia Prater</a> is a leading expert in the OOUX field, and I highly recommend her materials and podcasts on the subject.</p><p>On a personal note, I recently completed my first project using this approach for a native AI product. The methodology was incredibly helpful. It allowed me to visualise the system’s functionality and limitations more clearly, which also aided the engineers. Additionally, it made my design process more tangible through object mapping and user flows, enhancing the quality and accuracy of my proposed solutions.</p><figure><img alt="A screenshot of a computer screen showing the drafts and post-its as a result of a workshop" src="https://cdn-images-1.medium.com/max/1024/1*hXsz8GhQB8XN40M4EI2Rsw.png" /><figcaption>A beautifully chaotic collaboration between me and the engineering team using the OOUX approach</figcaption></figure><blockquote>ML is the new UX. I envision UX practitioners leveraging machine learning as a design material creatively and thoughtfully, guiding users and technologists toward a deliberative ML-mediated future — Qian Yang, Cornell University</blockquote><h4>5. Designing to reduce climate impact of AI</h4><p>Although this isn’t mentioned in the book and isn’t a ‘AI capability,’ it is certainly one of the key skills designers should possess, especially in the 21st century with the rise of AI technologies.</p><p>There’s an article called “<a href="https://www.designerfund.com/blog/how-to-design-climate-forward-ai-companies/">How to Design Climate-Forward AI Companies</a>” by Santhi Analytis that emphasises the important role designers play in mitigating the environmental impact of AI technologies. It frames the challenge of AI’s growing carbon footprint — fuelled by energy-intensive processes like model training and data center operations — as one that requires urgent attention from both engineers and designers. Designers can contribute by creating energy-efficient UI/UX elements, minimising unnecessary data and media loads, and applying green software principles. Additionally, designers can push for socially equitable uses of AI by developing inclusive, climate-conscious user experiences.</p><p>The Intercept Brasil (in Portuguese) also published last year<a href="https://portalinvestne.com.br/the-intercept-big-techs-apelam-para-energia-nuclear/"> an article stating that the major tech companies like Microsoft, Google, and Amazon are now turning to nuclear energy as a solution in response to the growing energy demands of AI and data centers.</a> Microsoft plans to reopen the Three Mile Island plant, Google has partnered with Kairos Power for small reactors, and Amazon has invested $500 million in nuclear technology. Many of these data centres are being built in countries from the Global South, where labor and infrastructure costs are lower, raising concerns about resource exploitation. While nuclear energy is carbon-free and efficient, it is costly and carries risks, and critics argue that “big tech” is addressing a crisis of its own making, prioritising rapid technological expansion over sustainability.</p><p>The industry’s “move fast” mentality raises concerns about whether nuclear energy can truly keep pace with AI’s accelerating energy consumption, or if it will simply become another chapter in big tech’s history of unchecked growth. This Vox documentary tries to answer this question:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYGfJeH5HRDQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYGfJeH5HRDQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYGfJeH5HRDQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d8c5a33bba53566072d960d2be0f0f4/href">https://medium.com/media/8d8c5a33bba53566072d960d2be0f0f4/href</a></iframe><p><a href="https://sloanreview.mit.edu/article/will-ai-help-or-hurt-sustainability-yes/">In this other article from MIT</a>, the author Andrew Winston also highlights the growing environmental impact of AI and provides recommendations to reduce its carbon footprint, such as using existing models instead of creating new ones. It emphasises the role of designers in this issue, urging them to develop AI expertise to simplify complex concepts, communicate the “nutriscore” of AI in their products (its usage and environmental cost), and adhere to an ethical “code of conduct” similar to the EU’s AI Act, ensuring AI products are safe, transparent, traceable, non-discriminatory, and environmentally responsible.</p><p>As designers, we can influence user behaviour and company policies by incorporating transparent data models that reflect the true costs of AI, thus ensuring the technology not only solves human problems but also helps tackle environmental challenges.</p><h3>Conclusion: Let’s take action</h3><p>It’s easy to feel overwhelmed by the urgent need for AI ethics. AI is a versatile and dynamic field, capable of performing a wide range of tasks that can help solve real-world problems. However, algorithmic systems often reflect and amplify existing societal biases. Until interfaces clearly communicate the logic behind these algorithmic decisions, users won’t be able to hold these systems accountable. This is why designers and the communities they serve need to understand digital rights. We must hold ourselves and the industry accountable for the choices we make through our designs.</p><p>The key question is: Will we allow machine learning to prey on those already victimised by society, or will we use this technology as a mechanism for equity and justice?</p><p>Here are some actions we can start taking as designers in this industry:</p><ul><li>✅ Design for anticipation to prepare for multiple possible futures, making our designs more flexible and future-proof</li><li>✅ Think critically about the long-term impacts of our designs and the data-driven decisions that underpin them</li><li>✅ Articulate digital rights and guide users with transparency toward options through design interactions</li><li>✅ Break down complex privacy agreements into quick, comprehensible, just-in-time interactions</li><li>✅ Prototype future-facing concepts, like personal privacy agents</li><li>✅ Support collective digital rights organisations and community-driven dataset initiatives</li><li>✅ Ask early questions about ethics and biases to ensure technology adapts to human needs, not the other way around</li></ul><p>How do you approach building AI products? What examples do you know of ethical and inclusive design solutions?</p><h3>References</h3><ul><li><strong><em>“</em></strong><a href="https://helenarmstrong.info/big-data-big-design/"><strong><em>Big Data, Big Design: Why Designers Should Care About Artificial Intelligence”</em></strong></a><em> — Helen Armstrong (Book)</em></li><li><a href="https://www.bloomsbury.com/ca/design-and-the-question-of-history-9781472521606/"><strong><em>“Design and the Question of History</em></strong></a><strong><em>” — </em></strong><em>Tony Fry, Clive Dilnot, Susan Stewart (Book)</em></li><li><a href="https://www.interaction-design.org/master-classes/human-centered-design-for-ai?r=bettina-martins-davila"><strong><em>“Human-Centered Design for AI”</em></strong></a><strong><em> — </em></strong><em>Webinar</em><strong><em> </em></strong><em>by Niwal Sheikh (Product Design Lead, Netflix) by IxDF</em></li><li><a href="https://www.designerfund.com/blog/how-to-design-climate-forward-ai-companies/"><strong><em>“How to Design Climate-Forward AI Companies”</em></strong></a><em> — Article by Santhi Analytis</em></li><li><a href="https://medium.com/@sarahtan.twh/the-problem-with-ai-development-today-designers-need-to-step-up-3d00aab146c8"><strong><em>“The problem with AI development today: Designers need to step up”</em></strong></a><strong><em> </em></strong><em>— Article by Sarah Tan</em></li><li><a href="https://sloanreview.mit.edu/article/will-ai-help-or-hurt-sustainability-yes/"><strong><em>“Will AI Help or Hurt Sustainability? Yes”</em></strong></a><em> — Article by Andrew Winston</em></li><li><a href="https://www.cloudflare.com/learning/ai/what-is-predictive-ai/"><strong><em>“What is predictive AI?” </em></strong></a><em>— Article by Cloudflare</em></li><li><strong><em>“</em></strong><a href="https://uxdesign.cc/generative-ai-for-designers-understanding-the-ethical-and-legal-implications-fa7d6ac1221e"><strong><em>Reviewing the Terms &amp; Conditions of popular generative AI tools</em></strong></a><strong><em>”</em></strong><em> — Article by David Serrault</em></li><li><a href="https://medium.com/@sarahtan.twh/the-problem-with-ai-development-today-designers-need-to-step-up-3d00aab146c8"><strong><em>“The Problem with AI Development: Designers need to step up”</em></strong></a><strong><em> </em></strong><em>— Article by Sarah Tan</em></li><li><a href="https://uxplanet.org/ux-design-for-ai-artificial-intelligence-d9adcee801e7"><strong><em>“Design For AI (Artificial Intelligence)” </em></strong></a><em>— Article by Sudarshan Sahu</em></li><li><a href="https://designintech.report/designintechreport-2024.html#/minute-rapid-walkthru"><strong><em>“Design Against AI” </em></strong></a><em>— Website by John Maeda</em></li><li><a href="https://portalinvestne.com.br/the-intercept-big-techs-apelam-para-energia-nuclear/"><strong><em>“The Intercept: ‘Big techs apelam para energia nuclear’”</em></strong></a><em> — Article from </em><a href="https://portalinvestne.com.br/author/administrador/"><em>Portal InvestNE</em></a><em> mentioning the original piece from The Intercept Brasil</em></li><li><a href="https://www.ooux.com/"><strong><em>“OOUX”</em></strong></a><em> — Website by Sophia Prater</em></li><li><a href="https://ainowinstitute.org/"><strong><em>“AI Now Institute”</em></strong></a><strong><em> </em></strong><em>— Website</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06c30e2601b8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-ai-desperately-needs-designers-06c30e2601b8">Why AI (desperately) needs designers</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[Mastering Design Tokens]]></title>
            <link>https://medium.com/nyc-design/mastering-design-tokens-d492cdd92720?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d492cdd92720</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[token-design]]></category>
            <category><![CDATA[design-handoff]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Sat, 21 Sep 2024 11:35:43 GMT</pubDate>
            <atom:updated>2024-10-09T10:48:08.169Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Designer’s Guide Inspired by Henry Daggett’s Approach</h4><p>This article explores <a href="https://www.henrydaggett.com/">Henry Daggett</a>’s approach to design tokens, offering a clear methodology for creating and implementing these essential components in a design system. Inspired by his masterclass <a href="https://www.interaction-design.org/master-classes/design-tokens-powering-your-design-system?r=bettina-martins-davila">“Design Tokens: powering Your Design System”</a>, I highlight Henry’s approach on the hierarchical structure for managing design tokens effectively.</p><figure><img alt="A young man with short, light brown hair and glasses is standing indoors in front of a modern, curved architectural structure. He is wearing a dark blue shirt and is smiling softly at the camera. Behind him, there is a large window reflecting a city skyline in the distance, and some greenery is visible in the foreground." src="https://cdn-images-1.medium.com/max/1024/1*k5G67lxvxfclMV55rJOFdQ.png" /><figcaption>This is Henry Daggett</figcaption></figure><h3>What are Design Tokens?</h3><p>Let’s start with the basics. Design tokens are the fundamental building blocks of a design system, representing the smallest reusable elements of design that can be consistently applied across a product. Or, how Henry Daggett puts it:</p><blockquote>Design tokens are visual design decisions stored as key/value pairs.</blockquote><p>What he means is that design tokens translate into variables that store visual design attributes such as colors, typography, spacing, shadows, and other style properties. They serve as a bridge between design and development, ensuring that design decisions are implemented consistently across various solutions.</p><p>As a designer, mastering the creation and management of Design Tokens can significantly improve my workflow, enhance collaboration with developers, and ensure scalability and consistency across the design system elements. Here are some of the benefits while using design tokens:</p><ul><li><strong>Consistency across platforms:</strong> Design tokens ensure that the same visual elements are used across different platforms (iOS, Android, web), providing a cohesive user experience.</li><li><strong>Scalability:</strong> As the product grows and evolves, design tokens allow for easy updates and maintenance of the design system. Changing a token value will automatically update all instances where the token is used.</li><li><strong>Improved collaboration:</strong> Design tokens act as a shared language between designers and developers, ensuring that the design vision is accurately translated into the product.</li><li><strong>Efficient handoff:</strong> A well-documented design token system simplifies the handoff process, enabling developers to implement designs more accurately and efficiently.</li></ul><h3>How to Create and Manage Design Tokens</h3><h4>Step 1: Identify Core Visual Attributes</h4><p>Begin by identifying the key visual attributes of all primary elements that must remain consistent throughout your product. First, understand what aspects can be tokenized:</p><ul><li>Background color, text color, border color</li><li>Font family, font size, font weight, line height, letter spacing</li><li>Margin, padding, grid size, spacing scales</li><li>Animation duration, animation easing</li><li>Contrast ratio, ARIA labels</li><li>Breakpoints, device size, responsive grid</li><li>Border width, border style, border radius</li><li>Box shadow, text shadow</li><li>Container size, aspect ratio</li><li>Image, blending mode</li><li>Icon name, icon color, icon size</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6AZ7-BvWnYEdtctlKGSYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyDHD74rD4TaTH1NpfYuCw.png" /></figure><p>For instance, the structure of visual elements proposed by Henry Daggett typically include:</p><ul><li><strong>Color Tokens:</strong> Define your color palette, including primary, secondary, and accent colors, as well as variations like shades and tints.</li><li><strong>Typography Tokens:</strong> Define font families, sizes, line heights, and weights.</li><li><strong>Spacing Tokens:</strong> Define the spacing system, including margins, padding, and grid spacing.</li><li><strong>Sizing &amp; Border Radius Tokens:</strong> Define consistent sizing for elements like buttons, icons, and inputs, and define the corner radius used across components.</li><li><strong>Shadow Tokens:</strong> Define the shadow styles used across components.</li></ul><p><strong><em>👉 Always begin by tokenizing colors!</em></strong><em> Next, focus on typography, spacing, and layout. Finally, if necessary, tokenize your design system components (such as event cards and list items).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9y8G8LJ-uQS6Y7VZVbZRmA.png" /><figcaption>Always start with colors! Next, focus on type, spacing and layout attributes.</figcaption></figure><h4>Step 2: Organize Your Tokens</h4><p>Organize your tokens into a hierarchical structure to make them easy to manage and understand. While I share Henry Daggett’s approach to organizing design tokens, it’s crucial to recognize that their structure and use can vary across different companies and teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qplov6QGCTm62Ug_oa8V4w.png" /><figcaption><em>Here’s a visual comparison between the design token structures used by different companies</em></figcaption></figure><p>Daggett’s methodology introduces two key concepts: <strong>core tokens</strong> and <strong>semantic tokens</strong>. These elements play distinct yet interconnected roles in a design system.</p><ul><li><strong>Core Tokens:</strong> These are the fundamental blocks that define raw values for visual properties, such as colors, typography, and spacing. These tokens are typically neutral and not tied to any specific context or meaning. For example, a core token might define a color value like --color-blue-500: #3498db; or a spacing value like --spacing-small: 8px;.</li><li><strong>Semantic Tokens:</strong> These apply meaning or context to the core tokens, defining how they are used in specific UI elements or scenarios. For instance, a semantic token might define a primary button’s background color as --button-primary-background: var(--color-blue-500); or a heading&#39;s text color as --heading-color: var(--color-gray-900);.</li></ul><p>As you can see, the semantic tokens reference the core tokens, providing a layer of meaning that makes it clear how and where the design values should be used in the product.</p><p>The picture below portraits this relationship between the core token in red (gray100) and the semantic tokens in blue:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MIsWFzDaXXpnKBRI1ghlpg.png" /><figcaption>Each core token can be associated with one or more semantic tokens</figcaption></figure><p>This means that changing the value of a core token (for instance, --color-blue-500) will automatically update all associated semantic tokens (for instance, --button-primary-background), ensuring consistency across the entire product. This relationship allows for a more flexible and maintainable design system.</p><p>For the semantic tokens, Henry Daggett suggests a hierarchical structure breakdown coming from the most abstract to the most concrete (left to right). Here’s how it looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W1xBDjc_-ij7yzhumCxRyw.png" /><figcaption>The design token structure breakdown by Henry Daggett</figcaption></figure><p>This approach is similar to the one used in programming languages, where tokens are organized hierarchically to represent different levels of abstraction — from general categories like “variable” or “function” to more specific modifiers such as “static,” “private,” or “async”.</p><p>For the semantic tokens, Henry proposes a structure that starts off with the context (category, concept, property) to the most specific (variant and state). Here’s an example of how to write a semantic token that describes the color of a selected element:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCiCopJRRqiy5d1ehjF6Ew.png" /><figcaption>The design token breakdown and its relationship with core token</figcaption></figure><p>You can also use math operations to describe the % of opacity a semantic token, for example. This means that you keep the design scalable and consistent because the token is still referring to the same core token:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOWeB_ILLAJjb8MCLe1F2A.png" /></figure><p>This hierarchical organization makes it easier for designers and developers to create and update design elements by modifying higher-level tokens that propagate changes down to more specific instances.</p><p>But don’t forget: When implementing tokens in your own projects, tailor your descriptions and categories to resonate with your specific team members. Choose an approach that aligns with your team’s needs and workflow, ensuring the system is both intuitive and effective for those who’ll be using it daily.</p><h4>Step 3: Document Your Design Tokens</h4><p>Last but not least, build a comprehensive database or documentation of all your design tokens as this serves as a single source of truth for both designers and developers.</p><p><a href="https://sugary-aardwolf-e7a.notion.site/Design-Tokens-Database-b41cecb1371b4d4aa157944056625191?pvs=4">Here’s a database I’ve created in Notion</a> to document and manage design tokens for my projects. It covers colors, typography, spacing, and shadow effects. Feel free to copy and use it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZ46KqftzHJWa22mYxOsQQ.png" /><figcaption>I’ve created a design tokens database template in Notion, which you’re welcome to copy and use!</figcaption></figure><p>This database offers several benefits:</p><ul><li><strong>Easy filtering: </strong>You can filter tokens by tags (category, concept, and properties) for quick access.</li><li><strong>Multiple views: </strong>Create different views to organize and access information efficiently.</li><li><strong>Figma integration:</strong> Most tokens are linked to Figma, streamlining the design process.</li><li><strong>Visual reference:</strong> Key color tokens are also added to Figma for easy visual reference.</li></ul><h4><strong>Bonus: Managing your tokens with Figma’s “Variants”</strong></h4><p>Leverage design tools like Figma to create and manage your design tokens. Figma’s “Variants” feature is particularly useful for creating and managing design tokens in prototypes because:</p><ul><li>It enables the creation of different states or variations of a component (e.g., button styles, color themes) while keeping them organized and easily accessible.</li><li>It simplifies the process of switching between different versions of a component, making it easier to test and visualize different design options.</li><li>It helps maintain consistency across a design system by centralizing variations of components in one place.</li><li>It leads to more efficient workflows and better organization of design elements, ultimately resulting in more consistent and scalable design systems.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eHoebbqmaqXSiwyyoh6qQ.png" /><figcaption>Source: Figma Learn</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxW9maZ7M7FFC4jS44kYjg.png" /><figcaption>Source: Figma Learn</figcaption></figure><p>The structured approach of core and semantic tokens, coupled with practical tools like Figma’s variants feature, empowers teams to create more efficient, maintainable, and cohesive design ecosystems. As the digital landscape evolves, mastering the use of design tokens will be crucial for creating seamless, consistent user experiences across various platforms and devices.</p><h3>Practical examples</h3><p>I’ll show now a practical example of how design tokens are used in code — applying Daggett’s structure to the design token names.</p><p><em>Can you see the difference between manually coding each button parameter and using design tokens for each value?</em></p><p>Here’s an example of how I declare core tokens for colors. For instance, the core token “primary100” is defined by the color value “#EFF8FF”.</p><pre>.primary100 : &quot;#EFF8FF&quot; ;<br>.primary200 : &quot;#B4DAFF&quot; ;<br>.primary300 : &quot;#84CAFF&quot; ;<br>.primary400 : &quot;#53B1FD&quot; ;<br>.primary500 : &quot;#2E90FA&quot; ;<br>.primary600 : &quot;#1570EF&quot; ;<br>.primary700 : &quot;#175CD3&quot; ;<br>.primary800 : &quot;#1849A9&quot; ;<br>.primary900 : &quot;#189B7F&quot; ;<br>.red100 : &quot;#FFCCCB&quot; ;<br>.red900 : &quot;#8B0000&quot; ;<br>.green100 : &quot;#90EE90&quot; ;<br>.green900 : &quot;#006400&quot; ;</pre><p>This color is then associated with one or more semantic tokens, each representing a specific application of the same color. For instance, the core token <strong>“primary100”</strong> can be linked to three specific usages, while <strong>“red100”</strong> is associated with two others.</p><pre>.primary100 = color.button.background.primary.default<br>              color.button.border.primary.default<br>              color.button.text.primary<br>              <br>.red100 =     color.input.border.error<br>              color.button.background.destructive.default</pre><p>The visual representation of this hierarchical structure — starting from the raw value and evolving into semantic tokens that describe specific usages — is nicely summarized by Henry Daggett in this slide:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8M_aaWnPsFB1EWStNPGmbQ.png" /></figure><p><em>Notice the difference between manually coding each button parameter and using design tokens.</em></p><p>When developers use tokens instead of raw values for style parameters, it ensures easier maintenance and scalability by providing a single source of truth. Tokens act as output values, behaving like instances that replicate the value of a master component.</p><p>The same principle applies to typography, for instance. Design tokens define heading and body text styles, maintaining consistency in font sizes and weights across the application.</p><p>Here’s an example of how to use raw values to define font size, weight, and line height:</p><pre>{<br>    &quot;typography&quot;: {<br>        &quot;heading&quot;: {<br>            &quot;fontSize&quot;: &quot;27px&quot;,<br>            &quot;fontWeight&quot;: &quot;500&quot;,<br>            &quot;lineHeight&quot;: &quot;32px&quot;<br>        },<br>        &quot;body&quot;: {<br>            &quot;fontSize&quot;: &quot;15px&quot;,<br>            &quot;fontWeight&quot;: &quot;200&quot;,<br>            &quot;lineHeight&quot;: &quot;24px&quot;<br>        }<br>    }<br>}</pre><p>With design tokens, we would use the semantic token instead — replacing the raw values that used to describe each attributes individually.</p><ul><li>for fontSize, “27px” becomes “{typography.heading.fontSize.large}”</li><li>for fontWeight, “500” becomes “{typography.heading.fontWeight.bold}”</li><li>for lineHeight, “32px” becomes “{typography.heading.lineHeight.large}”</li></ul><p>and so on and so forth!</p><h3>Best Practices for Design Token Management</h3><ul><li>Maintain clear and consistent naming conventions for your tokens;</li><li>Regularly review and update your design tokens to ensure they remain relevant and effective;</li><li>Collaborate closely with developers to ensure that the implementation of design tokens aligns with the design intent;</li><li>Consider accessibility when defining color and typography tokens to ensure your design system is inclusive;</li><li>And always start by tokenizing colors!</li></ul><p>By mastering the implementation and management of design tokens, we designers can significantly improve the consistency, scalability, and efficiency of our design systems. This approach not only good for the quality of the final product but also enables more efficient design iterations.</p><p>Remember, the key to successful design token implementation lies in clear communication, comprehensive documentation, and a collaborative approach between designers and developers. With these practices in place, you’ll be well on your way to creating more cohesive, scalable, and maintainable design systems.</p><h3>References</h3><ul><li><strong>Henry Daggett’s masterclass: </strong><a href="https://www.interaction-design.org/master-classes/design-tokens-powering-your-design-system">https://www.interaction-design.org/master-classes/design-tokens-powering-your-design-system</a></li><li><strong>Style Dictionary Documentation on design tokens:</strong> <a href="https://amzn.github.io/style-dictionary/#/tokens">https://amzn.github.io/style-dictionary/#/tokens</a></li><li><strong>Figma Learn:</strong> <a href="https://help.figma.com/hc/en-us/articles/360056440594-Create-and-use-variants">https://help.figma.com/hc/en-us/articles/360056440594-Create-and-use-variants</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d492cdd92720" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/mastering-design-tokens-d492cdd92720">Mastering Design Tokens</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Concept for Kuido: AI for Good ❤]]></title>
            <link>https://medium.com/design-bootcamp/design-concept-for-kuido-ai-for-good-8c80a8c8819b?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c80a8c8819b</guid>
            <category><![CDATA[design-methodology]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[design-for-ai]]></category>
            <category><![CDATA[ai-for-good]]></category>
            <category><![CDATA[virtual-assistant]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Thu, 25 Apr 2024 07:37:32 GMT</pubDate>
            <atom:updated>2024-05-03T11:41:28.079Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Journey of Designing Our First AI Product</h4><p>This article is a reflection on my first experience (alongside an amazing team!) helping design a solution for an AI product: a virtual assistant to help patients of chronic disease and caregivers better live with their condition.</p><p>I chose to participate in this project for two main reasons: firstly, I had never designed an AI product before and saw a unique opportunity for learning and growth. Secondly, and most importantly, this is an AI project dedicated to good, focusing on enhancing people’s lives with a strong ethical consideration.</p><h3>What’s Kuido?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQeEsthfaLDChDRIBxbsjQ.png" /><figcaption><a href="https://www.kuido.ai/">Kuido</a>, ChatGPT pour le vitiligo</figcaption></figure><p>Kuido is a non-profit initiative whose mission is to help patients of chronic disease and their caregivers better live with the illness. Kuido aims to enhance disease management and promote supportive behaviors by using artificial intelligence that leverages medically verified information and offers conversational interfaces to help patients and caregivers navigate their journey. We started with Vitiligo — an auto-immune skin condition that depigments the color of your skin.</p><p>Vitiligo affects 800,000 individuals in France, and between 1% and 2% of the global population. On average, each person knows two individuals affected by vitiligo.</p><p><em>👉 Visit </em><a href="http://www.kuido.ai/"><em>www.kuido.ai</em></a><em> for more information!</em></p><h3>Why this project?</h3><p>In March 2020, Nicolas Marchais, an engineer and entrepreneur, developed vitiligo. After months of therapeutic wandering and finding false information online on Google and various sites, Nicolas ended up speaking with a fellow patient who gave him advice that was contrary to what dermatologists had told him: that there were no treatments, that he had to live with it, and that it was not serious. Yet, seeing his skin lose color a little more each day created stress, a feeling of lack of control, and made it difficult to face others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bTClpbqp4upr2q49S38enw.jpeg" /><figcaption>Nicolas Marchais holding a prototype of Kuido app</figcaption></figure><p>At this point, Nicolas launched projects in artificial intelligence and decided to unite a team around this idea: to democratize access to information to help people take the first step and find the necessary motivation to understand where the disease comes from, existing treatments, lifestyle habits to adopt, and to feel psychologically supported.</p><h4>The team behind Kuido 👏</h4><p>People working in the Tech sector, sensitive to health issues in general and artificial intelligence, who wanted to create useful products for everyone: <a href="https://www.linkedin.com/in/sergeychuvayev/">Sergey</a>, <a href="https://www.linkedin.com/in/bettina-martins/">Bettina</a>, <a href="https://www.linkedin.com/in/tom-dimajo-b30612137/">Tom</a>, <a href="https://www.linkedin.com/in/romainhetzel/">Romain</a>, <a href="https://www.linkedin.com/in/williampambrun/">William</a>, <a href="https://www.linkedin.com/in/nicolas-marchais/">Nicolas</a>, <a href="https://www.linkedin.com/in/anaelchardan/">Nanou</a>, <a href="https://www.linkedin.com/in/michaelsaifoudine/">Michael</a> (<a href="https://www.klimb.group/">KLIMB</a>), <a href="https://www.linkedin.com/in/alixdebricourt/">Alix</a> (<a href="https://crush.family/">Crush Family</a>)</p><p>Regarding the design team, <a href="https://www.linkedin.com/in/romainhetzel/">Romain Hetzel</a> and I were the product designers responsible for this project.</p><h4>Project details</h4><p>The Kuido project began in September 2023, with each team member devoting between two to four hours per week. The whole team, including design and frontend, held weekly meetings. All project documentation, which includes the roadmap and sprint tasks, was managed within Notion.</p><ul><li><strong>Project Goal:</strong> Launch a beta version of <a href="http://kuido.ai/">Kuido.ai</a> app to collect user feedback on the core chat experience.</li><li><strong>Project Scope: </strong>Virtual assistant for web application on mobile, tablet, and desktop. Our primary goal is to optimize the chat experience, as it is the core functionality. In addition, we aim to design a vision for future versions of the product. By planning ahead, we can make more informed decisions in the present. Therefore, we have established two distinct scopes: Beta and V2.</li><li><strong>App launch: </strong>The Kuido app was launched after 3 months of collaborative work, on December 12, 2023</li><li><strong>Metrics:</strong> 100+ beta testers subscribed on <a href="http://www.kuido.ai/">www.kuido.ai</a>. Currently, we are contacting each user to arrange an interview and testing session.</li></ul><h3>Starting with Principles</h3><blockquote>How can we make an ethical AI product?</blockquote><p>This was our initial question. Romain and I had never worked on an AI project before Kuido, so we were both excited and filled with questions at the start of this project.</p><p>It’s important to say that a huge Discovery work was done at the beginning of the project by William, interviewing of healthcare workers in France, to understand the treatment journey of patients with chronic diseases, especially vitiligo.</p><p>To kick things off, I wanted to study first. So I started gathering reliable resources for building an ethical AI product correctly. One of the best materials I found was these webinars from IxDF on the topics of AI, ethics, and design:</p><ul><li><a href="https://www.interaction-design.org/master-classes/how-to-make-your-ai-project-a-success/recording">How to Make your UI project a success</a> by Greg Nudelman</li><li><a href="https://www.interaction-design.org/master-classes/conversation-design-practical-tips-for-ai-design/recording">Conversation Design: Practical Tips for AI Design</a> by Elaine Anzaldo</li><li><a href="https://www.interaction-design.org/master-classes/human-centered-design-for-ai/recording">Human-Centered Design for AI</a> by Niwal Sheikh</li></ul><h4>Defining design principles</h4><p>Reviewing all this material prompted me to begin by defining the key design principles for creating an ethical AI product.</p><p>This process included a deep dive into other design principles for conversational interfaces and virtual assistants. The website <a href="http://uxofai.com/">uxofai.com</a> was a substantial source of inspiration. We brainstormed various design principles, considering our project goals and functional priorities for the initial version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HLt2gG6poVmFDebz7Ku1oA.png" /><figcaption>Principles explorations from other AI products, used in the benchmarking</figcaption></figure><p>Romain and I developed a benchmark to identify user experience patterns and design principles from various e-health tools, virtual assistants, and AI products. This undertaking helped us recognize market standards and gain inspiration from design elements such as user interface, copy, and interactions. Moreover, it spotlighted areas for enhancement in other products and identified potential challenges to our product’s ethical approach.</p><p>Before this phase, we collected insights and conducted user interviews to guide our benchmarking efforts. Combined with our internal discussions, we created a framework for our benchmarking. This included themes and questions that were central to our project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ZtWMfMmv6PCR5OvXWpXog.png" /><figcaption>Our Benchmark guide</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wY3hOiC7sVsE6raki2S0gg.png" /><figcaption>Snaphshot from our benchmarking board</figcaption></figure><h3>Kuido’s Design Principles</h3><p>Finally, we selected 13 design principles for our project:</p><ul><li>We have 7 principles that are dedicated to <a href="https://uxofai.com/"><strong>UX of AI,</strong></a> the minimum set of principles we thought it was important to stick to in order to build an ethical product.</li><li>We selected a usability heuristic, “<a href="https://www.nngroup.com/articles/user-control-and-freedom/"><strong>User control and freedom</strong></a>”, and applied it to an AI product under the concept “Control: Keep users in control”. This is because user control and freedom are key to a positive user experience with any tool. However, it’s particularly crucial with an AI tool that users don’t merely become spectators but also know how to manage the process and collaborate effectively with the AI.</li><li>Lastly, we selected 5 principles on Conversational Design, that are more like practical tips on how to structure the sentences on the chat experience between users and virtual assistant.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTS_t4AxMONm80fVXvE8Kg.png" /><figcaption>Screenshot from our own Design Principles table in Notion</figcaption></figure><p>And here are some examples of how to implement these principles in the product:</p><h4>⭐ ️Principle: Start with the user</h4><p><em>Think about how people do the task today. Not all users know how to express their questions.</em></p><p>The primary challenge with this kind of virtual assistant is addressing the “cold start problem”: guiding users in understanding what types of questions they can ask, the extent of the assistant’s knowledge, and how the assistant can be beneficial to them.</p><p>To address this issue, our team has explored several strategies. After conducting internal workshops as part of our Discovery process, we mapped the primary jobs-to-be-done and identified potential key themes. We analyzed insights from interviews and created a user journey for two main personas — vitiligo caregivers and patients. This allowed us to identify the most challenging pain points in their journey. Furthermore, we determined how to categorize information in our database to provide “areas of interest” as conversation starters.</p><ul><li>Develop conversation-starting nudges</li><li>Base these nudges on various categories, which are divided by subject</li><li>Display these categories on a homepage for both new and returning users</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*asNadxm1cKhmNNLu0ux4WA.png" /><figcaption>Here are some examples of the categories we can display on the Homepage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fsNV1MgWzs69lAUmiZ_PkQ.png" /><figcaption>Part of the ideation process, Romain and I imagined a designated area on the Chat screen to display nudges in the form of cards</figcaption></figure><p>However, we did not plan to implement the Homepage for the beta launch. Users open the chat directly, as the virtual assistant launches the conversation with a brief presentation and a question to kick start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b8YO25EsuPQ7WNb6_WbRog.png" /><figcaption><em>Opening question “What do you want to know” inside the greeting from Kuido</em></figcaption></figure><h4>⭐ ️Principle: Set the right expectations:</h4><p><em>Generally, under-promising and over-delivering is a good way to build trust. Over time, users will learn how to best integrate the AI into their workflow.</em></p><p>The vision for this principle is that people understand the value offered by <a href="http://kuido.ai/">Kuido.ai</a> and know what questions to ask. What we can implement, for now, as part of the beta version, is to describe in simple terms the capabilities of the AI, as well as its limitations. Here are some ideas we established as a team:</p><ul><li>In the onboarding slides, clearly describe what Kuido can do. It’s important to explicitly state that Kuido is an AI assistant and not a real person.</li><li>Begin the chat experience with a self-introduction</li><li>Beneath the message bar, remind users of the AI assistant’s limitations</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*usosEp_LhQpT9NMHzoUFzQ.png" /><figcaption>Onboarding slides featuring an initial presentation about Kuido, including its range of knowledge and limitations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JFJJxd7hZKXuY2jBbb8LLQ.png" /><figcaption>Self-introduction from Kuido during the first experience: <em>“Welcome to Kuido 👋, your personal AI designed to assist you in navigating life with Vitiligo.”</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*je-AJDOwHReUCsbKTqdfWg.png" /><figcaption>Reminder to users right below the message bar: <em>“Kuido can make mistakes. If in doubt, please consult the referenced sources.”</em></figcaption></figure><h4>⭐ ️Conversation Design Principles</h4><p>In relation to Conversation Design (or CxD) principles, we established certain “rules” to be applied in designing the chat experience. We chose to implement a few principles to enhance the interactions on our conversational interface for the <a href="http://kuido.ai/">Kuido.ai</a> project, such as:</p><p>⭐ <strong>End-focus:</strong> Put the information you want the user to remember at the end of the sentence.</p><p><a href="https://youtu.be/LQMR_Sq4gec">Example that violates End-Focus principle</a>:</p><ul><li><em>User’s question: “Book it for June 31st”</em></li><li><em>Assistant’s answer: “There are only </em><strong><em>30 days</em></strong><em> in June”</em></li></ul><p><a href="https://youtu.be/R8PxWIL9n2s">Example that follows the End-Focus principle</a>:</p><ul><li><em>User’s question: “Book it for June 31st”</em></li><li><em>Assistant’s answer: “Actually, June has only </em><strong><em>30 days</em></strong><em>”</em></li></ul><p>⭐ <strong>Fronting:</strong> If the response to a user query can be short, succinct, and to the point, put that information at the beginning of the response (mirror or repeat back what the user said at the beginning of the sentence, to reassure the input was received).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*s-lATqUeTVUsYCanNfO__A.png" /><figcaption>Answer A is the correct one :)</figcaption></figure><p>⭐ <strong>Scoping:</strong> Phrase a question such that invites the (precise) responses you need from the user. User words that discourage other responses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*gNLRcNtUHwfohX8xdNPK0g.png" /></figure><h3>Workflow Development</h3><p>In parallel to the principles definition, we also focused on the user journeys: how to define the workflow new users and, later on, of returning users.</p><p>We held several internal workshops to establish initial workflows and brainstorm the layout and navigation structure. We transitioned to FigJam to develop the workflow more concretely. This decision was influenced by our brainstorming session drawings, research insights, and benchmarking exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mmiO22py-yi2TnHn3GvqxA.png" /><figcaption>Pictures from workshop doodles on a notebook</figcaption></figure><p>Rather than creating a one-size-fits-all solution, we developed workflows for two distinct user profiles: <strong>the patient and the caregiver.</strong> This approach ensured that our AI assistant, Kuido, can cater to both users who have vitiligo and those who use the app on behalf of a loved one.</p><p>The aim of this task was to ensure a quick time-to-value within the product. If a first-time user doesn’t understand the value proposition of <a href="http://kuido.ai/">Kuido.ai</a> or engage with the chat during their initial visit, they likely won’t return. As a result, our main UX efforts are centered on the new user journey, especially onboarding and the first chat experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcXu1EBj2sFregL5s4x9Iw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7d1z3xWOztzDeuOTLczhQ.png" /><figcaption>Userflow ideations on FigJam</figcaption></figure><h4>Discarding Ideas</h4><p>Product development isn’t just about what you include, but also what you discard. For instance, we decided against having Kuido deliver medical advice or diagnose the user. We want to clarify to users that Kuido is an AI assistant and is not intended to replace doctors or medical diagnoses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PdXDnVGPN7osr8PInhDyQA.png" /><figcaption>FigJam screenshot showing the discarded userflow</figcaption></figure><h3>Wireframes</h3><p>The wireframes were perfectly fine to start the implementation of the main layout and navigation patterns, as we were still engaged in testing and improving the chat experience. In addition to the chat experience, we identified other key pages necessary to realize the V2 vision: the Splash screen, Onboarding screens, and Homepage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dv2FbtDJnYDaYcI3MGkIJA.png" /><figcaption>Screenshot of some wireframes in Figma</figcaption></figure><h4>Discarding Wireframes</h4><p>Some initial wireframes were discarded from the final solution, including various ideas for onboarding users in the chat screen. Notably, one discarded idea was to assign a specific user role, either as a patient or caregiver, before sending the first message to the virtual assistant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGQexWINz7dxpqPurbzKJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9FTHpJraPvCvehkN6AqyGw.png" /></figure><h3>Lighter UI: build for learning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UK4hiyObOPca-dthZVkvA.png" /><figcaption>Kuido.ai brand 😍</figcaption></figure><p><a href="https://www.linkedin.com/search/results/all/?fetchDeterministicClustersOnly=true&amp;heroEntityKey=urn:li:fsd_profile:ACoAACFfXNQBmpxETezUl3rZjKOw50eeBG0thHE&amp;keywords=tom%20dimajo&amp;origin=RICH_QUERY_SUGGESTION&amp;position=2&amp;searchId=890064b7-0940-4ab9-8587-01c43776bbbb&amp;sid=L:f&amp;spellCorrectionEnabled=false">Tom Dimajo</a> was the brand designer responsible for conceiving an emotional identity to Kuido’s brand. As part of his task, Thomas also proposed some applications of the visual identity into the app screens, which later me or Romain could then refine.</p><p>As soon as we have established the core screens and functionalities, we could begin the UI phase — which involved considering the desconstruction of the current solution into components for the design library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qeCf4MJ1uCd7oTN5lxmnNA.png" /><figcaption>Brand design applied to the onboarding screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8pEErgaMG-1nGx5qUm6ymQ.png" /><figcaption>Brand design applied to the chat screens</figcaption></figure><p>We chose a lighter version of the UI for the project. The reason is that we are still uncertain about the level of interaction required with the components, making it premature to build them in-depth. We prioritized which components to construct for this initial version. Our decision was based on what would add value to the business, elements frequently used, and those requiring regular updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCuu1f70W5sy9OHwpelMsA.png" /><figcaption>Crafting components in Figma (starting to apply the brand guidelines to the app)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Ww8rPW4tD09iW7k1661pA.png" /><figcaption>UI tokens created in Figma for Sergey, the frontend developer. This allowed him to start implementing the UI progressively while we tested the experience.</figcaption></figure><blockquote><em>Build the </em>product<em> first, then </em>component<em>-ise (Henry Daggett)</em></blockquote><p>Following Henry Daggett’s model below, we created only one level of components (instead of using the atomic design approach). Additionally, we created another page with UI Tokens, allowing the frontend developer to build the UI components using base colors and text styles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfRbGO5zkY--WHV1F3IKHw.png" /><figcaption>Henry Daggett’s approach explained in a tweet</figcaption></figure><h3>Testing and Feedback</h3><p>Testing is a crucial part of any design process. We initially created a prototype within WhatsApp to directly interact with and test the virtual assistant, as the core chat experience was the first priority and we could continue testing and improving it with no need for a dedicated UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFnniA6k5osAU4sOnj-FHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n7LXjFeJKzG0o2fujmZiTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4H12nxbVv4F_mjL9vkuyIA.png" /><figcaption>Screenshots from WhatsApp prototype, to test chat-only XP</figcaption></figure><p>As our frontend developer joined, we began designing and testing application screens in a staging environment. This gradual process allowed us to incorporate the final UI components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gdMEbrLYD4_VotKVLv18g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y2reu_poWofByG1kap0lMQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sf6aQCLV2BNFUSv3pkLi-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOzXWnKGONhakbnBG3QW8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AHZ9uou3UhKdYmVWkVLBnA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mzPetrG0G6A8LMnZk_R7sg.png" /></figure><h3>Launch beta app to onboard users</h3><p>In early December 2023, once we achieved the minimum desired quality and stability for the chat experience, we decided to launch it to external users to gather more authentic feedback and start onboarding users.</p><p>Feedback from these early users has been invaluable, and we continue to manage user onboarding and conduct interviews (100+ beta users subscribed on <a href="http://kuido.ai/">Kuido.ai</a> in the first month).</p><h3>Learnings and Takeaways</h3><p>Designing for an AI-first product was a learning curve for the entire team. We drew inspiration from other products and sought to learn from those already working with and designing for AI, rather than designing with AI. We learned that the output of a virtual assistant is always a black box, and conversations are hard to design. We also learned the importance of being scrappy and designing for learning. We realized that while AI can enhance the experience, it should not replace it. Finally, we understood that conversation design is still experience design, and just like any other product, it needs to be easy, valuable, and thoughtful. And here are some of my takeaways that I believe are worth sharing:</p><h4>The output is always a blackbox</h4><ul><li>We can’t predict precisely what a virtual assistant will say. While we aim to minimize risks and anticipate interactions, there’s always some risk involved. This underscores the importance of an ethical approach and strict adherence to design principles from the product’s conception.</li><li>Integrate a confidence score, a common way of informing the user about the confidence level of an answer, to assess risks. This feature is still in our backlog.</li><li>Users will have the option to rate the accuracy of the virtual assistant’s responses, similar to Notion AI’s approach during their beta release. This method will allow us to build a trust relationship with users while improving the quality and accuracy of our responses. This feature is also in our backlog.</li></ul><figure><img alt="Screenshot of a chat window from Notion AI, explaining the user (me) what it does and highlighting they’re still in Beta presenting the message: “I’m still in Beta, so please use the 👍👎 buttons to help me improve”." src="https://cdn-images-1.medium.com/max/800/1*yL_9kTe8CS_ghCWoMW0otQ.png" /><figcaption>Here’s an example from Notion AI’s beta launch: they ask user feedback on the AI-generated outputs.</figcaption></figure><h4>Conversations are hard to design</h4><ul><li>Humans are already experts in communication and people immediately notice when conversation deviates from the expected mental model and will get frustrated easily.</li><li>Conversations require a lot of brain power and <strong>it’s very hard to multitask.</strong></li><li>Conversations should be easy (they should minimize cognitive load), rooted in how users actually talk, inclusive, emotive, empathetic, and have a good memory</li><li>Conversations should also be valuable, grounded in UX research, have a clear scope, be task-oriented, functional, privacy-minded, and secure.</li><li>In conversation, it’s key to stay on topic, reassure users that they’ve been heard, and remember that people tend to see human-like traits in everything. So, we need to make sure our chat stays relevant, echoes back user inputs for reassurance, and has a touch of human-like behavior, since people naturally interact that way with computers.</li></ul><h4>Be scrappy and design for learning</h4><ul><li>Focus on a narrow use case and specific goals that AI can achieve</li><li>AI should not tell an expert human how to do their job. AI provides suggestions. It is up to us to make the decision to use it or not.</li><li>Bias and hallucinations will always be there. We should mitigate it as much as possible. <strong>It is our responsibility as designers.</strong></li><li><strong>AI = Augmented Intelligence</strong>: Let it enhance your experience, not replace it!</li></ul><h3>Learn more about Kuido</h3><p>Our journey in designing Kuido is a testament to the transformative power of design. We’re excited to continue enhancing the user experience, always putting our users’ needs at the forefront. We invite you to join us on this journey, whether as a beta user, a team member, or a partner.</p><h4>Get access to Kuido app</h4><p>Feedback from our first users shows us the strong impact of the application on their understanding of the disease and their daily life. So, we decided to open our pioneer user program for the application to help us improve it.</p><p>👉 <a href="https://kuido.fillout.com/inscription"><strong>Subscribe</strong> <strong>to</strong> <strong>the</strong> <strong>beta</strong> <strong>program</strong></a></p><h4>Join the team</h4><p>As a pro-bono projet at Kuido we want to foster a <strong>collaborative</strong>, <strong>asynchronous</strong> &amp; <strong>contribution-based</strong> way of working. Learn about our team and the various roles we are currently seeking to fill!</p><p>👉 <a href="https://www.notion.so/Join-Kuido-4e574a7f7b064f3fa39ac788174f5d26?pvs=4"><strong>Check out the job openings for Kuido</strong></a></p><h4>Partner Up</h4><p>There are plenty of needs whether you are a designer, developer, media/tech/health/associative influencer, or a motivated project manager. The project is self-funded by members of the collective today, so if the mission speaks to your company or organization, do not hesitate to contact us!</p><p>👉 <a href="https://kuido.fillout.com/nous-rejoindre"><strong>Become a partner</strong></a></p><p>Have a good day! ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c80a8c8819b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/design-concept-for-kuido-ai-for-good-8c80a8c8819b">Design Concept for Kuido: AI for Good ❤</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[Good handoff improves UX quality]]></title>
            <link>https://uxdesign.cc/good-handoff-improves-ux-quality-939687e7ff9e?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/939687e7ff9e</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-handoff]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Mon, 26 Dec 2022 09:00:52 GMT</pubDate>
            <atom:updated>2022-12-26T12:40:53.451Z</atom:updated>
            <content:encoded><![CDATA[<h4>A guide to a streamlined design handoff between designers &lt;&gt; developers</h4><figure><img alt="Two American football players on the field passing the ball to each other" src="https://cdn-images-1.medium.com/max/1024/0*w5hdRV_XpB6hSx--" /><figcaption>Photo by <a href="https://unsplash.com/@chris_chow?utm_source=medium&amp;utm_medium=referral">Chris Chow</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Handing off deliverables and design specifications to developers is always an ongoing debate inside the product design community and product teams I’ve worked with. I believe there are no right or wrong answers because, in a given context, different teams should choose the methodologies and tools that work best for them.</p><p><strong>But why is design handoff important?</strong> Because that’s one critical point in the delivery process where teams usually compromise the UX quality of the designed solution. To set an example, <a href="https://uxdesign.cc/how-does-your-team-measure-ux-quality-bdefdb325e6f">the design team at HackerOne spotted that their handoff process was responsible for the drop in their UX quality in 23% of times.</a> Imagine how high this figure may be in other companies, where design teams don’t even have the culture of running and measuring handoff process to the development team.</p><blockquote>Design handoff is one critical point in the delivery process where teams usually compromise the UX quality of the designed solution.</blockquote><p><strong>And what is design handoff exactly?</strong> It is the process of handing over a finished design for implementation. It is a key moment in project management where knowledge is transferred and, thus, transformed. A well documented design handoff is essential, one whose specifications and documentation meet user needs, speaks their language and make their lives (jobs) easier.</p><p>If there’s no clear process in place, one that is respected and constantly improved by the team, it is very likely that information will be lost, guidelines won’t be followed, and design solutions won’t be respected.</p><p>Thus I will share in this article how I prepare and run design handoffs on my own projects, based on my past experiences in small and large product teams, and on my current processes as a freelance product designer.</p><h3>Step 1 — Have a single source of truth</h3><p>In all companies I’ve worked for, I encountered Jira as the main project management tool (I even wrote <a href="https://medium.com/the-ab-tasty-tech-blog/bring-value-to-your-design-work-in-every-development-sprint-8005d4ddddff">an article on Medium explaining how I decided to integrate design tasks inside development sprints to improve design and product collaboration</a>). Jira is a powerful management tool for agile software development and very useful for creating scrum and kanban boards in order to run and understand the project management processes properly.</p><figure><img alt="A screenshot of the software Jiram showing an example of Scrum board inside the tool" src="https://cdn-images-1.medium.com/max/1024/1*uNa2FKsXyI2TIUVeFB255w.png" /><figcaption>Example of a Jira’s Scrum board (taken from the internet)</figcaption></figure><p>Nonetheless, since I started freelancing, I see more and more early-stage start-ups relying on Notion to create and run their project management process.</p><figure><img alt="A screenshot of the Notion software showing a kanban board of a client of mine" src="https://cdn-images-1.medium.com/max/1024/1*Ahh1l9wUP-0dXzmBcfkA9g.png" /><figcaption>Capture of a client’s sprint backlog in Notion</figcaption></figure><p>Whatever works for your team, you should get familiar with the product management tool they use. This way, you can propose and manage the design handoff process to developers the best way. No need to jump from tool to tool: gain time and improve the transfer of knowledge by having one single source of truth.</p><h3>Step 2 — Structure your design workflow</h3><p>Figma is a collaborative prototyping tool and it allows us to create several supporting materials to the design process and final results. It becomes therefore very convenient to communicate details of your final design solution directly in the tool:</p><h4>2.1 Set up a page structure</h4><p>It’s very important to structure the design file since day 1. My philosophy is to let people know where to find what they are looking for.</p><p>In terms of design explorations and evolution, I usually split my design progress into different pages, separating the current designs from previous versions that are no longer relevant. Here’s an example:</p><figure><img alt="A screenshot of the left sidebar inside Figma software, showing the page structure I created for a client’s project" src="https://cdn-images-1.medium.com/max/632/1*4zkItar-DoubJzzcpRcVHA.png" /><figcaption>Page structure in Figma for a client’s project</figcaption></figure><p>Pro tip: If you have the Organisation and Enterprise plan on Figma, you can use their <a href="https://www.figma.com/best-practices/branching-in-figma/">branching feature</a>: you can create “branches” in your file, similar to branching strategy to software development. This is particularly useful if your master file is too heavy, to clean up the master file by pushing older iterations into a dedicated branch.</p><p>Besides findability, a nice structured Figma file also let people in the team understand the project steps and grasp the design decisions leading to the final solution.</p><h4><strong>2.2 Communicate project status</strong></h4><p>Each team uses different naming conventions to represent their project evolution. I usually use names that are based on phases of the project workflow, such as: discovery, ideation, prototyping, testing, in development, in review, live.</p><p>Some designers also show a more simpler classification: ongoing, in review and shipped.</p><figure><img alt="A screenshot of the Figma software, showing six different artboards with cover examples displaying different project status: in progress, completed and archived" src="https://cdn-images-1.medium.com/max/1024/1*vDvwrZMjGNDUGcSuWFc40w.png" /><figcaption>Cover pictures on Figma to display different project status (Mozza)</figcaption></figure><p>At <a href="https://mozza.io/">Mozza</a> — a collective of freelance product strategists and designers I work with — we use custom banners on the Figma file cover to reveal the current state of the project. In my previous role at Doctolib, we would also add the name of the designer responsible for the prototypes (and the date of the last update), since we were working with a team of 20+ product designers.</p><p>The name convention should be easily understood by the team collaborating with the project. Pick whatever works for you and your mates. This is ultimately a communication system to give visibility on the current state of the project so everyone is aligned.</p><h4><strong>2.3 Describe with words</strong></h4><p>I like to leave comments or create sticky notes to communicate the design decisions textually: raise a question, a concern, or to explain an interaction. It is very useful as a communication tool with the developers :)</p><figure><img alt="A screenshot of a Figma artboard with the design specifications of design components" src="https://cdn-images-1.medium.com/max/1024/1*EDHyD0_YnHGY1qL7toAknA.jpeg" /><figcaption>Design specifications to developers: I wrote comments on sticky notes to explain the desired interactions (in yellow) and added links (in green) to animation previews</figcaption></figure><figure><img alt="A screenshot of Figma software showing comments I created on top of the design artboards explaining especifications to developers" src="https://cdn-images-1.medium.com/max/1024/1*W3W0SuoEtrsmuBUH4H0dag.png" /><figcaption>Comments I wrote on Figma prototype to guide my client’s development team</figcaption></figure><h4>2.4 Describe with visuals</h4><p>An image isworth a 1000 words. This couldn’t be more true when documenting design decisions.</p><p>For instance, I find helpful to represent navigation flows and to explain all the possible paths and navigation levels in the prototype visually.</p><figure><img alt="A screenshot of a user flow for a mobile application" src="https://cdn-images-1.medium.com/max/1024/1*LQEn3RZUdWLNBHbYo2DiCw.png" /><figcaption>Representation of a user flow for the notifications center of a mobile application</figcaption></figure><figure><img alt="A screenshot of Figma software showing a navigation structure and layout structure I created for a project at Doctolib" src="https://cdn-images-1.medium.com/max/1024/1*w37hP0fJzJLt-HVLGhyvDg.png" /><figcaption>Navigation and page structure on Desktop and Mobile for a redesign project</figcaption></figure><p>Also, the live prototype (called “preview mode” on Figma) is always better than any written or visual explanation you might offer. It shows a specific user flow from end-to-end, presenting context and an interactive version of the final solution (including transition between screens, micro animations and other interactions). This is the type of information that it’s very hard to explain by written form, therefore this solution becomes handy to communicate the design decisions.</p><figure><img alt="A screenshot of Figma software showing the final solution of a task manager module I designed for Doctolib Practice, the B2B solution from Doctolib" src="https://cdn-images-1.medium.com/max/1024/1*E9Zz3w29t0OgCUfBZ09UqQ.png" /><figcaption>Snapshot of the live prototype of the task manager module I designed for Doctolib Practice (B2B product of Doctolib). <a href="https://www.figma.com/proto/2lGmiV5R1D8SoIUe64zPWn/%F0%9F%94%A5-Portfolio-Projects?page-id=129%3A2&amp;node-id=129%3A3799&amp;viewport=1673%2C-409%2C0.13&amp;scaling=min-zoom&amp;starting-point-node-id=129%3A4005">Click here to open the live prototype.</a></figcaption></figure><p>So, whenever possible, I provide a clickable prototype of my desired solution to developers. It’s not only a good opportunity to discuss technical constraints and run design reviews with the tech team, but it’s a powerful way to communicate my design solutions to stakeholders.</p><h3>Step 3 — Document your design deliverables</h3><p>Finally, development ticket. That’s where the magic happens! Inside the ticket description to developers, I always try to add the following design information:</p><ul><li>Project documentation (scope, ideation, discovery, etc)</li><li>User stories</li><li>Link to prototype</li><li>Link to preview mode, if applicable</li><li>Specifications on how to implement the final design solution: design system documentation, technical details, interactions, animations and intended behaviours</li></ul><p>If my design needs extra documentation to explain edge cases scenarios, for instance, it’s ok to create it in a different source (Google Docs, for instance) and attach it to the development ticket. Sharing compelling and useful/usable deliverables is important, such as test reports, field study findings or client feedback.</p><figure><img alt="A screenshot of a ticket description I did inside Jira software, containing user stories, pain points description, links to user research prototypes and takeaways and a link to the final prototype" src="https://cdn-images-1.medium.com/max/1024/1*Q3ULyDxC2IK77Zg2gOmRzA.png" /><figcaption>Ticket description I created on Jira gathering several information: user feedback, user stories, user testing resources, main pain points found and link to final mockups</figcaption></figure><p>Make sure your document is not too dense and extensive because this will reduce the chances that anyone, including the developer, will read in its entirety. Make your ticket description easy to read &amp; scan, but powerful and detailed!</p><p>There is no single process or tool that will respond to all needs. Each designer alongside their team should establish their preferred process and methodologies based on their goals and needs. But one thing is sure: the more streamlined the handoff process between designers and developers is, the greater the chances to improve UX quality of your design solution. A good handoff process will:</p><ul><li>Reduce noise in the communication</li><li>Decrease the time spent on looking for the right information</li><li>Help the team validate the feasibility of the solution</li><li>Make sure no information is lost</li></ul><p>Everybody wins 🌈</p><p>Let me know what you think about my approach and comment below: how do you handle your own design handoff process with developers in your team?</p><p>Happy holidays!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=939687e7ff9e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/good-handoff-improves-ux-quality-939687e7ff9e">Good handoff improves UX quality</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[Becoming manager of my own peers]]></title>
            <link>https://medium.com/doctolib/becoming-manager-of-my-own-peers-9210b4723195?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9210b4723195</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[designer]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Tue, 31 May 2022 13:59:51 GMT</pubDate>
            <atom:updated>2022-05-31T13:59:51.556Z</atom:updated>
            <content:encoded><![CDATA[<h4>4 things I learned as Product Design Manager at Doctolib</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nVHTm6E0RXhudSUJ4MB_AQ.png" /></figure><p>I started off my journey at <a href="https://medium.com/u/9b44a5a39387">doctolib</a> in July 2021 as a Senior Product Designer. After working for 3 years in a row in the digital marketing and CRO industry, I was happy to focus my energy in a professional role dedicated to improving the daily lives of healthcare professionals and to making healthcare more accessible and inclusive for patients in France, Germany and Italy (and counting).</p><p>After 3 months in the job, my manager asked me if I was interested in taking over a design lead position that was open in the team. To be honest, I never really wanted to become a team manager because management is a completely different job. In my previous job I was offered a management position but I refused the offer, not because I did not want to follow the management path, but simply because I did not trust in my own capacity to manage a team.</p><p>(<em>PS: I also think this is structural problem called patriarchy, where women feel less confident to take leadership roles and to trust their own capacity in professional settings, unlike men. But this is a conversation for a different article).</em></p><p>This time around was nonetheless different. Even though I’m still not sure if I want to follow the management path within the design field, I felt prepared to take this new opportunity in order to experience what’s like to be a team manager and learn about design leadership alongside my own peers. In January 2022, I became Product Design Manager of my own team: an amazing set of 6 Product Designers (+3 external consultants) based in Paris working in the B2B domain for Doctolib.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M0J31sFgBEFszKR1HzejrQ.jpeg" /><figcaption>The Doctolib Design Team ❤️ @Paris, April 2022</figcaption></figure><p>As I walk down this new path in my career, I decided to write down some of the learnings I had during my first weeks in the job.</p><p><em>These are personal impressions that my own experience has graced me with, so take these tips as friendly advice from someone who’s new to the job. If they resonate at any level with your own experiences, I’ll be happy to hear from you down below in the comments area :)</em></p><h4>1. It’s okay to delegate</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_e20Qb2AFlHmqxBki0d1g.png" /></figure><p>The first thing I realised as a fresh manager is that I don’t know everything and I can’t solve everything. A big part of my job, as I learned very quickly, is to trust people I manage to do their own job. For instance, to trust senior profiles to take over bigger roles and responsibilities, such as mentoring junior designers and onboarding new joiners.</p><p>Coming from a Senior Product Designer role myself, I was used to grasping the challenges and being hands-on, so I realised I had to switch my mindset a little bit. Delegating tasks to the team creates a cascade structure based on trust and recognition.</p><h4>2. Good communication is key</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E5H-wGoDz3GuVDpOqlxe0g.png" /></figure><p>I don’t mean only communication skills as in public speaking or being fluent in different languages (if that’s necessary for your job). Good communication also means being responsive and agile. Your managees should never feel abandoned nor that they don’t have a person to-go-to for: questions, a cry for help, feedback or just to share ideas about their job, the product or their day-to-day challenges.</p><p>You should try to make yourself available whenever possible — even when it’s not possible. You should be reactive to your team members messages and requests, by answering them as quick as possible (do not leave any messages or notifications from your team pending for hours) and by giving a clear and straight answer. If you don’t know the answer, you say you will look for the solution and get back to them <em>asap. </em>Simple as that :)</p><h4>3. Help your team grow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iMrsalWujiU2ywvQfGM10g.png" /></figure><p>Identify their highs and lows, their strengths and weaknesses, and propose concrete actions to help them improve their competencies in order to evolve in their career path. Provide a clear career path. Give junior designers a chance to grow and trust senior designers to take over responsibilities. Provide time for everyone to learn, so they can focus on their evolution. Everybody wins 🎉.</p><h4>4. Preserve a healthy environment</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVwkJnITy4VXd4u8M6h7Tw.png" /></figure><p>Or, <em>keep the “good vibes” atmosphere.</em> If everyone is happy and comfortable with the people they work with day-by-day, it is way much easier to cultivate trust between the team members. And how is this achieved? Well, in my modest and short experience so far, I detected 3 main points:</p><ol><li>Showing that you care about a good work/life balance. People working with you have different stories, different needs and different ways of navigating life — and this is ok! As a manager, you need to make sure that this person has everything they need in order to do their work the best way possible.</li><li>Fostering honest conversations with your team members: about work, the company, their salary, their lives. Reaching a level of honest connection with your team, seeing them and recognizing them as individuals with their own stories, can only lead to healthier relationships.</li><li>Protecting your team members from distractions, stress and anything else that might affect their motivation and, ultimately, their performance. By protecting your peers from any distractions that eventually may fall over them — as long as this does not affect the 2 previous points (work/life balance &amp; honesty and transparency amongst the team) — you’ll be able to cultivate and maintain a healthy environment for your team to perform and to grow.</li></ol><blockquote><em>“There is no formula for great creative work. But we can create good conditions for creativity to happen.” — </em><a href="https://uxplanet.org/key-take-aways-from-julie-zhuos-talk-the-many-facets-of-design-leadership-5d287be1551f"><em>Fengbo Li</em></a></blockquote><p>If you want to read more about other peoples’ experiences on design leadership, here are some nice articles I collected:</p><ul><li><a href="https://uxplanet.org/design-leadership-tips-for-design-team-leaders-9e2a770cdac8">Design leadership: Tips for design team leaders</a></li><li><a href="https://uxplanet.org/key-take-aways-from-julie-zhuos-talk-the-many-facets-of-design-leadership-5d287be1551f">Key take-aways from Julie Zhuo’s talk: The many facets of design leadership</a></li><li><a href="https://uxdesign.cc/transitioning-from-an-individual-contributor-to-a-design-lead-people-manager-18099fadd0d7">Transitioning from an individual contributor to a design lead role</a></li></ul><p>Thank you and stay safe ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9210b4723195" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doctolib/becoming-manager-of-my-own-peers-9210b4723195">Becoming manager of my own peers</a> was originally published in <a href="https://medium.com/doctolib">Doctolib</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What 21st-century design looks like]]></title>
            <link>https://uxdesign.cc/what-21st-century-design-looks-like-c08ffe98e428?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c08ffe98e428</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[decolonization]]></category>
            <category><![CDATA[t]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Fri, 09 Apr 2021 11:15:54 GMT</pubDate>
            <atom:updated>2021-04-09T11:15:54.370Z</atom:updated>
            <content:encoded><![CDATA[<h4>Don Norman and decolonial design.</h4><figure><img alt="Vehicles on a road in the UK next to an electronic sign, where it reads: “Stay at Home. Protect the NHS. Save lives.”" src="https://cdn-images-1.medium.com/max/1024/1*OlQsEjiXv2xFJVqzUBaAzQ.jpeg" /><figcaption>iMattSmart @<a href="https://medium.com/u/2053395ac335">Unsplash</a></figcaption></figure><p><strong>Back in October 2020 I had the pleasure to attend </strong>Don Norman’s Master Class transmitted by <a href="https://medium.com/r?url=http%3A%2F%2Finteraction-design.org">Interaction Design Foundation</a> in which he presented the challenges to the discipline of Design and to all designers in the 21st century. To help me grasp a bit better his ideas, I also read the article he wrote with Michael W. Meyer entitled “<a href="https://www.sciencedirect.com/science/article/pii/S2405872620300046#bfn1">Changing Design Education for the 21st Century</a>”.</p><p>I want to expose in this article the main takeaways I got from Don Norman’s ideas but not without patching them with other references, which I believe it will bring more context and texture to this discussion.</p><h3>The 21st Century Design</h3><p>Don Norman begins his speech by saying that design started as a craft and ever since students have been learning how to manufacture things in schools and universities. Design, however, is complex for it encompasses other numerous disciplines, as both practice and academic discipline, and this is why Norman focuses his ideas about the 21st Century Design on Human-Centered Design (HCD) professionals.</p><blockquote>By this we mean simply designers who design for people and society.</blockquote><figure><img alt="An illustration depicting diversity of a group of six people, with a slight sense of humour: some people have pink hair, a woman is wearing a mask, one person has vampire teeth and another one has a hairy face." src="https://cdn-images-1.medium.com/max/1024/1*5p-mBF0Skpm2mJotJgcPng.png" /><figcaption><a href="https://blush.design/artists/pablo-stanley">Pablo Stanley</a></figcaption></figure><p>The world is changing, new challenges are emerging but the current system of design education has not kept up with the new demands of the 21st century. For Don Norman, designers are starting to play a larger and larger role in not only designing solutions in siloed studios but also impacting decisions that affect businesses. However, unfortunately, designers are not trained properly.</p><blockquote>Education for designers (like nearly all education) is based on learning skills, nourishing talents, understanding the concepts and theories that inform the field, and, finally, acquiring a philosophy. It is unfortunate that our design schools proceed from wrong assumptions. The skills we teach are too often related to processes and working methods of an age that has ended — <a href="https://www.sciencedirect.com/science/article/pii/S2405872620300046#fn1">Vitor Papanek</a></blockquote><h4>Decolonial Design</h4><p>Unfortunately, designers are educated and trained under the mentality that one expert can solve everything. And that’s why we need a different approach to design, where specialists and professionals know how and when to step back and let the community participate and decide.</p><p>A designer can be the expert, but it’s the community that needs to ask for their expertise. Otherwise, it’s paternalism.</p><figure><img alt="Photo montage with a black and white picture of a demonstration crowd, on the background, and the images of the We The People posters, in colour, replacing the original posters in the picture." src="https://cdn-images-1.medium.com/max/1024/1*Liy1r39OlgOqIRZ2-Kpt4A.jpeg" /><figcaption><a href="https://www.kickstarter.com/projects/amplifierfoundation/we-the-people-public-art-for-the-inauguration-and">We the People</a> posters: art posters made public for Trump’s inauguration ceremony in 2017. Each poster features a powerful portrait of an American citizen — a Muslim woman clad in a star-spangled hijab; a Native American elder; a tender moment between a same-sex couple.</figcaption></figure><p>Letting everyone co-design and facilitating the design process with the community is the best way to adopt a decolonial approach in your projects. But in order for this to happen, however, one must recognise in the first place that design reproduces a colonial structure:</p><blockquote>To date, mainstream design discourse has been dominated by a focus on Anglocentric/Eurocentric ways of seeing, knowing, and acting in the world, with little attention being paid to alternative and marginalised discourses from the non Anglo-European sphere, or the nature and consequences of design-as-politics today — <a href="https://www.researchgate.net/publication/329375428_The_Decolonising_Design_Manifesto">The Decolonising Design Manifesto</a></blockquote><figure><img alt="Photograph showing an Arabic script on a wall in Syria alongside a graffiti of a Mickey Mouse character’s head with a red cross on top of it." src="https://cdn-images-1.medium.com/max/768/1*Uy0UgNfYr_yxO-XE43vl3w.jpeg" /><figcaption>‘Homeland is racist’, graffiti by Heba Amin, Caram Kapp, Don Karl, 2015. Photo by the artists.</figcaption></figure><p>To be direct, the colonial structure is part of a globalised system that constantly threatens to flatten disparate world views while advancing an agenda for the benefit of a privileged small group at the expense of everyone and everything else that doesn’t fit in this narrow perspective. And design, as both practice and academic discipline, is part of this structure. To put into Tony Fry’s words,</p><blockquote>there is no overarching “world” viewpoint from which to describe “the world” — to adapt such a perspective is an act of ethnocentric violence intrinsic to Eurocentrism — <a href="https://www.bloomsbury.com/us/design-and-the-question-of-history-9781472521606/">Design and the Question of History</a></blockquote><p>The focus of this is article is not about decolonising design therefore I won’t extend any longer on the topic (I guess I’ll write another article dedicated to the subject), but I know it is important to address it as part of our challenges as designers in the 21st century.</p><p>Breaking down this structure and renewing the approach on how we practice design is not an easy “habit” to change and it will take decades to happen, but as designers, our actions will define not only the stories and narratives we want to tell and endorse, but what world(s) we want to build — and for whom.</p><figure><img alt="Illustration of a world atlas upside down" src="https://cdn-images-1.medium.com/max/1024/1*X14Wmz-dW0CrJmlThgEHxw.jpeg" /><figcaption>On decolonial atlas, the south is the new north. <a href="https://haver.blog/2019/04/19/cool-classes-decolonial-theory-indigeneity-and-revolt/">Image</a></figcaption></figure><p>Even though our contemporary education seems flawed, Norman still affirms that designers are very well equipped to understand the structure of big challenges we’re currently facing in the world — such as the COVID-19 pandemic.</p><p>Why? Because designers focus on the people. And experts who don’t understand the people, will fail otherwise.</p><h3>Are designers well equipped to help to solve the challenges of the 21st Century?</h3><p>The COVID-19 pandemic opened our eyes on what’s happening with our social, political and environmental needs. On this take, Don Norman affirms that designers can bring all disciplines together to solve problems, such as the <a href="https://sdgs.un.org/goals">UN’s 17 sustainable development goals</a>, if we respect the 4 principles of Human-Centered Design:</p><ul><li>Focus on the people;</li><li>Solve the real core issue — and not the symptoms;</li><li>Everything is a system — thus every problem is interconnected;</li><li>We’re dealing with human beings, society, cultures, political issues. We have to find a common ground between different standpoints.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrmM0kRf8Dbk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrmM0kRf8Dbk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrmM0kRf8Dbk%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/54605d81020c52d591f1cc4a12dac436/href">https://medium.com/media/54605d81020c52d591f1cc4a12dac436/href</a></iframe><p>Let’s imagine we’re living in a pandemic.</p><p><em>(Just imagine…)</em></p><p>If we are to solve the problems of a virus pandemic, first we need to solve the problem with hygiene, as washing our hands is imperative to keep the virus away. That also means that people need to be informed and educated on the best way to protect themselves, which requires new solutions on education and communication.</p><figure><img alt="Illustration of two silhouettes of people with their smartphones on their hands where we can see the Whatsapp application logo in each one of it." src="https://cdn-images-1.medium.com/max/700/1*db3w4hMlBzoy30pjbyqwIg.jpeg" /><figcaption>Since 2018, Whatsapp (and more recently, Facebook and Twitter) have been trying to tweak their features to fight “fake news” across the Internet. Source: <a href="https://www.ft.com/content/c1158302-84cb-11e8-96dd-fa565ec55929">Financial Times</a>.</figcaption></figure><p>However, in big cities, there are many homeless people which don’t have access to clean water and no access to basic hygiene instruments. This means that we cannot tell these people to simply “stay home” or “wash your hands”, because they lack the most basic facilities for human dignity. And why are there homeless people in the world? We can take our time and list capitalism, patriarchy, racism, social inequality, just to name a few. On top of that, we have to think about the economic crisis that is triggered by the fact that people “need to stay home”. What is the responsibility of the State, the private enterprises or the banks in this situation? How people can survive if they have to protect themselves from the virus? Who can help them stay home? How can we help others to protect themselves and survive?</p><figure><img alt="Photograph of around 20 Anti-Fascist Deliverers, all with their right fists in the air, standing behind a pile of delivery backpacks showing off the company logos Rappi and iFood at Avenida Paulista in São Paulo, Brazil." src="https://cdn-images-1.medium.com/max/1024/1*wJvr1Bn7hf903NXnpeRfnw.jpeg" /><figcaption><a href="https://linktr.ee/entregadoresantifascistas">Entregadores Antifascistas</a> or Anti-Fascist Deliverers are a resistance group created in Brazil in the midst of the Coronavirus pandemic to fight for better salaries and working conditions. They organised a national strike on the 1st of July 2020. This image was taken in São Paulo, Brazil. Source: <a href="https://outraspalavras.net/outrasmidias/marcada-a-primeira-greve-nacional-de-entregadores/">Outraspalavras.net</a></figcaption></figure><figure><img alt="A photograph of an Anti-Fascist Deliverers riding his bicycle from the back. We can see a handwritten note glued on his backpack, partially covering the logo Rappi. The backpack has a very bright orange colour, contrasting with the grey shades of the city pavement, the buildings and the cloudy sky." src="https://cdn-images-1.medium.com/max/900/1*l8ojv3Hj5QJ8XJL5g3HHfg.jpeg" /><figcaption>Anti-Fascist Deliverer in the national strike in Porto Alegre, Brazil. The message reads: “Risking my life to feed your mouth and my own!” (free translation). Source: <a href="https://www.sul21.com.br/ultimas-noticias/geral/2020/08/entregadores-antifascistas-buscam-criar-cooperativa-com-aplicativo-proprio/">Sul21</a>.</figcaption></figure><p>And this will unveil even more different problems, displaying the interrelation of all problems as part of the same system. And this is why, as designers, we have to have a system-like thinking — because that’s how the world works.</p><blockquote>All important problems are difficult to solve. If they weren’t difficult, they wouldn’t be a problem — Don Norman</blockquote><h3>But I’m a designer sitting on my desk all day… what can I do?</h3><p>Victor Papanek wrote in 1971 a book called “Design for the real world”, where he introduces the text by saying that there is no field more dangerous than design.</p><figure><img alt="The book cover is depicted here against a flat red background. The cover presents a big bold text, align to the left, in lime green and white colours contrasting with the flat black background, where it reads: Design is composing an epic poem, for executing a mural, painting a masterpiece, writing a concerto. But the design is also cleaning and reorganizing a Real desk drawer, pulling an impacted tooth, baking an apple pie, choosing sides for a World backlot baseball game, and educating a child." src="https://cdn-images-1.medium.com/max/1024/1*-cjaYBJcRwrGQ3lteqxQVQ.jpeg" /><figcaption>One of the many book covers of Victor Papanek’s book <a href="https://www.copyrightbookshop.be/en/shop/victor-papanek-design-for-the-real-world/">Design for the Real World</a></figcaption></figure><p>But according to Don Norman, Papanek is wrong.</p><p>Designers are actually powerless. We are in the middle level of any department, where we are actually one of the services. Sometimes designers have no choice but to build what we are told to build. If not, we lose our jobs. What can we do then?</p><p>The answer is to find out different ways of doing things.</p><h4><strong>Move up on the corporate ladder to management and decision-making positions</strong></h4><p>In the design field what usually gives you money is the advertisement niche. And this is harmful because in most cases advertisement agencies are doing nothing but helping out the consumerism wheel. Plus, the monetary issue of generating constant profit by developing products that are disposable or programmed to fail (planned obsolescence) is already an old problem, but still more and more incentivised by the business model of many enterprises.</p><p>And this is one of those “decisions” that directly impacts the environment. In the United States, for example, it’s very easy to get money to create something new, but very expensive to maintain it, whether it is a mobile phone, a dam or a national health system.</p><figure><img alt="An abandoned truck, with no tires, no windows, and no back part, in the middle of a desert." src="https://cdn-images-1.medium.com/max/1024/1*Rq2rGhl00ZurLVCltLvjfA.jpeg" /><figcaption>Abandoned vehicle (Unsplash)</figcaption></figure><p>How to convince your managers and C-levels that you are a good designer? Promote them. Promote your boss, promote your client. Meaning: increase their margin of sales, profit, show the numbers, present a spreadsheet, learn their language.</p><h4><strong>Encourage young designers to do the same</strong></h4><p>We don’t know the answers for these big problems of our century, and that’s why we should mobilise the next generation of designers to think hard about these issues, and to rise inside their companies so they are respected and they have a voice within executives and decision-makers.</p><p>The good news is that more and more industries are starting to understand the importance of good design. This is part of the digital revolution. Thus, having a cohesive design approach nowadays makes the whole difference in the world.</p><h4><strong>Take part on collective initiatives, projects, clubs, groups</strong></h4><p>Find people, engage into similar causes, take concrete action and offer your design skills to meaningful projects. It’s not only a great opportunity to try something new — test a new tool or methodology — but it will take you out of your comfort zone and put your human-centered design skillset to the test. Whether is an environmental cause, educational claims or protests against a political figure, these experiences not only improve your craft but they help you shape your world views.</p><figure><img alt="Poster with an illustration of an Anti-Fascist Deliverer wearing red clothes and a yellow motorcycle helmet while raising his backpack with his hands above his head where it reads, in Portuguese, the word “strike”. The poster background is blue and on the left side of this illustration we read “stop the apps” and the date 27/07." src="https://cdn-images-1.medium.com/max/1024/1*m7fezoZAiaBBU5C-dz11Rg.png" /><figcaption>Many Brazilian designers across the country help the Anti-Fascist Deliverers movement by creating posters and other visual communication pieces. <a href="https://freedomnews.org.uk/2020/07/31/brazil-anti-fascist-couriers-form-workers-co-op-in-rio/">Source</a></figcaption></figure><p><em>During the first lockdown in April 2020 (even before the Anti-Fascist Deliverers group became a national movement), I joined a cause with other 1000 anonymous people in Brazil to, remotely, create a mobile application named </em><a href="http://www.idvogados.org/"><em>Idvogados</em></a><em> to connect deliverers and lawyers in the same city. The main goal of this project is to facilitate the access to their legal rights and to provide legal aid for free, if necessary.</em></p><h3>Takeaways</h3><p>In the 21st century, we don’t need to get rid of the “traditional design” but we need to become more responsible about our impact in the world. And to be a good designer in today’s world, one has to understand the world.</p><p>Maybe an undergraduation in design won’t make much sense any longer. Instead, an aspiring designer will be more competent if they study in depth other areas of knowledge.</p><blockquote>A good designer should work for things that go wrong. So when things go wrong, people know what to do. Because “there is no such thing as human error” — just design error.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7FJNsqoC4tI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7FJNsqoC4tI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7FJNsqoC4tI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b759c3ac5680cf4395ff44573c05ec3f/href">https://medium.com/media/b759c3ac5680cf4395ff44573c05ec3f/href</a></iframe><p>Don’t forget to read Don Norman’s paper on the subject of design education:</p><p><a href="https://www.sciencedirect.com/science/article/pii/S2405872620300046"><strong>Changing design education for the 21st century </strong></a><strong>— Michael W Meyer and Don Norman</strong></p><p>And here are some book titles to help you expand understand (better) the impact of design in our lives — socially, politically, economically and subjectively speaking:</p><p><a href="http://thepoliticsofdesign.com/"><strong>The Politics of Design</strong></a><strong> — Ruben Pater</strong></p><p><a href="https://www.artbook.com/9783945852262.html"><strong>The Politics of Design</strong></a><strong> — Victor Papanek</strong></p><p><a href="https://www.bloomsbury.com/us/design-and-the-question-of-history-9781472521606/"><strong>Design and the Question of History</strong></a><strong> — Tony Fry, Clive Dilnot and Susan C. Stewart</strong></p><p><a href="https://www.goodreads.com/book/show/1456132.Dise_o_gr_fico_para_la_gente"><strong>Diseño Grafico para la Gente</strong></a><strong> — Jorge Frascara</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*kWTtjvEkDAxLhIBY" /><figcaption>The UX Collective donates US$1 for each article published on 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=c08ffe98e428" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-21st-century-design-looks-like-c08ffe98e428">What 21st-century design looks like</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[Bring value to your design work in every development sprint]]></title>
            <link>https://medium.com/the-ab-tasty-tech-blog/bring-value-to-your-design-work-in-every-development-sprint-8005d4ddddff?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8005d4ddddff</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Tue, 05 Jan 2021 08:06:34 GMT</pubDate>
            <atom:updated>2021-01-05T08:56:02.646Z</atom:updated>
            <content:encoded><![CDATA[<h4>Research and ideation phases should become deliverables</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mVHJ0PjffJfB821mMB-pJA.jpeg" /><figcaption>By <a href="https://unsplash.com/@firmbee">https://unsplash.com/@firmbee</a></figcaption></figure><p>Highlighting the value of design work is always an ongoing discussion among designers and product teams: how to measure the impact of design decisions, why idea A was chosen over idea B, why did it take so long to start implementing project C, and so on... Well, one simple way the designer can help organise this confusion is to be more transparent about the design process. And how do we do that?</p><p>We can transform design tasks that are often “hidden” on backstage into deliverables that everyone can understand. The time has come to finally open the curtains and display the design process to everyone. And our main stage should be the development sprint — where all eyes are focused everyday, every week, every sprint.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3orif1JGGgjKDGfS3C%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3orif1JGGgjKDGfS3C%2Fsource.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3orif1JGGgjKDGfS3C%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="331" frameborder="0" scrolling="no"><a href="https://medium.com/media/dfaa8f91bc0b861d917750e449b73c61/href">https://medium.com/media/dfaa8f91bc0b861d917750e449b73c61/href</a></iframe><h3>What’s a development sprint?</h3><p><a href="https://medium.com/nyc-design/design-sprint-in-2-days-c7afbd9eabd3">In an earlier publication</a>, I summarised what a development sprint is: a short period of time (1–2 weeks) containing all main stages of product development, from ideation to user testing. For a more precise description, <a href="http://scrum.org/">Scrum.org</a> refers to it as:</p><blockquote>[…] a time-box of one month or less during which a “Done”, useable, and potentially releasable product <a href="https://www.scrum.org/resources/what-is-an-increment">Increment</a> is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F111GaZJtUrzC4o%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F111GaZJtUrzC4o%2Fgiphy-downsized.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F111GaZJtUrzC4o%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/e2c9add73b27c2f1e912d5879c1175a1/href">https://medium.com/media/e2c9add73b27c2f1e912d5879c1175a1/href</a></iframe><p>At AB Tasty we currently follow a development cycle of 6 weeks, encompassed by 3 sprints of 2 weeks. The main objective for each and every team is to deliver something valuable for the end-customer at the end of each 6 weeks cycle.</p><h3>The designer’s challenge</h3><p>In a perfect world, the design work is done and ready for implementation before the development sprint starts. This means that, if everything runs as planned, the design work is always ahead of the implementation phase.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7qE7o2j8WG1qoVfW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o7qE7o2j8WG1qoVfW%2Fgiphy-downsized.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3o7qE7o2j8WG1qoVfW%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/52a8d5e62a15f12d3d013138bd505dfc/href">https://medium.com/media/52a8d5e62a15f12d3d013138bd505dfc/href</a></iframe><p>By working ahead of the development sprint, designers can have time to frame the problem and validate the solution with the right specifications. This way, the product manager and developers are able to estimate the tasks, document the project, plan the sprint and prepare all the communication material around that specific release.</p><p>Nevertheless a huge amount of these tasks are not “visible” or “actionable” and yet they consume a great part of the designer’s day-to-day workload, and that’s why is important to show them as visible steps in the development sprint.</p><h3>This is how we do it</h3><p>Here are two quick examples of how I am working with my team. We use Jira to manage our 2-week sprints and the main goal, as designer, is to drag the design activities to “Done” at the end of the sprint — exactly the same a developer does with their implementation tasks.</p><p>However, we should note that the cards won’t probably go through all the existing steps in the sprint board because these steps were created having the development process in mind. Depending on how your team organized them, you should drag and drop your activity through the steps that make more sense to you — or you can customize the steps on your board with your team in order to accommodate both development and design tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zc5jK-m_C1QyZyV3hB-DbQ.png" /><figcaption>Example of a current sprint (with a filtered view) with visible Design tasks</figcaption></figure><h4>Example #1: Design Sprint preparation</h4><p>As you can see in the image above, the first card on the left is entitled “Design Sprint”. One of my goals for that sprint was to facilitate a 2-day design sprint session with my team (<a href="https://medium.com/nyc-design/design-sprint-in-2-days-c7afbd9eabd3">I already wrote an article about this 2-day approach</a>).</p><p>Before you start the Design Sprint session, it requires preparation. So this card was very useful to gather all important information before the session started, including the description of the project, the list of participants with their dedicated roles, materials and tools required for the session, the calendar of activities, links for the slides presentation, slack channel and other resources that would be important for the day of the Design Sprint. This way, all participants were in the loop of the project and they knew exactly what to expect, how to prepare for the session and what they needed to bring beforehand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFV2lYJsylUdw69KrlMMQQ.png" /></figure><h4>Example #2: User testing results</h4><p>Another very useful example on how to deliver design value during a development sprint is to disclose the process of user testing and its results. You can present the script and the methodology you used for the interviews, the links to the prototypes/solution you tested, the participants information and, of course, your findings — and possible next steps.</p><p>A nice bonus is that Jira has integrations with tools such as Zeplin and Invision, which provides nice embedded previews of your prototypes inside the ticket, making it even easier to scan the content and to understand the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Er-j7-5E2HOw4cGZaFgCSQ.png" /></figure><h3>Takeaways</h3><p>Communicating and displaying the impact of design as process is an asset not only for the team, but for the whole company. Why?</p><p><strong>✅</strong> The team is in the loop of the upcoming projects;</p><p>✅ We can track the time for each research or ideation processes of a given project, thanks to the logs in Jira;</p><p>✅ Better overview of the project lifecycle and easier source for documentation (research findings, benchmarking, design specs, etc);</p><p>✅ Making all this info accessible might help other teams that are working on similar projects (or that are affected by it);</p><p>✅ It gives visibility to the design work, usually done against the backdrop!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F2A8Vh81T3GTJir8qjK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F2A8Vh81T3GTJir8qjK%2Fsource.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F2A8Vh81T3GTJir8qjK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bce3fe903172e5f15f43294729049e7/href">https://medium.com/media/4bce3fe903172e5f15f43294729049e7/href</a></iframe><p>Plus, the advantage of using Jira is that you can link all your design activities to their dedicated projects epics and development tasks, so everyone in the team is aware of the workflow of your project as much as the design decisions behind it.</p><p>I hope you enjoyed some of my tips and let me know if you have any other ideas to share. Keep up the good work and stay safe ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8005d4ddddff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-ab-tasty-tech-blog/bring-value-to-your-design-work-in-every-development-sprint-8005d4ddddff">Bring value to your design work in every development sprint</a> was originally published in <a href="https://medium.com/the-ab-tasty-tech-blog">The AB Tasty Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Design: CX and UX as a competitive business advantage]]></title>
            <link>https://medium.com/the-ab-tasty-tech-blog/service-design-cx-and-ux-as-a-competitive-business-advantage-8f44eac2285?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f44eac2285</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[business-design]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 15:12:43 GMT</pubDate>
            <atom:updated>2020-06-02T15:12:43.908Z</atom:updated>
            <content:encoded><![CDATA[<h4>The potential of invisible design to impact business</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLPpSIfaegdkgWgOfyod2A.jpeg" /><figcaption>Image from <a href="https://unsplash.com/@darkjett">@darkjet</a></figcaption></figure><p>Many organisations today, from startups to governments, are investing in customer experience (CX) and user experience (UX) for their success, bringing more human-centred design capabilities to increase the business relevance of their projects for clients. And this is happening thanks to a growing number of organisations struggling to meet customers’ expectations and delivering a consistent quality of service across different channels, affirms Marzia Aricò <a href="https://www.liveworkstudio.com/blog/service-design-business-design/">in this article.</a></p><blockquote>“Design is trending in business. Management and IT consulting firms have started a race in acquisitions of strategic design firms, bringing human-centred design capabilities and talent in house to improve their digital offer” — Marzia Aricò</blockquote><p>According to J. Sorofman in a study from 2014 named “Gartner Surveys Confirm Customer Experience Is The New Battlefield”, 89% of companies expected to be competing mostly on the basis of customer experience by 2016, whereas only 36% were doing so back in 2010. When organisations start implementing it, they often start tracking customer satisfaction — with NPS, surveys and interviews, for instance. Meaningful iteration and UX research helps keeping the cycle of service design alive.</p><h3>But what is Service Design?</h3><p>Service Design is the practical application of design thinking to the development of services (<a href="https://www.interaction-design.org/literature/topics/design-thinking">design thinking</a> is a non-linear and iterative process to solve complex problems in a user-centered way).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qdEy2CpG5i3tcSpfp4FMSA.jpeg" /><figcaption>The Design Thinking process by H. Plattner, Institute of Design at Stanford. Additional visual design by Hidde Burgmans MSc (<a href="https://uxplanet.org/bridging-the-gap-between-service-design-and-scrum-why-ux-is-key-c81f1e66d203">UX Planet</a>)</figcaption></figure><p>However the biggest difference is in the practitioners: design thinking is mostly practiced by non-designers (it’s used as a mindset, a way of thinking) whereas service design is mostly practiced by designers, making use of more elaborate and extensive design methods to directly impact all facets of an organisation (business objectives are service related, like increasing NPS or minimising churn, for instance).</p><p>For this reason, we cannot define service design as a sole discipline because it’s an interdisciplinary field. When you design a service, you create experiences and to do so requires the manipulation and combination of both tangible and intangible mediums.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zs6pADsFRMFAk7FxeWcOsQ.jpeg" /><figcaption>“Bubble Bath” by <a href="https://unsplash.com/@runningvita">Vita Marija Murenaite</a></figcaption></figure><p>In <a href="https://www.thisisservicedesigndoing.com/">This is Service Design Doing</a> book, the author Marc Stickdorn stresses that the outcome of a service design process can have various forms: rather abstract organisational structures, operation processes, service experiences and even concrete physical objects. But the approach refers to the process of designing rather than to its outcome. According to Julia Pahl-Schoenbein, “service design skills are also useful because they can transform employees and managers to be truly user-centered”.</p><blockquote>“Service Design (…) is the activity of orchestrating people, infrastructure, communication and material components of a service in order to create value for all stakeholders involved, build a distinctive brand experience and maximise business potential” — <a href="https://www.koosservicedesign.com/blog/difference-between-design-thinking-service-design/">Koos Service Design</a></blockquote><h4>Service Design Thinking</h4><p>Designing a service entails a specific way of thinking, and this is why Marc Stickdorn and Jakob Schneider (from the book mentioned above) decided to call their approach <a href="http://thisisservicedesignthinking.com/"><strong>Service Design Thinking</strong></a><strong>, </strong>whereas<strong> </strong>service design applies design thinking to services and focus on doing, not just talking. In this book, the authors show us how to facilitate workshops and run projects, embed service design thinking in your organization — whether it’s a corporation, a government, an SME or a start-up — to change the way the teams work together as they adopt a more hands-on and human-centered approach, building success for your organization. To summarise: a great product empowered by a great service results on a great business 🤩.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*1vrQuzi8N3mVqGl5kyiDWQ.png" /><figcaption><a href="http://www.propublicobono.org/service-design/">http://www.propublicobono.org/service-design/</a></figcaption></figure><p>This approach only exists thanks to the popularity of design thinking, I dare say. Many tech companies started shedding light on the methodology a few decades ago in response to its adoption by many high-profile companies such as Google, Apple and Airbnb. According to their authors, Service Design Thinking is rooted in six principles currently (these principles went through an evolution from 2010 until 2017):</p><ol><li><strong>Human-centered:</strong> Consider the experience of all affected by the service;</li><li><strong>Collaborative: </strong>Stakeholders of various backgrounds and functions should be actively engaged in the service design process;</li><li><strong>Iterative:</strong> Service design is an exploratory, adaptive, and experimental approach, iterating toward implementation;</li><li><strong>Sequential:</strong> The service should be visualized and orchestrated as a sequence of interrelated actions:</li><li><strong>Real:</strong> Needs should be researched in reality, ideas prototyped in reality, and intangible values evidenced as physical or digital reality;</li><li><strong>Holistic:</strong> Services should sustainably address the needs of all stakeholders through the entire service and across the business.</li></ol><h3>Service Design at AB Tasty</h3><p>Customer relationship is key at AB Tasty. Nevertheless, the term “Service Design” was never embraced by us for a simple reason: it is a fairly new term (and I realized in France is not really used). Nonetheless, what we’ve been calling User Experience + Customer Experience is actually what Service Design entails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NVDy8YXBjC9eD8KjT_I_g.png" /><figcaption>How teams are organised at <a href="http://www.abtasty.com/">AB Tasty</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YKo_0P0rnRSr6DX4QEGJQ.png" /><figcaption>The total design spectrum by <a href="https://uxplanet.org/7-ux-principles-by-a-service-design-company-5a32da62f7e8">UX Planet</a></figcaption></figure><p>Since customer support is a big part of our product as well, we thought it was important to build internal training programs for our Customer Success Managers, Sales and HR. Thus, we created the <strong>UX Academy</strong><em>,</em> an internal program to promote UX as a strategic asset at AB Tasty. Also, we conduct parallel workshops on specific topics with the Client and Sales teams. The goal is to teach best practices and methodologies and make everyone understand their importance on practicing and promoting customer experience in the company.</p><p>As you can see in the picture above, the Product team is responsible for the user experience of the product itself but all other possible interactions between AB Tasty and our customers are handled by all teams.</p><blockquote>The main purpose of UX Academy, the internal Design training program at AB Tasty, is to see that Customer Experience is part of the UX process as a whole.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ioeHx_GlKV_6ulUiFOYFCw.jpeg" /><figcaption>Snap from one of the UX Academy sessions in our office in Madrid, March 2019</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtxHRUl1i0ZQ3vpKoXJFCQ.jpeg" /><figcaption>Design Thinking workshop in our office in Paris, January 2020</figcaption></figure><p>Objectively, all the participants feel more integrated in the Design process in the company. They know that what they do on a daily basis (onboarding clients, answering the phone, replying to support tickets and emails, building a training program, conducting face to face meetings or even just opening the door at our office) is all part of the user journey and therefore they are extremely important in building a strong customer experience and a holistic approach to the service we provide to our customers, partners, colleagues and investors.</p><p>Here’s a testemonial from Kasthuri as an example of the importance of integrating the Customer Success Managers in the design process at AB Tasty, so they can help our clients better understand user behaviour, identify and correct points of friction on their websites, and create personalized web experiences following UX best practices.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fpssw5fTMSYg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dpssw5fTMSYg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fpssw5fTMSYg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b93cd041056444acd82be7afbd0adb37/href">https://medium.com/media/b93cd041056444acd82be7afbd0adb37/href</a></iframe><h3>Let’s keep moving!</h3><p>We want to keep growing in this field and propose even more training programs to evangelize not only the employees at AB Tasty, but also to establish a stronger connection with our customers and partners through events, talks, fairs and workshops. For instance, we organise regular events with clients, partners and prospects in different locations around the globe. Few examples are “Mad CRO” in Madrid, “Conversion Stammtisch” in Berlin, “The Breakfast Club” in London and “Conversions &amp; Cocktails” in New York.</p><p>Also, we manage on a regular-basis Webinars with employees and guests to discuss different topics around conversion optimisation, design practices, marketing &amp; much more. Especially now, in this unprecedented time we are all facing worldwide due to COVID-19 pandemic, Webinars and other formats of remote training are very much appreciated by our clients and partners. <strong>On the link below you can watch the videos of all the Webinars we’ve made so far:</strong></p><p><a href="https://www.abtasty.com/resources/?_type=webinars">Resource library on customer experience optimization by AB Tasty</a></p><p>If you have any suggestions and ideas that might be useful for us to enrich this exchange, don’t hesitate to get in touch — we will be happy to hear from you! As you can see, Service Design is indeed a competitive business strategy and no product without a customer approach will survive these days.</p><p>Stay safe ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f44eac2285" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-ab-tasty-tech-blog/service-design-cx-and-ux-as-a-competitive-business-advantage-8f44eac2285">Service Design: CX and UX as a competitive business advantage</a> was originally published in <a href="https://medium.com/the-ab-tasty-tech-blog">The AB Tasty Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Writing, why is it so important?]]></title>
            <link>https://medium.com/the-ab-tasty-tech-blog/ux-writing-why-is-it-so-important-aaea8f08f6cf?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaea8f08f6cf</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Tue, 04 Feb 2020 11:34:24 GMT</pubDate>
            <atom:updated>2020-02-04T11:34:24.708Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX writing: why is it so important?</h3><h4>User Experience writing is more than content design. It’s content strategy for products.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9PHM8llqzQDEZUWPE-6BZA.jpeg" /></figure><blockquote>“As a writer who stumbled into UX one day many years ago, I was understandably excited; <strong>finally, organizations are realizing that copywriting shouldn’t only land on the marketing team’s desk” — </strong><a href="https://www.uxbooth.com/articles/what-is-ux-writing/"><strong>UX Booth</strong></a></blockquote><p>I’ve been spending the past few months curious about this emerging role of UX writer because I always liked to write and, as a UX Designer, I was wondering how I could do copywriting for products that could really impact user experience. I only discovered a few years ago that UX writing is an actual “thing” and many companies around the world are actually hiring UX writers to work on their teams.</p><p>After doing some research on the topic I came across different definitions, articles, courses and job descriptions for UX writers. Even though they present different points here and there, the vast majority share important common principles and best practices in the field. I will share some of them with you in this article, so you can start applying the principles of good UX writing as soon as you finish reading this article ⚡.</p><p>We can start by saying that UX writing only exists because we no longer tolerate interfaces like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*een7rEDlZgtuISLy4PmXSA.png" /><figcaption>When a wrong click might delete everything you have in your hard drive ✌️</figcaption></figure><p>or this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*0GgPFjqfRXVaOxcCmlbxqg.png" /><figcaption>Back in the day, when all you wanted was to watch your favorite movie on DVD 😭</figcaption></figure><p>This is why the necessity of thinking about the communication between user and interface became a very important field over the past decades (or at least since online platforms became more popular). UX writing was born to make users’ lives easier. Or, as <a href="https://blog.prototypr.io/why-every-writer-should-learn-ux-writing-f0dfc1154fab">Laurah Mwirichia</a> puts it:</p><blockquote>“[UX writing] It’s the lubrication, so to speak, between the user and the machine. Without any UX writing, the process can be counter-intuitive, and confusing. With terrible writing, the process is convoluted, messy and worst of all… frustrating”.</blockquote><p>The primary aim of UX writing is to settle communication between users and a digital product, helping them achieve their goals with language. It’s designing for content, <em>aka</em> writing for the interface, <em>aka</em> writing to promote user experience. UX writing is all about content strategy for products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsAJk8YKZHzlbwChf8dHkg.png" /><figcaption>How Google incorporates UX writing within UX <a href="https://uxplanet.org/ux-writing-how-to-do-it-like-google-with-this-powerful-checklist-e263cc37f5f1">according to Guy Ligertwood</a></figcaption></figure><p><strong>Nevertheless, UX writing is much more than copywriting. </strong>UX writing is product-oriented, focusing on helping users navigate the interface, whereas copywriting is sales-oriented, and is focused on attracting new customers. While UX writers are part of the design process (and work on design/product teams), copywriters take care of the outcome of that same process, selling the product to attract customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hPN9kEHJUZ8CD9HSKPIhw.png" /><figcaption><a href="https://uxdesign.cc/how-to-build-a-better-product-with-ux-writing-926d78209ce8">How to build a better product with UX writing</a></figcaption></figure><p>Although many UX writers also write microcopy, we can’t say the opposite is true, because microcopy writers might not be looking at the whole experience. For this reason, UX writing has become a dedicated job in many companies. Their main responsibility is to bridge the gap between content strategy and design.</p><blockquote>“It’s not the job of the UX writer to know all the right words. It’s the UX writer’s job to bring the customer’s perspective” — Shawn Roe</blockquote><h3>UX writing best practices:</h3><p>As you can see, user experience design is inherently connected to language and communication. However, writing is still something that most designers struggle with. For this reason, common conventions were established to help us create powerful conversational UI and improve the overall user experience — especially if you still don’t know how to best convey your words and guide users seamlessly throughout your product. So here are some best practices and <em>do’s </em>and<em> dont’s </em>for UX writing:</p><h4><strong>First, be clear:</strong></h4><blockquote>“For clarity we remove the technical terms and put the action in the context of the user.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H9Quay13nwADxg25jUqoqA.png" /><figcaption><a href="https://uxplanet.org/ux-writing-how-to-do-it-like-google-with-this-powerful-checklist-e263cc37f5f1">How Google does it</a></figcaption></figure><p>Often, the words used are <em>software</em> problems and not <em>people</em> problems. Pay attention to verbs. A verb is an action word, it tends to be the most powerful part of your sentence. In a perfect world, it would always relate to some action on the part of the user.</p><h4><strong>Also, be concise:</strong></h4><blockquote>“Writing is easy. All you have to do is cross out the wrong words.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkGjlKvxRyHFdcM8SQ1vZQ.png" /><figcaption><a href="https://uxplanet.org/ux-writing-how-to-do-it-like-google-with-this-powerful-checklist-e263cc37f5f1">How Google does it</a></figcaption></figure><p>Being concise doesn’t only mean keeping it short, it means something closer to being efficient. When we are writing concisely, we look at our message and make sure every word on the screen has a distinct job.</p><h4><strong>And, of course, be useful:</strong></h4><blockquote>“Give ’em what they want: If you understand people’s motivations, you can align yourself with them and help them get what they want.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_hONCirEZGT4BJ_driLBg.png" /><figcaption><a href="https://uxplanet.org/ux-writing-how-to-do-it-like-google-with-this-powerful-checklist-e263cc37f5f1">How Google does it</a></figcaption></figure><p>A call to action (CTA) guides people to their next step. You want your text to help people get where they want to go. For this reason the call to action needs to resonate with what people want to do.</p><p>These 3 main principles form the so-called “Triad”: Clear, Concise, Useful. The great challenge for the UX writer is to find the best balance between them all, even if you have to sacrifice one of them from time to time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hoNvS0POaJuwL1kquws_4w.png" /><figcaption><a href="https://blog.prototypr.io/why-every-writer-should-learn-ux-writing-f0dfc1154fab">Why every writer should learn UX writing</a></figcaption></figure><p>But wait, there is more! Here are other UX writing principles that I think are relevant 👇</p><h4><strong>Avoid long blocks of text</strong></h4><p>Users don’t read UI text — they scan it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fE_mCHsaNkeRmXppMONLxg.png" /></figure><h4><strong>Avoid double negatives</strong></h4><p>Double negatives increase cognitive load — they make users spend extra time decoding the message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*3Sdm8d1r8IODHYHBD42QUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*VPXeuhb9-vBlUidKelZPxA.png" /><figcaption><a href="https://uxmovement.com/buttons/when-cancel-buttons-should-not-say-cancel/">When cancel buttons should not say cancel</a></figcaption></figure><h4><strong>Begin with the objective and most important words</strong></h4><p>When a sentence describes an objective and the action needed to achieve it, start the sentence with the objective.</p><p>❌ “To see item’s properties, tap on it”</p><p>✅ “Tap on item to see its properties”</p><p>Or frontload the most important words into the beginning of any communication with the user:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*huVY7xYbEtYUnm4lhg5L4A.png" /><figcaption><a href="https://uxdesign.cc/how-to-write-for-interactions-3ff03080fb18">How to write for interactions</a></figcaption></figure><h4><strong>Use specific verbs whenever possible</strong></h4><p>Specific verbs are more meaningful to users than generic ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqW_EMzXFCdPMANx8j9gZw.png" /><figcaption><a href="https://www.cinnamon.agency/blog/post/watch_your_language_with_ux_writing">Watch your language with UX writing</a></figcaption></figure><h4><strong>Make the copy consistent</strong></h4><p>Inconsistency creates confusion. One typical example of inconsistency is replacing a word with a synonym in a different part of the UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hejnfpzZXU1vBdCPdKLdbw.png" /><figcaption><a href="https://www.cinnamon.agency/blog/post/watch_your_language_with_ux_writing">Watch your language with UX writing</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*N74DIYaemKQJjOzChkI1oA.png" /><figcaption><a href="https://producttribe.com/ux-design/ux-writing">UX Writing: make your product speak effectively</a></figcaption></figure><h4><strong>Avoid jargon</strong></h4><p>For clarity, you need to remove the technical terms and use familiar, understandable words and phrases instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*w7kWaPIOy0Mw1F8WM1geOA.png" /><figcaption><a href="https://uxdworld.com/2018/05/30/how-to-write-good-error-messages/">How to write good error messages</a></figcaption></figure><h4><strong>Write in the present tense</strong></h4><p>Avoid using the future tense to describe the action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ld2fJwLI3zFanOAUm2bvOQ.png" /><figcaption><a href="https://www.cinnamon.agency/blog/post/watch_your_language_with_ux_writing">Watch your language with UX writing</a></figcaption></figure><h4><strong>Write in the active voice</strong></h4><p>The passive voice makes readers yawn. Compare this sentence in both voices:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_U3NOCJSKX_3KMmFdfHIGg.png" /><figcaption><a href="https://www.cinnamon.agency/blog/post/watch_your_language_with_ux_writing">Watch your language with UX writing</a></figcaption></figure><h4><strong>Use numerals</strong></h4><p>Use numerals in place of words for numbers — they are easier to scan.</p><p>❌ “You have two missed calls”</p><p>✅ “You have 2 missed calls”</p><h4><strong>Be preventive, don’t scare your users off</strong></h4><p>Sometimes, descriptions of actions are inaccurate, especially when there is payment involved. Make sure your users have enough confidence to navigate your website before committing to any action or transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*CrZyqDkciANupKOXfrkdHQ.png" /><figcaption><a href="https://uxdesign.cc/use-plain-language-in-ux-writing-d7d5b0ea35f1">Use plain language in UX writing</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5PePjufQreT78_BuMmd5uw.png" /><figcaption>Airbnb</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*6AVbcutJr2qWeMnFn-FgFQ.png" /><figcaption>Google</figcaption></figure><h4>Keep it conversational</h4><p>We don’t want to deal with interfaces that sound like robots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZIgv6zuGZ14xgHBVpbPmKg.png" /><figcaption><a href="https://uxdesign.cc/how-to-write-for-interactions-3ff03080fb18">How to write for interactions</a></figcaption></figure><p>For example, Tumblr is human-oriented by using witty language to inform users that their username is already taken. They realized that it’s a frustrating experience when someone has already used your unique username, so they address this by giving a compliment. Instead of the offensive <em>This username is taken — </em>which means <em>You’re not creative enough</em> — they chose to give users a tap on the back: <em>It’s a good one, but it’s taken.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9ajp6PaYL_CpC07behV1w.png" /><figcaption>Tumblr</figcaption></figure><p>These are just a few examples of UX writing best practices that I picked for you (and myself) to start thinking about the importance of the role of a UX writer (or the role of a UX Designer that writes 🤓). It is always important to remember that unlike creative copywriting, which is concerned with acquiring new customers through sales-based communication, UX writing deals with current users that have already tried the product.</p><p>👉 <em>Remember: the voice and tone of your brand are really important for UX writing! This is another great topic to explore, so I will probably do it in another article. But, for now, just keep in mind that you should follow the guidelines of your brand’s voice and tone (if you have them formalized)— meaning, your words should be infused with your brand personality. You guarantee not only consistency in communication but also a familiar environment for your users, minimising possible misunderstandings.</em></p><blockquote>“UX writer’s main job is to make sure every step of the user flow is focused on the user’s need”.</blockquote><p><a href="https://producttribe.com/ux-design/ux-writing">Anastasiia Marushevska</a> also affirms that the UX writer’s task is to guide users through your product and be invisible at the same time, while establishing a powerful conversation tone with your users that will definitely improve their overall experience. And one good way of checking the impact of your changes is to A/B test the words on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0n5reCGyl4_qXUed7lk6lA.jpeg" /></figure><blockquote>“When trying to find the right words for your product never underestimate the power of A/B testing”</blockquote><p>Guy Ligertwood wrote an article on the importance of A/B testing to help you choose the right words on your website. One good example is to see how Google ran an A/B test on the start screen on Android Pay. They changed the button from ‘add card’ to ‘get started’ and it resulted in a 12% increase in click throughs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y4H6qHACW-SLyw5Ocn9hFA.png" /></figure><p>With <a href="http://www.abtasty.com/">AB Tasty</a> you can do this easily thanks to our WYSIWYG editor. It is the perfect approach to put into action all these best practices and validate the impact of good UX writing on your website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgfHEnutSVaMO_fxHnncpg.png" /><figcaption>How to quickly edit the text in the visual editor from AB Tasty</figcaption></figure><p>But, remember: although A/B testing can give you an overall yes-or-no result on what works better and what doesn’t, it doesn’t provide feedback on <em>why </em>certain types of text works or not. More complex texts need a deeper understanding of how users interact with content, so you will probably need to use other methods for more qualitative insights. For more information on this topic, I recommend this article:</p><p><a href="https://uxstudioteam.com/ux-blog/ux-copywriting/">UX Copywriting: 3 Testing Methods That Beat A/B Testing + QUIZ</a></p><p>Please feel free to share your thoughts and thanks a lot for reading until the end! ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaea8f08f6cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-ab-tasty-tech-blog/ux-writing-why-is-it-so-important-aaea8f08f6cf">UX Writing, why is it so important?</a> was originally published in <a href="https://medium.com/the-ab-tasty-tech-blog">The AB Tasty Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How internal usability testing sessions saved our beta release]]></title>
            <link>https://medium.com/nyc-design/how-internal-usability-testing-sessions-saved-our-beta-release-b23fcfafc3d9?source=rss-f30b3154f62c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b23fcfafc3d9</guid>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Bettina D'ávila]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 18:55:36 GMT</pubDate>
            <atom:updated>2019-08-17T07:46:35.726Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago I posted an article about a <a href="https://medium.com/nyc-design/design-sprint-in-2-days-c7afbd9eabd3">2-day Design Sprint</a>. In this event, our Sprint team successfully achieved to establish the long and short term goals for the project, finishing the last session with a tangible storyboard for our main user journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rMafnJzZLkc8T_2KW8nMJQ.jpeg" /><figcaption>Ongoing Design Sprint session at <a href="https://www.abtasty.com/">AB Tasty</a> in Paris, February 2019</figcaption></figure><p>After this Sprint session, the prototype was built within a few weeks time to be tested and implemented. But, instead of rolling-out the solution to beta testers, we decided to iterate a little bit more with internal customer success managers in order to validate our hypotheses. We ran five different sessions and I will share my learnings and take-aways with you right now.</p><h3>The Usability Testing Sessions</h3><p>We decided to run some usability testing sessions with our own customer success managers — who are not only the final users of the feature but also represent the voice of our customers — in order to detect important usability issues before rolling out the new feature to beta testers. This way, we not only detected major pain points in our hypotheses but we also gained time to pitch our customers about the new feature and if they would be willing to become beta testers.</p><h4><strong>The testers</strong></h4><p>Following the famous tips from Norman and Nielsen, we gathered five consultants to test our first solution in order to cover the majority of pain points we could find in the prototype. According to their study, “elaborate usability tests are a waste of resources. The best results come from testing no more than 5 users and running as many small tests as you can afford”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*2Q9Lfo_zjevBbADqlqBUmQ.gif" /><figcaption><a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">“Why You Only Need to Test with 5 Users”</a> by Norman Nielsen Group</figcaption></figure><p>But, be aware! Keep in mind that this strategy works well with an existing product, where we are digging for usability issues in order to improve the experience. If you’re thinking about designing a whole new product or service from scratch, consider doing <a href="https://uxdesign.cc/user-research-is-more-the-merrier-9ee4cfe46c7a">exploratory design research</a>.</p><h4><strong>The prototype</strong></h4><p>We created a click-dummy prototype in <a href="https://www.invisionapp.com/">Invision</a> to fake the navigation and interactions on screen. Our solution was already a high-fidelity mockup because the testers were already familiar with the tool and with the functionality of the feature. Moreover, beyond changes in the content and navigation path, we wanted to test the impact of the new UI elements in the overall user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H4uuDh8koU7z-3xkzRpatA.jpeg" /><figcaption>A glimpse of the Invision’s platform by <a href="https://tubikstudio.com/design-tool-review-prototyping-with-invision/">tubik</a></figcaption></figure><h4><strong>The session</strong></h4><p>Each session took around 30 minutes and it was composed by three participants: the interviewer, the note-taker and the interviewee (the interviewer and note-taker roles were taken by the UX Designer and the Product Manager, switching these roles between every session).</p><p>We created a script to guide the interviewer, with a narrative and a direction of the tasks the interviewee should try to complete during the session. We also applied the “Think Aloud” method — consisting in the interviewee saying out loud everything they are thinking, feeling, struggling with or happy about.</p><p>After each session, the interviewer and the note-taker would get together to discuss the notes, their different impressions of the session, so to finally confirm (or not) the major pain points and to validate (or not) the hypothesis being tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xN0kC6SnURuJhG7D-n_6Lw.jpeg" /><figcaption><a href="https://medium.com/u/2d64a3bb15a6">José Alejandro Cuffia</a> for <a href="https://unsplash.com/photos/TC5P6ZRxDbI">Unsplash</a></figcaption></figure><h4><strong>The outcome</strong></h4><p>With these five usability testing sessions we were able to validate crucial points of our solution within only just a few days.</p><p>We realised that our solution were way more complex than necessary and the users were overwhelmed with the cognitive load during the setup process. We also noticed that important buttons and sections seemed invisible to the user, or really difficult to find — greatly compromising the usability of the feature. On the other hand, we got great feedback on solutions that worked well, reassuring the team of the good choices we made.</p><p>Now, the follow-up step is to improve the mockups with the new feedback and re-test the solutions with the beta testers while we progressively roll out the feature to real customers.</p><h3>Big take-aways</h3><ul><li>Things can always be simpler. A lot of complexity was removed after receving feedback. If the problem is complex, that doesn’t mean the solution should also be;</li><li>Beta versions of your product still affect real customers. Don’t underestimate the value of a beta version, MVP or POC when you want to show the value of your product/service to real customers;</li><li>Positive feedback is also important for our validation. As much as identifying usability issues is relevant, we need to understand what solution works for the user as well (not only what is broken).</li></ul><p>Thanks for stopping by and I am eager to hear and share more similar experiences from fellow designers. Hit me up if you wanna chat and see you next time! 🤙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b23fcfafc3d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/how-internal-usability-testing-sessions-saved-our-beta-release-b23fcfafc3d9">How internal usability testing sessions saved our beta release</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>