Summary
AI tools like ChatGPT have exploded in popularity with good reason: they allow users to draft, summarize, and edit content with unprecedented speed. While these generic tools can generate any type of content or perform any type of content task, the user needs to craft an effective prompt to get high-quality output, and often needs to exchange multiple messages with additional guidance and requirements in order to improve results. When you’re building an AI-powered text generation feature, such as a product description or email writer, you typically can’t expect users to craft their own prompts. And unless you’re building a chat interface, you’re unlikely to offer the ability to iteratively improve the output. Instead, your feature needs a robust prompt skeleton that combines with user input to produce high-quality output in a single response. For the designer, this means building an interface that helps users provide the exact information that creates a successful prompt. This process is more complex than simple form design or a mad-lib prompt completion tool. The user input, often including free form text fields, might be required to fill in prompt variables, but it also could change the prompt structure itself, or even override base instructions. The effectiveness of the user input significantly influences the quality of the output, underscoring the need for designers to be deeply familiar with the backend prompt architecture so they can design the frontend. Drawing on recent text generation projects, I'll demonstrate how the interface design can respond to and evolve with the prompt architecture. I’ll talk about how to determine which prompt components to make invisible to the user, which to provide as predefined options, and which should be authored by the user in free-form text fields. Takeaways How prompt structure can impact user interface design and conversely, how design can impact prompt structure Techniques to provide effective user guidance within AI generation contexts to ensure consistently high-quality output Real-world examples and learnings from recent generative AI projects in an e-commerce software product
Key Insights
-
•
Designing AI text generation features requires predefining most of the prompt to ensure quality output, unlike general chat interfaces where users craft their own prompts.
-
•
Users should provide only essential variable inputs like product name, keywords, tone, and length while the rest of the prompt remains fixed and optimized by designers.
-
•
Free-text tone input confuses many users, making predefined tone options a better UX solution for brand-consistent content generation.
-
•
Providing six distinct, well-differentiated tones helps merchants easily select a voice that fits their brand and produce unique product descriptions.
-
•
Tone labels need to cover sufficiently different style zones, avoiding overlaps such as conversational vs friendly or witty vs humorous.
-
•
Detailed linguistic instructions behind each tone dropdown option improve output consistency, including vocabulary choice, pronouns, punctuation, and syntactic style.
-
•
Using AI to detect tone from existing website content is unreliable; the model gives inconsistent outputs with unjustified high confidence.
-
•
Balancing configurability and fixed prompt instructions is a core design challenge when building AI features with limited iterative prompting.
-
•
The UI must simplify complex prompt engineering by presenting users these configuration options in an intuitive and minimal way.
-
•
Generative AI models often default to a confident, positive tone, which designers need to explicitly adjust through persona prompts if a different tone is desired.
Notable Quotes
"If the user isn’t happy with the output, they might be able to change some of the inputs and try again, but the base instructions are predefined."
"When you’re building a specific AI feature, you don’t want to make your user write their own prompt."
"A prompt is a set of directions given to an LLM to generate text that meets criteria like format, length, tone, or topic."
"The tone of voice field turned out to be a much more complicated variable than it appears."
"Merchants often sell really similar products, so tone differentiated suggestions help them stand out with unique descriptions."
"People get stuck trying to articulate their brand voice in just one or two words during user testing."
"The LLM gave many different answers for the same passage and always reported it was 100% confident."
"Tones need to be distinct enough from each other so merchants can easily spot which one fits best."
"We had a quite a bit more detail in the prompt about vocabulary, pronouns, punctuation, and syntactic instructions for each tone."
"By default, generative AI has a very convincing, confident tone that never hedges, and you have to build other tones explicitly."
Or choose a question:
More Videos
"The hardest part about remote is making design reviews feel collaborative and team-based."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Knowing your subject matter as a UX leader is just as important as knowing your craft."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance frameworks can facilitate whatever an organization wants to do, fast or slow, loose or tight."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Sustainable practices are not just a luxury; they are a necessity for our survival."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"The squad model flopped for us after six months but created culture triads that stuck around."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Hip hop proves that we can re-animate spaces with highly generative communities that weren't built for us."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Marital status mattered because car buying decisions often involve family members, not just the individual."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"Most product teams work linearly, but systems thinking captures the real-world complexity of moving forward and sometimes stepping back."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
