<?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 Dianne Hultquist on Medium]]></title>
        <description><![CDATA[Stories by Dianne Hultquist on Medium]]></description>
        <link>https://medium.com/@diannehultquist?source=rss-44547659fbee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*78Kbrc6g0izDvz1h9Zx_Qw.png</url>
            <title>Stories by Dianne Hultquist on Medium</title>
            <link>https://medium.com/@diannehultquist?source=rss-44547659fbee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:26:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@diannehultquist/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[The Hidden Considerations for Safe & Inclusive AI]]></title>
            <link>https://medium.com/@diannehultquist/the-hidden-considerations-for-safe-inclusive-ai-c2c6c03114f3?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2c6c03114f3</guid>
            <category><![CDATA[ai-safety]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[ethical-ai]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 04:05:06 GMT</pubDate>
            <atom:updated>2026-01-26T04:05:06.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TF8PV3iFs_M8Dbjfr5P8HQ.jpeg" /><figcaption>An assortment of helmets and harnesses hanging on a line</figcaption></figure><p>AI is evolving at an unreal pace. New capabilities emerge daily, while legislation and ethical frameworks lag far behind.</p><p>For conversation designers, this is where our responsibility comes into play. We’re shaping systems that talk, guide, persuade, and sometimes intervene in moments of crisis. Part of our role is to build AI that is safe and inclusive.</p><p>Here are some less‑talked‑about considerations that deserve a spot in the design process.</p><h3>Safety and Guardrails: Designing for the Real World</h3><p>Safety isn’t a feature. It’s a foundation. Your AI product might be operated by users in unpredictable contexts, and the stakes can be high.</p><h4>Design for the environment your AI lives in</h4><p>A vehicular assistant, for example, shouldn’t be as verbose as a search engine assistant. Since the user needs to focus solely on driving, the assistant should never encourage long interactions. Safety is the design. Direct and distraction‑free.</p><h4>Build escalation paths for harmful language</h4><p>AI should be able to recognise phrases or tones that indicate self‑harm, violence, or crisis. This doesn’t mean diagnosing or making assumptions. Instead, it should detect and confirm risk, then escalate appropriately. Maybe the best choice is to transfer to trained professionals, or instead to provide immediate crisis resources. Either way, the system needs a plan.</p><h4>Prepare for emergencies</h4><p>Some AI systems live within deeply personal and active parts of our lives, like those integrated in our cars, homes, or wearables.</p><p>These systems must recognize emergencies. That could mean detecting a crash, a fall, a break-in, or a distress phrase, then sending essential information to emergency services and connecting the user to paramedics.</p><p>A big caveat is that these flows must also be airtight. They require strong testing, as well as requiring user opt-in before going into effect.</p><h4>Handle boundary‑testing behavior</h4><p>Users will push boundaries. Some will be hostile. Some will be inappropriate. Your AI needs to respond safely and respectfully. That includes:</p><p>- de‑escalation strategies<br>- neutral, non‑judgmental language<br>- clear refusal patterns<br>- guardrails that protect both the user and the brand</p><h3>Accessibility &amp; Inclusion: Designing for Everyone</h3><p>AI is global by default. Your users may speak multiple languages, use assistive technology, or interact in contexts you didn’t anticipate.</p><p>A good starting point is asking the right questions:</p><h4>What kind of AI are you building?</h4><p>A voice assistant has different constraints than a chatbot. A multimodal system has different needs than a smart home device. A robotic assistant introduces physical‑world risks. The modality shapes the accessibility strategy.</p><h4>What languages do your users use?</h4><p>Not just the “official” ones. You may need to go deeper and consider dialects, slang, regional phrasing, code‑switching, and multilingual households.</p><h4>What accessibility standards does your organization follow, and what should it follow?</h4><p>WCAG may be the baseline, but it’s not the ceiling. Many organizations follow outdated or minimal standards simply because that’s the minimum.</p><h4>What problems do users already face?</h4><p>Look at:</p><ul><li>support tickets</li><li>chat &amp; call logs</li><li>app store reviews</li><li>complaints about competitors</li><li>friction points in your current product</li></ul><p>These are gold mines for understanding where accessibility is failing.</p><h4>What assistive technologies do users rely on?</h4><p>Ensure seamless experiences with screen readers, switch devices, voice control, captioning tools, hearing aids, and smart home integrations. Inclusion isn’t about adding features. It’s about removing barriers.</p><h3>Match Your Language to Your Users</h3><p>Your AI should speak at the level your users understand.</p><p>If your users are at an eighth‑grade comprehension level, the language your AI uses needs to be at an eighth-grade level. If your users need to navigate a complicated domain like healthcare, law, finance, or insurance, then your AI needs to use guiding language and simplified explanations. Your AI needs to meet your users where they’re at, not the other way around.</p><h3>Final Thoughts</h3><p>Conversation design isn’t just about crafting natural dialogue. It’s about anticipating risk, designing for diversity, and building systems that behave responsibly in the world. As AI becomes more embedded in daily life, the role of the conversation designer becomes more critical.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2c6c03114f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cheat sheet for Conversational Experiences]]></title>
            <link>https://medium.com/@diannehultquist/cheat-sheet-for-conversational-experiences-b9ddaac08942?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9ddaac08942</guid>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[conversational-ai]]></category>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 00:59:58 GMT</pubDate>
            <atom:updated>2024-11-11T00:59:58.102Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fC8AycDAyEtoYBpohuhPJA.jpeg" /><figcaption>Conversations in a cozy cafe</figcaption></figure><p>Let’s try dissecting a human conversation. Everyday convos have layers that enrich the exchange, like the visual aspect of seeing someone&#39;s face, hand gestures, and eye contact. Verbal signals also act as subtle cues, hinting at each other when they finish a thought, move on to a different topic, or wait for a response.</p><p>AI can’t replicate these nuances, at least for now. This presents a challenge to make chats more conversational.</p><p>So, here is my simple cheat sheet for adding a human touch to AI conversations.</p><h3>Transitions</h3><p>Think about how much you cover within a 5-minute conversation. It’s probably a lot, but it feels natural with phrases like <em>“Okay,” “That reminds me of…,” </em>and <em>“Yeah and then…”</em></p><p>Good transitions instantly harmonize your AI’s prompts and the user’s utterances to create a flowing conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Otq5smhWeeyfSbI1Gj2vpw.jpeg" /><figcaption>An example of a transition at the start of a sentence</figcaption></figure><p>Transitional language can be used to:</p><ul><li>Switch to a different topic:</li></ul><blockquote><strong>Before you go</strong>, would you like to take a quick survey on your shopping experience? <br><strong>Now</strong>, would you like to see how this design would look like in your home?</blockquote><ul><li>Make lists cohesive and non-repetitive:</li></ul><blockquote><strong>Previously</strong>, you ordered vitamins on February 20th of this year. <br><strong>Now</strong>, you have a new vitamin order on its way to be delivered on March 24th. <br><strong>Soon</strong>, your future vitamin order will be automatically refilled and delivered on April 24th.</blockquote><ul><li>Make time lapses feel less choppy:</li></ul><blockquote>Please wait while I check to see if we have tables available for a party of four. (after five seconds pass) <strong>Alright</strong>, I see that we have a table you can reserve right now.</blockquote><h3>Natural Language</h3><p>To put it simply, natural language means no awkwardness. This is how you can make sure everything your bot says will fit within the overall picture.</p><p>Aligning your bot’s tone and language with their persona is a good place to start. This persona has been tailored to consider the specific industry and brand identity your AI represents, which are the source of how all its conversations should be framed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fs4AOl0SsSLRJu9NhPBbDw.jpeg" /><figcaption>An example of different ways a bot can say the same thing</figcaption></figure><p>Think about whether it makes more sense for your bot to use <em>“isn’t,” “is not,”</em> or maybe even a mix of both. Maybe their persona is friendly and approachable, so it makes more sense for them to say, <em>“You can go through our review process”</em> instead of <em>“You may undergo our review process.” </em>Maybe your bot will represent a government agency, so it’s best to read <em>“Thank you, now you’ll be transferred to an agent”</em> rather than <em>“For sure! Hang tight while I get you to an agent.”</em></p><p>The main idea is to use language that feels natural for the type of bot and end users you’re designing for.</p><h3>Context</h3><p>Some personas stride the line between casual and formal. It’s tricky to find a balance between the two. Go too much one way, and your bot can sound stiff. Go too much the other way, and your bot can sound unreliable.</p><p>The tone you should go with will often fluctuate, which is why you, as a designer, should be guided by context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AwJZ_PCPiCGXwEeR76XZSA.jpeg" /><figcaption>An example of changing dialogue based on context</figcaption></figure><p>Times to consider context might be:</p><ul><li>The tone of a caller’s utterance:</li></ul><blockquote><strong>Bot</strong>: Sorry to hear that. Would you like me to place a new order, free of charge? <br><strong>User</strong>: Sure. <br><strong>Bot</strong>: Okay, I placed a new order for you.<br>VS<br><strong>Bot</strong>: Sorry to hear that. Would you like me to place a new order, free of charge?<br><strong>User</strong>: Ugh! I’m never buying from your company again!<br><strong>Bot</strong>: My apologies again. Would you prefer for me to get a refund started for you?</blockquote><ul><li>Emphasis on the state of what can or cannot be done:</li></ul><blockquote>Your primary doctor is currently out of office and they <strong>aren’t</strong> taking voicemails at this moment. Would you like to talk to a different doctor <strong>that’s</strong> available right now?<br>VS<br>Your primary doctor is currently out of office and they <strong>are not</strong> taking voicemails at this moment. Would you like to talk to a different doctor <strong>that is </strong>available right now?</blockquote><ul><li>How users got to this stage of the experience:</li></ul><blockquote><strong>Customers who chose to file a complaint at the NLU</strong>: We appreciate all feedback. First, please enter your email address.<br><strong>Customers who chose to submit a positive employee review at the NLU</strong>: We love rewarding employees who go the extra mile! For the first step, please add your email address.</blockquote><h3>Reduce Cognitive Overload</h3><p>Picture this: you think you’ve got the perfect dialogue for your bot, so you present it to your stakeholders. But after going through the flow, they feel confused and overwhelmed. What can you do to fix this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ippLqRfRjP1URf5rL2pEPQ.jpeg" /><figcaption>An example of cognitive overload</figcaption></figure><p>This scenario sounds like users are experiencing cognitive overload. You can address it by:</p><ul><li>Keep language at a 5th-grade comprehension level:</li></ul><blockquote>Would you like to apperceive one of our wines selected from our connoisseurs?<br>VS<br>Would you like to try one of our expert-selected wines?</blockquote><ul><li>Reformatting confusing sentences and paraphrasing:</li></ul><blockquote>Your prescriptions will be available at 2:30 pm on Tuesday November 9th, but you will need to wait until our pharmacists call you before you can pick them up.<br>VS<br>Your prescriptions will be ready on Tuesday at 2:30 pm. Our pharmacists will call you once you can pickup your order.</blockquote><ul><li>Let your dialogue breathe with thoughtful pauses:</li></ul><blockquote>Okay. Let’s review the important coverage details we’ve covered today. First, your information will be deleted on &lt;date&gt; from our database. You will also be sent a confirmation email on that day. Last, you can let me know at any time before that date if you would like to reverse your decision and keep your information in our database. Would you like to finalize your decision and submit this form? (User: Yes.) Okay, your form has been submitted.<br>VS<br>Okay. Let’s review the important coverage details we’ve covered today. *pause* First, your information will be deleted on &lt;date&gt; from our database. You will also be sent a confirmation email on that day. *pause* Last, you can let me know at any time before that date if you would like to reverse your decision and keep your information in our database. *pause* Would you like to finalize your decision and submit this form? (User: Yes.) *pause* Okay, your form has been submitted.</blockquote><ul><li>Break long dialogue into chunks</li></ul><blockquote>Okay. Let’s review the important coverage details we’ve covered today.</blockquote><blockquote>First, your information will be deleted on &lt;date&gt; from our database. You will also be sent a confirmation email on that day.</blockquote><blockquote>Last, you can let me know at any time before that date if you would like to reverse your decision and keep your information in our database. Would you like to finalize your decision and submit this form?</blockquote><blockquote>(User: Yes.) Your form has been submitted.</blockquote><h3>Don’t Stop Here</h3><p>There are plenty of other ways to make AI interactions more conversational. This article simply serves as a jumping board for ideas.</p><p>Part 2 of other tips I couldn’t fit into this list will be in the works. :)</p><p>Illustrations were made using icons by icons8.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9ddaac08942" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I’ve Learned as a Newbie Conversation Designer]]></title>
            <link>https://medium.com/@diannehultquist/things-ive-learned-as-a-newbie-conversation-designer-6a0e69357e70?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a0e69357e70</guid>
            <category><![CDATA[newbie]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[conversational-ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Sun, 07 Apr 2024 01:38:39 GMT</pubDate>
            <atom:updated>2024-04-07T01:38:39.732Z</atom:updated>
            <content:encoded><![CDATA[<p>UX coursework never fully prepared me for real-world design. It’s been around only three months since I officially started working as a conversational AI designer, but there’s a lot I’ve learned so far. Although reviewing all of it in-depth is impossible, I wanted to delve into three significant, valuable tips.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVOWlneMklwmWeLeZOe3mQ.jpeg" /><figcaption>A man riding a bike in the middle of the street — Photo by <a href="https://www.pexels.com/photo/a-man-riding-a-bike-in-the-middle-of-the-street-20217671/">Mathias Reding</a></figcaption></figure><h3>Put Users First — ALWAYS</h3><p>Although it should be a given, it’s easy to lose sight of who you’re designing for. Business specs and metrics can cloud your judgment. As a newcomer, I’ve caught myself impulsively agreeing to non-designer feedback before realizing it’s not in the users’ best interest.</p><p>Still, it’s crucial to drill this into your mind: focus on user needs. Practicing empathy and human-centered design reduces the risk of developing bad user experiences later down the pipeline. And it will probably prevent a lot of headaches.</p><p>A great way to center users is to ask constantly, “<em>Is this the best experience for the user?</em>”</p><p>If the answer is anything other than a confident “<em>yes</em>,” figure out why not. This doesn’t always mean going back to the drawing board, but it does signal a need for adjustment.</p><p>However, something to keep in mind is to balance user needs with the needs of internal stakeholders. Does the project have a low budget? Will developers find it easier to build the experience in a specific way? You’ll likely find yourself in situations like these, requiring small and large compromises. It’s essential to take all factors into account to decide what the best user experience is.</p><h3>Design for AI Quirks</h3><p>Conversation design differs from other UX fields since AI is an ever-changing landscape.</p><p>It’s crucial to familiarize yourself with the AI you’re designing for. What are its capabilities and limitations? Does it adapt to the user? Is it multimodal? Depending on the answers to questions like these, you can effectively focus your design efforts on the right things.</p><p>Once you understand those answers, take a step back. Your goal as a conversation designer is to make the AI experience conversational (<em>insert dramatic gasp</em>). Consider how error handling, presenting options, and navigation are done in human conversations. You don’t want to enter “uncanny valley,” but make the dialogue flow naturally.</p><p>Also consider AI personas. UX designers and personas go together like bread and butter — the same goes for conversation designers.</p><p>But we don’t just design for our user personas; we also align our designs with the bot persona. These bot personas can include their personality, tone, language choice examples, and more. A significant difference, though, is that bot personas should focus on how the AI can help the user. Aligning your bot’s dialogue to its persona creates consistency for a good user experience.</p><h3>Start with the User Flow</h3><p>Tying back to the first point, users need worthwhile digital experiences. To make them, you need a starting point — meet user flows, your new best friend! These can be a pain to create, especially for more complicated experiences. But making them before design work will prevent even bigger pains.</p><p>A low-level flow for generalities can be helpful at the start, but keep in mind that a high-level flow is ultimately needed. Be sure to include all prompts, utterances, user actions, decisions, paths, data retrievals, and other steps. This is where it’s easy to get lost. Just make sure to prioritize the happy path.</p><p>There are several significant benefits to creating user flows before any design work.</p><ul><li><strong>Catching all the what-ifs</strong> <em>—</em> Discussing and iterating your flow with teammates puts more eyes on your flows. They may bring something to your attention that you weren’t aware of or point out anything missing. If this step is put off until later, chances are you’ll already be deep into designs when they realize something’s missing.</li><li><strong>Ensuring everyone’s on the same page</strong> <em>— </em>This is a process of presenting each flow iteration to your team; you create an opportunity for everyone to uncover issues and limitations now rather than later. Reviewing, discussing, and finalizing the user flow together will also let teammates know what to expect <em>before </em>work gets to them.</li><li><strong>Finding gaps in user stories</strong> <em>— </em>User stories might be created before or simultaneously as user flows. Nonetheless, those stories won’t be perfect at the start. Product managers can determine what needs to be updated before assigning them by comparing user stories to the finalized user flow.</li></ul><h4>I think it’s time to wrap this up…</h4><p>Even with AI advancements, we’ll always need to center our designs around users. These tips revolve around this core UX principle.</p><p>I definitely haven’t stuck to all these tips in the past, leading to mistakes and headaches. These tips partially serve as reminders to myself and as things to keep in mind for any other newbie designers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a0e69357e70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wix Conversation Design]]></title>
            <link>https://medium.com/@diannehultquist/wix-conversation-design-fc101e7f6733?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc101e7f6733</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Thu, 14 Dec 2023 06:02:50 GMT</pubDate>
            <atom:updated>2023-12-14T06:02:50.025Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Get answers verbally, visually, and at your own pace.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ISUHx8zn02QgmQwsqw4ZxQ.png" /><figcaption>A user calling the Wix AI for customer support</figcaption></figure><p><em>Wix is a cloud-based website builder. This case study was created in October 2023.</em></p><p><strong>Role</strong>: Conversation Designer for Wix (unaffiliated)</p><p><strong>Overview:</strong></p><p>Website builder tools make website design and development significantly easier than the traditional way. But when users run into website or account issues, they need help fast. These inquiries overwhelm call centers with questions that artificial intelligence (AI) could support. Wix users need a powerful resource to help them overcome these challenges they encounter.</p><p>For this project, I aimed to build a multimodal experience for a Wix AI agent that can help customers solve their technical and account-related issues. To know if it was successful, I would show the demo to users and get their feedback on whether it seems more accessible, the same, or a more challenging experience than speaking with a human agent.</p><h3>Inefficient and Slow Support</h3><p>The top 5 countries using Wix are the United States, the United Kingdom, Canada, Brazil, and Australia. 67% of users are small companies with less than 50 employees. Wix has more than 220 million users.*</p><p>Wix needs a support system that efficiently serves its large customer base; however, this is different. After reviewing customer support feedback, I saw some patterns. Often, their customer support has slow response times to inquiries, even in better instances. In the process, inquiries might get sent to several departments before being escalated to the correct one. And in the end, users may receive a generic response, if any.*</p><p>*enlyft.com/tech/products/wix-com</p><p>*softwareadvice.com/marketing/wix-profile/reviews/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zlr2kB2mcCfJnUneOfHvQ.png" /><figcaption>Two customer reviews that mention negative experiences with Wix support</figcaption></figure><h3>Representing Customers</h3><p>Using the customer feedback, I created a persona representing Wix customers&#39; frustrations and needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I65T3G-HTQ3dOBwhKkZ8Xw.png" /><figcaption>Wix customer persona named Mariana</figcaption></figure><h3>Factoring Humanity into the Equation</h3><p>The Happy Path shows the ideal experience a customer would have with the Wix AI agent. Notable features are predicted intents for existing users, conversational prompts, and transfers to human agents when needed.</p><p>The benefit of a voice user interface (VUI) with a natural language understanding (NLU) is that it provides flexibility and reliability. Unlike an interactive voice response (IVR) system, users can instantly contact the Wix customer care intelligent agent and ask for it to repeat information, send information with a text, and recognize nuanced language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1IPc4OBauJXDBnsMBMap1A.png" /><figcaption>Happy path showing the ideal flow a user would move through while calling the Wix AI</figcaption></figure><h3>Demo</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZ8xMPDYAUak%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZ8xMPDYAUak&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZ8xMPDYAUak%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7f8ddfc0ee687e6163479e4dbe1f2be/href">https://medium.com/media/e7f8ddfc0ee687e6163479e4dbe1f2be/href</a></iframe><h3>Feedback</h3><p>Some users said it was hard to tell whether the Wix AI would really help them or not. However, the overall feedback was that the AI would at least speed up the process a little bit. Users also mentioned that it could help them solve simpler issues.</p><h3>Other Opportunities</h3><p>The Wix AI has other dynamic possibilities beyond customer support calls. An example is that it could notify customers when they need to take action on their account, such as updating their form of payment or accepting updated terms of agreement. This could be sent as a text message, and users could call the Wix AI. It would recognize the phone number and present the action communicated in the text.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc101e7f6733" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BankBot Chatbot Design]]></title>
            <link>https://medium.com/@diannehultquist/bankbot-conversation-design-67107568ff12?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/67107568ff12</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[conversational-ai]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 07:52:14 GMT</pubDate>
            <atom:updated>2023-12-13T08:57:28.182Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A chatbot that customers love and cyber criminals fear.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elpwdeXCnWA--czUONI0Cw.png" /><figcaption>A mockup of BankBot in action</figcaption></figure><p><em>BankBot is a concept for a mobile banking AI chatbot. It gives users a quick and efficient option to report financial fraud. This project extended over the course of March— April 2023.</em></p><p><strong>Role</strong>: Conversation Designer for finance institutions</p><p><strong>Overview:</strong></p><p>What happens when you discover charges someone else made on your credit card?</p><p>Usually, this means waiting minutes to hours of calling your bank, staying on hold, and explaining every detail to a human agent. But it doesn’t have to be that way. An AI-powered chatbot to help users fulfill their banking needs faster is the solution.</p><p>Without needing to wait for a human agent, users are able to speed up the reporting process through BankBot’s conversational self-service features. I wanted to bring this process to life by creating a demo and getting user feedback. Then, I’d see if an AI-powered chatbot has potential within the banking space.</p><h3><strong>Mobile Banking and Chatbots are ‘Meh’</strong></h3><p>Survey participants reported using their banking app typically less than once per week or 1–3 times per week, spending less than 15 minutes per session. They normally use their app to check a current balance, view transaction history, and make transfers.</p><p>People described their past experiences with chatbots as pointless, unclear, and a waste of time. When do they resort to chatbots? They responded that they only use chatbots to ask simple questions for speed and convenience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d69VSvyU6kauLMRGB3PDxg.png" /><figcaption>Graph of banking app usage (left) and word cloud describing chatbot experiences (right)</figcaption></figure><h3><strong>Key Elements of BankBot</strong></h3><p>Given time constraints, I scripted for a single scenario and focused on key<br>aspects of the user journey that would be shown in the demo:<br>• Real-time retrieval and sending of information<br>• Explicit confirmations<br>• Thorough and conversational explanation of the report process</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJFRbRovOVvJTCGIOFk-fw.png" /><figcaption>BankBot user flow for reporting credit card fraud</figcaption></figure><h3><strong>Planning a Stress-Reducing Experience</strong></h3><p>Reporting fraud is scary. Customers are in a highly stressful situation, so every aspect of BankBot’s UI must be clear and straightforward.</p><p>BankBot’s personality is relaxed and trustworthy while using little to no filler language so that the user can report the fraud as quickly as possible.</p><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vYzi8EmTjpxlDXoN_i5myw.png" /><figcaption>Wireframes of BankBot UI and conventional experience</figcaption></figure><h3>Demo</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyX77yT2hKP8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyX77yT2hKP8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyX77yT2hKP8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7b1361500397f1c82ba25bb6f6805ca4/href">https://medium.com/media/7b1361500397f1c82ba25bb6f6805ca4/href</a></iframe><h3>Optimistic Feedback</h3><p>After showing the demo to mobile banking users, many said that they would likely enjoy using the chatbot instead of waiting for a human agent, or at the very least, feel secure in the fact that it is an option. Particularly, friends and family who have experienced fraudulent charges said BankBot would be helpful in taking action quickly to prevent more charges.</p><h3>Other Opportunities</h3><p>I would love to create another demo that shows other user flows for BankBot’s useful features. Changing passwords and making a payment are some of the features that are also dynamic experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67107568ff12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dutch Bros. UX Research & Redesign]]></title>
            <link>https://medium.com/@diannehultquist/dutch-bros-ux-research-redesign-3d80c4797aec?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d80c4797aec</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Sat, 09 Dec 2023 09:13:47 GMT</pubDate>
            <atom:updated>2023-12-13T08:57:45.585Z</atom:updated>
            <content:encoded><![CDATA[<p>Making navigation as enjoyable as coffee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e4mi8PbKtpNOEUjXsIUJyA.png" /><figcaption>The Before (left) and After (right) results of the Dutch Bros. website redesign</figcaption></figure><p><em>Dutch Bros. is a drive-thru coffee chain. This research and redesign project extended over the course of January — February 2023.</em></p><p><strong>Role</strong>: UX Researcher &amp; UX Designer for Dutch Bros. (unaffiliated)</p><p><strong>Team Members</strong>: Darby Woolslayer, Melissa Gibson, and Kayla Nelson</p><p><strong>Overview:</strong></p><p>Dutch Bros. satisfies many with their coffee, but do they also satisfy website users?</p><p>Out of a list of popular brands, Dutch Bros. stood out to us. Their website was suspected not to be user-friendly and frustrated many customers. My team and I wanted to evaluate the usability of the website and discover areas where the user experience does not meet expectations. After our research, we would provide UX recommendations and design wireframes.</p><h3><strong>All You Need is Coffee and Wifi</strong></h3><p>Our research began with conducting surveys to uncover what type of people are Dutch Bros. customers.</p><p>Overall, they are women aged 18–24 or 35–44 with some college experience. They use the internet daily and spend around 25–40 hours a week on the internet. Their favorite websites are Netflix, Facebook, YouTube, and Google. We used these insights to create our personas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xI0RLfn4waitJ6Mbpqc8XA.png" /><figcaption>User persona and a pie chart of survey results for internet usage</figcaption></figure><h3><strong>Confusing Navigation and IA</strong></h3><p>Across all team members’ heuristic evaluations, common pain points were with the navigation &amp; information architecture, trust &amp; credibility, and content quality. We also shared specific frustrations with button labels, banner sizes, titles, and attaining shipping information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtfSpojtZ2gUzzPlfFd4-w.png" /><figcaption>A table showing my heuristic evaluation results for the Dutch Bros. website</figcaption></figure><h3><strong>Where is Anything?</strong></h3><p>Our usability testing aimed to determine if users can successfully navigate the Dutch Bros. website. Users were asked to navigate tasks such as finding their local branch location, learning about Dutch Bros. philanthropic efforts, and navigating to and from the Dutch Bros. shop.</p><p><strong>Scenario 1</strong></p><p>4 out of 7 participants expressed frustration and/or dissatisfaction when tasked with finding their nearest Dutch Bros. branch location. The average time participants spent on this task was 39 seconds.</p><p><strong>Scenario 2</strong></p><p>6 out of 7 participants were distracted from the main task of locating information on philanthropy. The task was to find info about Dutch Bros. support for the Coalition to Back Black Business. However, this success rate was 86%. The average time on the task was 32 seconds.</p><p><strong>Scenario 3</strong></p><p>7 out of 7 participants had significant issues with navigating to the home page from the shop. The expected time on the task was 5 seconds, but the average time on this task was 42 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dG_dLedOX9SbjqMekNdpVQ.png" /></figure><h3><strong>User Frustrations</strong></h3><p>Testing results showed that users’ most common pain points were with the menu and navigation, website inconsistencies, difficulty accessing and viewing key information, and unimportant or irrelevant written content.</p><p>The first major pain point was the site’s navigation, including an inaccurate store locator. Next was the lack of credibility and company transparency since the career information on the “Our Impact” page was distracting and irrelevant. Last was the layout design which made navigating between the site and shop unintuitive.</p><h3><strong>What Needs to Change</strong></h3><p>Our first recommendation was to have placeholder text read “Enter your zip code.” Second, Dutch Bros. should dedicate the ‘My Impact’ page solely to Dutch Bros. philanthropic efforts. The third suggestion was to add global navigation by linking the homepage to the Dutch Bros. logo in the menu.</p><p>Wrapping up the project, we each built wireframes that reflected these suggestions and additional site improvements.</p><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdl9pyB5yh204HS7q4tp-Q.png" /><figcaption>Wireframes for Dutch Bros. pages that incorporate UX recommendations</figcaption></figure><h3>Other Opportunities</h3><p>Applying our thorough research to create an interactive prototype would be a great opportunity to conduct another round of usability testing. Our team would be able to compare the new results to previous results and reveal if our recommendations truly do improve the website’s usability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d80c4797aec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notion Timings Design]]></title>
            <link>https://medium.com/@diannehultquist/notion-timings-design-d7fbdaf0f2cd?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7fbdaf0f2cd</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[motion-graphics]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 09:12:22 GMT</pubDate>
            <atom:updated>2023-12-13T08:57:08.618Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Snappy timings that motivate, not procrastinate.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIaHJ4AhhHgZspciVwcIsA.png" /><figcaption>Closeup of Notion app UI design</figcaption></figure><p><em>Notion is a note-taking and productivity application. This case study was created in December 2022.</em></p><p><strong>Role</strong>: Interaction Designer for Notion (unaffiliated)</p><p><strong>Overview:</strong></p><p>Making lists, navigating pages, and editing Kanban boards in Notion is a breeze in web browsers. The mobile app experience is…something else.</p><p>I’m a Notion advocate, but I always choose the web browser platform over the app — its laggy responses to interactions make most users impatient. Working with the same user interface (UI), I wanted to step up Notion’s app interactions using industry-standard UI timings. I also wanted to test the success of the final prototype through user feedback and see if users appreciated the timely responses.</p><h3>Sketching &amp; Mapping Interactions</h3><p>Creating a navigation tree for the demo, I mapped out the user interactions and screens to demonstrate the improved timings. Also, simple sketches gave me an idea of the key elements Notion users normally interact with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yGLmu-yIy-PF3k3hKk6aAQ.png" /><figcaption>Navigation tree mapping out user interactions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QufJc3w5QiRkMrQrABcvgQ.png" /><figcaption>Sketches of key Notion elements</figcaption></figure><h3>Navigating Your Notes as a User</h3><p>Before jumping into wireframing and animating, the user flow needed to be mapped. I wanted to show a simple but effective flow of how many users interact with their Notion pages.</p><p>The user starts in the Notion app, viewing their Assignments Schedule page. They mark one of their assignments as Turned In and then swipe to open the menu. It’s time to get to work, so they open their WorkHub page and go to their To-Do list. Looking at a task, they realize they need a document and click on the search option in the global navigation to find what they’re looking for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cet-8W68cIEqRr4zMuzBsQ.png" /><figcaption>User flow showing the UI timings and interactions throughout notes screens</figcaption></figure><h3>Wireframes</h3><p>No changes were made to the UI other than several spacing changes to better the consistency across screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OrKYQx-5omDiyv0kS2T4-w.png" /><figcaption>Wireframes of Notion UI</figcaption></figure><h3>Demo</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JFWHCxMwep5oN_yvsNJ1hw.gif" /><figcaption>Demo showcasing the improved timings when navigating Notion pages</figcaption></figure><h3>Results</h3><p>After showing users the original app and my demo, users gave me feedback on how much more springy and satisfying the demo interactions were.</p><h3>Other Opportunities</h3><p>If I were to revisit this project, I’d like to add demo interactions for scrolling or opening assignments. These interaction timings in the most recent app version could still use improvement, giving me a good challenge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7fbdaf0f2cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Airbnb Redesign]]></title>
            <link>https://medium.com/@diannehultquist/airbnb-redesign-1c7f016d3a8a?source=rss-44547659fbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c7f016d3a8a</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Dianne Hultquist]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 03:12:10 GMT</pubDate>
            <atom:updated>2023-12-13T08:58:03.585Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Search for your next stay, not the search bar.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRN_GfikqeHREXYDilsgIQ.png" /><figcaption>The Before (left) and After (right) results of the Airbnb website redesign</figcaption></figure><p><em>Airbnb is an online marketplace that allows owners to rent out their homes and people to book homestay rentals. This case study was created in September 2022.</em></p><p><strong>Role: </strong>UX Researcher &amp; UX Designer for Airbnb (unaffiliated)</p><p><strong>Overview:</strong></p><p>New users can get overlooked. I consider myself tech-savvy, but I even had a hard time figuring out where to search for stays on Airbnb’s website.</p><p>On a mission to reclaim my tech-savvy status, I wanted to know if other first-time Airbnb website users had frustrations. I conducted an initial usability test to find user pain points. Insights were then used to design new user interface (UI) elements and test new participants to see if tasks were completed with a shorter time average.</p><h3>An Italian Vacation</h3><p>For usability testing, I gave participants a scenario: you and your family (4 adults total) are going to Milan, Italy, for a short trip and want to reserve an Airbnb for your stay. Your vacation plans are as follows:</p><ul><li>You all arrive in Italy on October 21st and check into Airbnb</li><li>You stay in Italy for a week</li><li>Leave Italy and check out of the Airbnb on October 28th</li></ul><p>With this in mind, they searched for a stay that met their needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ux_pFGVeuoog0XoxxrT97g.png" /><figcaption>Observation board of usability testing user feedback</figcaption></figure><h3>User Pain Points</h3><ol><li>Search Bar Appearance &amp; Location — Users took anywhere from <strong>15</strong> seconds to <strong>1.5</strong> minutes to find the search bar because of its subtlety.</li><li>Search Bar Placeholder Text — Users were frustrated that the phrases, text color, and font weight made the sections seem unclickable.</li><li>Controls to Expand — Many users only explored search results through the card listings, but there was no option to expand this section.</li><li>Map Listing Cards — Users were frustrated that they couldn’t find how to go to the listing’s details page since there was no CTA on the cards.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLXTeIjsgPgKtEqkAHlF3g.png" /><figcaption>Original element designs that were user pain points</figcaption></figure><h3>Clarity is Key</h3><p>Airbnb’s current design approach keeps navigation elements subtle. Sure, it looks nice. But, users need clear calls to action to know where and how to interact with the site.</p><p>In my designs, I wanted to emphasize important elements that helped users complete tasks, make the next steps straightforward, and add simple features that catered to user needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfiykbPzlG8vXkB1us1iGw.png" /><figcaption>Sketches and low-fidelity wireframes of pages to be redesigned</figcaption></figure><h3>Results</h3><p>I conducted a second usability test using my prototype of new designs. Participants completed a search within <strong>5</strong> to <strong>30</strong> seconds. Overall feedback was that the search bar was more noticeable. Also, participants who preferred search results as cards rather than map prices liked the added feature of expanding the card results.</p><p>Participants could find what they were looking for more quickly and appreciated the added features they voiced that they wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SOFNDxUaTAVaJMbRt5_G3w.png" /><figcaption>New designs for user pain point elements</figcaption></figure><h3>Interactive Prototype</h3><p>Explore the interactive <a href="https://www.figma.com/proto/4EjljMDMBR2XGYn17TxCSB/Airbnb-Re-Design?type=design&amp;node-id=132-4&amp;t=X8SaiKJmnfL3g8jq-1&amp;scaling=scale-down&amp;page-id=0%3A1&amp;starting-point-node-id=132%3A4&amp;mode=design">Figma prototype here</a>.✨ Feel free to click and scroll as if you were on the website.</p><h3>Demo</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbC7E_yIYxR8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbC7E_yIYxR8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbC7E_yIYxR8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3038c9fdb98362fffe8040661a10034/href">https://medium.com/media/a3038c9fdb98362fffe8040661a10034/href</a></iframe><h3>Other Opportunities</h3><p>I would have liked to give participants a second scenario with more details and criteria. This could have uncovered additional user pain points.</p><p>Some users prioritize places with pets allowed, and others prioritize wifi. The new scenario could ask participants to search listings for these specific needs, likely showing additional pain points with Airbnb’s search filters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c7f016d3a8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>