# Outcome-Oriented UI

DS234. Future / AI: Goal. Page: https://ui.codeatlas.com.br/atlas/outcome-oriented-ui/. Index: https://ui.codeatlas.com.br/llms/atlas.txt

Interface prioritizes verifiable results, not only commands.

- Status in 2026: Emerging. Appearing in practice, not yet settled.
- Trend 2027 to 2030: Potential (an editorial projection, not a forecast).
- The term: Known technical term or standard.

## Traits

- goals
- checks
- evidence

Typical settings: Business OS, Management.

## When to use it, and when not

Consider it when the task and motivation match: teams operating automations. Typical settings: business os, management.

Be careful when the risk below would hurt the main task: artificial metrics and black box.

Audience (a hypothesis about motivation and task, never measured, not a statement about any group): Teams operating automations.

## UX risk and how to reduce it

- Risk: Artificial metrics and black box.
- Mitigation and accessibility: Explicit success criteria.
- How to check: Test with realistic scenarios: task success, accuracy, reversal, auditability, understanding of what the system does on its own, and a human's ability to step in.

## Evidence

Emerging: exploratory work, with no causal validation for this style.

The sources support the principles that apply to this term. None shows that this style works better or is preferred.

- [E04] Hassenzahl (2004). The Interplay of Beauty, Goodness, and Usability in Interactive Products. https://doi.org/10.1207/s15327051hci1904_2 (Supported). Does not support: Results for other products, tasks or populations. The products were four skins of one kind of player.
- [E18] Luera, Rossi, Siu, Dernoncourt, Yu, Kim, Zhang, Chen, Salehy, Lipka, Basu, Mathur, Zhao (2025). Survey on User Interface Design and Interactions for Generative AI Applications. https://doi.org/10.1561/1100000106 (Supported). Does not support: That any pattern works better, or that a generative interface should act without the user's direction: the survey leaves out implicit signals from the user and reports no outcome comparison. The abstract read is the arXiv version of the same survey (earlier title); the published monograph's own text was not reachable.

## Limits

- The atlas is a broad, living catalogue, not every style that exists. No authority enumerates them, and the classes (movement, aesthetic, design system, layout, pattern, principle) overlap.
- The 1 to 5 scores are relative editorial judgements. They are not results of a study and not a measure of quality.
- An audience is a hypothesis about motivation, task and context. It was never measured and says nothing about any age, gender or other group.
- The sources support underlying principles (visual complexity, legibility, grouping, accessibility, platform conventions). None shows that a particular style works better or is preferred.
- The 2027 to 2030 trend is an editorial projection, not a forecast.
- Terms in the Future / AI category rest on exploratory work, some of it preprints, with no causal validation.

Last reviewed 2026-10-25.

## Heuristic scales

Relative editorial judgements from 1 to 5, not results of a study.

- Visual complexity: 2 / 5 (heuristic)
- Expressiveness: 2 / 5 (heuristic)
- Information density: 4 / 5 (heuristic)

## In our library

No design-style recipe implements this term yet; build it from `--ca-*` tokens.

## Prompt for your AI

```text
Design this interface in the "Outcome-Oriented UI" direction (future / ai, goal): Interface prioritizes verifiable results, not only commands.
Visual and interaction traits to use: goals, checks, evidence.
Main UX risk: Artificial metrics and black box. Mitigate it: Explicit success criteria.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.
```