Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
AI in Real Life: Using LLMs to Turbocharge Microsoft Learn
Summary
Enthusiasm for AI tools, especially large language models like ChatGPT, is everywhere, but what does it actually look like to deliver large-scale user-facing experiences using these tools in a production environment? Clearly they're powerful, but what do they need to make them work reliably and at scale? In this session, Sarah provides a perspective on some of the information architecture and user experience infrastructure organizations need to effectively leverage AI. She also shares three AI experiences currently live on Microsoft Learn: An interactive assistant that helps users post high-quality questions to a community forum A tool that dynamically creates learning plans based on goals the user shares A training assistant that clarifies, defines, and guides learners while they study Through lessons learned from shipping these experiences over the last two years, UXers, IAs, and PMs will come away with a better sense of what they might need to make these hyped-up technologies work in real life.
Key Insights
-
•
Most AI applications no longer require building foundation models from scratch; the focus is now on application development and integration.
-
•
Single, all-purpose chatbots (everything chatbots) are insufficient because they handle high ambiguity and diverse, often complex tasks poorly.
-
•
Sarah introduces the ambiguity footprint as a framework to measure AI application complexity and risks across several axes such as task complexity, context, interface, prompt openness, and sensitivity.
-
•
AI features that support simple, complimentary user tasks, rather than critical or complex ones, are easier and safer to build and scale.
-
•
Visible AI interfaces, like chatbots, set clearer user expectations but introduce more ambiguity and management overhead compared to invisible AI (e.g., keyboard optimizations).
-
•
Prompt engineering plays a crucial role in defining the boundaries of AI output, from very open-ended to highly restricted scopes.
-
•
Retrieval Augmented Generation (RAG) helps manage up-to-date context by dynamically querying relevant data chunks rather than using static corpus.
-
•
Evaluating AI outputs rigorously is essential but often underprioritized; without clear quality metrics, teams end up relying on subjective or anecdotal assessments.
-
•
Data ethics and distributed AI implementations can create blind spots, limiting feedback loops necessary for continuous AI model improvement.
-
•
Incrementally building AI applications with smaller ambiguity footprints helps organizations develop expertise and controls before tackling more complex, open-ended AI products.
Notable Quotes
"You’re not doing IA, but you’re always doing it."
"An everything chat bot is almost certainly not how you’re going to build it; realistically you’re building three apps in a trench coat."
"AI is ambiguous at best because we’re fully in the realm of probabilistic rather than deterministic programming."
"The more complex the task, the less likely it is to be successful with current AI."
"A task where AI adds a little something is honestly easier to get right than one where it’s absolutely critical."
"Visible AI interfaces introduce another place where you can add ambiguity."
"Retrieval Augmented Generation lets you supply specific relevant information to the model dynamically rather than everything at once."
"Evaluation might be the most important part of your entire development effort and is often the hardest to do well."
"You can’t just eyeball results and call it good; AI applications are expensive and complex and require systematic evaluation."
"Never build or buy an everything chat bot again; start with less ambiguous, targeted AI experiences."
Or choose a question:
More Videos
"There are no mistakes in jazz, just missed opportunities."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"A really strong book has to be designed as a journey with a consistent voice guiding the reader."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Staff and principal designers need to balance zooming in on execution and zooming out to define strategic vision and minimize risk."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"You might find that spending the most time getting people interested in collaboration is where the work really happens."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"Processing limits and licensing terms currently restrict how much video and audio these AI tools can handle."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Random assignment to treatment or control is essential—if it’s not random, it’s not a true experiment."
Joshua NobleCasual Inference
October 6, 2023
"If the scale delivers bad news, we jump on and off to check; if it delivers good news, we accept it quickly."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"If something makes you feel unwelcome, the code of conduct explains how to engage with staff to resolve issues."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"We often say don’t make me think. When that’s not possible, reuse and recycle those learnings."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023