06 / 20AI × interface

A prompt box works for exploration. Task-based tools need more context and guidance.

That interface was useful because it exposed the raw capability of large language models with almost no product design between the model and the user. But it should not be mistaken for the final form of AI interaction.

A blank prompt asks too much from people.

The user has to understand what the system can do, know how to describe the task, provide the right context, judge the output and work out what to do next. In effect, the person becomes the workflow engine.

01Prompts suit experiments

That is fine for experimentation. It is weak product design.

Figma’s writing on the future of software explores interfaces that adapt to context. Products should offer more than a prompt box: actions, visible state and structured controls can carry much of the interaction.

A travel system does not need to ask users to write an essay describing how to compare flights. It already knows the destination, dates, budget and preferences available in the interface.

A CMS does not need a prompt asking, “Please make this content suitable for LinkedIn.” It already knows the article, brand voice, target channel and approval status.

02Design around the task

The system should reduce the amount of prompting required.

Instead of exposing the model directly, good interfaces can provide suggested actions, previews, editable plans, approval checkpoints, source references, confidence cues and reversible changes.

For suitable tasks, the user can spend less time crafting an instruction and more time checking the proposed action.

03Professional tools need context

In a business environment, users should not have to remember the organisation’s governance rules every time they ask an AI system for help. The product can encode those rules.

If customer data is sensitive, the action can be restricted. If publication requires approval, the interface can make approval mandatory. If an agent is about to change ten records, the system can preview the plan before execution.

This is the difference between adding AI to a product and redesigning the product around AI.

04The interface still matters

It will become more contextual.

Some interactions will remain conversational. Others will become buttons, suggestions, generated controls, visual plans, timelines and editable artefacts.

The best products will use language when language is the easiest interface, and structured interaction when structure is better.

05Move beyond the prompt

The next generation of AI UX should make the next action clear. Users need enough context to judge an output and enough control to correct it before it changes a real workflow.

SourcesResearch trail

References used for this article

  1. 01Figma, 12 Defining Web Development Trends for 2026
  2. 02Figma, What does the future of software look like?
  3. 03Figma AI