Product designer work is changing in two important ways. Designers are using AI tools to create and test ideas faster, while more products are embedding AI directly into the user experience.
These changes are related, but they are not the same. Using AI to generate an interface is a design workflow. Designing a product in which AI makes recommendations, generates content, or interprets user input is a human-AI interaction challenge. This article focuses primarily on the second challenge: how product designers can create AI-powered experiences that are useful, understandable, and worthy of trust.
AI can help create an interface faster. Product design determines whether an AI-powered experience should exist and how it should behave.
AI as a Design Tool: Faster Production
A randomized controlled study released on September 22, 2026 examined AI as a design-production tool. It tested 50 product designers and 50 product managers completing standardized design tasks with and without Figma Make. Among participants who completed the tasks, access to the prompt-to-design tool was associated with approximately 20% shorter completion times. The gains were larger for product managers, while the benefit for professional designers varied by task.
The result is meaningful, but it requires context. The study is a recent preprint, and its authors include Figma researchers. It offers promising evidence that AI can accelerate parts of the design workflow. It does not evaluate whether AI-powered products are trustworthy, usable, ethical, or appropriate for a particular user need.
Figma’s 2026 survey of 906 digital designers found that 89% said AI helped them work faster, 91% said it improved their designs, and 80% said it improved collaboration. Yet 87% also said creative autonomy helped them perform at their best, while 91% valued clear goals and expectations.
What Faster Production Changes
When interfaces become easier to generate, polished output stops being sufficient evidence of good product design. A convincing screen can hide a weak problem definition, unsupported assumptions, inaccessible behavior, or a feature that should never have been built.
A 2026 study comparing generative-interface workflows found that structured, breadth-first exploration exposed more possibilities than jumping directly into a high-fidelity result. Professionals still preferred high fidelity because it matched their working practices and because generative tools had raised expectations for visual polish.
That tension is important. AI makes it tempting to polish the first plausible answer. Product design requires exploring alternatives before committing to one.
Faster production changes how designers work. The remainder of this article addresses the separate challenge of designing products in which AI affects the experience itself, including decisions about user need, uncertainty, trust, control, privacy, and error recovery.
Start With the User Need, Not the AI
The first responsibility of an AI product designer is to determine whether AI is appropriate for the user’s problem. Google’s People + AI Guidebook recommends connecting real user needs with the specific strengths of AI before defining the solution.
The question is not “Where can we add AI?” It is “What is difficult for the user, and what is the simplest responsible way to help?”
Designing AI Means Designing for Uncertainty
Traditional interfaces generally follow explicit rules. Selecting Save should produce the same kind of outcome each time. AI-driven experiences are probabilistic. The same input can generate different results, and a fluent answer can still be wrong.
Microsoft’s evidence-based Guidelines for Human-AI Interaction organize the experience across four moments: the initial interaction, regular use, an AI failure, and behavior over time. This is more useful than treating trust as a disclosure added at the end of the flow.
Design for Calibrated Trust, Not Maximum Trust
The objective is not to make users trust AI as much as possible. It is to help them rely on the system to the appropriate degree. Overtrust can cause people to accept weak recommendations, overlook errors, or disclose information they would otherwise protect. Too little trust makes a useful feature feel unpredictable and not worth the effort.
Google’s People + AI research connects trust with fulfilled expectations. Helpful explanations allow users to understand why a result appeared and decide whether it deserves confidence.
The interface should not say, “This is perfect for you.” It can say, “Recommended because you selected a 90-minute comedy and usually finish character-driven films.” The second statement exposes reasoning the user can inspect.
Design for Error Before the Ideal Result
AI failure is not an unusual edge case. It is part of the normal interaction model. A responsible product flow helps the user recognize a weak result, understand what influenced it, correct it without starting over, and continue without AI when necessary.
“Something went wrong” gives the user no useful direction. “We could not use your viewing history, so these suggestions are based only on the preferences you selected” communicates the limitation while preserving agency.
Overreliance Is a Product-Design Problem
A 2025 Microsoft Research study surveyed 319 knowledge workers and collected 936 examples of generative-AI use. It found that confidence in AI, confidence in one’s own ability, and the nature of the task influenced whether people applied critical thinking and how much cognitive effort they invested.
That finding has a direct interaction-design implication. An interface can encourage reflection or quietly reward automatic acceptance.
Prototype the Human-AI Interaction
Static screens cannot fully represent an AI experience. The design includes variation, timing, misunderstanding, correction, permission, feedback, and change over repeated use. Prompt-to-prototype tools make these scenarios faster to construct. That speed should be used to test more states—not merely to create a polished happy path sooner.
Tonight Mode: An AI Product Design Concept
To turn these principles into a testable experience, I created Tonight Mode for a fictional streaming platform called Luma. The problem is familiar: people can spend more time browsing than watching, especially when several viewers are trying to agree on one title.
Tonight Mode collects a small amount of explicit context—who is watching, available time, mood, familiarity, and content boundaries—then produces exactly three recommendations. Each result explains why it appeared and allows the group to inspect, correct, replace, or reject it.
Try the Live Tonight Mode Prototype
Explore the working prototype and test how the experience handles group preferences, recommendation explanations, user correction, privacy choices, and recovery. The prototype uses fictional content and simulated recommendation logic; it does not connect to a real streaming account or AI model.
If the prototype does not load here, open the Tonight Mode prototype in a new tab.
The Product Brief Used for Figma Make
Why Tonight Mode Uses AI
The feature has a credible reason to use AI. A group decision may involve different profiles, time limits, mood, viewing history, content boundaries, language, and availability. There is no single correct answer, and producing a small set of relevant options can reduce meaningful effort.
AI should not control every part of the experience. Subscription access, maturity restrictions, explicit exclusions, and availability should remain governed by reliable rules. The AI helps interpret preferences and generate options; it does not override the boundaries of the service or the household.
Use AI for the ambiguity. Use rules for the promises the product must keep.
Trust and Explanation in Tonight Mode
Every recommendation includes a short reason, such as: “Suggested because all three viewers like clever mysteries, it fits within 100 minutes, and no selected profile has watched it.” The explanation gives users something concrete to evaluate.
The Why this pick? view separates explicit session choices from signals used with permission. Users can remove a factor and regenerate the result. The experience avoids revealing individual viewing behavior to the rest of the group.
This is also where explanation design can fail. A persuasive explanation may make a weak recommendation appear more credible. Testing should therefore examine whether the explanation improves understanding or merely increases compliance.
User Control, Feedback, and Privacy
Tonight Mode keeps recommendation, selection, playback, and saving as separate actions. The system does not autoplay a title or quietly update permanent preferences. After a selection, users choose whether the session remains temporary or contributes to future personalization.
Social AI Requires More Than Personalization
A household decision is not the same as an individual recommendation. The experience must consider whether one person dominates the setup, whether every viewer feels represented, and whether an explanation accidentally exposes private behavior.
The prototype should be tested with real groups, not only individuals pretending to select several profiles. Researchers should observe who holds the device, who chooses the constraints, how disagreements are negotiated, and whether the final recommendation feels collectively acceptable.
Ethical Data Practices Are Part of the Interface
Data ethics should not live only inside a privacy policy. It affects defaults, labels, explanations, and controls. Product designers should identify the minimum information required, distinguish user-provided data from inference, make correction and deletion possible, and keep the product usable when personalization is declined.
For a shared streaming experience, an explanation must not reveal that one household member watched a particular title, searched for a sensitive subject, or received a recommendation based on inferred identity. Group-level language can explain relevance without exposing private activity.
European Commission guidance published in 2026 also explains transparency obligations under Article 50 of the EU AI Act, including informing people when they are directly interacting with certain AI systems. Requirements depend on the product and context, but transparency should be designed into the experience rather than added before launch.
How I Would Test the Prototype
A polished recommendation screen is not enough. The research must examine whether people understand the AI’s role, rely on it appropriately, recover from weak results, and retain meaningful control.
Useful metrics could include time to a mutually accepted choice, recommendation rejection rate, use of explanations, corrections per session, successful recovery from errors, privacy-setting comprehension, and the percentage of sessions that return to regular browsing. Watch time alone would be an incomplete measure of success.
Intelligence Augmentation, Not Artificial Authority
The strongest AI products do not ask people to surrender judgment. They expand what people can notice, compare, create, or accomplish. AI contributes scale, pattern recognition, and rapid generation. People contribute goals, context, values, and final judgment.
In Tonight Mode, the system narrows a complex catalog, but the viewers make the decision. In a workplace product, AI might summarize evidence while a professional verifies it. In a creative product, AI might generate alternatives while the creator chooses and refines the direction.
The interface should make the division of labor clear: what the AI contributed, what the person controls, and how the person can intervene.
The Skills Product Designers Need in 2026
AI fluency matters, but it means more than learning how to prompt. A product designer needs enough understanding of AI capabilities and limitations to shape a responsible experience.
Will AI Replace Product Designers?
AI will automate parts of product-design work. Interface variations, early prototypes, routine documentation, research assistance, and production tasks are already becoming faster.
The U.S. Bureau of Labor Statistics now explicitly recognizes that generative AI can increase the productivity of web and digital interface designers. Its 2025–2035 projections nevertheless show employment in that occupation growing by approximately 6%, from about 132,700 to 140,800 positions.
The more defensible conclusion is not that every design job will remain unchanged. Production-only work faces pressure when production becomes easier. At the same time, more AI-powered products require coherent interaction models, testing, accessibility, governance, privacy, and human oversight.
A 2026 paper in PNAS Nexus describes a wider shift in design toward stewardship, curation, translation, and responsibility for preserving human intent. That is a useful description of the emerging product designer role.
What Product Designers Should Show in Their Portfolios
In the age of AI, a polished final screen is only the beginning. A strong case study should reveal the reasoning behind the product and the evidence that changed it.
An imperfect prototype and the decision it helped change may demonstrate more product-design ability than a flawless interface presented without evidence.
Frequently Asked Questions
What is an AI product designer?
An AI product designer shapes products in which artificial intelligence affects the core experience. The work includes problem framing, interaction design, prototyping, research, accessibility, trust, user control, data practices, evaluation, and collaboration with product, engineering, research, legal, security, and data teams.
How is AI product design different from traditional product design?
Traditional products usually rely on predictable rules. AI products may generate variable output, make inferences, personalize behavior, or act with partial autonomy. Designers therefore need to address uncertainty, explanations, correction, feedback, model limitations, and behavior over time.
When should a product use AI?
AI can be useful when the experience must interpret unstructured information, identify patterns, adapt to context, generate several plausible options, or support an open-ended task. A conventional interface is often better when the desired outcome is exact, repeatable, easily expressed through rules, or too consequential for unreliable output.
What should designers test in an AI experience?
Designers should test user understanding, the quality and variability of output, appropriate reliance, error recognition, correction, feedback, permissions, privacy, accessibility, manual fallback, and the experience after repeated use—not only whether users complete the happy path.
Do product designers need to code?
Not every product designer must become a software engineer, but design-to-code fluency is increasingly valuable. Understanding responsive behavior, state, components, data, and technical constraints helps designers create stronger prototypes and collaborate more effectively with engineering.
Can an AI-generated prototype be used in production?
Not automatically. Generated output still requires product validation, code review, accessibility testing, security assessment, privacy review, performance testing, accurate content, and alignment with the product architecture and design system.
The Future of Product Design Is Human-Led
AI can generate more screens, variations, and possibilities than a product team could previously explore. That abundance makes selection, interpretation, and responsibility more important—not less.
The product designer in the age of AI must know when to use intelligence and when to use a rule; when to remove friction and when to preserve reflection; when to personalize and when to protect privacy; when to accept a generated direction and when to challenge it.
The differentiator is not simply the ability to prompt. It is the ability to turn uncertain technology into a clear, useful, accessible, and trustworthy human experience.
Sources:
Stewart et al., Does AI Save Time on Product Design? A Randomized Controlled Experiment
Figma, State of the Designer 2026
Figma, Why Demand for Designers Is on the Rise
Chen et al., Rethinking the UI of GenUI: A Tale of Two Designs
Sato, From Vibe to Code—and Back
Candello et al., The Emerging Use of GenAI for UX Research
Microsoft Research, The Impact of Generative AI on Critical Thinking
Microsoft Research, Guidelines for Human-AI Interaction
Google People + AI Research, User Needs and Defining Success
Google People + AI Research, Trust and Explanations
Google People + AI Research, Errors and Graceful Failure
Google People + AI Research, Feedback and Control
PNAS Nexus, The New Division of Labor in Design With AI
Stanford HAI, 2026 AI Index Report
U.S. Bureau of Labor Statistics, Occupational Projections and Worker Characteristics
European Commission, Guidelines on AI Transparency Obligations


