<?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 Smashing Magazine on Medium]]></title>
        <description><![CDATA[Stories by Smashing Magazine on Medium]]></description>
        <link>https://medium.com/@smashingmag?source=rss-5ef3beaef7aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*UQN-quH8HarEW_xcKwF5yA.png</url>
            <title>Stories by Smashing Magazine on Medium</title>
            <link>https://medium.com/@smashingmag?source=rss-5ef3beaef7aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:01:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@smashingmag/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[Can You Design A Website For The Five Senses?]]></title>
            <link>https://medium.com/@smashingmag/can-you-design-a-website-for-the-five-senses-c94fe98a4ae8?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/c94fe98a4ae8</guid>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 07:56:01 GMT</pubDate>
            <atom:updated>2023-09-15T07:56:01.380Z</atom:updated>
            <content:encoded><![CDATA[<p>// written by <a href="https://www.smashingmagazine.com/author/suzanne-scacca/">Suzanne Scacca</a></p><p>Maybe it’s the whiff of someone’s perfume. Or a bite of pizza from a new restaurant. Or a song playing over the loudspeakers at the store. But the second it hits, you’re immediately transported to another place, time, or mood.</p><p>Imagine if your website could evoke this kind of response. Visitors who respond to the sensory stimulation would instantly be in a more positive headspace, which they’d then associate with the site and your brand.</p><p>Just be careful if you’re going to attempt this. Not every sense-triggered memory or emotion is going to be a positive one, so you want to focus on more generalized and shared experiences that come with little risk of backfiring.</p><p>Here are some ideas to help you do this:</p><h3>Designing For The Sense Of Sight</h3><p>A website is a medium to be seen, so you’d assume that the sense of sight is the most powerful one to play with. But there’s a difference between a visitor taking in the photos and words on a web page and <em>feeling</em> something because of what they’ve seen.</p><p>The truth is, sight is the most pragmatic of the senses. Typically, what you see is what you get.</p><p>Nevertheless, it is possible to design a website so that it alters the mood of anyone who visits it.</p><p><a href="https://www.smashingmagazine.com/2010/01/color-theory-for-designers-part-1-the-meaning-of-color/">Color theory</a> is one tool you can use to inspire visitors to feel a certain way based on what they see. However, that can be problematic as colors often have multiple meanings not just across cultures but within them as well. So, while you might think you’re making visitors feel happier with bright yellow hues, it could instead be making them feel overwhelmed and anxious.</p><p>What I’d suggest you focus on is how to use visuals to create an immersive experience that transports your visitors to another place or time. They shouldn’t need to look past the homepage for it either (though it’s a good idea if you can make it extend across the site).</p><p>Travel and hospitality sites have a tendency to do this well. Let’s look at an example.</p><p><a href="https://www.visitphilly.com/">Visit Philly</a> is a tourism site I like to use to find things to do around the city. And that’s because this is how most of the pages on the site are designed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Va254tOLnk4ncdCETpdWw.png" /><figcaption>The homepage of the Visit Philly website welcomes people to the City of Brotherly and Sisterly Love. (Source: <a href="https://www.visitphilly.com/">Visit Philly</a>)</figcaption></figure><p>Each page feels like a physically immersive experience without forcing visitors to watch a background video or scroll through a carousel of photos. Instead, each full-sized image perfectly encapsulates the setting that awaits each visitor.</p><p>Unlike staged, overly manipulated or stock photos that portray an unrealistic reality, <a href="https://www.nngroup.com/articles/photos-as-web-content/">visitors aren’t likely to ignore this kind of content</a>. Because it’s real and it’s also easy to put themselves in the shoes of the people they’re looking at. The man and his dog. The family going for a walk. Or the people enjoying the spectacle that is Spruce Street Harbor Park:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84BzZP0JZsnpxKBUJOUB5w.png" /><figcaption>A page dedicated to Spruce Street Harbor Park in Philadelphia. (Source: <a href="https://www.visitphilly.com/">Visit Philly</a>)</figcaption></figure><p>For people who’ve been to Philadelphia, the visuals on this site are likely to lure them back to the good times they had. And for people who are new to the city, the oversized visuals that show off the city’s hotspots enable them to picture what it’s like to go, which is a very effective way to sell someone on an experience.</p><h3>Designing For The Sense Of Smell</h3><p>Back in elementary school, our teachers would reward us with good scores on homework and tests with a handwritten note like “Great work!” and a scratch-n-sniff sticker. Like these ones available on <a href="https://www.etsy.com/listing/742393212/1970s-original-scratch-n-sniff-stickers?ga_order=most_relevant&amp;ga_search_type=all&amp;ga_view_type=gallery&amp;ga_search_query=scratch+and+sniff+stickers&amp;ref=sr_gallery-1-12">Etsy</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUD2dIz4Oh4hzwrYTF3dSg.png" /><figcaption>A pack of 1970s Scratch ’N’ Sniff stickers are available through Etsy. (Source: <a href="https://www.etsy.com/listing/742393212/1970s-original-scratch-n-sniff-stickers?ga_order=most_relevant&amp;ga_search_type=all&amp;ga_view_type=gallery&amp;ga_search_query=scratch+and+sniff+stickers&amp;ref=sr_gallery-1-12">Etsy</a>)</figcaption></figure><p>If you don’t know what these are, the name says it all. You scratch your nail against the sticker and it smells just like the picture on it.</p><p>Looking at this photo, I can still smell the “Berry Good” strawberry. This is going to sound crazy, but it reminds me of success. I don’t know if my teachers had an entire pack of the strawberry stickers, but it’s the one I got most frequently. And so I guess that’s why I associate it with good grades just by looking at it.</p><p>This is what you want to aim for with your website. You want to depict some recognizable scent in a way that the majority (if not all) of your visitors instantly feel good.</p><p>For example:</p><p>A used bookstore or library website with imagery that depicts rows upon rows of old books like the <a href="https://providenceathenaeum.org/">Providence Athenaeum</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3VXmuUdyvX6I_1ZVDaPCg.png" /><figcaption>The Providence Athenaeum homepage ‘smells’ like old books. (Source: <a href="https://providenceathenaeum.org/">Providence Athenaeum</a>)</figcaption></figure><p>Voracious readers will definitely be able to smell the athenaeum and its old collection of books through this photo.</p><p>Or how about a company that’s known for making cleaning products like <a href="https://tide.com/">Tide</a>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l4O2HgdzPh9Tqe4V5z50tw.png" /><figcaption>The Tide homepage includes a couple images of freshly cleaned and folded laundry. (Source: <a href="https://tide.com/">Tide</a>)</figcaption></figure><p>Even if you don’t use Tide to do your laundry, you know exactly what the first image in this carousel is going to smell like.</p><p>Fresh laundry is the scent of cleanliness and comfort. I’d also argue that it’s the scent of satisfaction because nothing feels better than getting laundry done and over with.</p><p>I also really like what <a href="https://www.coffeeculturecafe.com/">Coffee Culture Cafe &amp; Eatery</a> has done with its homepage video:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*izLLpPvPyTfZIZFp-6_q0w.png" /><figcaption>Coffee Culture Cafe puts its coffee beans on full display. (Source: <a href="https://www.coffeeculturecafe.com/">Coffee Culture Cafe &amp; Eatery</a>)</figcaption></figure><p>It’s not abnormal for a restaurant or cafe to show photos of its food or drinks. However, this is the raw product: the coffee beans. And as any coffee drinker can attest, this photo smells delicious and is something that’s sure to awaken their anticipation in ordering their first cup.</p><h3>Designing For The Sense Of Sound</h3><p>I was driving to the beach over the weekend when a song came on that made me smile. It was “What I Got” by Sublime, a song I listened to many times when making the long drive to the beach with friends in college.</p><p>Although I was alone on this particular trip and headed to a different beach, there was something about that song that instantly transformed my mood. The stress I was feeling about work melted away and all I could focus on was how good it was going to feel to spend the day in the sunshine by the water.</p><p>That’s something that the right sound can do. It can pull us out of the present and take us back to a memory of the past. Or it can overwhelm us with emotion that has no real grounding in the moment and, yet, there it is.</p><p>It doesn’t have to be music. And, honestly, on a website, it shouldn’t be. But that doesn’t mean you can’t still appeal to visitors’ ears through design.</p><p>There are two ways to approach this.</p><p>The first is to include imagery that depicts a predictable sound and one that brings joy (or whatever positive emotion you’re shooting for). Take the website for <a href="https://www.kindermusik.com/">Kindermusik</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7m5x3lta_1vL4LrwimBDA.png" /><figcaption>Kindermusik website shows how kids learn through music. (Source: <a href="https://www.kindermusik.com/">Kindermusik</a>)</figcaption></figure><p>For many of us, the xylophone was one of the first instruments we were introduced to as kids. So, it’s hard to imagine anyone seeing the top photo and not immediately hear the sounds of a kid banging away on the bars.</p><p>And while this school is all about providing kids with music-based education, not every image sounds like music. For instance, the Benefits page has this photo at the top:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSWlEtweK0rV-02roozPTw.png" /><figcaption>A baby laughs at the top of the Kindermusik Benefits page. (Source: <a href="https://www.kindermusik.com/">Kindermusik</a>)</figcaption></figure><p>There might not be any sound coming through this site, but we all know the distinctive sound of a baby’s laugh. For parents trying to decide where to have their kids educated, they’ll be pleased to hear the sound of a child laughing as they visit this web page.</p><p>The other way to approach sound in design is to remove it entirely from the experience.</p><p>This works well for places like <a href="https://www.scandinave.com/vieux-montreal/en/">Scandinave Spa</a> where customers come to enjoy the solitude and silence as they retreat from pressures of society, work, life and so on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKCObnxP6qHKlKsLhqfCiA.png" /><figcaption>The Scandinave Spa uses images that sound quiet. (Source: <a href="https://www.scandinave.com/vieux-montreal/en/">Scandinave Spa</a>)</figcaption></figure><p>If a lack of noise is what makes the real-life experience so valuable, then choosing images that represent this is really important. So, obviously, sites like these won’t have images of people standing around talking, nor will they incorporate bright or flashy lights.</p><p>A calm experience is best depicted by an absence of noise, movement and distraction.</p><h3>Designing For The Sense Of Taste</h3><p><a href="https://www.psychologytoday.com/us/blog/psychology-tomorrow/201904/the-cooking-show-paradox">Dr. Bence Nanay</a> wrote about the cooking show paradox on Psychology Today, debating why it is that so many people enjoy watching someone else cook. It can’t possibly be to learn how to cook as recipes are everywhere online. And while they might enjoy the competitive aspect of some of these shows, he suggests the main reason is this:</p><blockquote><em>Watching cooking shows is eating vicariously in the most literal sense possible — we get mental imagery of tasting and smelling the food without actually tasting or smelling it.</em></blockquote><p>I think we can expand a bit further on Nanay’s argument.</p><p>I also believe that people become more invested in an outcome when they get to see the process of it being made. This isn’t something we’re usually allowed to see as consumers. We go out to eat and the food is sitting there on a plate for us. So, there’s something about the build-up of watching food or drinks being made that adds something extra to the experience.</p><p>That’s why I don’t think it’s enough to just use static <a href="https://www.smashingmagazine.com/2020/06/web-designers-help-restaurants-digital-experiences/">photos of a restaurant’s dishes</a> or food company’s products on a website. Not if you want to deeply connect to the visitors’ sense of taste, that is.</p><p>For instance, this is the video that’s embedded into the top of <a href="https://sweetcharlies.com/">Sweet Charlie’s</a> website:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2Fr8xV5kDu2I0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fwatch%3Fv%3Dr8xV5kDu2I0&amp;image=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fi.ytimg.com%2Fvi%2Fr8xV5kDu2I0%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/29de14b140a1a5c29b2a770270b73bf0/href">https://medium.com/media/29de14b140a1a5c29b2a770270b73bf0/href</a></iframe><p>If you’ve ever been to a shop that makes rolled ice cream, you know just how enjoyable it is to watch this process in person. So, for a website to recreate that process — especially for first-time customers wondering what the heck <em>rolled</em> ice cream is — it’s a brilliant move.</p><h3>Designing For The Sense Of Touch</h3><p>The sense of touch is a relatively easy one to depict on the web. We see it all the time on ecommerce sites that allow shoppers to zoom in on fabrics and get a sense for what they feel like to touch or wear.</p><p>Like the zoom-in capabilities <a href="https://www.anthropologie.com/?ref=logo">Anthropologie</a> gives its shoppers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KOAEHkks6E9V1dGX1lEZbw.png" /><figcaption>Anthropologie allows shoppers to zoom in on each item in its online store. (Source: <a href="https://www.anthropologie.com/?ref=logo">Anthropologie</a>)</figcaption></figure><p>But this is nothing more than window-shopping done virtually. Anyone could walk through a store and brush their hands through racks of clothes. Don’t get me wrong, it’s a necessary functionality. However, this isn’t how we use the sense of touch to create a deeper connection with visitors.</p><p>We need to play around with more drastic tactile sensations.</p><p>One element you might want to fixate on is temperature. If there’s a heating or cooling element, work with that.</p><p>Another element you can play with is the feeling or pressure of human touch. There are many applications for this, though it’s particularly useful for websites that advertise therapeutic services.</p><p>For instance, this is how <a href="https://www.massageenvy.com/">Massage Envy</a> invites people to its spa services:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M0OKhzs659kkeEoOT8ygig.png" /><figcaption>The Massage Envy website uses images of people getting massages instead of just empty massage rooms and tables. (Source: <a href="https://www.massageenvy.com/">Massage Envy</a>)</figcaption></figure><p>This is a good start. Some spa and massage websites just show images of empty massage rooms and tables. At least here prospective customers can kind of see the massage process.</p><p>I don’t think there’s much to <em>feel</em> here though as the positioning of the masseuse and pressure being applied seem unrealistic. I’m guessing it’s a stock photo chosen for its symmetry, color and attractiveness.</p><p>But there are ways to capture the tangible experience while still making it look good for a website. For instance, the <a href="https://thebodhispa.com/">Bodhi Spa</a> uses a video to take visitors through various services they can experience — alone or with others — at the space.</p><p>At one point, they’re shown someone getting a massage:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNxxdc6Lnj4QaZh9UJr-LQ.png" /><figcaption>The video on the home page of the Bodhi Spa website shows a woman receiving a hands-on massage. (Source: <a href="https://thebodhispa.com/">Bodhi Spa</a>)</figcaption></figure><p>Notice the symmetry of this screengrab and how it doesn’t have to come at the expense of authenticity. Plus, the video shows customers how the massage feels as the masseuse applies pressure and moves her hands around the woman’s neck and head.</p><p>Visitors then get to see a couple enjoying the benefits of hydrotherapy, with the woman picking up a handful of salt and placing it in the pool they’re in:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UBQ2gKtMMpH_mc2Ui4g_cA.png" /><figcaption>The Bodhi Spa intro video shows a couple enjoying the benefits of salt therapy. (Source: <a href="https://thebodhispa.com/">Bodhi Spa</a>)</figcaption></figure><p>There’s a lot to <em>touch</em> in this video. The fine salt crystals. The warm water in the hydrotherapy tub. And, shortly after this screengrab, the couple holds hands as they enter the cool-down room.</p><p>A copywriter can certainly convey a lot of the feel-good benefits of something like this, but it’s also effective to let visitors see it with their own two eyes and experience it vicariously through others.</p><h3>Wrapping Up</h3><p>While I think that trying to design for all five senses at once would lead to sensory overload, choosing one particularly potent sense to design for is a great idea.</p><p>If you can find a way to recreate that sense through your site, your visitors may experience:</p><ul><li>Heightened awareness,</li><li>Positive and happier thoughts than before they entered the site,</li><li>A greater connection to the bigger picture and a willingness to take next steps on the site.</li></ul><p>We often focus on how to connect to our audience through their pain, but why don’t we focus on connecting through happiness for a change? I think we could all use a little more of that these days.</p><p><strong>Editor’s Note</strong>: <a href="https://www.smashingmagazine.com/2020/08/design-website-five-senses/"><em>This article was originally published on Smashing Magazine</em></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c94fe98a4ae8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modern Technology And The Future Of Language Translation]]></title>
            <link>https://medium.com/@smashingmag/modern-technology-and-the-future-of-language-translation-9721f3a5274d?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/9721f3a5274d</guid>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 07:36:46 GMT</pubDate>
            <atom:updated>2023-09-15T07:37:19.636Z</atom:updated>
            <content:encoded><![CDATA[<p>// written by <a href="https://www.smashingmagazine.com/author/adriano-raiano/">Adriano Raiano</a></p><p>Multilingual content development presents its own set of difficulties, necessitating close attention to language translations and the use of the right tools. The exciting part is that translation technology has advanced remarkably over time.</p><p>In this article, we’ll explore the growth of translation technology throughout time, as well as its origins, and lead up to whether machine translation and artificial intelligence (AI) actually outperform their conventional counterparts when it comes to managing translations. In the process, we’ll discuss the fascinating opportunities offered by automated approaches to language translation as we examine their advantages and potential drawbacks.</p><p>And finally, we will speculate on the future of language translation, specifically the exhilarating showdown between OpenAI and Google in their race to dominate the AI landscape.</p><h3>The Evolution Of Translation Technology</h3><p>Translation technology can be traced back to <a href="https://www.forbes.com/sites/thomasbrewster/2015/09/03/microsoft-dumb-attacks-cracks-next-gen-cryptography/?sh=5e6394e95b55">Al-Kindi’s Manuscript on Deciphering Cryptographic Messages</a>. However, with the arrival of computers in the mid-twentieth century, translation technology began taking shape. Over the years, significant milestones have marked the evolution, shaping how translations are performed and enhancing the capabilities of language professionals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SuQzTybbGKSDs-LHtwrWMg.jpeg" /><figcaption>Image source: <a href="https://www.reddit.com/r/ThisDayInHistory/comments/ksk54x/tdih_january_7_1954_georgetownibm_experiment_the/">Reddit</a>.</figcaption></figure><p>Georgetown University and IBM conducted the so-called <a href="https://en.wikipedia.org/wiki/Georgetown%E2%80%93IBM_experiment">Georgetown-IBM experiment</a> in the 1950s. The experiment was designed primarily to capture governmental and public interests and funding by demonstrating machine translation capabilities. It was far from a fully featured system. This early system, however, was rule-based and lexicographical, resulting in low reliability and slow translation speeds. Despite its weaknesses, it laid the foundation for future advancements in the field.</p><p>The late 1980s and early 1990s marked the rise of <strong>statistical machine translation (SMT)</strong> pioneered by IBM researchers. By leveraging bilingual corpora, SMT improved translation accuracy and laid the groundwork for more advanced translation techniques.</p><p>In the early 1990s, commercial <strong>computer-assisted translation (CAT)</strong> tools became widely available, empowering translators and boosting productivity. These tools utilized translation memories, glossaries, and other resources to support the translation process and enhance efficiency.</p><p>The late 1990s saw IBM release a <a href="https://www.infoamerica.org/documentos_pdf/bar05.pdf">rule-based statistical translation engine</a> (pdf), which became the industry standard heading into the new century. IBM’s translation engine introduced predictive algorithms and statistical translation, bringing machine translation to the forefront of language translation technology.</p><p>In the early 2000s, the first <strong>cloud-based translation management systems (TMS)</strong> began appearing in the market. While there were some early non-cloud-based versions in the mid-1980s, these modern systems transformed the translation process by allowing teams of people to work more flexibly and collaborate with other company members regardless of their location. The cloud-based approach improved accessibility, scalability, and collaboration capabilities, completely changing how translation projects were managed.</p><p>2006 is a significant milestone in translation management because it <a href="https://blog.google/products/translate/ten-years-of-google-translate/">marks the launch</a> of <strong>Google Translate</strong>. Using predictive algorithms and statistical translation, Google Translate brought machine translation to the masses and has remained the <em>de facto</em> tool for online multilingual translations. Despite its powerful features, it gained a reputation for inaccurate translations. Still, it plays a pivotal role in making translation technology more widely known and utilized, paving the way for future advancements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*cNB3uiX121_f8OSm-Gh2_Q.jpeg" /><figcaption>Image source: <a href="https://www.bureauworks.com/blog/5-best-machine-translation-tools-with-examples">Bureau Works</a>.</figcaption></figure><p>In 2016, Google Translate made a significant leap by introducing <a href="https://en.wikipedia.org/wiki/Google_Neural_Machine_Translation"><strong>neural machine translation</strong></a><strong> (NMT)</strong>. NMT surpassed previous translation tools, offering improved quality, fluency, and context preservation.</p><p>NMT set a new commercial standard and propelled the field forward. By 2017, <a href="https://www.deepl.com/">DeepL</a> emerged as an <strong>AI-powered machine translation system</strong> renowned for its high-quality translations and natural-sounding output. DeepL’s capabilities further demonstrated the advancements achieved in the field of translation technology.</p><p>From 2018 onward, the focus has remained on enhancing NMT models, which continue to outperform traditional <strong>statistical machine translation (SMT)</strong> approaches. NMT has proven instrumental in improving translation accuracy and has become the preferred approach in today’s many translation applications.</p><h3>What Translation Technology Came Into Place Over the Years</h3><p>Translation technology has evolved significantly over the years, offering various tools to enhance the translation process. The main types of translation technology include:</p><ul><li><a href="https://en.wikipedia.org/wiki/Computer-assisted_translation"><strong>Computer-assisted translation</strong></a><strong> (CAT)</strong><br>These software applications support translators by providing databases of previous translations, translation memories, glossaries, and advanced search and navigation tools. CAT tools revolutionize translation by improving efficiency and enabling translators to focus more on the translation itself.</li><li><a href="https://www.atanet.org/client-assistance/machine-translation/"><strong>Machine translation</strong></a><strong> (MT)</strong><br>Machine translation is an automated system that produces translated content without human intervention. It can be categorized into rule-based (RBMT), statistical (SMT), or neural (NMT) approaches. MT’s output quality varies based on language pairs, subject matter, pre-editing, available training data, and post-editing resources. Raw machine translation may be used for low-impact content while post-editing by human translators is advisable for high-impact or sensitive content.</li><li><a href="https://locize.com/blog/tms/"><strong>Translation management systems</strong></a><strong> (TMS)</strong><br>TMS platforms streamline translation project management, offering support for multiple languages and file formats, real-time collaboration, integration with CAT tools and machine translation, reporting features, and customization options. TMS solutions ensure organized workflow and scalability for efficient translation project handling.</li></ul><p>Translation technology advancements have transformed the translation process, making it more efficient, cost-effective, and scalable.</p><h3>Finding The Right Translation Approach: Machine Vs. Human</h3><p>Finding the proper translation approach involves weighing the benefits and drawbacks of machine translation (MT) and human translation. Each approach has its own strengths and considerations to take into account.</p><p>Human translation, performed by professional linguists and subject-matter experts, offers accuracy, particularly for complex documents like legal and technical content. Humans can grasp linguistic intricacies and apply their own experiences and instincts to deliver high-quality translations. They can break down a language, ensure cultural nuances are correctly understood, and inject creativity to make the content compelling.</p><p>Collaborating with <strong>human translators</strong> allows direct communication, reducing the chances of missing project objectives and minimizing the need for revisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MtGi85X_HBbyBP8g_Yd9mw.jpeg" /><figcaption>Image source: <a href="https://bdtechtalks.com/2018/08/30/race-between-humans-and-artificial-intelligence/">TechTalks</a>.</figcaption></figure><p>That said, human translation does have some downsides, namely that it is <strong>resource-intensive</strong> and <strong>time-consuming</strong> compared to machine translation. If you have ever worked on a multilingual project, then you understand the costs associated with human translation — not every team has a resident translator, and finding one for a particular project can be extremely difficult. The costs often run high, and the process may not align with tight timelines or projects that prioritize speed over contextual accuracy.</p><p>Nevertheless, when it comes to localization and capturing the essence of messaging for a specific target audience, human translators excel in fine-tuning the content to resonate deeply. Machine translation cannot replicate the nuanced touch that human translators bring to the table.</p><p>On the other hand, <strong>machine translation</strong> — powered by artificial intelligence and advanced algorithms — is rapidly improving its understanding of context and cultural nuances. Machine translation offers speed and cost-efficiency compared to that manual translations, making it suitable for certain projects that prioritize quick turnarounds and where contextual accuracy is not the primary concern.</p><p>Modern TMSs often integrate machine and human translation capabilities, allowing users to choose the most appropriate approach for their specific requirements. Combining human translators with machine translation tools can create a powerful translation workflow. Machine translation can be used as a starting point and paired with human post-editing to ensure linguistic precision, cultural adaptation, and overall quality.</p><p>Translation management systems often provide options for leveraging both approaches, allowing for flexibility and optimization based on the content, time constraints, budget, and desired outcome. Ultimately, finding the proper translation approach depends on the content’s nature, the desired accuracy level, project objectives, budget considerations, and time constraints. Assessing these factors and considering the advantages and disadvantages of human and machine translation will guide you in making informed decisions that align with your or your team’s needs and goals.</p><h3>AI and Machine Translation</h3><p>Thanks to machine learning and AI advancements, translation technology has come a long way in recent years. However, complete translation automation is not yet feasible, as human translators and specialized machine translation tools offer unique advantages that complement each other.</p><blockquote>“The future of translation lies in the collaboration between human intelligence and AI-powered machine translation. Human translators excel in creative thinking and adapting translations for specific audiences, while AI is ideal for automating repetitive tasks.”</blockquote><p>This collaborative approach could result in a seamless translation process where human translators and AI tools work together in unison.</p><p>Machine-translation post-editing ensures the accuracy and fluency of AI-generated translations, while human translators provide the final touches to cater to specific needs. This shift should lead to a <strong>transition from computer-assisted human translation to human-assisted computer translation</strong>. Translation technology will continue to evolve, allowing translators to focus on more complex translations while AI-powered tools handle tedious tasks. It is no longer a question of whether to use translation technology but which tools to utilize for optimal results.</p><p>The future of translation looks promising as technology empowers translators to deliver high-quality translations efficiently, combining the strengths of human expertise and AI-powered capabilities.</p><h3>The Rise of Translation Management Systems</h3><p>Regarding AI and human interaction, TMSs play a crucial role in facilitating seamless collaboration. Here are five more examples of how TMSs enhance the synergy between human translators and AI.</p><h4>Terminology Management</h4><p>TMSs offer robust terminology management features, allowing users to create and maintain comprehensive term bases or glossaries, ensuring consistent usage of specific terminology across translations, and improving accuracy.</p><h4>Quality Assurance Tools</h4><p>TMSs often incorporate quality assurance tools that help identify potential translation errors and inconsistencies. These tools can flag untranslated segments, incorrect numbers, or inconsistent translations, enabling human translators to review and rectify them efficiently.</p><h4>Workflow Automation</h4><p>TMSs streamline the translation process by automating repetitive tasks. They can automatically assign translation tasks to appropriate translators, track progress, and manage deadlines. This automation improves efficiency and allows human translators to focus more on the creative aspects of translation, like nuances in the voice and tone of the content.</p><h4>Collaboration And Communication</h4><p>TMSs provide collaborative features that enable real-time communication and collaboration among translation teams. They allow translators to collaborate on projects, discuss specific translation challenges, and share feedback, fostering a cohesive and efficient workflow.</p><h4>Reporting And Analytics</h4><p>TMSs offer comprehensive reporting and analytics capabilities, providing valuable insights into translation projects. Users can track project progress, measure translator productivity, and analyze translation quality, allowing for continuous improvement and informed decision-making.</p><p>By leveraging the power of translation management systems, the interaction between AI and human translators becomes more seamless, efficient, and productive, resulting in high-quality translations that meet the specific needs of each project.</p><h3>Google And OpenAI Competition</h3><p>We’re already seeing <a href="https://www.fastcompany.com/90839649/google-not-openai-has-the-most-to-gain-from-generative-ai">brewing competition between Google and OpenAI</a> for dominance in AI-powered search and generated content. I expect 2024 to be the year that the clash involves translation technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7KEehJkzgq_njFnCqznuNQ.png" /><figcaption>Image source: <a href="https://www.answeriq.com/google-vs-open-ai/">Answer IQ</a>.</figcaption></figure><p>That said, when comparing OpenAI’s platform to Google Translate or DeepL, it’s important to consider the respective strengths and areas of specialization of each one. Let’s briefly consider the strengths of each one to see precisely how they differ.</p><h4>Continuously Improved And Robust Translation</h4><p>Google Translate and DeepL are dedicated to the field of machine translation and have been, for many years, focusing on refining their translation capabilities.</p><p>As a result, <strong>they have developed robust systems that excel in delivering high-quality translations</strong>. These platforms have leveraged extensive data and advanced techniques to improve their translation models, addressing real-world translation challenges continuously. Their systems’ continuous refinement and optimization have allowed them to achieve impressive translation accuracy and fluency.</p><h4>Generating Text</h4><p>OpenAI primarily focuses on generating human-like text and language generation tasks.</p><blockquote>“While OpenAI’s models, including ChatGPT, can perform machine translation tasks, they may not possess the same level of specialization and domain-specific knowledge as Google Translate and DeepL.”</blockquote><p>The primary objective of OpenAI’s language models is to generate coherent and contextually appropriate text rather than specifically fine-tuning their models for machine translation.</p><p>Compared to ChatGPT, Google Translate and DeepL excel in <a href="https://en.wikipedia.org/wiki/Domain-specific_language">domain-specific</a> sentences while factoring in obstacles to translation, such as background sounds when receiving audio input. In that sense, Google Translate and DeepL have <a href="https://www.lenseup.com/en/does-chatgpt-work-well-for-translating/#:~:text=Google%20Translate%20and%20DeepL%20both,domain%2Dspecific%20and%20noisy%20sentences">demonstrated their ability to handle real-world translation challenges effectively</a>, showcasing their continuous improvement and adaptation to different linguistic contexts.</p><h3>The Future Of Machine Translation</h3><p>Overall, when it comes to machine translation, Google Translate and DeepL have established themselves as leaders in the field, with a focus on delivering high-quality translations. Their extensive experience and focus on continual improvement contribute to their reputation for accuracy and fluency. While OpenAI’s ChatGPT models technically offer translation capabilities, they may not possess the same level of specialization or optimization tailored explicitly for machine translation tasks.</p><p>It’s important to note that the <strong>landscape of machine translation is continuously evolving</strong>, and the relative strengths of different platforms may change over time. While Google Translate and DeepL have demonstrated their superiority in translation quality, it’s worth considering that OpenAI’s focus on language generation and natural language processing research could benefit future advancements in their machine translation capabilities. Together, the three systems could make a perfect trifecta of accurate translations, speed and efficiency, and natural language processing.</p><p>OpenAI’s commitment to pushing the boundaries of AI technology and its track record of innovation suggests it may invest more resources in improving machine translation performance. As OpenAI continues to refine its models and explore new approaches, there is a possibility that it could bridge that gap and catch up with Google Translate and DeepL in terms of translation quality and specialization.</p><p>The machine translation landscape is <strong>highly competitive</strong>, with multiple research and industry players continuously striving to enhance translation models. As advancements in machine learning and neural networks continue, it’s conceivable that newer platforms or models could emerge and disrupt the current dynamics, introducing even higher-quality translations or specialized solutions in specific domains.</p><p>So, even though Google Translate and DeepL currently hold an advantage regarding translation quality and domain-specific expertise today in 2023, it’s essential to acknowledge the potential for future changes in the competitive landscape in the years to come. As technology progresses and new breakthroughs occur, the relative strengths and weaknesses of different platforms may shift, leading to exciting developments in the field of machine translation.</p><h3>Conclusion</h3><p>In summary, the evolution of translation technology has brought advancements to the multilingual space:</p><ul><li>The choice of translation approach depends on project requirements, considering factors such as <strong>accuracy, budget, and desired outcomes</strong>.</li><li>Machine translation offers <strong>speed and cost-efficiency</strong>, while human translation excels in complex content.</li><li><strong>Collaboration</strong> between human translators and AI-powered machines is best to get accurate translations that consider voice and tone.</li><li><strong>Translation management systems</strong> are crucial in facilitating collaboration between AI and human translators.</li></ul><p>While Google Translate and DeepL have demonstrated higher translation quality and specialization, OpenAI’s focus on human-like text generation may lead to improvements in machine translation capabilities. And those are only a few of the providers.</p><p>That means the future of translation technology is incredibly bright as platforms, like <a href="https://locize.com/">locize</a>, continue to evolve. As we’ve seen, there are plenty of opportunities to push this field further, and the outcomes will be enjoyable to watch in the coming years.</p><h4>Further Reading On SmashingMag</h4><ul><li>“<a href="https://www.smashingmagazine.com/2023/03/ai-technology-transform-design/">How AI Technology Will Transform Design</a>,” Nick Babich &amp; Gleb Kuznetsov</li><li>“<a href="https://www.smashingmagazine.com/2023/06/ai-detect-sentiment-audio-files/">Using AI To Detect Sentiment In Audio Files</a>,” Joas Pambou</li><li>“<a href="https://www.smashingmagazine.com/2018/04/rise-intelligent-conversational-ui/">The Rise Of Intelligent Conversational UI</a>,” Burke Holland</li><li>“<a href="https://www.smashingmagazine.com/2022/12/future-design-human-powered-ai-driven/">The Future Of Design: Human-Powered Or AI-Driven?</a>,” Keima Kai</li></ul><p><strong>Editor’s Note</strong>: <a href="https://www.smashingmagazine.com/2023/07/modern-technology-future-language-translation/"><em>This article was originally published on Smashing Magazine</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9721f3a5274d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving The Double Diamond Design Process]]></title>
            <link>https://medium.com/@smashingmag/improving-the-double-diamond-design-process-c28b782e03f4?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28b782e03f4</guid>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 07:19:58 GMT</pubDate>
            <atom:updated>2023-09-15T07:19:58.890Z</atom:updated>
            <content:encoded><![CDATA[<p>// written by <a href="https://www.smashingmagazine.com/author/andybudd/">Andy Budd</a></p><p>As a designer, you’re no doubt familiar with the <a href="https://blog.logrocket.com/ux-design/modern-double-diamond-design/">concept of the Double Diamond</a>, that super simple graphical representation of the ideal design process. Typically you’ll see two squares rotated 45 degrees: the first square will say something like “discover” and “define,” while the second one will encourage you to “explore” and “create.” Each diamond will have a heading, such as “problem” and “solution,” or the more punchy “design the right thing” and “design the thing right.” Along the side of each diamond, there will be a label explaining how you must first diverge, i.e., come up with lots of options before you can converge into a single answer.</p><p>It’s one of the simplest articulations of the design process out there. It’s also why many designers hate their jobs. Let me explain…</p><p><strong>Note</strong>: <em>If you’re curious as to who and when nailed down the Double Diamond concept in its present modern form — which we see being referenced practically everywhere nowadays — check the </em><a href="https://www.smashingmagazine.com/2023/08/improving-double-diamond-design-process/#appendix-how-do-we-describe-the-design-process"><em>Appendix</em></a><em> at the end of the article (“How do We Describe Design Process?”).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HEqXV2nm1yeSV0vVuMoY_w.jpeg" /><figcaption>The traditional “Double Diamond” as viewed by designers.</figcaption></figure><h3>Designers Are Problem-Finders And Problem-Solvers</h3><p>As designers, we like to think of ourselves as problem-finders as well as problem-solvers. Give us a user challenge, and we’ll use our research skills to uncover what’s <em>really</em> going on below the surface! We’ll take this information, reframe the problem, and come up with an even better solution — one that’s never been considered before. That’s what the double diamond is all about. It’s about avoiding the <em>obvious, shallow solutions</em> and instead freeing us up to be truly creative.</p><blockquote><em>“The formulation of a problem is often more essential than its solution, which may be merely a matter of mathematical or experimental skill. To raise new questions, new possibilities, to regard old problems from a new angle, requires creative imagination and marks real advance in science.”</em></blockquote><blockquote><em>— Albert Einstein &amp; Leopold Infeld (via: “</em><a href="https://www.infoq.com/articles/problem-reframing-method/"><em>Using the Problem Reframing Method</em></a><em>”</em></blockquote><p>I think the best example of this can be found in the UK TV program <a href="https://en.wikipedia.org/wiki/Blue_Peter"><em>Blue Peter</em></a>, a British children’s television entertainment program created by John Hunter Blair, which is the longest-running children’s TV show in the world.</p><p>A few years back, Blue Peter got to interview <a href="https://en.wikipedia.org/wiki/Jony_Ive">design legend Jony Ive</a>. They explained to Jony how they’d set a challenge for their young viewers to design a lunchbox, pencil case, and school bag, all in one. He responded by saying that you needed to be <em>really careful</em> not to have the word “box” in the brief because it might determine the path you went down. You could imagine if Jony had set the challenge, he might have asked the kids to “design a means of storing and transporting your lunch to school.” A nice reframing of the problem which didn’t contain the proposed solution!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2FFLUn7xCuQxo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fwatch%3Fv%3DFLUn7xCuQxo&amp;image=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fi.ytimg.com%2Fvi%2FFLUn7xCuQxo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e57ec6cbea8106186c572f6367cad82c/href">https://medium.com/media/e57ec6cbea8106186c572f6367cad82c/href</a></iframe><p>I’ve been in countless meetings where stakeholders have effectively made the same “mistake” as the Blue Peter presenters when they defined what the outcome should be. And I have seen an equal number of annoyed designers, questioning the point of them even being there if they’re just going to be told what to design and how to design it. (And, of course, they rarely say this to the stakeholders’ faces. Instead, they simply moan about it behind their backs.)</p><h3>Exploring The Context</h3><p>Designers understandably feel frustrated when asked to “design a lunchbox” because it immediately limits the potential outcome. This goes against what they’ve been taught design is all about and what design workflow models, such as the Double Diamond claim.</p><p>In an ideal world, designers would much prefer to spend time “bathing” in the problem space. This would include wanting to understand the variety of food items kids take to school with them and the level of protection they need. It would also involve following kids’ journeys over a couple of weeks to see how the products are used and talking to kids, to understand what they think is <em>cool</em>, and to their parents, to understand what’s <em>practical</em>. Of course, there’s a good chance that after all this, you might decide that a lunch box is <strong>exactly</strong> the sort of thing you should be designing! However, rather than this being only a hypothesis, you’ll now have confidence that you’re on the right path.</p><p>The architect Eliel Saarinen talks eloquently about the importance of designing a thing by considering it in its context:</p><blockquote><em>“Always design a thing by considering it in its next larger context — a chair in a room, a room in a house, a house in an environment, an environment in a city plan.”</em></blockquote><blockquote><em>— </em><a href="https://noisydecentgraphics.typepad.com/design/2009/09/always-design-a-thing-by-considering-it-in-its-next-larger-context-a-chair-in-a-room-a-room-in-a-hou.html"><em>Eliel Saarinen</em></a></blockquote><p>As such, it’s natural for designers to want to diverge, even if they end up converging on exactly the same thing. However, for our business partners, this sort of behavior can be very frustrating.</p><h3>What If You Actually Just Want A Lunch Box?</h3><p>While designers like to believe they’ve been hired to “think outside the lunch box” (sorry for the pun), the truth of the matter is that most business stakeholders don’t see design this way.</p><p>Instead, when most business stakeholders are tasked with creating a way for kids to take food to school, they immediately think of “lunchbox.” They will then ask their industrial designers and graphic designers to come up with something interesting that parents and children will buy; ideally, something which can be made cost-effectively using their existing factories, equipment, and supply chain. Oh, and they need it ready for when the kids go back to school in three months’ time, as that’s peak lunchbox-buying season.</p><blockquote><strong><em>Question:</em></strong><em> How many UX Designers does it take to screw in a lightbulb?<br></em><strong><em>Answer:</em></strong><em> First, we need to undertake a six months long project understanding the role of light in society!</em></blockquote><p>In this context, the organization has <em>already decided</em> that the lunchbox is a perfectly reasonable, logical, and obvious solution, so when the design team starts pushing back and asking for time to do <a href="https://webtorque.org/is-ux-research-about-de-risking-design/">additional research</a>, it sounds like a waste of time. Or worse, it might sound like the design team is actively trying to derail the project. As such, much as I hate to say this, sometimes you’ve just got to <em>grit your teeth and design the darn lunchbox</em>.</p><h3>How Design Actually Gets Done (Outside Apple And Airbnb)</h3><p>While the double diamond concept is a wonderful model, it’s also largely a fantasy. Instead, most organizations will have a few meetings which generally won’t involve design (sorry). If you’re lucky, they might look at some external survey data or market data and come to the conclusion that we, too, need a lunchbox.</p><p>Getting anything done inside even a relatively small organization takes effort, as anybody who has ever been tasked to organize a team lunch or a short company retreat will know. As such, it usually requires a senior stakeholder to galvanize support. Because of this, “customer discovery” is often more about finding evidence to back up the assertion that this is the <em>right thing</em> to build rather than potentially discovering that it’s the <em>wrong thing</em> to build.</p><p>By the time the idea gets to design, the decision has usually been made, resources have usually already been allocated, a launch date may have been set (often arbitrarily and without really understanding how long designing the thing will actually take), and there’s little or no interest in doing anything which might slow this decision train down or derail it altogether. I call this process the <strong>reverse double diamond</strong>.</p><p>While this way of working may seem crazy to designers, in most organizations, this is <em>exactly</em> how things work, and fighting against that process is truly an uphill battle. However, there is an opportunity here if you want to grab it, which lies in the second half of the “reverse double diamond” concept.</p><h3>The Reverse Double Diamond (Or Making It Work Better)</h3><p>Now, let me start with this: I’m not claiming that the reverse double diamond is ideal. Far from it. However, it is a realistic model for how work actually gets done.</p><p>I also believe there is a way for design teams to slowly — and I really do mean <em>slowly</em> — pivot away from this and towards the traditional double diamond. But you’re not going to get there by adding a couple of slides about it to the design deck your boss asks you to present at the next leadership away day. Instead, it’s all about what you do post-launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7lW9uLM0Pr3OBA-2aNNBAw.jpeg" /><figcaption>The “Reverse Double Diamond” concept which is based on how most companies actually operate.</figcaption></figure><p>If you take a close look at the model above, you’ll see that the first part of the reverse double diamond is essentially accepting the status quo, letting your boss tell you to deliver the metaphorical equivalent of a “lunchbox feature,” and creating the best version possible with the time and information available. However, <em>the trick</em> to making the reverse double diamond work is to actively monitor how this new feature performs and — wait for it — <strong>make suggestions about how it can be improved post-launch</strong>.</p><p>Once the lunchbox feature has been delivered and is out in the wild, the stakeholder who sponsored it no longer needs to be protective of it. The problem switches from being a delivery problem (“Can we actually get this thing launched?”) to being a <strong>value extraction problem</strong> (“How can we make this existing thing work better?”). This is the exact point in time where you put your business hat on, look at the stats, and say something like this, “This feature currently has relatively low utilization of only 5%. However, we believe that with some tweaks, we can get this up to 20%.”</p><p>In ye olde days, this used to be called “making a business case,” and it’s frankly much easier to make a business case for something that <strong>already exists</strong> and you believe can be made better than it is doing research on something that <strong>doesn’t yet</strong> exist and might be just fine as it is.</p><p>In essence, you’re still doing research work, and you’re still going to be exploring a <em>range of potential solutions</em> — you’re just doing this once the feature is already out in the market and you know exactly how it’s performing. Of course, this all depends on a number of things, including how well or poorly the feature performs, how good your design and product leaders are at making a business case, and how much work the design team has on. Unless you’re able to make a solid release plan, it’s likely that the second half of the reverse double diamond will actually be uncoupled from the first.</p><p>For companies that have featured teams and growth teams, it’s even possible that your feature teams will deliver the first half of the reverse double diamond before handing it over to the growth team to do the second half. As a result, this process is less than ideal. However, it’s much more pragmatic and goes fine “with the grain” of most organizations.</p><h3>Iterating Towards The Traditional Double Diamond</h3><p>Earlier, I hinted that this process might, over time, allow you to get to the “design nirvana” represented by the traditional double diamond. The logic here is that by constantly improving products post-launch, the organization learns to trust the design team’s ability and, more importantly, their vision.</p><p>As you garner more trust and evidence, over time, you can start making the case that it would be quicker and more cost-effective if you spent a few weeks upfront trying to avoid the mistakes, which can often take months or even years to address. Mistakes that will also often result in some lost revenue. In fact, this is effectively the same argument many designers make for adopting the traditional double diamond workflow in the first place — you’re just doing so by using evidence rather than belief and theory.</p><h3>Conclusion</h3><p>The Double Diamond concept is great, but it’s just not the way most organizations function. If, as a designer, you set your expectations around this theoretical model, you’re going to be continually disappointed! However, designers are meant to be great at understanding how things <em>actually work</em> rather than how we <em>think</em> they should work.</p><p>If we want to initiate change, we need to ask for more accurate models of how design actually works inside our organizations and <strong>target the areas where we have the most leverage</strong>. I believe this means adopting some variant of the “reverse double diamond” idea, accepting that we’re going to be told to deliver “lunch box features” 90% of the time, and <strong>shifting our attention away from pre-launch solutions to post-launch solutions</strong>.</p><p>We can design and then release a good first version of a product out into the world as quickly as possible and then use our business and communication skills to petition for and make measurable improvements to it. And if we can do this consistently, there’s a slim — but tangible! — chance that we can switch the “double diamond” back around.</p><h4>Further Reading</h4><ul><li>“<a href="https://www.smashingmagazine.com/2019/07/mvp-app-development/">Should You Create An MVP Before Creating An App?</a>,” by Suzanne Scacca <em>(Smashing Magazine)</em><br>Apps are neither small undertaking nor cheap to build and maintain. So, before you move ahead with creating a new mobile app or SaaS for your client, perhaps you should consider launching a minimum viable product (MVP) instead. With an MVP, you have a low-risk and lower-cost way of testing your concept on the market. What’s not to love about that?</li><li>“<a href="https://www.smashingmagazine.com/2015/12/getting-back-into-right-deliverables-business/">Getting Back Into The (Right) Deliverables Business</a>,” by Rian van der Merwe <em>(Smashing Magazine)</em><br>“Get out of the deliverables business” has become quite a mantra in the lean startup and UX movements. There’s much to love in that sentiment. After all, for every wireframe you make, you’re not shipping code to customers. But just like with the concept of a minimum viable product (MVP), it’s likely that we’ve taken this sound advice to an extreme which actually is hurtful to the creation of good products. What follows is the author’s account of navigating these stormy design seas together with the community.</li><li>“<a href="https://www.eleken.co/blog-posts/design-thinking-minimum-viable-product">Design Thinking &amp; Minimum Viable Product: Is This the Right Approach?</a>,” by Masha Panchenko <em>(Eleken Blog)</em><br>Design thinking has become a highly popular approach during the last forty years. It is used in IT, business, education, design — literally everywhere. There is even a book about applying design thinking for personal use called <em>Designing Your Life</em>. We don’t know if design thinking will help to change your life for the better, but what we know is that design thinking is a great approach when it comes to building a Minimum Viable Product.</li><li><a href="https://designingyour.life/the-book/"><em>Designing Your Life</em></a>, a book by Bill Burnett &amp; Dave Evans<br>A book that shows you how to build — to design — a life you can thrive in at any age or stage. Designers create worlds and solve problems using design thinking. Everything in our lives was designed by someone, and every design starts with a problem that a designer or team of designers seeks to solve. In this book, the authors show us how design thinking can help us create a life that is both meaningful and fulfilling, regardless of who or where we are, what we do or have done for a living, or how young or old we are.<br><em>(Editor’s Note: This book was, in fact, also recommended to me by </em><a href="https://www.smashingmagazine.com/author/joshua-mauldin/"><em>Joshua Mauldin</em></a><em> a while ago, and I cannot but highly recommend it to everyone! It’s a fantastic, very useful read. — M.B.)</em></li><li>“<a href="https://www.infoq.com/articles/problem-reframing-method/">Using the Problem Reframing Method</a>,” by Sebastian Straube <em>(product management &amp; discovery coach at Accenture Business Agility)</em><br>Avoid jumping directly into solution thinking and not empathizing with the problem itself; looking at a problem from different angles helps to build more innovative, sustainable solutions, and you need to try different reframing practices and methods as there is not a one-size-fits-all approach.</li><li>“<a href="https://webtorque.org/is-ux-research-about-de-risking-design/">Is UX Research About ‘De-risking’ Design?</a>,” by Jonathan Baker-Bates <em>(UX architect at LBi, VP of UX at TES Global)</em><br>Is UX research centered on helping designers predict eventual outcomes of design interventions, or is its role to “de-risk” UX and business ideas? Research is often framed as a way of lowering the risk to the business (this applies both to design validation as well as to exploratory research), but research should be checking whether what we said about a given intervention actually tends to happen.</li><li>“<a href="https://blog.logrocket.com/ux-design/modern-double-diamond-design/">Modern Double Diamond design: Rethinking a classic design process</a>,” by Victory Brown<br>To accomplish your tasks, you’ll need to set up a process that will allow you to complete them quickly and also give the best results. Sometimes the design process can be a jungle of trends and patterns; it involves a lot of back and forth to produce the best design solutions. No design is the final design, and every procedure can be iterated on. This is why the Design Council came together in 2005 to develop a new approach to designing solutions with creative thinking, systems design, and design management in mind: the Double Diamond design process.</li><li>“<a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/">History of the Double Diamond</a>”<br>This article describes the history behind the Double Diamond concept, created by the Design Council (established in 1944 by Winston Churchill’s wartime government). Over the course of several sessions, the group came up with a simplified way to describe any design and innovation process. It is based on four distinct phases that the design team, deliberately seeking a memorable device, named <strong>Discover</strong>, <strong>Define</strong>, <strong>Develop</strong>, and <strong>Deliver</strong>.</li></ul><h4>Appendix: “How Do We Describe The Design Process?”</h4><p>A short bit of history. In 2003, the <a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/">Design Council</a> promoted the positive impact of adopting a strategic approach to design and the value of “design management” as a practice. However, they had no standard way of describing the supporting process. Richard Eisermann, Design Council’s then Director of Design and Innovation, thought this was incompatible with their broader message, so he asked his team, “How do we describe the design process?”</p><blockquote><em>“The team put in the work trying to define design, process, methods, etc. What we did with the Double Diamond was codify it, rename the steps, and popularize it. It was important work, but we were certainly standing on the shoulders of giants.”</em></blockquote><blockquote><em>— Richard Eisermann</em></blockquote><p>Of course, kite-shaped (diamond-shaped) process models have been referenced as far back as the 1960s, but models of the design process were not widely shared at this point. Part of the Design Council’s reason for creating the Double Diamond concept was to address this lack of visibility. Today the Double Diamond is considered a universally accessible description of the design process, has become an accepted part of design language, and is used and referenced worldwide.</p><p>→ <a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/">History of the Double Diamond</a>, <a href="https://www.designcouncil.org.uk/who-we-are/our-history/">The Design Council</a></p><p><strong>Editor’s Note:</strong> <a href="https://www.smashingmagazine.com/2023/08/improving-double-diamond-design-process/"><em>This article was originally published on Smashing Magazine</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28b782e03f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Better Design Handoff File In Figma]]></title>
            <link>https://medium.com/@smashingmag/designing-a-better-design-handoff-file-in-figma-e86b44d9068d?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/e86b44d9068d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Thu, 07 Sep 2023 20:53:32 GMT</pubDate>
            <atom:updated>2023-09-07T20:54:48.720Z</atom:updated>
            <content:encoded><![CDATA[<h4>Let’s explore <em>how</em> to create a design handoff document that attempts to strike the right balance between providing developers with the information they need while still allowing them the flexibility to bring the design to life in their own way.</h4><p>// written by <a href="https://www.smashingmagazine.com/author/ben-shih/">Ben Shish</a></p><p>Creating an effective handoff process from design to development is a critical step in any product development cycle. However, as any designer knows, it can be a nerve-wracking experience to send your carefully crafted design off to the dev team. It’s like waiting for a cake to bake — you can’t help but wonder how it will evolve in the oven and how it will taste when you take it out of the oven.</p><p>The relationship between designers and developers has always been a little rocky. Despite tools like Figma’s <a href="https://help.figma.com/hc/en-us/articles/360055203533-Use-the-Inspect-panel">Inspect feature</a> (which allows developers to inspect designs and potentially convert them to code in a more streamlined way), there are still many barriers between the two roles. Often, design details are hidden within even more detailed parts, making it difficult for developers to accurately interpret the designer’s intentions.</p><p>For instance, when designing an image, a designer might import an image, adjust its style, and call it done. More sophisticated designers might also wrap the image in a frame or <a href="https://help.figma.com/hc/en-us/articles/5731482952599-Using-auto-layout">auto layout</a> so it better matches how developers will later convert it to code. But even then, many details could still be missing.</p><p>The main problem here is that <strong>designers typically create their designs within a finite workspace</strong> (a frame with a specific width). In reality, however, the design elements will need to adapt to a variety of different environments, such as varying device sizes, window widths, screen resolutions, and other factors that can influence how the design is displayed. Therefore, developers will always come back with the following questions:</p><ul><li>What should be the minimum/maximum width/height of the image?</li><li>What is its content style?</li><li>What effects need to be added?</li></ul><p>In reality, these are the details that need to be addressed.</p><blockquote>Every developer works, thinks, and writes code differently, which means there is no such thing as the ideal handoff document. Instead, our focus should be on creating a non-perfect but still effective and usable handoff process.</blockquote><p>Designers, let’s face the truth: There’s <em>no perfect handoff</em>.</p><p>So, how can the handoff files be improved?</p><h3>1. Talk To Developers More Often</h3><p>Design is often marked as complete once the design handoff file is created and the developers start transforming it into code. However, in reality, the design is only complete when the user finds the experience pleasant.</p><p>Therefore, crafting the design handoff file and having the developer help bring your design to the user is essentially another case study on top of the one you have already worked on. To make it perfect, just as you would talk to users, you also need to communicate with engineers — to better understand their needs, how they read your file, and perhaps even teach them a few key things about using Figma (if Figma is your primary design tool).</p><p>Here are a few tips you can teach your developers to make their lives easier when working with Figma:</p><h4>SHOW DEVELOPERS THE SUPERPOWER OF THE INSPECT PANEL</h4><p>Figma’s Inspect feature allows developers to see the precise design style that you’ve used, which can greatly simplify the development process. Additionally, if you have a design library in place, Inspect will display the name of each component and style that you’ve used. This can be incredibly helpful for developers, especially if they’re working with a style guide, as they can use the component or style directly to match your design with ease.</p><p>In addition to encouraging developers to take advantage of the Inspect panel, it’s sometimes helpful to <strong>review your own design in a read-only view</strong>. This allows you to see precisely what the developers will see in the Inspect panel and ensures that components are named accurately, colors are properly linked to the design system, and other vital details are structured correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wa78X4VfGjc0g0G1t6v6Ow.png" /><figcaption><em>Figma’s Inspect panel allows you to view properties and values for any selected object/layer. (Image source: “</em><a href="https://help.figma.com/hc/en-us/articles/360055203533-Use-the-Inspect-panel"><em>Use the Inspect panel</em></a><em>” help page)</em></figcaption></figure><h4>SHARE WITH DEVELOPERS THE WAY TO EXPORT IMAGES/ICONS</h4><p>Handling image assets, including icons, illustrations, and images, is also an essential part of the handoff process, as the wrong format might result in a poor presentation in the production environment.</p><p>Be sure to align with your developers on how they would like you to handle the icons and images. It could either be the case where they would prefer you to export all images and icons in a single ZIP file and share it with them or the case where they would prefer to export the images and icons on their own. If it’s the latter, it’s important to explain in detail the correct way to export the images and icons so that they can handle the export process on their own!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0DgwAzjfzIIwydB0LPAvhw.png" /><figcaption><em>Figma’s export feature allows designers and developers to export content into different formats.</em></figcaption></figure><h4>ENCOURAGE THEM TO USE FIGMA’S COMMENTING FEATURE</h4><p>It’s common for developers to have questions about the design during the handoff process. To make it easier for everyone involved, consider teaching them to leave comments directly in Figma instead of sending you a message. This way, the comments are visible to everyone and provide context for the issue at hand. Additional features, such as comment reactions and the “mark as resolved” button, further enable better interaction between team members and help everyone keep track of whether an issue has been addressed or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5pANnFbj52fAykL9v5iWA.png" /><figcaption><em>Figma’s </em><a href="https://help.figma.com/hc/en-us/articles/360041068574-Add-comments-to-files"><em>comment feature</em></a><em>.</em></figcaption></figure><h4>LEVERAGE CURSOR CHAT</h4><p>If you and the developers are both working within the same Figma file, you can also make use of the <a href="https://help.figma.com/hc/en-us/articles/1500004414842-Send-messages-with-cursor-chat">cursor chat feature</a> to clarify any questions or issues that arise. This can be a fun and useful way to collaborate and ensure that everyone is on the same page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZI1d4Y-ktl3gG083UNyKFw.png" /><figcaption><em>Figma’s </em><a href="https://help.figma.com/hc/en-us/articles/1500004414842-Send-messages-with-cursor-chat"><em>cursor-chat feature</em></a><em>.</em></figcaption></figure><h4>USE FIGMA AUDIO CHAT</h4><p>If you need to discuss a complex issue in more detail, consider using Figma’s audio chat feature. This can be a quick and efficient way to clarify any questions or concerns arising during the development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSZlbH0ypo5N9_8auw1IJA.jpeg" /><figcaption><em>Figma’s audio chat feature. (Image source: “</em><a href="https://help.figma.com/hc/en-us/articles/1500004414622-Use-audio-to-chat-with-your-team"><em>Use audio to chat with your team</em></a><em>” help page)</em></figcaption></figure><p>It’s important to keep in mind that <strong>effective collaboration relies on good communication</strong>. Therefore, it’s crucial to talk to your developers regularly and understand their approach to reading and interpreting your designs, especially when you first start working with them. This sets the foundation for a productive and successful partnership.</p><h3>2. Documenting Design Decisions For You And Developers</h3><p>We have to be honest, the reason why building our design portfolios often takes <em>a</em> <em>lot</em> of time is the fact that we do not document every design decision along the way, and so we need to start building the case studies later by trying our best to fetch the design files and all the stuff we need.</p><p>I find it useful to document my decisions in Figma, not only just designs but, if appropriate, also competitor analysis, problem statements, and user journeys, and leave the links to these pages within the handoff file as well. The developer might not read it, but I often hear from the developers in my team that they like it as they can also dig into what the designers think while working on the design, and they can learn tips for building a product from us as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAjaOlL-W0WgMK8gq8ZhCQ.jpeg" /><figcaption><em>An example of how I am structuring a Figma design file.</em></figcaption></figure><h3>3. Don’t Just Leave The Design There. Add The Details.</h3><p>When it comes to design, <em>details matter</em> — just leaving the design “as is” won’t cut it. Adding details not only helps developers better understand the design, but it can also make their lives easier. Here are some tips for adding those crucial design details to your handoff.</p><h4>NUMBER THE FRAME/FLOW IF POSSIBLE</h4><p>I really like the Figma <a href="https://www.figma.com/community/file/1004041613962064465"><strong>handoff template</strong></a> that Luis Ouriach (<a href="https://medium.com/@disco*lu">Medium</a>, <a href="https://twitter.com/disco*lu">Twitter</a>) created. The numbering and title pattern make it easy for developers to understand which screen belongs to which flow immediately. However, it can be complicated to update the design later as the numbering and title need to be <em>manually</em> updated.</p><p><strong>Note:</strong> <em>While there are plugins available (like, for example, </em><a href="https://www.figma.com/community/plugin/1057630145566901048"><em>Renamed</em></a><em>), which can help with renaming multiple frames and layers all at once, this workflow can still be inconvenient when dealing with more complicated naming patterns. For instance, updating “1. Welcome → 2. Onboarding → 3. Homepage” into “1. Welcome → 2. Onboarding → 3. Sign up → 4. Homepage” can become quite a hassle. Therefore, one alternative approach is to break down the screens into different tickets or user journeys and assign a number that matches each ticket/user journey.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVEWNugPdJJGB6AygrCHgQ.png" /><figcaption><em>An example of a numbering system based on </em><a href="https://twitter.com/disco_lu"><em>Luis</em></a><em>’s </em><a href="https://www.figma.com/community/file/1004041613962064465"><em>Figma design template</em></a><em>.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6tbRYX2JCIXGb-HdBslBGA.png" /><figcaption><em>An example of an alternative approach of structuring the screens.</em></figcaption></figure><h4>NAME THE LAYERS IF POSSIBLE</h4><p>We talked about numbering/naming the frames, but naming the layers is equally important! Imagine trying to navigate a Figma file cluttered with layers and labels like “Frame 3123,” “Rectangle 8,” and “Circle 35.” This can be confusing and time-consuming for both designers and developers, as they need to sift through numerous unnamed layers to identify the correct one.</p><p><strong>Well-named layers facilitate better collaboration</strong>, as team members can quickly locate and comprehend the purpose of each element. This also helps ensure consistency and accuracy when translating designs into code.</p><p>If you search around in Figma, you will find a number of plugins that can help you with naming the layers in a more systematic way.</p><h4>ADD THE DETAILS FOR INTERACTION: MAKE USE OF FIGMA’S SECTION FEATURE</h4><p>This might seem trivial, but I consider it important. Design details shouldn’t be something like “This design does X, and if you press that, it will do Y.” Instead, it’s crucial to include details like the hover state, initial state, max width/height, and the outcome of different use cases.</p><p>For this reason, I appreciate the new section feature that Figma has released. It allows me to have a big design at the top so that developers can see all of the design at once and then look at the section details for all the design and interaction details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eDRelK3Xsr50A3J5A0aAA.jpeg" /><figcaption><em>I like to use </em><a href="https://help.figma.com/hc/en-us/articles/9771500257687-Organize-your-canvas-with-sections"><em>Sections</em></a><em> to describe the details of the design. With this approach, I can create direct links to specific sections and guide the developer to review them with more ease.</em></figcaption></figure><h4>MAKE USE OF THE INTERACTIVE PROTOTYPE AND FIGJAM FEATURES TO SHOW THE USER FLOW</h4><p>Additionally, try to share with the developers how the design screens connect to one another. You can use the interactive prototype feature within Figma to connect the screens and make them move so that developers can understand the logic. Alternatively, you can use FigJam to connect the screens, allowing developers to see how everything is connected at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRKOqnKjSix1O3x_1rj7UQ.jpeg" /><figcaption><em>FigJam allows designers to connect screens and present them easily.</em></figcaption></figure><h3>4. The Secret Weapon Is Adding Loom Video</h3><p>Loom video is a lifesaver for us. You only need to record it once, and then you can share it with anyone interested in the details of your design. Therefore, I highly recommend making use of Loom! For every design handoff file, I always record a video to walk through the design. For more complicated designs, I will record a separate video specifically describing the details so that I don’t need to waste other people’s time if they’re not interested.</p><p>To attach the Loom video, I use the <em>Loom</em> plugin and place it right beside the handoff file. Developers can play it as many times as needed without even disturbing you, asking you more questions, and so on.</p><p>→ Download the <a href="https://www.figma.com/community/plugin/1050134017138821899/Loom-Embed"><strong>Loom Embed</strong></a> Figma plugin</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ZV-Mfem3oJxlvRmv5HQ9A.jpeg" /><figcaption><em>An example of how I attach my Loom video.</em></figcaption></figure><h3>5. The Biggest Fear: Version Control</h3><p>In an ideal world, the design would be completely finalized before developers start coding. But in reality, design is always subject to adjustments, even after development has already begun. That’s why <a href="https://www.atlassian.com/git/tutorials/what-is-version-control#:~:text=Version%20control%2C%20also%20known%20as,to%20source%20code%20over%20time.">version control</a> is such an important topic.</p><p>Although Figma has a branching feature for enterprise customers to create new designs in a separate branch, I find it helpful to keep a few extra things in your design file.</p><h4>HAVE A SINGLE SOURCE OF TRUTH</h4><p>Always ensure that the developer handoff file you share with your team is the single source of truth for the latest design. If you make any changes, update the file directly and keep the original as a duplicate for reference. This will prevent confusion and avoid pointing developers to different pages in Figma.</p><p>If you have access to the <strong>branching feature</strong> in Figma, it can be highly beneficial to utilize it to further streamline your workflow. When I need to update a handoff file that I have already shared with the developers, my typical process is to create a new branch in Figma first. Then I update the developer handoff file in that branch, send it to the relevant stakeholders for review, and finally merge it back into the original developer handoff file once everything is confirmed. This ensures that the link to the developer handoff file remains <em>unchanged</em> for the developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNEn-OJ8rQaKEOdCv6ZavQ.png" /><figcaption><em>An example of how my Branches look like in Figma.</em></figcaption></figure><h3>CHANGELOGS/FUTURE PLAN <a href="https://www.smashingmagazine.com/2023/05/designing-better-design-handoff-file-figma/#changelogs-future-plan">#</a></h3><p>Include a <a href="https://en.wikipedia.org/wiki/Changelog">changelog</a> in the handoff file to help developers understand the latest changes made to the design.</p><p>Similarly to changelogs, if you already know of future plans to adjust the design, write them down somewhere in Figma so that the developers can understand what changes are to be expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMi8BWC_ANXWH13OXFZMyw.jpeg" /><figcaption><em>An example of how my changelog looks like.</em></figcaption></figure><h3>6. Make Use Of Plugins</h3><p>There are also a number of plugins to help you with creating your handoff:</p><ul><li><strong>EightShapes Specs</strong><br><em>EightShapes Specs</em> creates specs for your design automatically with just one click.<br>→ Download the <a href="https://www.figma.com/community/plugin/1205622541257680763/EightShapes-Specs"><strong>EightShapes Spec</strong></a> Figma plugin</li><li><strong>Autoflow</strong><br><em>Autoflow</em> allows you to connect the screens visually without using FigJam.<br>→ Download the <a href="https://www.figma.com/community/plugin/733902567457592893"><strong>Autoflow</strong></a> Figma plugin</li><li><strong>Style Organizer</strong><br><em>Style Organizer</em> allows you to make sure all of your styles are linked to your component/style so that developers won’t need to read hex code in any case.<br>→ Download the <a href="https://www.figma.com/community/plugin/816627069580757929"><strong>Style Organizer</strong></a> Figma plugin</li></ul><h3>7. The Ultimate Goal Is To Have A Design System</h3><p>If you want to take things a step or two further, consider pushing your team to adopt a <a href="https://www.invisionapp.com/inside-design/guide-to-design-systems/"><strong>design system</strong></a>. This will enable the designs created in Figma to be more closely aligned with what developers expect in the code. You can match token names and name your layers/frames to align with how developers name their containers and match them in your design system.</p><p>Here are some of the benefits of using a design system:</p><ul><li><strong>Consistency</strong><br>A design system ensures a <em>unified visual language</em> across different platforms, resulting in a more consistent user experience.</li><li><strong>Efficiency</strong><br>With a design system in place, designers and developers can <em>reuse components and patterns</em>, reducing the time spent on creating and updating individual elements.</li><li><strong>Collaboration</strong><br>A design system facilitates better communication between designers and developers by establishing a <em>shared language</em> and understanding of components and their usage.</li></ul><p><strong>Note:</strong> <em>If you would like to dig deeper into the topic of design systems, I recommend reading some of the </em><a href="https://www.smashingmagazine.com/category/design-systems/"><em>Smashing Magazine articles on this topic</em></a><em>.</em></p><h3>Conclusion: Keep Improving The Non-Perfect</h3><p>Ultimately, as I mentioned at the beginning, there’s no <em>one-size-fits-all approach</em> to developer handoff, as it depends on various factors such as product design and the engineers we work with. However, what we can do is work closely with our engineers, communicate with them regularly, and collaborate to find solutions that make everyone’s lives easier. Just like our designs, the key to successful developer handoff is prioritizing good communication and collaboration.</p><h4>FURTHER READING</h4><ul><li>“<a href="https://www.interaction-design.org/literature/topics/design-handoffs">Design Handoffs</a>,” Interactive Design Foundation</li><li>“<a href="https://phase.com/magazine/designer-and-developer-handoff-guide/">A Comprehensive Guide to Executing The Perfect Design-to-Development Handoff</a>,” Phase Mag</li><li>“<a href="https://blog.zeplin.io/design-handoff-101-how-to-handoff-designs-to-developers">Design Handoff 101: How to handoff designs to developers</a>,” Zeplin Blog</li><li>“<a href="https://twitter.com/101babich/status/1635584302200274944">How to communicate design to developers (checklist)</a>,” <a href="https://twitter.com/@101babich">Nick Babich</a></li><li>“<a href="https://www.smashingmagazine.com/2014/10/front-end-development-ode-to-specifications/">A Front-End Developer’s Ode To Specifications</a>,” Dmitriy Fabrikant, Smashing Magazine</li><li>“<a href="https://www.smashingmagazine.com/2020/09/figma-developers-guide/">Everything Developers Need To Know About Figma</a>,” Jurn van Wissen, Smashing Magazine</li><li>“<a href="https://www.smashingmagazine.com/2023/02/meet-penpot-open-source-design-platform-designers-developers/">Penpot, An Open-Source Design Platform Made For Designers And Developers Alike</a>,” Mikołaj Dobrucki, Smashing Magazine</li><li>“<a href="https://www.smashingmagazine.com/2023/03/best-handoff-is-no-handoff/">The Best Handoff Is No Handoff</a>,” Vitaly Friedman, Smashing Magazine</li></ul><blockquote>Editor’s Note: <a href="https://www.smashingmagazine.com/2023/05/designing-better-design-handoff-file-figma/">This article was originally published on Smashing Magazine</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e86b44d9068d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Better Error Messages UX]]></title>
            <link>https://medium.com/@smashingmag/designing-better-error-messages-ux-f89ed25cb795?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/f89ed25cb795</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[error]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[forms]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Thu, 07 Sep 2023 16:02:28 GMT</pubDate>
            <atom:updated>2023-09-07T16:06:15.874Z</atom:updated>
            <content:encoded><![CDATA[<h4>When we design interfaces, we rarely think about <strong>error messages</strong> first. But error messages can make or break the experience in situations when things go south. Let’s fix that. By Vitaly Friedman.</h4><p><strong>Errors are everywhere</strong>, and so are error messages. They are of course common in web forms, but also in complex tables, contradictory filters and failed interactions. They can be small error notes and large error summaries; short <strong>tooltips</strong> and lengthy toast messages. So how do we choose the right ones? Let’s start from the basics.</p><p><em>This is an upcoming chapter of </em><a href="https://smart-interface-design-patterns.com/"><em>Smart Interface Design Patterns</em></a><em> 🍣 , a growing library for UX designers and interface designers (</em><a href="https://smart-interface-design-patterns.com/"><em>use the code MEDIUM for friendly 15% off</em></a><em>).</em></p><h3>1. Never Rely On Color Alone</h3><p>With error messages, we almost subconsciously think of <strong>bold red text</strong>. That’s indeed common, but often not enough to indicate to users that something is wrong.</p><figure><a href="https://design-system.service.gov.uk/components/error-message/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4Cdkr0kHPPpcyvZ-.jpg" /></a><figcaption>The <a href="https://design-system.service.gov.uk/components/error-message/"><strong>Error message component</strong></a> on Gov.uk can’t be improved much: the message is clear, fair and with an icon pointing attention to the message.</figcaption></figure><p>Due to color vision deficiencies, it’s a good idea to <strong>always complement error messages with an icon</strong>, e.g. white exclamation mark on a red background — next to the error messages, or within the input field.</p><figure><a href="https://carbondesignsystem.com/components/notification/usage/#inline-notifications"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wkrGGWMHObgv63Q7.png" /></a><figcaption>Error messages in the <a href="https://carbondesignsystem.com/components/notification/usage/#inline-notifications"><strong>Carbon Design System</strong></a> by IBM. Error messages appear above the buttons on tap/click.</figcaption></figure><p>As you can see in the first example, we can <strong>highlight the entire section</strong>, along with the field, label, the hint, the error message and the input field — e.g. with a thick vertical line next to it. We might also display an <a href="https://design-system.service.gov.uk/components/error-summary/"><strong>error summary</strong></a> on the top of the page, with the links to the problematic areas in the form.</p><h3>2. Never Cover User’s Input</h3><p>When we display error messages, we convey to users that there is a problem, but also try to guide users to a solution. This, however, requires the ability to <strong>consult the error as the error is being fixed</strong>. In other words, users would be able to edit the input field while also reviewing the error message(s) provided to them.</p><figure><a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*qVQ4Mz2kQwe5hddH.jpg" /></a><figcaption>When inline validation meets error recovery. A common example when the message covers the content. Via <a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><strong>UX Design World</strong></a>.</figcaption></figure><p>So far so good. However, things become quite complicated once we also have a tooltip in play. When a tooltip is open, users might lose sight of both the error message and the input. Should they desire to be able to see <strong>all 3 pieces of information at once</strong>, they’d be out of luck.</p><figure><a href="https://carbondesignsystem.com/components/toggletip/usage/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SByFsJ90dRiMVYBg.png" /></a><figcaption>When a tooltip blocks the content, an example from the <a href="https://carbondesignsystem.com/components/toggletip/usage/"><strong>Carbon Design System</strong></a>.</figcaption></figure><p>We can fix it relatively easily. First of all, we avoid tooltips that open on hover, and display the tooltip text <strong>only once tapped or clicked</strong>. That means that a tooltip text will never disappear automatically, and will have to be closed manually.</p><p>Then, we use the <a href="https://design-system.service.gov.uk/components/details/"><strong>details component</strong></a> and <strong>inline accordions</strong> as an alternative to tooltips. Hence, we <strong>make space</strong> for the content of the tooltip to expand between the label and the other content, so nothing will be covered. The error message would appear at all times as well, next to the input field.</p><figure><a href="https://design-system.service.gov.uk/components/details/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YJZukRA0rE7dBL2m.png" /></a><figcaption>The <a href="https://design-system.service.gov.uk/components/details/"><strong>details component</strong></a>, with the details appearing on tap/click.</figcaption></figure><p>This way, we show all 3 pieces of information at the same time — and <strong>users always have a choice</strong> to select what exactly they’d like to see. Is it too much? Maybe. But that’s a great option to keep in mind: at least to always display the input field and the error at the same time without them being overlapped by the tooltip.</p><h3>3. In Forms, Display Error Messages Above Input</h3><p>Now this might sound a little bit confusing at first. Usually error messages are sitting conveniently under the input field, or perhaps — less frequently — on the right side of it. As it turns out, there are a few <strong>accessibility issues</strong> that come as a cost of these conventions.</p><ul><li><strong>Users of a magnifying software</strong> might miss the error message when it’s located on the right,</li><li><strong>On mobile</strong>, users might not be able to see the error message under the input because it will be <a href="https://adrianroselli.com/2017/01/avoid-messages-under-fields.html"><strong>covered by the virtual keyboard</strong></a>,</li><li><strong>When editing input</strong>, error messages might be covered by browser’s autofill or input’s autocomplete suggestions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tFrB9uzNiHX2ol1N.png" /></figure><p>Displaying error messages <strong>above input fields</strong> typically helps us avoid accessibility issues listed above. The cost of it, though, are <strong>layout shifts</strong>: with every new error appearing dynamically, the entire form has to shift vertically as we need to make space for the error message to appear. But sometimes it might be very much worth it.</p><h3>4. In Tables, Display Error Messages Inline</h3><p>When displaying error messages in tables, it might be a good idea to consider alternative approaches as otherwise we would end up with a lot of <strong>layout shifts</strong> for each row.</p><p>One of the simpler patterns is to <strong>display the error message in the same row where the content lives</strong>. In that case, the error message is more likely to live under the input field, not above it. Lengthy error messages could be collapsed and expanded with an accordion.</p><figure><a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gNEdV2lFiR5c-7W3.png" /></a><figcaption>Error messages could live in the same row where the erroneous content lives. Image source: <a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><strong>UX Design World</strong></a>.</figcaption></figure><p>If the same error <strong>affects multiple rows</strong>, we might want to <strong>highlight the rows</strong> that contain errors and display an error message at the very top of the page that would explain the error and what needs to be done to fix it.</p><figure><a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0J_J87vred7Qk5zf.png" /></a><figcaption>If an error appears multiple times, and its simple to explain, it might be a good idea to show it on the very top of the page. Image source: <a href="https://uxdworld.com/2020/04/22/inline-editing-and-validation-in-tables/"><strong>UX Design World</strong></a>.</figcaption></figure><h3>5. Don’t Rely on Toast Error Messages</h3><p>But what about good ol’ <strong>toast error messages</strong>? Those animated <strong>notifications</strong>, informing users about change of status of the system with floating messages. They might be uncommon for forms, but they frequently appear in tables and enterprise dashboards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*2IZj-MWqN5nm2i7n.png" /></figure><p>There are a few common <strong>usability issues</strong> with toast error messages:</p><ul><li>Users often don’t get a chance to <strong>fully read or understand the error message</strong> before it has disappeared, and there is no way to restore it or keep it floating.</li><li>Toast messages typically <strong>appear on the edges of the screen</strong>, and usually it’s quite <a href="https://www.nngroup.com/articles/errors-forms-design-guidelines/"><strong>far away from the erroneous input</strong></a>. There is a disconnect between the error message and the input, and it’s rarely possible to read the error message and correct the mistake at the same time.</li><li>Lengthy toast messages usually <strong>block large areas of content</strong> that a user might be relying on — and potentially even the input that has caused the error.</li><li>Toast messages <strong>need to be announced to screen reader users</strong> while also allowing them to bring the focus back and forth between the error message and the erroneous input.</li><li>With toasts, we usually don’t have enough space to provide a detailed help using <strong>images or videos</strong>, and have to rely on plain text and links to external help pages.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ba8CiAAKmXXNuaJc.png" /><figcaption>This might not be ideal: error messages appearing as toasts in a complex UI.</figcaption></figure><p>If anything, toasts should be <a href="https://www.benrajalu.net/articles/ux-of-notification-toasts"><strong>persistent if displaying information that can be acted upon</strong></a>, and users should be able to manually dismiss the notification.</p><p>Personally, I’d definitely <strong>stay away from error messages as toasts</strong>, even if they are persistent. The more we can connect an error with its cause, the less likely it is to be overlooked. And the better we can explain how to solve the error next to its cause, the faster users will understand what they need to do.</p><h3>6. Allow Users to Override Error Messages</h3><p>No single validation library will be extremely reliable and bulletproof for all the edge cases, so eventually some percentage of your customers will be left out there in the woods, trying to figure out what to do next to proceed. That’s quite suboptimal.</p><p><strong>Aggressive validators cost money</strong>. Especially when they come in tandem with disabled buttons that literally block users without telling them what exactly needs to be done to fix the issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3_mu2EVrHz09cdl3.png" /><figcaption>Overriding address validator might be a very good idea.</figcaption></figure><p>For cases when a validator might be too restrictive, we can allow customers to <em>override validator’s warning</em>. We will get some wrong addresses as a result of that. But as a business, we need to measure just how much money we are losing due to increase in service desk inquiries vs. how much money we gain by allowing people to find a way to proceed even although the interface doesn’t want to play along. More often than not, it’s worth it.</p><p>While this pattern works flawlessly for address input and telephone input, it probably won’t work for any input that needs to follow a particular convention — such as the length and checksum of an IBAN number or a credit card number. There, instead of giving customers a carte blanche, we need to <em>meticulously review the input</em> and guide them towards what exactly the problem seems to be. And help them resolve it.</p><h3>Wrapping Up</h3><p>At the first glance, dealing with error messages might not sound like a big deal. However, as we dive into fine details, there are <strong>plenty of considerations</strong> that might either cause high abandonment or help people resolve issues quickly.</p><p>With these guidelines, we should be better off when boosting our error messages UX. And if you can’t really do much around the way errors appear in your product, explore what you can do to <strong>replace generic error messages with helpful ones</strong>. This might be a small change with a huge impact that will eventually show up in large business KPIs dashboards.</p><h3>Coming Up: Interface Design Live UX Training</h3><figure><a href="https://smart-interface-design-patterns.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eo5aipilAy_3P7hz" /></a><figcaption><a href="https://smart-interface-design-patterns.com/">Smart Interface Design Patterns</a>, a friendly video course on UX and design patterns.</figcaption></figure><p>This section is an upcoming part of <a href="https://smart-interface-design-patterns.com/">Smart Interface Design Patterns</a>, a friendly video course 🍣 with live sessions, real UX challenges, personal 1:1 feedback and UX certification.</p><p>Thank you so much for your support, everyone — and happy designing! 🎉🥳</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f89ed25cb795" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Gorgeous Free And Open-Source Typefaces And When To Use Them]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@smashingmag/7-gorgeous-free-and-open-source-typefaces-and-when-to-use-them-2c0fd23eb4f8?source=rss-5ef3beaef7aa------2"><img src="https://cdn-images-1.medium.com/max/1000/0*3z_Rs9GbUlcLqOim.png" width="1000"></a></p><p class="medium-feed-snippet">By Noemi Stauffer</p><p class="medium-feed-link"><a href="https://medium.com/@smashingmag/7-gorgeous-free-and-open-source-typefaces-and-when-to-use-them-2c0fd23eb4f8?source=rss-5ef3beaef7aa------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@smashingmag/7-gorgeous-free-and-open-source-typefaces-and-when-to-use-them-2c0fd23eb4f8?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c0fd23eb4f8</guid>
            <category><![CDATA[typeface-combinations]]></category>
            <category><![CDATA[typeface-design]]></category>
            <category><![CDATA[fonts]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[typeface]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 19:36:20 GMT</pubDate>
            <atom:updated>2019-08-09T22:40:46.370Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Common Concerns And Privacy In Web Forms (Part 1)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@smashingmag/common-concerns-and-privacy-in-web-forms-part-1-3e68f4d4727a?source=rss-5ef3beaef7aa------2"><img src="https://cdn-images-1.medium.com/max/1902/1*hOddrw-JefM7OpKUXE0ZNQ.png" width="1902"></a></p><p class="medium-feed-snippet">by Vitaly Friedman</p><p class="medium-feed-link"><a href="https://medium.com/@smashingmag/common-concerns-and-privacy-in-web-forms-part-1-3e68f4d4727a?source=rss-5ef3beaef7aa------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@smashingmag/common-concerns-and-privacy-in-web-forms-part-1-3e68f4d4727a?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e68f4d4727a</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[privacy-protection]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[privacy-by-design]]></category>
            <category><![CDATA[privacy-policy]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Wed, 22 May 2019 08:36:05 GMT</pubDate>
            <atom:updated>2019-05-23T13:27:46.371Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Getting Started With CSS Layout]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@smashingmag/getting-started-with-css-layout-58dc92809293?source=rss-5ef3beaef7aa------2"><img src="https://cdn-images-1.medium.com/max/2600/1*pZWMN0lPVfh3XmddXwPWoQ.jpeg" width="6016"></a></p><p class="medium-feed-snippet">Whether you&#x2019;re fairly new to CSS or an experienced developer from elsewhere in the stack who wants to make sure your understanding of&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@smashingmag/getting-started-with-css-layout-58dc92809293?source=rss-5ef3beaef7aa------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@smashingmag/getting-started-with-css-layout-58dc92809293?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/58dc92809293</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 17:00:00 GMT</pubDate>
            <atom:updated>2020-01-27T18:31:32.405Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[More Than Pixels: Selling Design Discovery]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@smashingmag/more-than-pixels-selling-design-discovery-e4695f0f7e7b?source=rss-5ef3beaef7aa------2"><img src="https://cdn-images-1.medium.com/max/2600/1*1-vRJqwOWcQq7gQIeoMmyg.jpeg" width="5184"></a></p><p class="medium-feed-snippet">Have you ever faced challenges when trying to sell Design Discovery to a potential client? In this article, Kyle Cassidy takes a deep dive&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@smashingmag/more-than-pixels-selling-design-discovery-e4695f0f7e7b?source=rss-5ef3beaef7aa------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@smashingmag/more-than-pixels-selling-design-discovery-e4695f0f7e7b?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4695f0f7e7b</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 17:30:00 GMT</pubDate>
            <atom:updated>2020-01-27T18:19:30.471Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Building Diverse Design Teams To Drive Innovation]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@smashingmag/building-diverse-design-teams-to-drive-innovation-3a28cc0e9bf0?source=rss-5ef3beaef7aa------2"><img src="https://cdn-images-1.medium.com/max/2600/1*U4d1eLxkpfJBCYxOv-3i-Q.jpeg" width="3600"></a></p><p class="medium-feed-snippet">This article is for people who are part of a design team (or any team) that makes crucial business decisions with stakeholders and how&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@smashingmag/building-diverse-design-teams-to-drive-innovation-3a28cc0e9bf0?source=rss-5ef3beaef7aa------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@smashingmag/building-diverse-design-teams-to-drive-innovation-3a28cc0e9bf0?source=rss-5ef3beaef7aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a28cc0e9bf0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[Smashing Magazine]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 17:00:00 GMT</pubDate>
            <atom:updated>2020-01-27T18:33:52.526Z</atom:updated>
        </item>
    </channel>
</rss>