<?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 Lisa Kas on Medium]]></title>
        <description><![CDATA[Stories by Lisa Kas on Medium]]></description>
        <link>https://medium.com/@lisakas?source=rss-7bd5933803c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gAT8yjFx7IYG_xncsblsqQ.png</url>
            <title>Stories by Lisa Kas on Medium</title>
            <link>https://medium.com/@lisakas?source=rss-7bd5933803c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:58:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lisakas/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[UX Writing principles]]></title>
            <link>https://uxplanet.org/ux-writing-principles-37bd0f47ab1b?source=rss-7bd5933803c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/37bd0f47ab1b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Lisa Kas]]></dc:creator>
            <pubDate>Wed, 08 Feb 2023 18:03:49 GMT</pubDate>
            <atom:updated>2023-02-08T18:03:49.969Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>UX Writing Principles</strong></h3><h4>How to write content for your users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EQq5HWHuMJWUTkAED5WaGQ.jpeg" /><figcaption><a href="https://www.behance.net/leonohchida">Illustration by Eleonore Millet</a></figcaption></figure><h3><strong>What is UX writing?</strong></h3><p>UX writing is the craft of writing content in a way that is easy to read, functional, and which also encourages interaction.</p><blockquote>“ Design in the absence of content is not designed, it’s decoration.” Jeffrey Zeldman</blockquote><p>Here are some pieces of advice to better write to your users.</p><h3>Make your content user-centered</h3><h4><strong>1. Use active voice</strong></h4><p>In <strong>active voice</strong>: the subject of the sentence<strong> does the action</strong>.<br>In <strong>passive voice</strong>: the subject of the sentence <strong>has the action done</strong> to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4XNfi3BoAEcX699fSXM-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Gaxq0PQKI8Msezj-7XgxQ.png" /></figure><p>There is <strong>an exception</strong> to the rule<strong>: </strong>when you want to specifically highlight the action over the subject (e.g. <em>“Your video was updated by a team member”).</em></p><h4>2. <strong>Make it simple</strong></h4><p>Use <strong>everyday words</strong> that are easy to understand.<br>Don’t use technical words, unfamiliar acronyms, or corporate jargon,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1w-_scDgfESqJ_8XOVYJCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ilhm1ckQsAX6g_qvmLy86g.png" /></figure><h4>3. <strong>Write positively</strong></h4><p>Use <strong>positive language</strong>.<br>Avoid the use of words like <em>haven’t</em>, <em>can’t</em>, <em>don’t…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-BeObtO5DZbTsbAqyzFDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CoSJoaXDgf46W2k3NMD5g.png" /></figure><h4>3. <strong>Remain consistent</strong></h4><p>Use consistent language to help users better understand the meaning, and avoid confusing them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlnoP9qUlf6u-qwjwblYjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sEHD51KdiNl4USmoXoGfhg.png" /></figure><h3>Write intuitive text for forms</h3><h4>1. Title</h4><p>The title describes the content of a form. <br>A form can also have a subheading with a short description.</p><ul><li>Titles should be short and clear.</li><li>Use lowercase in the title, except for the first letter of the first word.</li><li>Don’t use periods.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*coGfoWyaZoeogEkuSOW3fQ.png" /></figure><h4>2. Labels</h4><p>Labels tell the users what information belongs in a field.</p><p>Labels describe the required information clearly and concisely — ideally in one word. Don’t use more than one line and avoid using verbs.</p><p>If most of the fields are required, you can just mark optional fields by placing <strong>“(optional)”</strong> behind the label.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ePOe7zzxwtsbxX8j_8tVLg.png" /></figure><h4>3. Placeholders</h4><p>Placeholder text is used as a hint in the field.</p><p>You can have 2 types of placeholders:</p><ul><li><strong>Example placeholder:</strong> it includes an example of the information required.</li><li><strong>Actionable placeholder:</strong> it includes a verb and has an actionable form.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aTVfWmAKc24x9_bZmeA8nQ.png" /></figure><h4>4. <strong>Help text</strong></h4><p>Help text appears below a field or as hover text to provide additional information.</p><p>To avoid overloading, the form shows help text only where users really need assistance.</p><p>Ideally, don’t use more than one line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdqbROgBJ-B5Y972eBsDYw.png" /></figure><h4>4. Call To Actions</h4><p>CTA should describe the action that will occur if the user clicks on them.</p><p>The content should be clear, direct and explicit.</p><p>Do not use generic terms that do not provide useful information to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fc3Ol_oSMEIQeVZAUzD8oQ.png" /></figure><h3>Adapt lists type</h3><h4>1. <strong>Bulleted lists</strong></h4><p>Use a bulleted list when items are related, but priority doesn’t matter.</p><p>Make sure that each sentence has the same structure.</p><p>For example, all items begin with a verb conjugated in the same way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tao4a1CmWQ38YH1ta9GcoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0MyZ1PJ83CBdvmEIpSp0HA.png" /></figure><h4>2. <strong>Numbered lists</strong></h4><p>Use a numbered list when item sequence or priority does matter, such as step-by-step instructions.</p><p>Make sure that each step is well detailed.</p><p>It’s better to have more but clear steps, than having fewer steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HgWbpi3WgWpVS2ImbSqrdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*afDXmpZ35g6ZejfgRCIamA.png" /></figure><h3>Use punctuation correctly</h3><h4>1. <strong>Periods</strong></h4><p>Avoid using periods unless it’s a full sentence description.</p><p><strong>Use for:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S2q3dOEH0Mc57_bCXSci3g.png" /></figure><p><strong>Don’t use for:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OWGyqzepWLMt-RsK8sSeAA.png" /></figure><h4>2. Exclamation marks</h4><p><strong>Avoid</strong> exclamations marks.</p><p>The exclamation mark has an emotional value that other punctuation marks don’t have. It’s associated to strong emotions like joy or anger.</p><h3><strong>Write intuitive feedback messages</strong></h3><p>Keep in mind that most users would rather scan text instead of reading everything.<br>Therefore, get right to the bottom of the problem and avoid too many details.</p><h4><strong>1. Error message</strong></h4><p>Error messages inform users about a problem and how they can solve it.</p><p>Provide error messages <strong>after</strong> users have taken an action to inform about:</p><ul><li>What happened</li><li>Consequences</li><li>How to move forward</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8i7E1DSH-RnnF3HI-SyOw.png" /><figcaption>Types of error messages</figcaption></figure><h4><strong>2.</strong> <strong>Warning message</strong></h4><p>Warning messages inform users about a potential problem and how they can prevent or solve it.</p><p>Provide warning messages <strong>before</strong> users have taken an action to inform about:</p><ul><li>Potential problem</li><li>If action is required, or not</li><li>How to move forward</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*6i_DXQENob5cfJhWKeMACw.png" /></figure><h4>3. <strong>Info message</strong></h4><p>Info messages help users understand a situation in a motivational way.</p><p>Inform users about an important change:</p><ul><li>Get right to the bottom of the topic</li><li>Why this information is important</li><li>Avoid being disruptive</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*7EDrqaqncuMzUbh2vYSniw.png" /></figure><h4>4. Success message</h4><p>Success messages inform users about the completion of a task.</p><p>We provide success messages <strong>after</strong> users have taken an action to inform about:</p><ul><li>The reason for the success</li><li>How to view what they’ve achieved</li><li>How to undo it</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*jSl-capkOFSUfIVGXJEMkg.png" /></figure><h3>Create a conversation with pronouns</h3><p>Pronouns help our product sound human and conversational.</p><p><strong>Be consistent:</strong> using pronouns across all features increases our consistency and can improve the user experience.</p><p>PlayPlay is used to create and share videos. We use the first-person singular pronoun <strong>“<em>I, me, my</em>” </strong>to underline privacy and trust, e.g: “My account”, and “My private videos”.</p><p>To make our product human and conversational we use the first-person plural <strong>“<em>we, us, our</em>”</strong> when referring to Play Players and all our services, e.g. when customer support gives feedback after receiving a request.</p><p>Use <strong><em>“my/mine” </em></strong>if the user performs an action, such as clicking a link, e.g. “My last video”</p><p>Use <strong><em>“your” </em></strong>if the product is presenting information to the user, e.g “Your primary and secondary colors are the same”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37bd0f47ab1b" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/ux-writing-principles-37bd0f47ab1b">UX Writing principles</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a UX design style guide for your team]]></title>
            <link>https://uxplanet.org/creating-a-ux-design-style-guide-for-your-team-e756210865a4?source=rss-7bd5933803c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e756210865a4</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Lisa Kas]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 11:17:36 GMT</pubDate>
            <atom:updated>2022-04-19T15:35:24.208Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to build one yourself</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzQ1yzqL7FRfP-Ri1syQJQ.jpeg" /><figcaption><a href="https://www.behance.net/leonohchida">Illustration by Eleonore Millet</a></figcaption></figure><p>A design guideline is a document that lists all the choices and conventions taken in the company, in order to keep the design and development team aligned. Being connected to, for instance, the design guideline, allows a given prototype to be developed faster and without complications.</p><blockquote><em>Here is an example of what we defined in our guideline with my previous UX Lead:</em></blockquote><h4><strong>1. Base unit</strong></h4><p>A base unit is an 8x8 pixel square. To create margins and padding, the base unit is scaled by two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_33cAqDgMLUF8O3pIiNEQ.png" /><figcaption><em>Based on the </em><a href="https://www.carbondesignsystem.com/guidelines/2x-grid/overview/"><em>grid concept from IBM Carbon Design System</em></a></figcaption></figure><h4>2. <strong>Grid</strong></h4><p>A grid is built by multiplying or dividing in two, using percentages for flex grids and scaled base units for fixed grids. While 2x is the recommended method, dividing by thirds is also possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*T7T2RcYNv_D4q6mQwKBrZA.png" /><figcaption><em>Based on the </em><a href="https://www.carbondesignsystem.com/guidelines/2x-grid/overview/"><em>grid concept from IBM Carbon Design System</em></a></figcaption></figure><h4><strong>3. Spacings</strong></h4><p>Spacing is context-based. Use smaller increments in scaling for fine-tuning elements inside a component (eg. label and input field), and larger ones for elements on a page (eg. spacing between two sections, or between title, headers, and content).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbSrDh6wqhD3E6tuoF8o2g.png" /></figure><h4>4. Breakpoints</h4><p>Defining breakpoints allows the designers and developers to uniform the design even if the screen sizes are different. With the pervasiveness and diversity of mobile devices, as designers, we need to cater to the variety of screen sizes. This is a challenge that every web and app designer currently faces.” (<a href="https://www.interaction-design.org/literature/article/adaptive-vs-responsive-design">Adaptive vs. Responsive Design article</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*9vfK937NdWQDERLm166j1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RxzPZbDBjTtioyK4cHsMsQ.png" /></figure><h4>5. <strong>Color palette</strong></h4><p>Usually, the color palette is divided into groups:</p><ul><li>Primary/secondary</li><li>Gray shades</li><li>Status (success, warning…)</li></ul><p>Be careful to:</p><ul><li>Use color sparingly</li><li>Verify colors against WCAG for contrast</li><li>Not use status colors as only indicators</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8e0FNLBszjxqkNq1jjXR4Q.png" /></figure><h4><strong>6. Typography</strong></h4><p>The three main elements of typography are font style, appearance, and structure. It plays a much larger role than appearance. It’s a way to create a visual hierarchy on your site. It will also help balance graphics on a webpage page. You need to make sure it’s clear and easy to follow.</p><blockquote>I advise you to take a look at <a href="https://refactoringui.com/">Refactoring UI</a> on the “Font” section.</blockquote><h4>7. <strong>Font size</strong></h4><p>There are three things you need to consider when you select the font size for your website, the size of type, line spacing, and the age of the reader. It’s not a big surprise that the older you get the worse your eyes get. So, smaller fonts are going to be more difficult to read for a lot of audiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fqaxD3jun_Ff-xiGyE4kIQ.png" /></figure><h4>8. <strong>Text values</strong></h4><p>Sentence case, unless defined by client internal branding guide:</p><ul><li>Only the first letter uppercase, the rest lowercase</li><li>Common uses: titles, table headers, buttons, form field labels</li></ul><p>Avoid all caps, with certain heading/title exceptions</p><p><em>Example:</em></p><ul><li><em>EN: “Date of claim” not “Date of Claim”</em></li><li><em>FR: “Date du sinistre” not “Date du Sinistre”</em></li></ul><p>Style guides:</p><ul><li><a href="http://download.microsoft.com/download/b/3/4/b34f7185-afca-4846-8fbf-672a1b9afce2/jpn-jpn-styleguide.pdf">Japanese language style guide</a></li><li><a href="https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style">US/International Wiki style guide</a></li></ul><h4>9. <strong>Numerical values</strong></h4><ul><li>Regional standards take precedent</li><li>In the case of ambiguity, use a style guide below</li><li><a href="http://publications.europa.eu/code/en/en-4100500en.htm">EU standards</a></li><li><a href="https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Numbers">US/International standards</a></li><li><a href="https://en.wikipedia.org/wiki/Date_format_by_country#Listing">Date format by country</a></li></ul><h4>10. <strong>Rules for buttons</strong></h4><ul><li>Button text should be explicit</li><li>The button should have default, hover, active, focus, selected, and disabled states</li><li>One primary action per page/screen and the rest are secondary</li><li>In my company, we use Cancel/OK in this exact order (read left to right), as well as Secondary/Primary</li><li>Multiple buttons at the bottom of a modal align-right</li><li>Align buttons to content when applicable</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2oOIh6e1I983qU7aMqjTA.png" /><figcaption><em>Based on the states from </em><a href="https://material.io/design/interaction/states.html#usage"><em>Material Design</em></a></figcaption></figure><h4>11. Rules for buttons and actions</h4><ul><li>Avoid having multiple primary actions at a time. There can be multiple secondary actions with a weaker visual emphasis.</li><li>The user should always get feedback on their actions, either through explicit changes in UI or with visual confirmation.</li></ul><h4>12. Rules for buttons and recommendations</h4><ul><li>Labels on buttons should be explicit and inform the user about what will happen after it is pressed e.g. ‘Apply’, ‘Save’, ‘Send’ rather than ‘OK’.</li><li>Buttons should have multiple stages to indicate when they are e.g. disabled, hovered, pressed.</li></ul><h4>13. <strong>Rules for forms</strong></h4><ul><li>A label on top of the input field; in the case of an inline label and input field, right align label against an input field.</li><li>Labels should always be present (not placed inside the input).</li><li>Adjust the width/height of input fields accordingly to the content size, to<br>provide better visual cues (eg. shorter field for zip code, the taller field for textarea).</li><li>Input fields should have a state indicator for active/focused, disabled, and error.</li><li>The error message should be in the same proximity as the field.</li><li>When possible — and we should always aspire to do so — add cues in the input field to increase usability (eg. split phone numbers and add date separators automatically…).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-Ca70RNSbYkOsiijdlHkA.png" /></figure><h4>14. <strong>Rules for table(s)</strong></h4><ul><li>Text values align left</li><li>Numerical values align-right</li><li>Headers align with content</li><li>No center alignment except in the case of buttons and icons</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*O22xYmhQkBMvSWpYYN2mUg.png" /></figure><h4><strong>15. Jakob’s law</strong></h4><p>Follow standards and patterns. Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*B5D3QW0ndGzKSQFC5VybVQ.png" /><figcaption><a href="https://lawsofux.com/">From https://lawsofux.com/</a></figcaption></figure><h4>16. <strong>Hick’s law</strong></h4><p>The time it takes to make a decision increases with the number and complexity of choices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*k9TJQGbxNEm_aXRJAA9R5A.png" /><figcaption><a href="https://lawsofux.com/">From https://lawsofux.com/</a></figcaption></figure><h4>17. <strong>Miller’s law</strong></h4><p>The average person can only keep 7 (plus or minus 2) items in their working memory.</p><p><em>Avoid 1) too many choices, 2) too much thought required, or 3) lack of clarity.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*2zZEzGcSiUeKidVLvtx5Aw.png" /><figcaption><a href="https://lawsofux.com/">From https://lawsofux.com/</a></figcaption></figure><h4><strong>18. Law of similarity</strong></h4><p>The human eye tends to perceive similar elements in a design as a complete picture, shape, or group, even if those elements are separated.</p><p>If it looks like a button or link users expect to be able to click on it. Elements should be visually consistent throughout the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*FwLbWGzsDiOBOdcpc-n0eQ.png" /><figcaption><a href="https://lawsofux.com/">From https://lawsofux.com/</a></figcaption></figure><p>Having a design guideline will help you and your team to be consistent and structured in the interface.</p><p>My advice is to not be too complex in the principles to follow. Choose the most important one and teach your team to follow them.</p><p>Through my experiences, the guideline helped me to gain time during the design and the implementation phases. Why? Because we made fewer mistakes in the basic UX/UI design choices, and it helped the devs to be more autonomous during the implementation.</p><p><a href="https://www.carbondesignsystem.com/guidelines/2x-grid/overview/">https://www.carbondesignsystem.com/guidelines/2x-grid/overview/</a></p><p><a href="https://www.interaction-design.org/literature/article/adaptive-vs-responsive-design">https://www.interaction-design.org/literature/article/adaptive-vs-responsive-design</a></p><p><a href="http://download.microsoft.com/download/b/3/4/b34f7185-afca-4846-8fbf-672a1b9afce2/jpn-jpn-styleguide.pdf">http://download.microsoft.com/download/b/3/4/b34f7185-afca-4846-8fbf-672a1b9afce2/jpn-jpn-styleguide.pdf</a></p><p><a href="https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style">https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style</a></p><p><a href="http://publications.europa.eu/code/en/en-4100500en.htm">http://publications.europa.eu/code/en/en-4100500en.htm</a></p><p><a href="https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Numbers">https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Numbers</a></p><p><a href="https://en.wikipedia.org/wiki/Date_format_by_country#Listing">https://en.wikipedia.org/wiki/Date_format_by_country#Listing</a></p><p><a href="https://lawsofux.com/">https://lawsofux.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e756210865a4" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/creating-a-ux-design-style-guide-for-your-team-e756210865a4">Creating a UX design style guide for your team</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to the dark side of UX design]]></title>
            <link>https://uxplanet.org/welcome-to-the-dark-side-of-ux-design-77eeb1fd024f?source=rss-7bd5933803c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/77eeb1fd024f</guid>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[insurtech]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[dark-patterns]]></category>
            <dc:creator><![CDATA[Lisa Kas]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 19:21:17 GMT</pubDate>
            <atom:updated>2022-04-19T15:36:10.383Z</atom:updated>
            <content:encoded><![CDATA[<h4>Dark UX patterns in insurtech</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wScBXi8C-UR6D9t8TljKCA.jpeg" /><figcaption><a href="https://www.behance.net/leonohchida">Illustration by Eleonore Millet</a></figcaption></figure><p>A good UX has a direct impact on the user’s emotion, and as such, it also impacts the view of the company as a whole. If I had a dollar for everytime I heard someone say “The product is great, but the customer support is so bad it’s not worth it”, well, you know the rest. It sometimes happens that a company focusing on the business aspect will create inconsistencies in the product. In the best (or rather, more ethical case), these inconsistencies are mistakes. In the worst cases, they can actually be introduced on purpose, to push the user toward a choice he would not have taken. This is a typical short/long investment scenario: in the short term, they will make higher margins (people paying more than they would), however, if the word spreads, it can have an important impact on the reputation of the company. This is a typical situation faced as a UX designer, and especially so in the insurtech, which I will now discuss.</p><h4><strong>UX design in insurtech</strong></h4><p>I used to be a UX designer in an insurtech company specializing in anti-fraud and claim automation, where my main role was designing the claim automation process. The goal of a claim automation system is above all to improve the claim handlers’ jobs by automating part of the repetitive work, offering them more time to focus on complex cases; secondly, to improve the experience of the users by offering them a faster &amp; better experience, as well as provide information customised for the client.</p><p>So, we had two types of users:</p><ul><li>Claim handlers, specialized in insurance, work with unadapted software which sometimes decreases their productivity.</li><li>Policyholders, who are beginners about insurance and simply want to declare a claim.</li></ul><p>A couple of months after I joined the insurance world, I started wondering:</p><blockquote>What is the main goal of insurance companies? Improve the experience of the user by improving the claim declaration system or try to lead the user to choose the solution that the insurance company prefers?</blockquote><p>This is how I discovered the world of dark UX.</p><h4><strong>Entering the real world of dark UX</strong></h4><p>According to Brownlee (Fast Co. Design), dark patterns are deceptive or manipulative UX/UI designs that try to exploit human psychology to get users to do things they don’t really want to do. This term was coined in 2010, after the explosion of the e-commerce industry on the web to generate more sales, more subscribers, transactions, etc…It was from this moment that designers and business people began to create interfaces meant not to be simpler, as you would expect, but to manipulate users. At that time, Harry Brignull (Phd Cognitive Science, 2010) more specifically defined it as a user interface that was carefully designed to entice users to do things, such as buying insurance with their purchase or signing up for recurring bills. I think that we all fell into a trap of this kind one day; if not, I advise you to visit a well-known site reporting examples of <a href="https://darkpatterns.org/types-of-dark-pattern">dark patterns</a>. As you may be starting to realise, dark patterns and UX principles are quite contrasting: on one side, we want to make the experience smooth and transparent for the users, and on the other, we’re trying to make them do things they wouldn’t normally do.</p><h4><strong>A dark UX case in insurtech</strong></h4><p>I once took part in a meeting with a client, which I still remember today. At that time, I had just arrived at the company, and I was discovering the different projects slowly. At this meeting, the client asked us to modify part of the online claim declaration. We had already done several design iterations, and my UX colleague, therefore, had prepared the designs presenting the various solutions that the insured could choose after declaring his claim. The problem we faced was that the client wanted to show the solution that gave the most profit to the company while hiding the other solutions behind a small link at the bottom left of the page. The reaction of my colleague was to protest by explaining the lack of transparency they will create by doing that. They did not care and, as my colleague said after the meeting, “the client has the final word and we can’t go against him”. At that time, I accepted this answer.</p><p>A couple of months later, the insurance company decided to make some user tests with external people who faced water damage recently. They first told us the story about their water damage, their concerns, decisions they took, how they declared it. We then asked them to test our claim declaration system. On four users, one stopped at the solution page and started to notice that the other solutions were hidden and did not appreciate the lack of transparency he was facing. He felt manipulated, and it increased the negative concerns he had in front of insurance companies and this one in particular. The user had retained the lack of transparency of the solution and the company behind its existence as well. This is a typical example of an existing dark pattern generating frustration in a user.</p><blockquote>The question we can ask today as professionals behind the product is: how to avoid these dark patterns?</blockquote><h4><strong>Avoid mixing insurtech and dark UX</strong></h4><p>As a product specialist, we are responsible for expressing our dissatisfaction with clients’ decisions when they are contrary to the ethics of our work or the company. It is up to us to support our comments with facts and data showing the wrong choice of certain clients — we are responsible for the transparency of the products put into production. To do this, we must propose different solutions that also take into account the expectations of our users as well as our clients.</p><blockquote>Innovation starts by listening to our users, building for them, and most importantly, with them. Never forget that avoiding the dark pattern is creating more transparency, bringing more confidence, and providing a better experience.</blockquote><p>As explained above, user experience is connected to business purposes, and business purposes can lead to dark patterns. In my previous company, through our claim automation products, we aimed to improve claims reporting by providing a better experience for our users. This means more automation, fast claim declaration, and a visually pleasing interface. However, better UX also requires product transparency. It is our duty to create experiences that are transparent and unambiguous and which enable the users to follow the action plan they have set for themselves. As UX designers, product managers, it is our responsibility to represent the company and the product we aim to build; a long-term sustainable product, instead of finding short-term improvements through dark design patterns.</p><p><a href="https://www.fastcompany.com/3060553/why-dark-patterns-wont-go-away">https://www.fastcompany.com/3060553/why-dark-patterns-wont-go-away</a></p><p><a href="https://uxdesign.cc/dark-patterns-in-ux-design-7009a83b233c">https://uxdesign.cc/dark-patterns-in-ux-design-7009a83b233c</a></p><p><a href="https://www.darkpatterns.org/types-of-dark-pattern">https://www.darkpatterns.org/types-of-dark-pattern</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77eeb1fd024f" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/welcome-to-the-dark-side-of-ux-design-77eeb1fd024f">Welcome to the dark side of UX design</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>