<?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 Poulami Chakraborty on Medium]]></title>
        <description><![CDATA[Stories by Poulami Chakraborty on Medium]]></description>
        <link>https://medium.com/@poulamic?source=rss-d53de65cf88------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MRuy4JsWCeSdB3tSpq-YaA.jpeg</url>
            <title>Stories by Poulami Chakraborty on Medium</title>
            <link>https://medium.com/@poulamic?source=rss-d53de65cf88------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:13:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@poulamic/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[Thinking in frameworks: communicating system status]]></title>
            <link>https://uxdesign.cc/thinking-in-frameworks-communicating-system-status-eaf6f7b58bab?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaf6f7b58bab</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Sat, 14 Aug 2021 11:05:59 GMT</pubDate>
            <atom:updated>2021-08-23T17:39:15.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>Notifications, alerts, and indicators.</h4><figure><img alt="Lo-fi wireframe of alerts" src="https://cdn-images-1.medium.com/max/1024/1*GptuVu6qxyJY_AUejx4hyg.png" /></figure><p>Quite a few articles have been written on notification design. But most of them have been in the context of consumer-facing products. The main focus as such has been on best practices to avoid overwhelming and annoying users with too many notifications.</p><p>Yet notifications are inherently powerful tools to keep users updated about the system status — visibility is one of the <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 usability heuristics</a> for interface design.</p><p>This is especially important in information-heavy enterprise domains — with multiple background events — where users are continuously trying to sort out relevant information without missing major errors or failures. A well-designed notification system can add value and stay focused in light of all information fighting for the user’s attention. Notifications should help reach a goal rather than pestering them.</p><h3>Indicators, Validations, and Notifications</h3><p>Three common approaches for status communication include validation, notifications, and status indicators.</p><ul><li><strong>Indicators:</strong> An indicator is a way of making a page element (be it content or part of the user interface) stand out to inform the user that there is something special about it that warrants the user’s attention. (ex: sale sign, usage/performance indicators)</li><li><strong>Validations:</strong> Validation messages are error messages related to users’ inputs — they communicate whether the data just entered was incomplete or incorrect.</li><li><strong>Notifications:</strong> Notifications are informational messages that alert the user of general occurrences within a system.</li></ul><p><a href="https://www.nngroup.com/articles/indicators-validations-notifications/">This NN Group article goes in-depth on picking the correct communication method</a>. I won’t be getting into this differentiation here.</p><p><em>I will be using notifications as a umbrella term for push/in-app notifications, alerts, validations and indicators unless otherwise specified.</em></p><h3>Why think in frameworks?</h3><p>As products grow and features are added, the notification list would also increase. Case-by-case design means an inconsistent design language. A comprehensive policy and design framework is necessary to ensure a consistent and good UX.</p><p>Thinking in systems helps to look at the bigger picture, account for scalability and be prepared for unforeseen use cases.</p><p>Moreover a consistent notification pattern and language increases the learnability and glancability of the design.</p><h3>Components of a notification</h3><ul><li><strong>Information:</strong> This is the message we are trying to convey. This should provide users enough context to quickly identify the issue and decide if the information is important.</li><li><strong>Source/ context:</strong> This is the feature/data from which the notification originates. Based on how the notification is anchored, we may need to include this information in the message.</li><li><strong>Action</strong> (optional)<strong>:</strong> These are potential remediation steps that the user can or should take.</li><li><strong>Anchor/Mode:</strong> This is where the notification will surface (ex: notification centers, contextual badges, emails, webhook integrations, etc.)</li><li><strong>Notification indicators or counters:</strong> This are the visual cues to make users aware of the fact that there is something that needs their attention. This can include the number of unread notifications. <br>Consider the bubbling up of notifications in a category (ex: in whatsapp the messages tab shows the number of unread threads in addition to unread threads showing number of unread messages)</li><li><strong>Meta-data:</strong> Time, reason they are seeing this notification, etc.</li></ul><figure><img alt="A lo-fi wireframe of a notification card labelling some of the components mentioned above" src="https://cdn-images-1.medium.com/max/507/1*B3ptRYqjjK_oegR7cGH5Tw.png" /><figcaption>(Some) Components of a notification</figcaption></figure><h3>Classifying Notifications</h3><p>There exists multiple criteria on which notifications can be classified:</p><ul><li><strong>Active vs Passive:</strong> whether user needs to take action</li><li><strong>Urgency:</strong> how critical is it for user to see the notification immediately (critical, warning)</li><li><strong>Type:</strong> alerts, validations, or indicators</li><li><strong>Trigger:</strong> <strong>task-generated</strong> (ex: request successfully completed) vs <strong>system-generated</strong> (ex: upgrade available)</li><li><strong>Persistence:</strong> whether user can dismiss the notification (ex: ongoing issue like system problems need to be persistent)</li></ul><h3>Standard UI Patterns used for notifications</h3><ul><li><strong>Indicators</strong> <br>Indicators are visual cues intended to attract the user’s attention to dynamic information. It is anchored to UI components. Shapes and colors are some common ways used for such information. <a href="https://carbondesignsystem.com/patterns/status-indicator-pattern/">Carbon Design System is a good reference for a detailed indicator design</a>.</li></ul><figure><img alt="Example of 3 UI patterns used as indicator — error, warning and info" src="https://cdn-images-1.medium.com/max/144/1*Bqx6aOiXTgST6ae7BULUdQ.png" /></figure><ul><li><strong>Validations (Inline)</strong> Validations are messages to alert users of errors in input fields. This is contextual, preferably inline and anchored to the input field.</li></ul><figure><img alt="Example of validation through two input fields — one with validation message" src="https://cdn-images-1.medium.com/max/382/1*LrFOoUXTc7ByvF0ge-weCg.png" /></figure><ul><li><strong>Toast, Snackbars, In-app push notifications</strong> Toasts and snackbars are generally used for non-urgent (good-to-know) system feedback to a user action (ex: “Form submitted”). These are also be used after user has left the input screen. <br>The information is concise as users are aware of the context. <br>In-app notifications (which are similar to snackbars) are used to alert users of activity in different part of the product. Example: New message in slack). <br>These messages are generally not critical and don’t require any or immediate action. In most cases, these automatically disappear after some time. <br>The elements are displayed non-intrusively so that user’s current activity remains visible and interactive. A possible side-affect is that these could go unnoticed. So, don’t use (only) toasts to communicate critical information.</li></ul><figure><img alt="A typical toast notification UI" src="https://cdn-images-1.medium.com/max/234/1*cLOduLLM4qAcznMPBePfUA.png" /></figure><ul><li><strong>Notification Center</strong> <br>Notification center is an exclusive place for notifications. It’s generally a flyout but can also be a dedicated page. <br>The anchor is this UI component, no matter the origin of the notification. Existence of a notification center may set the expectation of user to be able to find all critical alerts at a place. <br>Don’t push all notifications to notification center to avoid overwhelming users.</li></ul><figure><img alt="Lo-fi wireframe of a notifications center" src="https://cdn-images-1.medium.com/max/480/1*WuXfVaRL3xYlCLHTInTM4A.png" /></figure><ul><li><strong>Modals<br></strong>Modals are the most disruptive to the user experience and hence should be sparingly used. They are useful when we need to block tasks to gain user’s focus. For instance: to alert an user that their progress will be lost if they navigate away from a flow.</li></ul><figure><img alt="Lo-fi wireframe of a modal" src="https://cdn-images-1.medium.com/max/363/1*zNYSCWyMuuG5FGPnf5ihZQ.png" /></figure><h3>Creating the Framework</h3><p>Begin by listing all existing notifications or, in case of new products, major notifications. Next is prioritizing and categorizing them to use as a baseline for creating the policies.</p><h4>1.</h4><p>The first step is determining the <strong>criteria for showing a particular notification</strong>. Ask if the notification deserves user’s attention or is it unnecessary noise. Don’t use alerts for unimportant information (ex: ‘You have logged in’). It can lead to desensitization of users.</p><blockquote>“If everything is important, then nothing is.” ― Patrick M. Lencioni</blockquote><h4>2.</h4><p>Not every notification is equal. With multiple notifications vying for the user’s attention, there has to be a <strong>logical way of prioritizing information</strong>.</p><p>One factor would be the <strong>UI pattern used</strong> — for example, user’s attention would more naturally turn towards a larger alert banner than an indicator.</p><p>The second prioritizing would be the <strong>severity of the message </strong>— info/ warning/ error/critical.</p><figure><img alt="Wireframe of error and warning alert bars" src="https://cdn-images-1.medium.com/max/411/1*7Q5sJo4oqXiUf_njZxnMnQ.png" /></figure><p>Generally, standard color, icons and conventions are used to differentiate.</p><p>The same notification ‘ can have different severity based on a value (Ex: ‘You have used 60% of storage’ and ‘You have used 95% of storage’)</p><p>Put urgent and important notifications front and center. Otherwise put it out of the way — a consistent design pattern will let users to find them if they really want to see it.</p><h4>3.</h4><p>Trigger for the notification — when would this notification surface? Under what condition, if any, will it be resurfaced as reminder?</p><h4>4.</h4><p>Are there associated actions that would help remediate the issue? Or any documentation to link users to? How do they understand exactly what is going on and how to get themselves out of the snag? What happens if user doesn’t take any action? What’s the escalation policy? (Ex: ignored alerts to be transformed to global banners or sent as email)</p><p><strong>Here is a checklist based on the above points:</strong></p><p>[ ] Why are we showing the notification?</p><p>[ ] Trigger</p><p>[ ] Anchor/Mode (can be more than 1)</p><p>[ ] Severity (Critical/Urgent/Warning)</p><p>[ ] Associated actions</p><p>[ ] Persistence (can’t be dismissed/can be dismissed/auto-dismiss)</p><p>[ ] Permanence (can be retrieved in log)</p><p>[ ] Escalation criteria</p><figure><img alt="Spreadsheet with the following column headers: Message, Trigger, Anchor, Severity, Actions, Dismissible components, UI components" src="https://cdn-images-1.medium.com/max/1024/1*tuPRmPSmvn4IOz_NXKebHA.png" /></figure><p>Your design system would lay out the rules for when each of this components can or should be used. For reference:</p><p><a href="https://www.carbondesignsystem.com/components/overview/">Carbon Design System</a></p><p><a href="https://clarity.design/core-components/">Clarity Design System</a></p><h4>Other considerations</h4><ul><li><strong>Tone:</strong> Have a consistent tone for all notifications</li><li><strong>UX Copy &amp; Terminology:</strong> Concise and clear language for easy-to-read notification content.</li><li><strong>Consistency &amp; conventions:</strong> Color, shape, dimensions, and position of objects play a significant part in communicating information. Following universal standards and consistent patterns requires less thought on part of users.</li><li><strong>Accessibility:</strong> Make notifications accessible</li><li><strong>Cross-device, redundancy and sync:</strong> If the same notification is being conveyed in multiple places — for example: in-page alert and notification center — sync notification status (read/unread or removed from queue) when user takes action in one place.</li><li><strong>Clustering, Grouping, Filtering, Stacking:</strong> Consider how notifications can be meaningfully clustered (ex: multiple comments on a post), grouped and/or filtered by feature or anchor, and inline,toast notifications can be stacked.</li><li><strong>Logs:</strong> Consider if and how logs of previous notifications need to be preserved.</li><li><strong>Sound:</strong> Sound is an useful medium to draw attention to in-app notifications.</li></ul><h4>More references:</h4><p><a href="https://uxdesign.cc/a-comprehensive-guide-to-notification-design-2fff67f08b7a">A comprehensive guide to notification design</a></p><p><a href="https://puppet.com/blog/designing-systems-not-just-ui-alerts-notifications/">Designing systems, not just UI: alerts &amp; notifications</a></p><p><a href="https://www.nngroup.com/articles/errors-forms-design-guidelines/">NN Group How to Report Errors in Forms: 10 Design Guidelines</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*NIck2EJvh-aFQ-0F.png" /><figcaption>The UX Collective donates US$1 for each article we publish. This story contributed to <a href="https://www.wcd.school/">World-Class Designer School</a>: a college-level, tuition-free design school focused on preparing young and talented African designers for the local and international digital product market. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaf6f7b58bab" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/thinking-in-frameworks-communicating-system-status-eaf6f7b58bab">Thinking in frameworks: communicating system status</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In defense of reusing existing design patterns]]></title>
            <link>https://uxdesign.cc/in-defense-of-reusing-existing-design-patterns-9d216e09dfce?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d216e09dfce</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Sun, 25 Jul 2021 17:14:48 GMT</pubDate>
            <atom:updated>2021-07-25T17:14:48.527Z</atom:updated>
            <content:encoded><![CDATA[<h4>Leveraging affordances, signifiers, and standard interaction patterns for intuitive design.</h4><figure><img alt="xkcd comic. Situation: There are 14 competing standards person: “14?! Ridiculuos. We need to develop one universal standard that covers everyone’s use cases. Soon: There are 15 competing standards" src="https://cdn-images-1.medium.com/max/1024/1*oO87aH9eW3Rz3AJQaBS4bA.png" /><figcaption>source: xkcd.com</figcaption></figure><p>A known mantra in UX design is: ‘Don’t make me think’.</p><p>In other words — make interactions intuitive.</p><p>Intuitive design implicitly suggests to the user possible functionalities and expected outcomes of the product. Affordances play a significant part in determining how intuitive a design is.</p><p><strong>Affordances are the possibilities of utilizing or interacting with an object based on its appearance and capabilities</strong>. For example, a horizontal, flat, extended, rigid, and knee-high surface looks like it can be sat upon. So it affords sitting. A raised ‘button’<em> </em>looks clickable. It affords to click.</p><p>The concept of affordance was first coined by psychologist James J. Gibson who worked in the field of perception. According to Gibson, affordances are implicit qualities of an environment about what it offers provides, or furnishes. Affordances are not necessarily visible.</p><p>The concept was borrowed in multiple fields, including in interaction design by Don Norman. In his book <em>The Design of Everyday Things, </em>he adapted the concept to <strong>perceived affordances</strong> — what someone thinks an object can do (perception). This is the widely accepted definition of the interaction design field.</p><p>Wikipedia has a clear example to distinguish between the two interpretations:</p><p><em>If an actor steps into a room containing an armchair and a softball, Gibson’s original definition of affordances allows that the actor may throw the chair and sit on the ball, because this is objectively possible. Norman’s definition of (perceived) affordances captures the likelihood that the actor will sit on the armchair and throw the softball.</em></p><p>Effectively, Norman’s affordances “suggest” how an object may be interacted with. (<a href="https://www.alice.id.tue.nl/references/norman-2008.pdf">Norman later explained that this restriction of the term’s meaning had been unintended, and added the concept “signifiers</a>”)</p><p><strong>Signifiers are (additional) cues about how people may interact with an object</strong>.</p><p>Signifiers are used to:</p><ul><li>Clarify affordances and make intended way of using an object more explicit. Example: pull/push signs on door, earcons in voice interfaces etc.</li><li>Communicate state of an object or what an interaction or action with it will lead to. Example: the red dot to signify hot water on a tap, state of fan regulators, etc.</li></ul><p>The concept of signifier is borrowed from <a href="https://en.wikipedia.org/wiki/Signified_and_signifier">signified and signifier concept in semiotics</a>.</p><blockquote>Affordances define what actions are possible. Signifiers specify how people discover those possibilities.</blockquote><blockquote>— Donald A. Norman, The Design of Everyday Things</blockquote><p><strong>Together affordances and signifiers make objects — even those otherwise unfamiliar — intuitive.</strong></p><p>Signifiers are context-dependent and convey different meanings based on the object it is associated with. For example: an ‘+’ icon on an accordion and one on a button allude to different responses.</p><h3>GUIs — where do the perceptions arise from?</h3><p>Unlike the physical world, objects in GUIs do not have innate affordances — they are actually created — intentionally or unintentionally, successfully or unsuccessfully — by the ‘designer’.</p><p>The user’s perceived affordance of the interface elements are shaped by their past experiences in the real world or previous interactions with similar products.</p><p>Examples of physical world experienced extrapolated into digital products would be skeuomorphic designs, common icons, etc.</p><p>The influence of past design conventions would be knowing logo as a navigator to home page of a website, or recognizing header elements to be links even without any signifier. Another example would be knowing buttons are clickable, cross-hair cursor allows selecting, areas with scrollbar are scrollable, etc.</p><p><strong>If a design convention is used frequently, it becomes a perceived affordance.</strong></p><p>Perceptions aren’t static — they evolve with user’s experience across the physical and digital worlds. This is Jakob’s law.</p><blockquote><strong><em>Jakob’s law:</em></strong><em><br>Users spend most of their time on other sites, and they prefer your site to work the same way as all the other sites they already know</em></blockquote><p>To give an example: I had been using underline as a way to emphasize words and phrases since childhood. And yet, now I cannot not associate underlines with hyperlinks.</p><h3>Cost of absent signifiers</h3><p>When facing a signifier-less design, users may be confused about what they should or can do.</p><p>They may have to resort to sub-optimal and unnecessary ways to explore interface to find clickable components, out-of-view elements and hidden gestural interaction. These explorations would be through hovering, swiping, clicking, etc.</p><p>Such interactions lead to <a href="https://www.nngroup.com/articles/flat-design-long-exposure/">increased cognitive load and reduce efficiency and ease-of-use</a>.</p><p>Let’s also consider the higher-level consequences of designing such patterns.</p><p>Say — as a designer — we are able to <a href="https://www.nngroup.com/articles/flat-design-long-exposure/">use other design conventions</a> (UX copy, layout, etc.) as signifiers to alleviate the usability .</p><p>However, a large part of the web is not designed by designers. When non-designers borrow practices from such trends, a lot of the nuances and understanding of principles including affordances are absent. This affects the user experience on the web as a whole.</p><h3>Putting theory into practice</h3><ul><li><strong>Research</strong>: Well, this is going to be the first point in any design process. Find out user’s mental model. <a href="https://www.alice.id.tue.nl/references/norman-2008.pdf">As Norman notes here, signifier is an important communication device — whether or not communication was intended</a>. Good designers have a better understanding of how users perceive things so that they can use affordance as a tool. This understanding comes from research. <br>Consider different factors which may affect affordance; ex: <a href="https://dl.acm.org/doi/abs/10.1145/1028014.1028025">culture</a>.</li><li><strong>Design conventions and patterns:</strong> Leverage existing components, metaphors and patterns whenever possible instead of forcing users to learn something new. Maintain consistency within your design system. <br>If you are using a familiar recognizable pattern (a like button, swipe) don’t change the interaction — because if you do, it is a new and confusing pattern that user needs to <em>learn</em>. (This may not be possible at individual level — but we need to define standard interaction behavior for common patterns. I cannot count the number of times I have clicked on overlays to close a modal which didn’t allow that — only because some other modals do)</li><li><strong>Deliberately design the affordance and signifiers:</strong> A good understanding of different affordances and when and how to use them is important to be able to map objects to functions. <a href="https://www.smashingmagazine.com/2014/06/affordance-most-underrated-word-in-web-design/">Natasha Postolovski has written a detailed article on different types of affordances in this Smashing Magazine article.</a> The next part is consciously designing for each step of the interaction. Redundancy doesn’t harm.</li></ul><p>Let’s look at two common interactions in UI design and the associated affordance/signifiers.</p><h4><strong>Button</strong></h4><figure><img alt="A wireframe to highlight the signifiers of button in default, hover and disabled state" src="https://cdn-images-1.medium.com/max/733/1*1asNWeOpvAJ0PYg0Q_DiGw.png" /></figure><p>Here are three states of a button — default, hovered and disabled. The affordance is clickability.</p><p>Let’s look at all the signifiers in place:</p><ul><li>The text label on the button (including any helper text near the component)</li><li>The icon on the component</li><li>The visual design within the context of your design system.<br>- A filled button may be signify the primary action as opposed to an outlined secondary button.<br>- A background may signify clickability</li><li>The color of the button within your system or convention.<br>- Color as feedback on hover<br>- Color to indicate favorable or unfavorable actions (red for destructive actions)</li><li>Shadows to indicate raised or clickable component</li><li>The mouse pointer to indicate click-ability</li></ul><h4><strong>Drag-and-drop</strong></h4><figure><img alt="A wireframe to highlight the signifiers of an object being dragged to drop, and the target area" src="https://cdn-images-1.medium.com/max/594/1*LXdnyNr0WiotYaVjqI4enw.png" /></figure><p>Drag-and-drop is relatively a more complex interaction pattern as compared to a click. Here we use signifiers to convey continuous information about the results of user actions and the current state of the object being dragged:</p><ul><li>feedback that the component is now ‘draggable’ (mousetip changing from point to grip)</li><li>position/shadow of the object being dragged</li><li>possible places to drop the component</li><li>action that will happen if component is ‘dropped’ (ex: if it is too ‘far’ from the target area, it will go back to its original position)</li><li>the expanded drop zone around the target parent where the object can be safely dropped</li></ul><h3>Conclusion</h3><p>Intuitive use of products involves utilizing knowledge gained through other experiences, and mapping mental representations of past experiences and the current interaction. Affordances are a great way to ‘design’ this intuitiveness.</p><p>While we have some standard patterns, it is to note that standards and ‘intuitiveness’ are not constant — users are continuously interacting with different products and updating their representations, making ‘intuitiveness’ a moving target.</p><p>The objective of this article is to be more mindful and conscious about affordances while designing. Utilize existing patterns rather than creating a new one. Moreover, apart from just visual representations, shift the focus to complete interactivity.</p><h4>Other References:</h4><p><a href="https://en.wikipedia.org/wiki/Affordance">Wikipedia: Affordance</a><br><a href="http://cs.brown.edu/courses/cs137/2017/readings/Gibson-AFF.pdf">The theory of affordances</a><br><a href="https://uxdesign.cc/affordances-and-signifiers-82bd6f50fc1a">H Locke: Affordances and signifiers</a><br><a href="https://uxplanet.org/ux-design-glossary-how-to-use-affordances-in-user-interfaces-393c8e9686e4">UX Design Glossary: How to Use Affordances in User Interfaces</a><br><a href="https://gravyanecdote.com/bigbookofdashboards/affordances-and-signifiers/">Affordances and Signifiers: applying design theory to your dashboards</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*xDRoAzYhZYtx9nLh.png" /><figcaption>The UX Collective donates US$1 for each article we publish. This story contributed to <a href="https://www.wcd.school/">World-Class Designer School</a>: a college-level, tuition-free design school focused on preparing young and talented African designers for the local and international digital product market. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d216e09dfce" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/in-defense-of-reusing-existing-design-patterns-9d216e09dfce">In defense of reusing existing design patterns</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for information density]]></title>
            <link>https://uxdesign.cc/designing-for-information-density-69775165a18e?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/69775165a18e</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Sat, 17 Jul 2021 09:51:32 GMT</pubDate>
            <atom:updated>2021-07-17T09:51:32.844Z</atom:updated>
            <content:encoded><![CDATA[<h4>Balancing visual and structural simplicity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HHD8tGKYi63eVaZD" /><figcaption>Photo by <a href="https://unsplash.com/@strivingblogger?utm_source=medium&amp;utm_medium=referral">Striving Blogger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>KISS or ‘Keep it Simple Silly’ and ‘Less is More’ are adages we frequently encounter in design books, articles, and courses.</p><p>How do you achieve that in information-dense complex enterprise applications?</p><p>Complex enterprise products house multiple features and apps — spanning across hundreds of sections — for multiple specialized needs. A lot of these features and workflows are intertwined — one action affecting several others. <strong>Eliminating or separating functions may reduce the functionality and utility.</strong></p><p>Thus, the go-to strategies of breaking down processes, separating content into pages, hiding away complexities within menus and cards to unclutter the UI may end up adding structural or navigational complexity. The <a href="https://www.nngroup.com/articles/interaction-cost-definition/">interaction cost </a>may <a href="http://www.guuui.com/issues/04_03.html">offset or even overshadow that usability improvements through the visually simple UI</a>.</p><p>Balancing the information density (data, control panels, interconnected features) with a simple user interface is surely a daunting task.</p><p>But the good news is that irrespective of the domain and the exact information, underlying usability principles, and design and interaction patterns still apply. If applied well, a high density page need not be cluttered or compromise usability.</p><h3>Before you begin</h3><ul><li><strong>Know your users’ goals:</strong> As in any other design decisions, understanding user goals, workflows is essential to understand their needs and priorities. Users don’t want to see all the data, they want to see the data they need at that point. Knowing your user will give you a better idea of what those needs are for each point. Trying to guess or making assumptions about the most common or popular tasks may backfire. If your product has multiple user groups, you need to consider all the different roles, their goals, and the level of expertise, and their cognitive capacity.</li><li><strong>Know your data:</strong> Working with real data and having a correct estimate of quantity (list items, table rows, article length, etc.) &amp; quality of data helps to visualize and consider all possible scenarios and edge cases. Understand the variables, what answers do they provide to users and how they are interconnected.</li><li><strong>Know your design goal:</strong> Have a decided goal for every page and section before starting the designing process. That would help in deciding the information architecture. If applicable, consider future feature additions — design with scalability in mind.</li><li><strong>Know your product implementation:</strong> Lags, waiting time, handling errors, disconnected workflows may play a part in design decisions.</li></ul><h3>Progressive Disclosure</h3><p>Before moving to definitive UI patterns, let’s talk about the overall approach for handling information-density: <a href="https://www.nngroup.com/articles/progressive-disclosure/">Progressive Disclosure</a>.</p><p>Progressive disclosure is a strategic approach for managing information complexity by showing only the information necessary at a point in the interaction, and revealing more content as the user interacts with the interface. In short, it’s about deciding what needs to be visible upfront and what can be a click or a scroll away.</p><p>Progressive disclosure isn’t exclusive to UI design —<a href="https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism)"> inverted pyramid (journalism)</a> and <a href="https://www.mat.ucsb.edu/~g.legrady/academic/courses/11w259/schneiderman.pdf">Ben Shneiderman’s visual information-seeking mantra</a> are similar approaches.</p><h3>UI Patterns</h3><p>Alright, now finally let’s look at the design patterns.</p><h4>Modals</h4><p>Modals (or overlays/dialog-boxes) seem to be a most-loved pattern in a lot of feature-heavy interfaces. It also seems to be the most misused pattern — as a way out of redesigning existing screens as more features mushroom within the app. This contributes significantly to UX debt.</p><p>Yet, used correctly, modals can be an effective and efficient design pattern.</p><p>Modals provide a way to direct users&#39; complete focus on a workflow, making it highly powerful for confirmation screens, alerts (‘You are being locked out’) and warnings, onboarding, etc.</p><p>Modals can be used for simple tasks (ex: adding or editing a field) instead of redirecting users to a new page.</p><p><strong>When not to use modals</strong></p><ul><li>The overlay to isolate the flow also means loss of context, information and functionality (ex: copy/paste) from the original screen. <a href="https://uxplanet.org/modality-the-one-ux-concept-you-need-to-understand-when-designing-intuitive-user-interfaces-e5e941c7acb1">Use modals only for self-contained methods</a>.</li><li>Don’t use modals to show information unrelated to task, or to show error messages of tasks completed on the main page.</li><li>For more complex processes, it’s better to utilize the full available real-estate. If not, consider breaking down the process into stepped modals.<br>Don’t nest another modal or pop-up within a modal!</li><li>Avoid uninitiated pop-ups. One exception to this is the session expiry message.</li></ul><p><strong>Design considerations for modal</strong></p><ul><li><a href="https://ux.stackexchange.com/questions/39298/research-on-scrolling-within-modal-web-pros-cons">Scrolling</a>, exiting behavior.</li><li>Placement on screen</li></ul><p><a href="https://www.nngroup.com/articles/modal-nonmodal-dialog/">This NN/g article is a comprehensive dive into best practices for modal &amp; nonmodal dialogs</a>.</p><h4>Accordions</h4><p>Accordions are the archetypal design pattern for progressive disclosure — vertically stacked list of headers that can be clicked to reveal or hide content.</p><p>This is a perfect pattern <strong>for optional or advanced details</strong> which aren’t required frequently. Or when there are multiple user groups interested in different data. Accordions reduce the amount of information presented initially and reduce scrolling.</p><p>Headings increase the glanceability &amp; users can decide what information they want to see.</p><p>An advanced pattern of accordion is <strong>expandable table rows</strong>.</p><p><strong>When not to use accordions</strong></p><ul><li>Do not use accordions if users need to necessarily or frequently see all or most of the hidden content. That just adds clicks and makes the interaction bulky.</li><li>Lengthy accordion content can lead to confusion in navigating — if the content is longer than viewport, context of the section they are in may be missing. Also, consider also the case of scrolling to close.</li></ul><p><strong>Design considerations for accordions</strong></p><ul><li>Use proper descriptive headings — they give an idea about the content and serve as navigation marks.</li><li>Plan for the interaction experience. There is a layout shift in opening and closing accordions — account and design for that experience.</li></ul><p>This<a href="https://www.smashingmagazine.com/2017/06/designing-perfect-accordion-checklist/"> Smashing Magazine article dives into all the design details to consider in accordions</a> while this <a href="https://www.nngroup.com/articles/accordions-complex-content/">NN/g cautions against incorrect usage of accordions</a>.</p><h4>Dropdown Menus</h4><p>Dropdowns are a handy way to group and list options, menus or commands.</p><p>This is a familiar pattern.</p><p>Dropdowns are a good option when there are too many actions available in a section(ex: the menu buttons on a browser). Hiding rarely used actions in dropdowns reduces the noise and cognitive load for primary actions.</p><p><strong>Mega-menus</strong> are an advanced version of dropdowns where the choice becomes progressively more specific. They can also come with certain <a href="https://www.smashingmagazine.com/2021/05/frustrating-design-patterns-mega-dropdown-hover-menus/">interaction frustrations</a>.</p><p><strong>When not to use dropdowns</strong></p><ul><li>Do not hide primary or frequently used content in dropdowns.</li></ul><p><strong>Design considerations for dropdowns</strong></p><ul><li>Consider the findability of items within the menu — create meaningful orders and grouping. Make it searchable.</li><li>For disabled options, have an accessible way of communicating the cause of unavailability.</li></ul><h4>Tabs</h4><p>Tabs are another pattern to alternate between sections in a page. They are a great way to meaningfully separate content into sections and make visible to users what content is available to them. Tabs can also be used to create alternate views of same content for different goals.</p><p>Tabs are best used as primary/secondary navigation or as in-page components when only a section changes. If majority of the page including the primary/secondary menu, maybe a different pattern is more applicable.</p><p>Tabs can be horizontal or vertical. Vertical sidenavs can be a scrollable section in case of too many sections.</p><p>A more complex version of vertical tabs is a <strong>tree structure</strong>.</p><p>Tabs are best used for a limited &amp; fixed number of options — all the tab headings should be visible. The number of sections may be a factors (in combination with other layout pattern ) for determining the orientation.</p><p><strong>When not to use tabs</strong></p><ul><li>Do not use multiple rows/columns of tab items.</li><li>Tabs shouldn’t be used to separate related content or when users may need to see two sections simultaneously. Tabs sections should be similar — a good way to judge is to see if all the tab headers can be logically put into a product (Ex: Gmail’s primary, social tabs are different categories of mail). Try to keep content and interaction similar across the tabs.</li><li>Don’t use tabs if the number of sections are dynamic or may grow in future.</li></ul><p><strong>Design considerations for tabs</strong></p><ul><li>Make the headers short and clear.</li><li>Correctly prioritize the importance and order of tabs in choosing the initial/default view.</li><li>Make tabs visually distinct from links.</li><li>Keep the header sticky if content is longer than viewport (scrolling).</li><li>Content amount in the sections should be approximately same to avoid layout shifts while tabbing.</li></ul><h4>Tables</h4><p>Tables are a good way to organize information and make use of the available real estate. Moreover, sorting, filtering, etc. improves the data consumption experience.</p><p>Pagination helps in decreasing loading time, again adding to the benefits.</p><p>More advanced options like expandable rows as mentioned before are other ways to further increase the efficiency of this very useful pattern.</p><p><a href="https://uxdesign.cc/data-table-for-enterprise-ux-cb48fb9fdf1e">This article lists a number of advanced table UI and interactions for complex data</a>.</p><h4>Cards</h4><p>Cards are a design components to group information and actions of a particular item. Cards help surface the most important bits of data and action of list (grid) items to the surface while pushing the meaty details behind another click. They may be easier to skim and look cleaner than tables when there are a lot of meta-data to display.</p><h4>Truncated Content</h4><p>For long text, truncating content with a ‘Read More’ button is another way to save real-estate in a page.</p><p>This is best used for secondary or rarely read meta information (product description in Amazon) or previews (review list in Goodreads).</p><p>If this is a commonly required content or the main content (ex: the content of the blog in the article page), then it’s better to show the whole content and give it it’s own page.</p><h4>Scrolling (&amp; Inline scrolling)</h4><p>Scrolling isn’t as bad as it seems to be. Studies have <a href="https://articles.uie.com/page_scrolling/">disproved the myth that users are</a> unwilling to scroll.</p><p>Scrolling doesn’t negatively affect the experience if content is well-organized and scrollable. If they can easily locate their content with a<strong> </strong><a href="https://www.nngroup.com/articles/scrolling-and-attention/"><strong>reasonable</strong> amount of scrolling</a>.</p><p>Inline scrolling refers to adding independent scrolling to sections of a page. This provides a way to cramming more information in the page, but at the cost of <a href="https://baymard.com/blog/inline-scroll-areas">confusing interactions and reduced usability</a>. Thus, this is better avoided.</p><h3>Bringing it all together</h3><p>In a page all of the patterns work in conjunction with each other for the ultimate UX. Consider the strengths and interactions and how they may work with or against other patterns.</p><figure><img alt="An wireframe of slack annotated to show a few of the design patterns mentioned in the article" src="https://cdn-images-1.medium.com/max/1024/1*bBm5IpckwQvxcHOOgKCe9Q.png" /><figcaption>Example of design patterns in usage. Guess the app :P</figcaption></figure><p><a href="http://designingwebinterfaces.com/designing-web-interfaces-12-screen-patterns">Theresa Neil’s 12 Standard Screen Patterns</a> is a great reference for common familiar page layouts.</p><p>What you use in your design will ultimately depend on your specific use case.</p><p>But it’s better to know the strengths, pitfalls, and constraints of patterns available — no use reinventing the wheel. Also, having a good understanding of the standard helps to adapt it for our purposes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*HkAmGS_LiByelZiT.png" /><figcaption>The UX Collective donates US$1 for each article we publish. This story contributed to <a href="https://www.wcd.school/">World-Class Designer School</a>: a college-level, tuition-free design school focused on preparing young and talented African designers for the local and international digital product market. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69775165a18e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-for-information-density-69775165a18e">Designing for information density</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design principles to revisit for Voice UX]]></title>
            <link>https://uxdesign.cc/design-principles-to-revisit-for-voice-ux-design-5a8b6fd0e8ed?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a8b6fd0e8ed</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Mon, 10 Jun 2019 14:18:04 GMT</pubDate>
            <atom:updated>2019-06-18T14:58:18.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WOoCw3a1MqV-oYX5" /><figcaption>Photo by <a href="https://unsplash.com/@inakihxz?utm_source=medium&amp;utm_medium=referral">Iñaki del Olmo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>1. Hick’s Law</h4><p><a href="https://www.interaction-design.org/literature/article/hick-s-law-making-the-choice-easier-for-users">Hick’s law</a> is a psychological principle which states that the more options are available to a person, the longer it will take for him or her to make a decision about which option is best.</p><p><strong>Where can we apply it in VUX design:</strong><br>When presenting users with a list of options to choose from, don’t overwhelm users with too many choices. Limit number of options to three.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*Slacv-ICw9lm7shHPkcjQA.png" /></figure><h4>2. Serial Position Effects</h4><p><a href="https://en.wikipedia.org/wiki/Serial-position_effect">Serial-position effect</a> is the tendency of a person to recall the first and last items in a series best, and the middle items worst.</p><p>There are two main concepts involved in the serial position effect:</p><ol><li><strong>The </strong><a href="https://www.interaction-design.org/literature/topics/primacy-effect"><strong>Primacy Effect</strong></a><strong>: </strong>Items that are presented at the beginning of a list are recalled with greater accuracy than items in the middle of a list.</li><li><strong>The </strong><a href="https://www.interaction-design.org/literature/topics/recency-effect"><strong>Recency Effect</strong></a><strong>: </strong>Items that appear at the end of a list are also more likely to elicit better recall than items presented in the middle of a list.</li></ol><p><strong>Where can we apply it in VUX design:</strong><br>In dialogue design, include the most important information at the beginning or the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*pQu1xn0jZztS2Ntv5TN_TQ.png" /></figure><h4>3. Progressive Disclosure</h4><p><a href="https://www.interaction-design.org/literature/topics/progressive-disclosure">Progressive disclosure</a> is an interaction design pattern that sequences information and actions across several steps.</p><p><strong>Where can we apply it in VUX design:</strong><br>Don’t ask for more than one information during a prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*NgK1G3hVBCAzvxrG-71p1w.png" /></figure><h4>4. Five Hat Racks</h4><p>Originally stated by the information design guru Richard Saul Wurman, the <a href="https://infovis-wiki.net/wiki/Five_Hat_Racks">Five Hat Racks</a> theory states that there are only five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse)</p><p><strong>Where can we apply it in VUX design:</strong><br>Grouping or chunking things based on these categories can be a way to increase the number of choices without overwhelming the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*vzy2q1JT0nWS7JxyJUNtQA.png" /></figure><h4>5. Framing</h4><p>The <a href="https://en.wikipedia.org/wiki/Framing_effect_(psychology)">framing effect</a> is a cognitive bias where people decide on options based on if the options are presented with positive or negative semantics; e.g. as a loss or as a gain.</p><p><strong>Where can we apply it in VUX design:</strong><br>In error cases, offer a way to correct the error and continue, rather than only an error message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*bTeioqRidAbfbd3bvRpjIA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a8b6fd0e8ed" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-principles-to-revisit-for-voice-ux-design-5a8b6fd0e8ed">Design principles to revisit for Voice UX</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maybe your voice assistant needn’t do it all]]></title>
            <link>https://uxdesign.cc/maybe-your-voice-assistant-neednt-do-it-all-41971455f?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/41971455f</guid>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Sun, 09 Jun 2019 02:51:46 GMT</pubDate>
            <atom:updated>2020-03-04T19:25:29.930Z</atom:updated>
            <content:encoded><![CDATA[<h3>Maybe your voice assistant need not do it all</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*99XG1fInqEFBuDXYYb6PCw.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@rawpixel?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">rawpixel.com </a>from <a href="https://www.pexels.com/photo/photography-of-people-using-smartphones-1413653/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Voice interfaces have finally made the jump from science fictions to the realm of current technological possibilities. And it’s currently seeing a huge mass-market adoption.</p><p>From the perspective of User Experience (UX) design, this is an opportunity to apply the principles of the user-centered design to shape the young technical capability. And we designers are already on the task — working hard to supplant all earlier ‘primitive’ interfaces with the ‘natural’ interface.</p><p>But are there any problems with such a focused approach to Voice User Interface (VUI) design?</p><p>To answer that, let’s look at two important challenges which we are trying to tackle in VUIs.</p><h4><strong>1. A voice assistant should sound ‘human’</strong></h4><p>Any voice interface today is modeled on human conversation behaviors. But is that a case of designers basing their designs on their own mental models?<br>I am not denying that human’s conversation would influence a user’s perception of a Voice User Interface (VUI) — in fact, there are a lot of articles outlining how significant that influence is. However, that isn’t the only factor influencing the user’s mental model. User’s perception of a user interface (UI) is also influenced by GUIs, IVRs, chatbots, and any interaction with machines as well.</p><p>So, while they expect the freedom to speak to the machine ‘in their own tongue’, they may also rely on common vocabulary with ‘machines’ (ex: ‘log out’, ‘check-out’) Speaking keywords is cognitively less taxing than formulating complete phrases. So, maybe, for first-time users, it is ok to list down possible commands ‘robotically’ rather than ask open-ended questions (and wait for no-user-input error state to read out these options).</p><p>Secondly, VUIs can give a terse response for confirmation states rather than try to sound witty every time. There are two reasons for this — first, witty/lengthy responses every time voids the intention of using voice for speed. An experienced user doesn’t require the level of confirmation. Second, while this doesn’t seem to be a problem now, when the breadth of VUI usage of a user increases, this may become irritating. This has already been demonstrated by the enthusiasm by which <a href="https://www.reddit.com/r/amazonecho/search/?q=brief%20mode&amp;restrict_sr=1">Reddit users are embracing Alexa’s brief mode</a>.</p><p>Third, there is the ambiguous question of how much we want a machine to sound like a human. The entire <a href="https://www.fastcompany.com/40588020/the-case-against-teaching-kids-to-be-polite-to-alexa">‘should you say please to Alexa’</a> boils down to a basic fact — should we treat VUIs as human? There is no clear answer yet.</p><p>Of course, chatbots and services <a href="https://www.aarp.org/home-family/personal-technology/info-2018/isolation-loneliness-technology-help.html">designed specifically for banter</a> are exceptions.</p><h4><strong>2. Voice can/needs to support everything</strong></h4><p>Currently, services arenas are rushing to jump on the VUI bandwagon — from education to healthcare to banks. But can and should everything be supported by voice?</p><p>Some tasks are less efficient by voice. While it is easier to speak a command to complete or reach the end stage of complex tasks, it is much easier to glance over a list on screen than have an assistant read it out. Also, GUIs have made a lot of progress in increasing glanceability through icons. VUIs don’t have anything concrete corresponding to icons yet.</p><p>However, the above point becomes void when the assistant is smart to choose and read out only the ‘best’ and ‘personalized’ result for you.</p><p>Which brings me to my next point. <a href="https://fs.blog/2017/07/filter-bubbles/">Filter bubbles</a>. The term “filter bubble” refers to the results of the algorithms that dictate what we encounter online. According to Eli Pariser - the person who first coined the term - those algorithms create “a unique universe of information for each of us … which fundamentally alters the way we encounter ideas and information.”<br>It&#39;s important to note that while adults are mostly using VUIs for a few tasks and simple questions, <a href="https://www.forbes.com/sites/forbestechcouncil/2018/06/08/the-hyper-adoption-of-voice-technology/#17ffdaba7058">kids using VUIs from a young age are using VUIs to find answers for all of their questions.</a> <strong>As designers, shouldn’t we take into consideration the effects of our designs on such a vulnerable target group?</strong></p><h3>So, is voice bad?</h3><p>I am not contesting against the usefulness of VUIs. It is undoubtedly a powerful platform. <strong>However, design decisions shouldn’t be made to forcefully fit voice technology.</strong></p><p>Voice is another tool for designers to tackle challenges in human-computer interaction. It is a versatile tool, not one that can supplant every other tool. Every type of interface has its unique benefits, behavioral or technical, that works for certain types of users or situations.</p><p>All in all, voice is supposed to be the infrastructure for user experience, and not the end goal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41971455f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/maybe-your-voice-assistant-neednt-do-it-all-41971455f">Maybe your voice assistant needn’t do it all</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Voice Interaction Flows]]></title>
            <link>https://uxdesign.cc/ux-design-for-voice-interfaces-part-ii-3b0056020cd3?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b0056020cd3</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Mon, 31 Dec 2018 04:31:04 GMT</pubDate>
            <atom:updated>2019-01-01T04:46:46.284Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part II</h4><h4>UX Design for voice interfaces</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9J083mH7dcsti72x" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>This is the second of a 3-part series on my design process for Voice Interfaces. The </em><a href="https://uxdesign.cc/no-my-voice-assistant-neednt-read-me-my-social-media-feed-69052144b6f0"><em>first part</em></a><em> covered defining the product. This part is about designing the conversation.</em></p><p>Voice interfaces are now implicitly expected to be conversational — as opposed to command-based modality and/or one-turn exchanges. <br>Designing a conversational interface involves influencing user requests to, and modeling the responses from our voice agent.</p><p>A voice input or request has two layers:<br><strong>Utterance:</strong> What the user says is a user utterance. Basically, an utterance is how a user phrases a request.<br>Example: A user can frame a request in any of the following ways:<br><em>“Set an alarm for 8&#39;o clock”<br>“Alarm 8 a.m”<br>“I want to set an alarm”<br>“Wake me up at 8”</em></p><p>These are just a few. There may be1000 ways to ask to set an alarm.<br>While it is not possible to list the exhaustive set of utterances for any given goal, listing a few variations <em>would be helpful in later part of the process.</em></p><p><strong>Intent: </strong>This is the main objective behind any user request.<br>Example: In the above cases, the intent is to set an alarm. <br>Intent can be again divided into two types: primary intent is the actual task the user wants to do.<br>Secondary intents are for tasks to complement <strong>primary</strong> tasks.<br>Example: If the primary intent is to order a coffee, choosing a delivery address different from the default one could be a secondary intent.</p><p><strong>Our assistant will support all primary user intents which correspond to the goals identified in the previous step.</strong></p><p>(<em>Any intent mentioned from here on will refer to a primary intent</em>)</p><h4>Conversation Modelling — Happy Flow</h4><p>For a particular intent, we first model a complete conversation for the ‘happy paths’. ‘Happy paths’ are ones in which the user reaches the ideal outcome in the least (or within a certain) number of steps.<br>This step also helps us recognize the <strong>‘slots’ or ‘variables’</strong> required to fulfill the request. <strong>Variables </strong>are inputs or additional information which the user needs to provide to complete the intent.</p><p>Example:</p><blockquote>User: I’d want to order a <strong><em>Salted Caramel Mocha Frappuccino</em></strong><br>Assistant: Sure, what size would you like?<br>User: <strong><em>Grande</em></strong><br>Assistant: 1 Grande Salted Caramel Mocha Frappuccino. Would you want it delivered to your <strong><em>office</em></strong>?<br>User: Yes<br>Assistant: Ok. Should I order it?<br>User: Wait, I would like <strong>non-fat milk</strong><br>Assistant: Sure. Changed your milk preference to non-fat milk. Should I confirm the order?<br>User: Yes <br>Assistant: Order placed successfully. Your coffee will be reach you soon.</blockquote><p>This is one possible way by which a user can complete a coffee order. Users may provide different amounts of information, and in different ways. Some may give all the information up front, while others provide it piece by piece. Some may have a lot of information to add, others just the mandatory information.<br>To handle this, the assistant needs to know the <strong>mandatory variables </strong>in what order to ask for them to complete the flow (in the above example in bold). These variables are necessary to complete the request.<br>The assistant needs to be, also, able to understand the <strong>optional variables</strong> (in the above example in bold italics). These are filters/customizations or choices to over-ride defaults, which users may request.</p><p>At the end of this step, we list out these mandatory variables, and all the optional variables we can think of, before we proceed to the next step.</p><p>The catalogue of utterance variation,<strong><em> </em></strong><em>carried out</em><strong><em> </em></strong><em>earlier,</em> increases the chance of stumbling upon all<strong> </strong>possible<strong> variables </strong>in a flow.</p><h4>User flow</h4><p>Now it is time to extensively chart out all possible ‘flows’ or paths to complete a goal. It takes into account all the ways that a user may choose to phrase a request.</p><p><strong>Prompts</strong> will be designed to ask for any missing mandatory variable &amp; get the user to goal completion through the most optimized path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOGz5SpTNA-o1OoXSfGR2A.jpeg" /><figcaption>Sample flow</figcaption></figure><p>The flow needs to handle edge cases and error cases.<br>Example of possibilities to consider when creating flows:<br><strong>Invalid requests — </strong>User asks for something which is not possible.<strong> (</strong>ex:<strong> </strong>“Rate Ready Player Five 6 stars on Goodreads” or “the fifth one” while choosing from a list of 4 items<strong>)<br>Details in Multiple results — </strong>How much information to give out in case of multiple results<strong> (</strong>ex: “What do I have planned today”? — if there are 5 results, how do you read it out: summarize, read out 1 in detail and wait for user to say “next”, or read out the title of each<strong>)<br>Disambiguation — </strong>Some user requests may have ambiguous variables and require a little clarification before they can be fulfilled. Policies need to be defined for such cases. (ex: if user says weather in Springfield, you may ask each the user to clarify of the 34 Springfields they mean, or choose one based on their past behavior, or which is nearest)<strong><br>Empty result state —</strong>We cannot forget about the<strong> </strong>‘0 results’ found pages. Without any specifically added responses for those cases, the default dialogues may end up sounding very mechanical (ex: “Find me non-stop AA flights from San Francisco to Vancouver” — there are no matching results.The assistant shouldn’t respond with “I found 0 results”.<strong>)<br>No user response — </strong>Sometimes,<strong> </strong>the user may fail to answer within the response time after a prompt. There’s no way of knowing why a user didn’t reply, but repeating the same prompt again may not be the best available option. What should be the behavior for a particular state - Can we consider providing hints as to what they can say? Ask for a different piece of information, or phrase the earlier question in a different way? Not do anything?<strong><br>Over-answers —</strong> User may provide more information than what is being prompted. Of course, it depends on the platform capability, but the best experience is for the platform to be able to accommodate such cases. Asking for information which user has already provided makes the system look stupid. (ex: <br>Use: Set me a reminder<br>Assistant: What is this reminder for?<br>User: “Doctor appointment for 4 p.m. tomorrow</p><p>User has already provided the time for the appointment. So, it’s better not to prompt them for it again)<strong><br>Optional variables — </strong>While user shouldn’t be prompted for optional variables, they shouldn’t be prevented from providing them either. So, the VUI should make accommodations to support such requests. In other words, we need to make sure that the conversation shouldn’t fall apart (“I am sorry, I don’t understand that) when user says “with extra Chocolate curls” instead of “yes”/ “no”.<strong><br>Intelligent Learning (over time)—</strong>Are there any prompts that can be removed over time as the system learns more about the user? (“Book me an Uber” — if the user regularly requests Uber at 5 p.m. from his office location, maybe we can avoid asking the user for destination under those circumstances; inform the user of the assumption directly in the confirmation state. However, user should be easily able to override such defaults.)<strong><br>Context-retention—</strong>Natural conversations are not always one-turn.We need to consider how user may follow up after any response. (ex: “Is it going to rain today?” followed by “What about weekend?”)<strong><br>No hierarchy — </strong>Unlike GUIs, there are no back buttons in voice interfaces. Conversations only move forward. The user should be able to provide additional (optional) information at any stage without losing any previous progress. (Example: In the above happy path, modifying the type of milk during confirmation did not require the user to provide delivery address again)<br><strong>Feedback of cancellation — </strong>Conversations don’t end abruptly. So, it’s necessary that we make sure to account for cases where user cancels a flow, or doesn’t opt for any suggested action. The assistant should provide the proper feedback that the task has been cancelled.<br><strong>No assistant response </strong>— In some cases like “Play music”, “Turn on lights”, assistant needn’t give any reply, and just complete the task. These kinds of design specifications should also be included in the VUI.</p><h4>Sample dialogue</h4><p>Once we have finalized the flow, we can phrase the assistant responses or <strong>dialogues</strong> to make your interactions feel natural. Moreover, we need to adjust the language and tone to align with the persona we have defined for the assistant.</p><p>At this step, it helps to go back to the utterance variation catalogue and test if the dialogues seem ‘natural’ with any user utterance. If not, some response variation needs to be added &amp; mapped to different user utterances.<br>Example: will the assistant response work for both “I’d want to order a Salted Caramel Mocha Frappuccino” and “Is it possible to get a Salted Caramel Mocha Frappuccino delivered now?”</p><p>Variations of responses are added so that the responses don’t feel repetitive and robotic.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b0056020cd3" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-design-for-voice-interfaces-part-ii-3b0056020cd3">Creating Voice Interaction Flows</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Requirements for Voice Interfaces]]></title>
            <link>https://uxdesign.cc/no-my-voice-assistant-neednt-read-me-my-social-media-feed-69052144b6f0?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/69052144b6f0</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[voice-ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Sat, 17 Nov 2018 00:26:40 GMT</pubDate>
            <atom:updated>2019-10-04T08:05:10.169Z</atom:updated>
            <content:encoded><![CDATA[<h4>Defining UX requirements for a Voice User Interface Product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pB1rCPy8Ksy2Yqkr" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I have been designing Voice UX for about two and a half years. During this period, I was lucky to get to work on a plethora of domains, devices, <em>and</em> platforms. I have had opportunities to work with a melange of designers and add new tools to my skill set.</p><p>I also got a chance to experiment with my process — from implementing theoretical methods, borrowing from my fellow designers, learning from my pet projects.</p><p>Here, I am trying to document my Voice User Experience(VUX) design which I have now roughly settled on. (I am no way claiming that you should adopt this process, or that it is the best/only process. I am sharing my two cents, on the off chance that somebody finds it helpful.)</p><p>Ok, so here goes..</p><p>When designing for Voice, I can roughly divide my work into three phases: 1. Discover &amp; Define 2. Ideate &amp; Design 3. Evaluate</p><p>In this post, I would expand on the <strong>Discover &amp; Define</strong> phase. This phase is a collaboration with Product Managers(PM), Developers, and Marketing teams.</p><h4>Project Kick-off &amp; Validation</h4><p>The starting point for any project is a loose brief of the project idea — the high-level purpose of the project. <br>Ex: <em>I want users to be able to access Goodreads through voice.<br>(I will be using a Goodreads voice app as an example throughout the article)</em></p><p>To check the possibility of a compelling product, a research phase is necessary. The following needs to be covered: <br>1. <strong>User Needs:</strong> What is the user need that the product is addressing? What are the main tasks users will be performing? Who is the target audience, and what are their expectations from a voice interface? <br>The methods used could be primary (user interviews), or secondary ( existing research, analytics from an existing product).</p><p>2. <strong>Competitor Audit:</strong> If a similar product exists in the marketplace, looking into its user reception &amp; feedback helps to find points of interest. Moreover, this gives an idea regarding user mental models &amp; expectations.</p><p>3. <strong>Research the platform/tech:</strong> If working on a new voice platform, it is very important to grasp its capabilities &amp; limitations. Points considered are follow-up support, multiple-user support, barge-in command support, anaphora, etc. (If you are completely new to voice interfaces, you can refer to <a href="https://medium.com/@joshdotai/16-voice-control-terms-you-need-to-know-4a79303db08a">this VUI glossary </a>to understand a few jargons.)</p><p>Another important consideration is if the platform has/needs a display component. <a href="https://www.uxmatters.com/mt/archives/2018/10/voice-first-versus-the-multimodal-user-interfaces-of-the-future.php">That will impact the supported features and goals.</a></p><h4>User Scenarios</h4><p>Based on the (primary/secondary) research, we can now create a few core user scenarios.</p><p>Ex: in Goodreads, few user scenarios:</p><ol><li><em>John’s friend, Andrew mentions an amazing book he has recently completed. He insists that John should definitely read it. John adds the book to his ‘to-read’ shelf.</em></li><li><em>Sally is binging on Netflix after a long day at work. The title of the book in one of the character’s hand looks quite appealing. She looks up the book on Goodreads.</em></li></ol><p>Mostly, the core functionality of an app becomes the most important user scenario. Ex: a weather app offering information on weather, and alerts. However, in some cases, that may not hold true. Ex: in Goodreads, scrolling to check friend’s activity doesn’t seem a scenario for voice interface.</p><h4>Journey Mapping</h4><p>For each of the user scenarios, we outline the user journey to find where voice modality can fit in. <br>We look into each step to see voice is suited to complete the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*rsd1A0tZlGElpMXiBS-kjw.png" /><figcaption>Here, all the steps can be supported by voice</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*HwXe5HtuOFy-6hMRZIhEpg.png" /><figcaption>Voice-only may not be the best medium for the last task</figcaption></figure><p><em>For beginners, </em><a href="https://www.webcredible.com/blog/designing-voice/"><em>Webcredible’s checklist</em></a><em> is a good resource about deciding if voice would be a correct modality for a task.</em></p><h4>Defining Goals/Capabilities</h4><p>From the journey maps, we can now decide the user goals that will be supported:<br>1. If all the steps are suitable for voice, <strong>and</strong> the platform supports all the tasks, that journey can be a goal.<br>2. If a step is not suited for voice, is it possible (good UX) to complete a part of the task, and let the user finish the rest (synced device)? If so, it can be added as a goal.</p><p><em>Goal 1: Look up a book.<br>Goal 2: Look up rating of a book<br>Goal 3: Mark a book as to-read, currently reading, read<br>etc.</em></p><p>Note: For some cases, some core goals need to be added even if they don’t fulfill these criteria. <br>Ex: A banking app needs to handle <strong>the user utterance</strong> to transfer money, even if the platform/tech doesn’t handle it. Designing for that goal is all about the best way of error-handling.</p><h4>Defining Personality</h4><p>In voice interfaces, the product’s personality is overt. The personality is defined by the voice and tone of verbal interactions. <br>For existing services, personality may already be defined. That can be referenced to maintain a consistent personality across mediums. <br>If the personality is yet to be created, it needs to <a href="https://alistapart.com/article/personality-in-design">align with the product’s purpose</a>.</p><p>Also to be factored in is the platform’s defined persona, ex: <a href="https://developer.amazon.com/docs/alexa-design/design-form.html#alexa-is-a-persona-not-the-device-itself">Alexa has some defined rules regarding her behavior.</a></p><p>This concludes the define phase. <br>Documents at the end of the phase: The Product Spec, usually maintained by PM. (This may get updated later, based on unforeseen issues during design and development phase)</p><p>Note: I am in no way affiliated to Goodreads, just a frequent user of the product.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69052144b6f0" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/no-my-voice-assistant-neednt-read-me-my-social-media-feed-69052144b6f0">UX Requirements for Voice Interfaces</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning to voice interface design]]></title>
            <link>https://uxdesign.cc/ux-design-for-voice-interfaces-789a934e3b51?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/789a934e3b51</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Fri, 20 Jul 2018 14:26:59 GMT</pubDate>
            <atom:updated>2018-08-02T12:20:30.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVu5_G5zGM040x66Y9_a5w.jpeg" /></figure><p>With voice interfaces, a whole new avenue is opening up for UX designers to design better, intuitive, human-centered experiences. While the principles of user-centered design remain same across all mediums, there are few differences when translating from screen-based interfaces to voice. Below listed are few things I learned over the last two years designing for Voice.</p><p><strong>Define your product AND communicate that to user<br></strong>Defining the end-product is the first step in any UX design process. Voice is no exception. You start by defining what your system will and won’t do.</p><p>In visual interfaces, the GUI provides the affordance for supported tasks. In VUIs (Voice User Interfaces), the only way for user to discover supported tasks is through trial and error- trying different commands and their variations. So, in voice, it becomes very important to communicate to the user at the onset what can be done, and what cannot. For example: the assistant may be able to complete the primary tasks of a service (book a cab) , but not handle secondary tasks of the same (previous ride details).</p><p><strong>Replace user journey with user flow diagram<br></strong>A customer journey map is a visualization of the process that a person goes through to accomplish a goal.User flow diagrams visualizes the complete path in a product. They focus on a task to be accomplished by the user all alternative paths for accomplishing a goal, as well as the eventual next step.</p><p>In VUIs, you have no control over user utterances. There is no harm in going exhaustive and listing out all possible commands at any step of the process. For example: after user has asked a VA to read out a message, there can be a follow-up to forward it or read the ‘last’ one.</p><p>It is easy to forget some of the less common edge cases. But when you take the time to map everything out in a user flow diagram, you are forced to be thorough and think through every possibility.</p><p><strong>Defining the personality<br></strong>Voice interfaces ushers in with itself the inherent expectations of being ‘human’. To keep up this simulacrum, it is important that the personality of the agent is defined to make it more relatable, and relevant to the users. Defining the personality will be done based on brand identity of the company/service as well as the VUI’s defined role. The personality will define the tone, word choice (and the voice) of the agent.</p><p>You cannot really choose to ignore this step; remember that no personality is also a personality. If you don’t assign a personality to your product, the user will.</p><p><strong>UX writing, a.k.a Dialogue design</strong> <br>Unlike in GUIs, where an UX designer could get away with placeholder Lorem Ipsum to be later dealt with by UX/content writers, in VUIs that is not an option.</p><p>Dialogues are UI elements in VUIs. Dialogues need to written so as to sound natural, be clear, concise and align with the personality you have defined. So, make sure you <strong>design</strong> real dialogues instead of using fill-ins. design to speak .</p><p><strong>Testing</strong> <br>In case of GUIs, if development goes well, what you see (design) is what you get as the final product. That isn’t the case for VUIs. The deliverables you give will be written, but conversation are heard and not read. So, make sure that the final product actually aligns with the way you envisioned it. Based on what you hear, some tweaking may be required.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=789a934e3b51" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-design-for-voice-interfaces-789a934e3b51">Transitioning to voice interface design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges in designing Voice Interfaces]]></title>
            <link>https://uxdesign.cc/challenges-in-designing-voice-interfaces-9b25e3d572bd?source=rss-d53de65cf88------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b25e3d572bd</guid>
            <category><![CDATA[voice-ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[voice-interfaces]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Poulami Chakraborty]]></dc:creator>
            <pubDate>Fri, 01 Sep 2017 18:51:42 GMT</pubDate>
            <atom:updated>2019-02-05T09:13:29.484Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-eXkpk28Z2BmvyF4gX2rcQ.jpeg" /></figure><p>Voice is becoming a popular mode of interaction with technology. While it has long been touted as the next big thing, there are still a few major challenges in designing a voice assistant(VA).</p><p><strong>1.Expectation setting:<br></strong>At the onset, we have to understand that voice interfaces hauls in with itself the inherent expectations we have from speech based communications (with people)- contextual awareness, understanding of vocal communication(tone, pitch, volume, pauses, accents, emphasis) besides verbal language (actual words), high-level language concepts like idioms,metaphors, etc. While voice interfaces are beginning to tackle natural language commands and context-retention, it has still a long way to go before it reaches human-like level of NLU and intelligence. <br>For example:<br><em>What is </em><strong><em>last</em></strong><em> event in today’s program?</em><br><em>When was my </em><strong><em>last</em></strong><em> doctor’s appointment?<br></em>You could understand that ‘last’ in the second meant previous. But can your VA? <br>This is just a simple example. It will be a long time before all of these and the more complex nuances of language can be handled. <br>Till then, designing for voice will require a significant stress on expectation management. <a href="https://www.interaction-design.org/literature/article/how-to-manage-the-users-expectations-when-designing-smart-products">This article </a>has some great points about setting correct expectations.</p><p><strong>2. Capability Discoverability:<br></strong>In the absence of a visual interface, it becomes very difficult to relay to the user the potential and highlights of the system.This may play out in either of the two ways — users will stick to using only few features of the system, or they may try out a lot of commands to gauge the capabilities of the system. In the second case, if many queries fall into categories other than what was designed as your system’s biggest strength, user may never be able to discover all the features of your system and/or give up on it.<br>For example: based on Cortana’s capabilities, it was best positioned for the workplace, <a href="https://community.spiceworks.com/blog/2964-data-snapshot-ai-chatbots-and-intelligent-assistants-in-the-workplace">which was later proven</a>. Knowing this earlier would have prevented people forsaking it based on comparison with other VAs which are more suited for home environment.</p><p><strong>3. Handling distractions:<br></strong>In real life conversations as well in visual/touch interfaces, if you get distracted in the middle of a task, it is possible to later pick up the flow from where you left off. Same is not the case with voice interfaces- context is not retained for incomplete tasks. In addressing this issue, there will arise the subsequent problem of recounting to the user the state at which he/she left off and other details/data of the half-completed task.<br>For example: User gets interrupted while sending a message. Can they pick up from where they left off? If so, how can the VA evince earlier progress? Reading out everything (recipient, incomplete message, attachments) may irk the user. The policy could be also be to only give out the most important details like recipient (again, how to create a scalable policy for that?) before sending. One approach could be building in enough intelligence and natural language understanding to make the process user-initiated.</p><p><strong>4. Accessibility:<br></strong>In designing for voice interfaces, especially in voice-only systems, it is important to not completely exclude users with speech impairments such as articulation disorders, stuttering, etc. While the state will improve as speech recognition improves, for now we can design with empathy to handle back-to-back ASR(<a href="https://usabilitygeek.com/automatic-speech-recognition-asr-software-an-introduction/">Automatic Speech Recognition</a>) error.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b25e3d572bd" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/challenges-in-designing-voice-interfaces-9b25e3d572bd">Challenges in designing Voice Interfaces</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>