Don't botch the bot: Designing interactions for AI
Summary
It seems like every company is adding a conversational AI chatbot to their website lately, but how do you actually go about making these experiences valuable and intuitive? Savannah Carlin will present a case study on a conversational AI chatbot—Marqeta Docs AI—that she designed for a developer documentation site in the fintech industry. She will share her insights, mistakes, and perspectives on how to use AI in a meaningful, seamless way, especially for companies like Marqeta that operate in highly regulated industries with strict compliance standards. The talk will use specific examples and visuals to show what makes conversational AI interactions uniquely challenging and the design patterns that can address those challenges. These include managing user expectations, handling errors or misunderstandings within the conversation, and ensuring that users can quickly judge the quality of a bot’s response. You’ll gain a deeper understanding of the intricacies involved in designing interactions for AI, along with practical advice you can apply in your own design processes. Take-aways What to consider before you add AI to your product to ensure it will be valuable, usable, and safe for its intended workflows The interactions that are unique to conversational AI experiences and the design patterns that work for them Common challenges in designing conversational AI experiences and how to overcome them
Key Insights
-
•
Defining a clear and specific primary use case is crucial before starting any generative AI chatbot project.
-
•
High-quality, thoroughly reviewed training data is foundational to delivering accurate and useful AI outputs.
-
•
Initial state messaging must clearly frame what the chatbot can and cannot help with to reduce irrelevant or off-topic queries.
-
•
Loading indicators for AI text responses should be subtle, with progress reflected by text appearing rather than distracting animations.
-
•
Supporting efficient scrolling and prompt review is vital since users frequently check and refine their inputs against often long answers.
-
•
Error states in AI chatbots shift from traditional fixed errors to helping users write better prompts to get more relevant results.
-
•
Transparency about accuracy, AI limitations, and source citations builds user trust, especially in regulated domains like FinTech.
-
•
Providing users with prompt engineering guidance via documentation significantly improves the quality of chatbot interactions.
-
•
Accessibility considerations, like keyboard navigation and screen reader compatibility, must be integrated from the start, especially given the large text outputs.
-
•
Chatbots can reduce customer support friction and encourage users to ask questions they might not have otherwise, enhancing user engagement with the product.
Notable Quotes
"If you have any doubts about the quality of the training data, do not proceed."
"You want to assist people in framing the interaction and setting their expectations correctly so they know how to be successful."
"The biggest difference with error states in AI bots is helping people write prompts effectively, not just recovering from simple failures."
"Loading text itself is a loading indicator; the letters appearing show progress better than jumpy animations."
"People often forget what they wrote and then want to check their prompt again before refining it."
"Every output should have at least three source links, almost like citations in a research paper."
"We had to be very careful about accuracy because we're in FinTech and compliance is critical."
"People started asking questions to the bot that they wouldn’t have taken the time to email about."
"It’s really important to be clear and transparent about what the tool is good at and what it’s not good at."
"Accessibility testing included making sure everyone could navigate it using a keyboard alone."
Or choose a question:
More Videos
"We need to figure out how to assess design projects and designers better because employers need to make choices, but design resists simple scoring."
Nathan Shedroff Hugh Dubberly Thomas J. McLeishHow Will Design be Taught When the Schools Shut Down?
May 8, 2026
"Being design-driven is a means to an end. We aim to be 1% better every day with data-driven obsession."
John Paul de Guzman10k Screens Later: How We Became a Data-Driven Design Organization
September 24, 2024
"The hardest part is acting on feedback, which requires integrating tools and aligning multiple teams like research, product, marketing, and customer success."
Aleksandra Korczynska Caroline Jarrett Justyna ParmeeSurvey Tools
March 12, 2026
"One hallmark of a healthy team is how well team members feel cared for so they can shine."
Kristin SkinnerTheme 2: Introduction and Provocation
January 8, 2024
"Workshop content is equivalent to a one-day in-person event spread over 10 virtual hours with coaching and support."
Rachael Dietkus, LCSW Victor Udoewa Jennifer StricklandEverything You Need to Know about the Civic Design 2022 Call for Presentations
May 17, 2022
"The poetic and humanistic aspects of design are getting squeezed out by prescriptive delivery models."
Uday GajendarThe Rise of Meta-Design: A Starter Playbook
May 19, 2022
"Feedback is a lot like holding up a mirror. You're reflecting what's already working and like using a flashlight to hide in the corners."
Vanessa VarinFeedback: The Other F-Word
September 10, 2025
"Horst Rittel introduced wicked problems to describe problems where consensus on definition is difficult, and calling them problems can be misleading—maybe they’re better called messes or tangles."
Hugh DubberlyProblems with Problems: Reconsidering the Frame of Designing as Problem-Solving
June 19, 2019
"Balancing risk and confidence helps teams move at the right speed for the right decisions."
Sean McKayCoexisting with non-researchers: Practical strategies for a democratized research future
March 11, 2025
Latest Books All books
Dig deeper with the Rosenbot
How can I use an AI chatbot like Rosenbot to get quick answers on UX and product design topics?
What are effective behaviors that design operations teams should focus on to deliver value and build trust?
Why is prior authorization such a persistent problem and how can patient-centered solutions be designed around it?