🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋 Introduction
  • ✨ Discovery
  • 🤔 Empty state
  • ✍🏻 Query & Intent
  • 💥 Trigger
  1. Working with Features
  2. Building with AI

LLM Inputs

PreviousBuild a proof of conceptNextLLM Responses

Last updated 1 year ago

Assumed audience: You’re a product designer working on an LLM powered feature. You’re familiar with how LLMs work. Use this as a starting point for further exploration and innovation.

👋 Introduction

When designing for LLMs, there are a few additional states that a designer would need to consider. These are peculiarities specific to how LLMs work (eg. slower load time, streaming capability), and common interaction patterns we’re noticing across products (eg: empty states doubling down on educating users, explicit triggers, feedback). We’ll dive into the details of each state in this article.

✨ Discovery

The user finds your feature, in a context where it’s useful to them. Some common signifiers for AI are sparkles (✨), and bots (🤖).

🤞 Try to layer your LLM capability on an existing feature. This makes sure that the user discovers it in the right context.

🤞 If your LLM feature is stand-alone, use an existing pattern, or ensure your AI signifier stands out to pique interest.

🤞 Maybe you don’t need discovery, user’s input, or a trigger at all. You can weave in your LLM response into an action that a user is already taking frequently, and improve the experience there.

🤔 Empty state

When they click on the entry point, the empty state should help users understand what they can do with this feature. This is important to get right since LLMs are a new tech capability, and your users may not be familiar with what it can do.

🤞 Give examples of what the user can ask. If your examples are context specific, they are more useful.

✍🏻 Query & Intent

The user types in their query. As they’re typing, the system is constantly trying to identify what type of result it should provide.

🤞 Understand how intent detection is going to work in your specific implementation. Play out the different scenarios to stress the pattern you choose.

💥 Trigger

The user hits “enter” or the “send” icon. It’s a good idea to give LLM features an explicit trigger (vs triggering API calls with each character being typed). This is because API calls to your model are relatively expensive, and your results are not going to show up instantaneously anyway.

4️⃣