What is an intent-driven interface?

Definition

An intent-driven interface begins with a user's stated goal rather than requiring the user to navigate a fixed sequence of screens. The system interprets the requested outcome and selects an appropriate arrangement of information, actions, and controls.

A reliable design keeps important decisions visible and constrains what can be generated. It should preserve accessibility, permissions, product rules, and predictable recovery even when the layout changes for different requests.

ELI5

An intent-driven interface changes to help with the task a person is trying to complete. Instead of making everyone learn the same menus, it presents the information and controls that fit the current goal.

For example, someone could ask to compare three travel options, and the interface could assemble a comparison table with filters and a booking action. The system still needs rules so it does not hide costs or offer actions the user cannot safely take.

Acronyms and aliases

intent-driven UX variant

Frequently asked questions

Does an intent-driven interface remove every fixed screen?

Not necessarily. Products can combine stable screens for familiar or sensitive tasks with generated layouts for goals that benefit from adaptation.

How does an intent-driven interface stay predictable?

It can use approved components, explicit schemas, design constraints, visible state, and consistent rules for important actions.

Videos explaining intent-driven interface